DID Use Case: Public Pointers to Private Data

      
  

  
  
  
  

 Has anyone scoped what the computing load/requirements the resolver network would entail?   
  

  
We know that for DNS, we have 13 root authorities running several hundred servers in over 100 locations, relaying to 23,000 DNS servers all over 200 countries.    What’s the projected encryption/decryption workload, for a full DID/credential/claim network... and what’s a fair and equitable monetization model to support this eco-system?
  
  
  
  
 Moses
  

      

  
>   
>   From:    =Drummond Reed  <drummond.reed@evernym.com>   
>   
>   
>   
>
> Sent:  Wednesday, June 13, 2018 9:24 AM
>   To:  John, Anil  <anil.john@hq.dhs.gov>
>   Cc:  W3C Credentials CG  <public-credentials@w3.org>
>   Subject:  Re: DID Use Case: Public Pointers to Private Data
>
>   
>
>   
>
>   
>   
>   
>   
>
> Just that any peer can use a DID resolver to look up the   DID document for any other peer. I often use the analogy (which is just an   analogy)   that it's the   decentralized   cryptographic equivalent of DNS.   
>
>   
>   
>   
>   
>   
>   
  
  
  
  
  
 -
  
 Moses Ma   
  
 moses.ma@futurelabconsulting.com