Cryptlet smart contract

Patent metadata

Field	Value
Publication number	US-11488121-B2
Application number	US-201715593001-A
Country	US
Kind code	B2
Filing date	May 11, 2017
Priority date	May 11, 2017
Publication date	Nov 1, 2022
Grant date	Nov 1, 2022

Abstract

The disclosed technology is generally directed to secure transactions. In one example of the technology, a smart contract is generated based at least in part on a schema and provided information. The smart contract may be caused to be deployed on a ledger as a smart contract ledger instance. A unique address associated with the deployed smart contract ledger instance may be received. A cryptlet binding for a first contract cryptlet that is associated with the smart contract ledger instance may be generated. The cryptlet binding may be sent to the first contract cryptlet. Responsive to a state change associated with the first contract cryptlet, an update may be communicated to the smart contract ledger instance.

First claim

I claim:

1. An apparatus, comprising:
a device including at least one memory adapted to store run-time data for the device, and at least one processor that is adapted to execute processor-executable code that, in response to execution, enables the device to perform actions, including:
generating a smart contract based at least in part on a schema and provided information;
causing deployment of the smart contract on a ledger as a smart contract ledger instance, wherein the smart contract includes a first contractual agreement agreed upon by at least two counterparties;
causing a start of execution of a first contract cryptlet, wherein the first contract cryptlet is associated with the smart contract ledger instance, and wherein the first contract cryptlet includes smart contract logic that implements the first contractual agreement;
receiving a unique address associated with the deployed smart contract ledger instance;
determining a first mapping, wherein the first mapping is a mapping between the first contract cryptlet and a mapped entity, such that the mapped entity is at least one of another smart contract or another cryptlet, and such that the mapping enables routing of messages between the first contract cryptlet and the mapped entity;
generating a cryptlet binding for the first contract cryptlet such that the cryptlet binding includes at least one binding, such that at least one of the at least one binding includes the first mapping;
sending the cryptlet binding to the first contract cryptlet; and
responsive to a state change associated with the first contract cryptlet, communicating an update to the smart contract ledger instance.

2. The apparatus of claim 1 , wherein the cryptlet binding further includes at least a second binding, and wherein each binding in the cryptlet binding includes a mapping between the first contract cryptlet and at least one of a smart contract, another cryptlet, or a public key that is associated with a counterparty to the smart contract.

3. The apparatus of claim 1 , wherein the cryptlet binding represents at least one of properties or rules for the first contract cryptlet.

4. The apparatus of claim 1 , wherein the first contract cryptlet executes in an enclave, and wherein the enclave is a private, tamper-resistant execution environment that is secure from external interference.

5. The apparatus of claim 1 , wherein the cryptlet binding includes a mapping to a utility cryptlet that presents and attests to a value of particular market data.

6. The apparatus of claim 1 , wherein the first contract cryptlet is a software component that inherits from base classes and implements interfaces that provide cryptographic primitives and integrations for distributed trust applications, and wherein the first contract cryptlet includes logic that is configured to implement the smart contract in conjunction with the cryptlet binding.

7. The apparatus of claim 1 , wherein the unique address associated with the deployed smart contract ledger instance is a unique identifier of the smart contract ledger instance.

8. The apparatus of claim 1 , wherein the ledger is stored on a datastore.

9. The apparatus of claim 8 , wherein the datastore is stored on a blockchain.

10. The apparatus of claim 1 , wherein generating a smart contract based at least in part on the schema and the provided information is done after receiving a contract request to make a Previously Presented contract.

11. The apparatus of claim 10 , the actions further comprising:
after receiving the contract request, fetching the cryptlet binary for the first contract cryptlet, and causing the start of execution of the first contract cryptlet.

12. The apparatus of claim 11 , the actions further comprising:
receiving, from the first contract cryptlet, a request for information;
making a request for the information; and
receiving the provided information in response to the request for the information.

13. A method, comprising:
creating a smart contract based at least in part on a schema and provided information;
communicating the smart contract to a ledger such that the smart contract is deployed on a ledger as a smart contract ledger instance, wherein the smart contract includes a first contractual agreement agreed upon by at least two counterparties;
causing a start of execution of a first contract cryptlet, wherein the first contract cryptlet is associated with the smart contract ledger instance, and wherein the first contract cryptlet includes smart contract logic that implements the first contractual agreement;
receiving the address associated with the deployed smart contract ledger instance, wherein the address associated with the deployed smart contract ledger instance is a unique address;
determining a first mapping, wherein the first mapping is a mapping between the first contract cryptlet and a mapped entity, such that the mapped entity is at least one of another smart contract or another cryptlet, and such that the mapping enables routing of messages between the first contract cryptlet and the mapped entity;
via at least one processor, creating a cryptlet binding for the first contract cryptlet such that the cryptlet binding includes at least one binding, such that at least one of the at least one binding includes the first mapping;
providing the cryptlet binding to the first contract cryptlet; and
communicating an update to the smart contract ledger instance responsive to a state change associated with the first contract cryptlet.

14. The method of claim 13 , wherein generating a smart contract based at least in part on the schema and the provided information is done after receiving a contract request to make a Previously Presented contract.

15. The method of claim 14 , further comprising:
after receiving the contract request, fetching the cryptlet binary for the first contract cryptlet, and causing the start of execution of the first contract cryptlet.

16. A processor-readable storage medium, having stored thereon processor-executable code that, upon execution by at least one processor, enables actions, comprising:
causing storing of a smart contract on a ledger as a smart contract ledger instance, wherein the smart contract includes a first contractual agreement agreed upon by at least two counterparties;
causing a start of execution of a first contract cryptlet, wherein the first contract cryptlet is associated with the smart contract ledger instance, and wherein the first contract cryptlet includes smart contract logic that implements the first contractual agreement;
receiving a unique identification associated with the smart contract ledger instance;
determining a first mapping, wherein the first mapping is a mapping between the first contract cryptlet and a mapped entity, such that the mapped entity is at least one of another smart contract or another cryptlet, and such that the mapping enables routing of messages between the first contract cryptlet and the mapped entity;
communicating a cryptlet binding to the first contract cryptlet such that the cryptlet binding includes at least one binding, such that at least one of the at least one binding includes the first mapping; and
updating the smart contract ledger instance based on communication from the first contract cryptlet.

17. The processor-readable storage medium of claim 16 , wherein the unique identification is an address of the smart contract ledger instance.

18. The processor-readable storage medium of claim 16 , the actions further comprising:
generating a smart contract b

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Gray John Marley

Classifications

• H04L9/0897

  involving additional devices, e.g. trusted platform module [TPM], smartcard or USB · CPC title

• G06Q20/3829

  involving key management · CPC title

• H04L9/50 Primary

  using hash chains, e.g. blockchains or hash trees · CPC title

• G06Q20/065 Primary

  using e-cash · CPC title

• H04L9/3236

  using cryptographic hash functions · CPC title