Methods, systems, and devices for managing digital assets

Abstract

Embodiments relate to methods, systems, devices, and computer readable medium for managing digital assets, such as cryptocurrencies and public key and private key pairs. The method includes identifying a public key or public address of a digital asset. The method includes identifying a public key of an authorized custodian of the digital asset. The method includes identifying a signed proof of management hash. The method includes determining whether an entity is the authorized custodian of the digital asset by generating an entity hash and comparing it to a first decrypted result. The first decrypted result is obtained by decrypting, using the public key of the authorized custodian, the signed proof of management hash. When the generated entity hash is determined to match the first decryption result, the method includes returning a confirmation that the entity is the authorized custodian of the digital asset.

What is claimed is: 
     
         1 . A method of managing a digital asset, the method comprising:
 identifying a first payload, the first payload including:
 a public key of a digital asset or a corresponding public address for the public key of the digital asset, the public key of the digital asset having a corresponding private key; 
   identifying a public key of an authorized custodian of the digital asset or a corresponding public address for the public key of the authorized custodian of the digital asset;   identifying at least one of a proof of ownership hash for the digital asset and a signed proof of ownership hash for the digital asset;   performing a proof of management setup process for the custodian of the digital asset, the proof of management setup process including:
 generating a proof of management hash, the proof of management hash generated by hashing at least one of the following:
 the first payload; 
 the public key of the authorized custodian or the corresponding public address for the public key of the authorized custodian of the digital asset; 
 the proof of ownership hash; and 
 the signed proof of ownership hash; and 
 
 signing, by the authorized custodian of the digital asset, the proof of management hash to arrive at a signed proof of management hash; and 
   performing a proof of management verification process, the proof of management verification process for determining whether an entity is the authorized custodian of the digital asset, the proof of management verification process including:
 obtaining the public key of the authorized custodian of the digital asset; 
 obtaining the signed proof of management hash; 
 generating an entity hash, the entity hash generated by hashing at least one or more of the following:
 the first payload; 
 a public key of the entity or a corresponding public address for the public key of the entity; 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; 
 
 obtaining a decrypted proof of management hash, the decrypted proof of management obtained by decrypting, using the public key of the authorized custodian of the digital asset, the signed proof of management hash; 
 comparing the generated entity hash to the decrypted proof of management hash; and 
 responsive to a determination that the generated entity hash matches the decrypted proof of management hash, returning a confirmation that the entity is the authorized custodian of the digital asset. 
   
     
     
         2 . The method of  claim 1 , further comprising:
 performing a proof of ownership setup process for an owner of the digital asset, the proof of ownership setup process including:
 generating the proof of ownership hash, the proof of ownership hash generated by hashing at least the first payload; and 
 signing, using the private key of the digital asset, the proof of ownership hash to arrive at the signed proof of ownership hash. 
   
     
     
         3 . The method of  claim 1 , wherein at least one of the following apply:
 the proof of ownership hash is a hash generated by hashing at least the first payload;   the signed proof of ownership hash is obtained by signing, using the private key of the digital asset, the proof of ownership hash; and   the first payload includes an owner identifier, the owner identifier being a unique identifier for use in identifying an owner of the digital asset.   
     
     
         4 . The method of  claim 2 , wherein at least one of the following apply:
 the owner identifier includes a legal entity identifier (LEI); and   the owner identifier includes a legal name of the owner of the digital asset.   
     
     
         5 . The method of  claim 1 , wherein prior to generating the entity hash:
 identifying a hashing algorithm used to generate the proof of management hash; and   using the identified hashing algorithm to generate the entity hash.   
     
     
         6 . The method of  claim 1 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing at least the signed proof of management hash; and 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         7 . The method of  claim 1 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing one of the following:
 at least the first payload; 
 at least the proof of management hash; or 
 at least the signed proof of management hash; and 
 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         8 . The method of  claim 6 , further comprising performing, after performing the proof of authority setup process, a proof of authority verification process, the proof of authority verification process for determining whether an entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset, the proof of management verification process comprising:
 obtaining the public key of the digital asset;   obtaining the signed proof of authority hash;   identifying an entity identifier for the entity, the entity identifier being a unique identifier for use in identifying the entity;   generating a second entity hash, the second entity hash generated by hashing one of the following:
 at least the first payload and at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least one of the following:
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; or 
 
 a second signed entity hash, the second signed entity hash being a digital signature, by the entity, of a hash of at least one of the following: 
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; 
   deriving the proof of authority hash from the signed proof of authority hash, the deriving including decrypting, using the public key of the digital asset, the signed proof of authority hash;   comparing the generated second entity hash to the derived proof of authority hash; and   responsive to a determination that the generated second entity hash matches the derived proof of authority hash, returning a confirmation that the entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset.   
     
     
         9 . A method of managing a digital asset, the method comprising:
 identifying a first payload, the first payload including:
 a public key of a digital asset or a corresponding public address for the public key of the digital asset, the public key of the digital asset having a corresponding private key; 
   identifying a custodian identifier, the custodian identifier being a unique identifier for use in identifying an authorized custodian of the digital asset;   identifying at least one of a proof of ownership hash for the digital asset and a signed proof of ownership hash for the digital asset;   performing a proof of management setup process for the custodian of the digital asset, the proof of management setup process including:
 generating a proof of management hash, the proof of management hash generated by hashing at least one of the following:
 the first payload; 
 the custodian identifier; 
 the proof of ownership hash; and 
 the signed proof of ownership hash; and 
 
 signing, by the authorized custodian of the digital asset, the proof of management hash to arrive at a signed proof of management hash; and 
   performing a proof of management verification process, the proof of management verification process for determining whether an entity is the authorized custodian of the digital asset, the proof of management verification process including:
 identifying an entity identifier for the entity, the entity identifier being a unique identifier for use in identifying the entity; 
 obtaining the signed proof of management hash; 
 generating an entity hash, the entity hash generated by hashing at least one of the following:
 the first payload; 
 the entity identifier for the entity; 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; 
 
 obtaining a decrypted proof of management hash, the decrypted proof of management obtained by decrypting, using the public key of the authorized custodian of the digital asset, the signed proof of management hash; 
 comparing the generated entity hash to the decrypted proof of management hash; and 
 responsive to a determination that the generated entity hash matches the decrypted proof of management hash, returning a confirmation that the entity is the authorized custodian of the digital asset. 
   
     
     
         10 . The method of  claim 8 , further comprising:
 performing a proof of ownership setup process for an owner of the digital asset, the proof of ownership setup process including:
 generating the proof of ownership hash, the proof of ownership hash generated by hashing at least the first payload; and 
 signing, using the private key of the digital asset, the proof of ownership hash to arrive at the signed proof of ownership hash. 
   
     
     
         11 . The method of  claim 8 , wherein at least one of the following apply:
 the proof of ownership hash is a hash generated by hashing at least the first payload;   the signed proof of ownership hash is obtained by signing, using the private key of the digital asset, the proof of ownership hash; and   the first payload includes an owner identifier, the owner identifier being a unique identifier for use in identifying an owner of the digital asset.   
     
     
         12 . The method of  claim 11 , wherein at least one of the following apply:
 the owner identifier includes a legal entity identifier (LEI); and   the owner identifier includes a legal name of the owner of the digital asset.   
     
     
         13 . The method of  claim 8 , wherein prior to generating the entity hash:
 identifying a hashing algorithm used to generate the proof of management hash; and   using the identified hashing algorithm to generate the entity hash.   
     
     
         14 . The method of  claim 8 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing at least the signed proof of management hash; and 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         15 . The method of  claim 8 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing one of the following:
 at least the first payload; 
 at least the proof of management hash; or 
 at least the signed proof of management hash; and 
 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         16 . The method of  claim 15 , further comprising performing, after performing the proof of authority setup process, a proof of authority verification process, the proof of authority verification process for determining whether an entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset, the proof of management verification process comprising:
 obtaining the public key of the digital asset;   obtaining the signed proof of authority hash;   identifying an entity identifier for the entity, the entity identifier being a unique identifier for use in identifying the entity;   generating a second entity hash, the second entity hash generated by hashing one of the following:
 at least the first payload and at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least one of the following:
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; or 
 
 a second signed entity hash, the second signed entity hash being a digital signature, by the entity, of a hash of at least one of the following:
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; 
 
   deriving the proof of authority hash from the signed proof of authority hash, the deriving including decrypting, using the public key of the digital asset, the signed proof of authority hash;   comparing the generated second entity hash to the derived proof of authority hash; and   responsive to a determination that the generated second entity hash matches the derived proof of authority hash, returning a confirmation that the entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset.   
     
     
         17 . A method of managing a digital asset, the method comprising:
 identifying a public key of a digital asset or a corresponding public address for the public key of the digital asset, the public key of the digital asset having a corresponding private key;   identifying at least one of a public key of an authorized custodian of the digital asset, a corresponding public address for the public key of the authorized custodian of the digital asset, and a custodian identifier, the custodian identifier being a unique identifier for use in identifying the authorized custodian of the digital asset;   identifying a signed proof of management hash;   performing a proof of management verification process, the proof of management verification process for determining whether an entity is the authorized custodian of the digital asset, the proof of management verification process including:
 generating an entity hash, the entity hash generated by hashing at least one of the following:
 the public key of the digital asset; 
 the public address for the public key of the digital asset; 
 the public key of the authorized custodian of the digital asset; 
 the public address for the public key of the authorized custodian of the digital asset; 
 an entity identifier for the entity, the entity identifier being a unique identifier for use in identifying the entity; 
 a hash of a first payload, the first payload including at least one of the public key of the digital asset, the public address for the public key of the digital asset, and the entity identifier for the entity; and 
 a signed hash of the first payload; 
 
 decrypting, using the public key of the authorized custodian of the digital asset, the signed proof of management hash to arrive at a first decryption result; 
 comparing the generated entity hash to the first decryption result; and 
 responsive to a determination that the generated entity hash matches the first decryption result, returning a confirmation that the entity is the authorized custodian of the digital asset. 
   
     
     
         18 . The method of  claim 17 , further comprising:
 performing a proof of ownership setup process for an owner of the digital asset, the proof of ownership setup process including:
 generating a proof of ownership hash, the proof of ownership hash generated by hashing at least the first payload; and 
 signing, using the private key of the digital asset, the proof of ownership hash to arrive at a signed proof of ownership hash. 
   
     
     
         19 . The method of  claim 17 , wherein:
 the first payload includes an owner identifier, the owner identifier being a unique identifier for use in identifying an owner of the digital asset.   
     
     
         20 . The method of  claim 19 , wherein at least one of the following apply:
 the owner identifier includes a legal entity identifier (LEI); and   the owner identifier includes a legal name of the owner of the digital asset.   
     
     
         21 . The method of  claim 17 , wherein prior to generating the entity hash:
 identifying a hashing algorithm used to generate the proof of management hash; and   using the identified hashing algorithm to generate the entity hash.   
     
     
         22 . The method of  claim 18 , further comprising:
 performing a proof of management setup process for the authorized custodian of the digital asset, the proof of management setup process including:
 generating a proof of management hash, the proof of management hash generated by hashing at least one of the following:
 the first payload; 
 the public key of the authorized custodian of the digital asset; 
 the public address for the public key of the authorized custodian of the digital asset; 
 the entity identifier for the entity; 
 the proof of ownership hash; and 
 the signed proof of ownership hash; and 
 
 signing, by the authorized custodian of the digital asset, the proof of management hash to arrive at the signed proof of management hash; 
   
     
     
         23 . The method of  claim 22 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing at least the signed proof of management hash; and 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         24 . The method of  claim 22 , further comprising:
 performing a proof of authority setup process, the proof of authority setup process including:
 generating a proof of authority hash, the proof of authority hash generated by hashing one of the following:
 at least the first payload; 
 at least the proof of management hash; or 
 at least the signed proof of management hash; and 
 
 signing, by an owner of the digital asset, the proof of authority hash to arrive at a signed proof of authority hash. 
   
     
     
         25 . The method of  claim 24 , further comprising performing, after performing the proof of authority setup process, a proof of authority verification process, the proof of authority verification process for determining whether an entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset, the proof of management verification process comprising:
 obtaining the public key of the digital asset;   obtaining the signed proof of authority hash;   identifying an entity identifier for the entity, the entity identifier being a unique identifier for use in identifying the entity;   generating a second entity hash, the second entity hash generated by hashing one of the following:
 at least the first payload and at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least one of the following:
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; or 
 
 a second signed entity hash, the second signed entity hash being a digital signature, by the entity, of a hash of at least one of the following:
 the first payload; 
 at least one of the following:
 a public key of the entity or a corresponding public address for the public key of the entity; and 
 the entity identifier; 
 
 a hash of at least the first payload; and 
 a signed hash of at least the first payload; 
 
   deriving the proof of authority hash from the signed proof of authority hash, the deriving including decrypting, using the public key of the digital asset, the signed proof of authority hash;   comparing the generated second entity hash to the derived proof of authority hash; and   responsive to a determination that the generated second entity hash matches the derived proof of authority hash, returning a confirmation that the entity has been authorized, by the owner of the digital asset, to be the authorized custodian of the digital asset.