SYSTEM AND METHODS FOR CREATING, TRANSFERING, AND INVOKING A TRANSFERABLE PROMISE

• US 20200134615A1
• Filed: 10/31/2018
• Published: 04/30/2020
• Est. Priority Date: 10/31/2018
• Status: Abandoned Application

• Current Assignee: Zhongwei Wu
• Original Assignee: Zhongwei Wu
• Inventors: Wu, Zhongwei
• Application Number:
  US16/175,953
• Publication Number:
  US 20200134615A1
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures
• CPC Class Codes: G06Q 20/3827 Use of message hashing
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/42 Confirmation, e.g. check or permission by the legal debtor of payment
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/088 Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A transaction network comprising a plurality of party devices interconnected via a communication network, each party device corresponding to a transaction party. The transaction network facilitates localized creation and enforcement of a transferable promise involving an obligor and an owner, the obligor being required to perform an obligatory action upon the owner invoking the transferable promise. The transferable promise is encrypted and signed to protect its integrity, and is invocable only by the owner. The obligor further verifies the transferable promise upon its invocation to prevent a double-spend attempt. The transferable promise contains a continuation executed upon invocation to cause an executing device of the obligor to perform the obligatory action. The transferable promise is adapted to effect the delivery of a digital asset or digital representation of a physical asset, or the performance of a service, and may be transferred, assigned, and sold between transaction parties as an asset.

Claims

1. A method for creating, enforcing, and transferring an enforceable obligation between a plurality of transaction parties, comprising the steps of:

providing a transaction network comprising a plurality of party devices which are operably connected via a network, each party device corresponding to one of the transaction parties;

creating a transferable promise between at least two of the transaction parties, each transaction party having a private key known only to the transaction party and a public key, one of the transaction parties corresponding to an owner and another one of the transaction parties corresponding to an obligor which must perform the obligation, wherein the obligor is adapted to secure the transferable promise by encrypting the transferable promise using the public key of the owner and signing the transferable promise using the private key of the obligor, and wherein the owner is adapted to present the transferable promise to the obligor by un-signing the transferable promise using the public key of the obligor, decrypting the transferable promise using the private key of the owner, and sending the un-signed and decrypted transferable promise to the obligor;

defining the obligation as an obligatory action stored within the transferable promise which the obligor is required to perform;

securing the transferable promise by the obligor by encrypting the transferable promise using the owner'"'"'s public key and then signing the transferable promise with the obligor'"'"'s private key;

sending the secured transferable promise to the owner by the obligor;

invoking the secured transferable promise by the owner by un-signing the transferable promise using the obligor'"'"'s public key and decrypting the transferable promise using owner'"'"'s private key, and presenting the resulting un-signed and decrypted transferable promise to the obligor;

verifying the transferable promise by the obligor, and ensuring the transferable promise is valid and a double-spend attempt is not present;

and causing the obligor to perform the obligatory action.

2. The method as described in claim 1, wherein:

the step of defining the obligation further comprises the step of defining a plurality of attributes stored within the transferable promise comprising a type and an amount, whereby the type describes the obligatory action and the amount quantifies the obligatory action.

3. The method as described in claim 2, wherein:

the step of defining the obligation is followed by the step of;

defining a continuation stored within the transferable promise which is adapted to enact performance of the obligation, the continuation having a plurality of parameters and a segment of code, whereby the parameters comprise the type and the amount of the transferable promise and a plurality of runtime environment variables, the parameters define a control state; and

the step of causing the obligor to perform the obligatory action further comprises the steps of executing the continuation by the obligor using the obligor'"'"'s party device, reifying the control state of the continuation on the obligor'"'"'s party device, and executing the segment of code to perform the obligatory action.

4. The method as described in claim 3, wherein:

the step of defining a continuation further comprises the creating a hash of the code of the continuation and storing the hash within a type field, and publishing the type by making the type field visible to the transaction network.

5. The method as described in claim 4, wherein the step of sending the signed and encrypted transferable promise to the owner by the obligor is followed by the step of:

initiating a promise transfer by the owner, the promise transfer having a transfer sender corresponding to the owner and a transfer recipient which is another transaction party, presenting the secured transferable promise to the obligor by the owner, verifying the un-signed and decrypted transferable promise by the obligor as valid and that no double-spend attempt is present, updating the transferable promise so that the transfer recipient replaces the transfer sender as the owner of the transferable obligation, securing the transferable promise by the obligor by encrypting the promise with the public key of the transfer recipient and signing the encrypted promise using the obligor'"'"'s private key, and completing the promise transfer by sending the secured transferable promise to the transfer recipient by the obligor, whereby the transferable promise is invocable by the transfer recipient as the owner.

6. The method as described in claim 5, wherein the step of initiating a promise transfer is followed by the step of:

initiating a promise assignment by the obligor, the promise assignment having an assignment sender corresponding to the obligor and an assignment recipient corresponding to another transaction party, presenting the secured transferable promise to the owner by the sending obligor, verifying the un-signed and decrypted transferable promise by the owner, sending the unsigned and decrypted transferable promise to the assignment recipient by the obligor acting as the assignment sender, updating the transferable promise so that the assignment recipient replaces the assignment sender as the obligor of the transferable obligation, securing the transferable promise by the assignment recipient as the obligor by encrypting the promise using the owner'"'"'s public key and signing the encrypted promise using the recipient obligor'"'"'s private key, and completing the promise assignment by sending secured transferable promise to the owner by the assignment recipient as the obligor, whereby the assignment recipient is required to perform the obligation as the obligor.

7. The method as described in claim 6, wherein the steps as recited are followed by the steps of:

initiating an aggregated promise transfer having a plurality of input transferable promises which share one aggregated promise obligor, a plurality of aggregated promise senders, and a plurality of aggregated promise recipients, whereby the owner of each input transferable promise corresponds to one of the aggregated promise senders, and the aggregated promise obligor is the obligor of all the input transferable promises, whereby the aggregated promise transfer is consented to by all involved transfer parties;

presenting each input transferable promise to the aggregated promise obligor by each aggregated promise sender;

verifying each input transferable promise by the aggregated promise obligor;

creating an output transferable promise for each aggregated promise recipient by the aggregated promise obligor whereby the owner of each output transferable promise is one of the aggregated promise recipients, setting the amount of each output transferable promise so that the total of the amounts of the output transferable promises is equal to the total of the amounts of the input transferable promises, and defining the continuation of each output transferable promise; and

securing each output transferable promise by the aggregated promise obligor whereby each output transferable promise is encrypted using the public key of the owner of each output transferable promise and signed using the private key of the aggregated promise obligor, and sending each secured output transferable promise to its owner.

8. The method as described in claim 7, wherein the steps as recited are followed by the steps of:

initiating an aggregated promise assignment having a plurality of input assignment promises which share one aggregated assignment owner, a plurality of aggregated assignment senders, and a plurality of aggregated assignment recipients, whereby the obligor of each input aggregated assignment promise corresponds to one of the aggregated assignment senders, whereby the aggregated promise assignment is consented to by all involved assignment parties;

presenting each input assignment promise to the aggregated assignment owner by each assignment sender;

verifying each input assignment promise by its aggregated assignment owner;

creating an output assignment promise for each output assignment recipient whereby the obligor of each output assignment promise is the aggregated assignment recipient which created it, setting the amount of each output assignment promise so that the total of the amounts of the output assignment promises is equal to the total of the amounts of all the input assignment promises, and defining the continuation of each output assignment promise; and

securing each output assignment promise by its obligor whereby each output transferable promise is encrypted using the public key of the aggregated assignment owner and signed using the private key of the aggregated assignment recipient, and sending each secured output aggregated transferable promise to the aggregated assignment owner.

9. The method as described in claim 8, wherein the steps as recited further comprise the steps of:

initiating a multi-promise transaction between at least a first transaction party and a second transaction party, comprising a transfer of a first promise from the first transaction party to the second transaction party, and a transfer of a second promise from the second transaction party to the first transaction party, securing the transfers of the first and second promises by encoding each as a new promise to transfer the first and second promises upon request by the respective owner of each promise, and simultaneously sending both the first and second transfer promises to the respective owners only when both the first and second promises are secured, thus enforcing a transaction mechanism that requires an exchange of digital assets amongst all involved transaction parties;

10. The method as described in claim 9, wherein the step of invoking the transferable promise by the owner is preceded by the step of:

initiating a promise market transaction between two transaction parties comprising a seller and a buyer whereby the seller is the owner of the transferable promise, and the buyer is the owner of a currency promise to deliver currency or a crypto-currency, transferring the transferrable promise from the seller to the buyer, and simultaneously transferring the currency promise from the buyer to the seller.

11. The method as described in claim 10, wherein:

the obligation is the delivery of a digital asset;

the step of defining the obligation comprises defining the obligation as an obligatory action stored within the transferable promise which the obligor is required to perform to deliver the digital asset to the owner, defining a plurality of attributes stored within the transferable promise comprising a type and an amount, whereby the type describes the digital asset and the amount quantifies the digital asset; and

the step of causing the obligor to perform the obligatory action further comprises the step of delivering the digital asset to the owner.

12. The method as described in claim 11, wherein:

the digital asset is digital or fiat currency; and

the step of causing the obligor to perform the obligatory action further comprises the step of deducting the amount of the digital asset from a digital asset balance maintained by the obligor and adding the amount of the digital asset to a destination digital asset balance specified by the owner.

13. The method as described in claim 12, wherein:

the digital asset is a digital representation indicating custody of a physical asset; and

the step of causing the obligor to perform the obligatory action further comprises the step of granting to the owner a right to take custody of the physical asset.

14. The method as described in claim 10, wherein:

the obligation is a service; and

the step of defining the obligation comprises defining the obligation as an obligatory action stored within the transferable promise which constitutes the service, defining a plurality of attributes stored within the transferable promise comprising a type and an amount, whereby the type describes the service and the amount quantifies the performance of the service.

15. The method as described in claim 14, wherein:

the step of defining the obligation further comprises the steps of defining the type as a complex computation problem, and defining a plurality of problem variables within the attributes; and

the step of causing the obligor to perform the obligatory action further comprises the step of executing the segment of code to perform the obligatory action by calculating the complex computation problem and delivering a result to the owner.

16. The method as described in claim 15, wherein:

the party device of the obligor has a computer storage device which is accessible to other party devices via the network;

the step of defining the obligation further comprises the steps of defining the type as a storage request, and defining the amount as a data storage capacity; and

the step of causing the obligor to perform the obligatory action further comprises the step of executing the segment of code to perform the obligatory action by enabling the owner to access the computer storage device and store data therein.