Granted Patent B2

US 12,652,173 · App. 18/886,680 · Granted Jun 9, 2026

Inventors: Todd Little (Lafayette, CO); Gourav Sarkar (Bangalore, IN); Paritosh Das (Bangalore, IN)

Assignee: ORACLE INTERNATIONAL CORPORATION

H04L9/3239G06F16/27H04L9/3213H04L9/50

Abstract

Claims (60)

1 . A system for generating a blockchain token from a set of declarations, comprising:

a computer system operating as a distributed ledger, the distributed ledger comprising at least a chaincode component and a ledger component;

wherein the system automatically generates a chaincode based upon received instructions comprising a specification file, the automatically generated chaincode being deployed to a local fabric;

wherein the specification file comprises a plurality of definitions, the plurality of definitions comprising one or more of asset definitions, behavior definitions, and/or role definitions;

wherein the automatically generated chaincode deployed to the local fabric is tested, the testing comprising:

scaffolding a code of a smart contract based upon the specification file,

testing the scaffolded code at the local fabric, and

based upon the testing of the scaffolded code at the local fabric, updating the specification file to provide an updated specification file; and

automatically generating, based upon the updated specification file, a second chaincode for deployment to the distributed ledger.

2 . The system of claim 1 , wherein automatically generating the second chaincode comprises:

automatically building a smart contract based upon the received instructions and the updated specification file, the smart contract being associated with a token specified within the updated specification file;

wherein the smart contract defines optional roles for the token specified within the updated specification file, the optional roles being specified by role definitions of the specification file; and

wherein the smart contract is tested and deployed to the chaincode component.

3 . The system of claim 2 , wherein a behavior specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more behaviors for the constructed token.

4 . The system of claim 2 , wherein a role specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more of a plurality of token roles, the plurality of token roles comprising a minter role, a burner role, and a notary role.

5 . The system of claim 1 , wherein automatically generating the second chaincode comprises:

generating the chaincode based upon the updated specification file and the received instructions, the received instructions specifying instructions to generate a token for use on ledger component,

retrieving, from the received instructions, at least one assigned behavior,

assigning the at least one assigned behavior to the token via the automatically generated second chaincode, and

detecting whether a token role is associated with the token within the received instructions, and upon detecting that no token role is assigned to the token, assigning each of a plurality of token roles to the token via the automatically generated second chaincode.

6 . The system of claim 5 , wherein the plurality of token roles comprise a minter role, a burner role, and a notary role.

7 . A method for generating a blockchain token from a set of declarations, comprising:

providing a computer system operating as a distributed ledger, the distributed ledger comprising at least a chaincode component and a ledger component;

automatically generating a chaincode based upon received instructions, the instructions comprising a specification file, the automatically generated chaincode being deployed to a local fabric, and wherein the specification file comprises a plurality of definitions, the plurality of definitions comprising one or more of asset definitions, behavior definitions, and/or role definitions;

testing the automatically generated chaincode deployed to the local fabric, the testing comprising:

scaffolding a code of a smart contract based upon the specification file,

testing the scaffolded code at the local fabric, and

based upon the testing of the scaffolded code at the local fabric, updating the specification file to provide an updated specification file; and

automatically generating, based upon the updated specification file, a second chaincode for deployment to the distributed ledger.

8 . The method of claim 7 , wherein automatically generating the second chaincode comprises:

automatically building a smart contract based upon the received instructions and the updated specification file, the smart contract being associated with a token specified within the updated specification file;

wherein the smart contract defines optional roles for the token specified within the updated specification file, the optional roles being specified by role definitions of the specification file; and

wherein the smart contract is tested and deployed to the chaincode component.

9 . The method of claim 8 , wherein a behavior specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more behaviors for the constructed token.

10 . The method of claim 8 , wherein a role specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more of a plurality of token roles, the plurality of token roles comprising a minter role, a burner role, and a notary role.

11 . The method of claim 7 , wherein automatically generating the second chaincode comprises:

generating the chaincode based upon the updated specification file and the received instructions, the received instructions specifying instructions to generate a token for use on ledger component,

retrieving, from the received instructions, at least one assigned behavior,

assigning the at least one assigned behavior to the token via the automatically generated second chaincode, and

detecting whether a token role is associated with the token within the received instructions, and upon detecting that no token role is assigned to the token, assigning each of a plurality of token roles to the token via the automatically generated second chaincode.

12 . The method of claim 11 , wherein the plurality of token roles comprise a minter role, a burner role, and a notary role.

13 . A non-transitory computer readable storage medium having instructions thereon for generating a blockchain token from a set of declarations, which when read and executed cause a computer to perform a method comprising:

running a distributed ledger on the computer, the distributed ledger comprising at least a chaincode component and a ledger component;

automatically generating a chaincode based upon received instructions, the instructions comprising a specification file, the automatically generated chaincode being deployed to a local fabric, and wherein the specification file comprises a plurality of definitions, the plurality of definitions comprising one or more of asset definitions, behavior definitions, and/or role definitions;

testing the automatically generated chaincode deployed to the local fabric, the testing comprising:

scaffolding a code of a smart contract based upon the specification file,

testing the scaffolded code at the local fabric, and

based upon the testing of the scaffolded code at the local fabric, updating the specification file to provide an updated specification file; and

automatically generating, based upon the updated specification file, a second chaincode for deployment to the distributed ledger.

14 . The non-transitory computer readable storage medium of claim 13 , wherein automatically generating the second chaincode comprises:

automatically building a smart contract based upon the received instructions and the updated specification file, the smart contract being associated with a token specified within the updated specification file;

wherein the smart contract defines optional roles for the token specified within the updated specification file, the optional roles being specified by role definitions of the specification file; and

wherein the smart contract is tested and deployed to the chaincode component.

15 . The non-transitory computer readable storage medium of claim 14 , wherein a behavior specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more behaviors for the constructed token.

16 . The non-transitory computer readable storage medium of claim 14 , wherein a role specified within the updated specification file defines, for a token constructed by the smart contract and deployed to the ledger component, one or more of a plurality of token roles, the plurality of token roles comprising a minter role, a burner role, and a notary role.

17 . The non-transitory computer readable storage medium of claim 13 , wherein automatically generating the second chaincode comprises:

generating the chaincode based upon the updated specification file and the received instructions, the received instructions specifying instructions to generate a token for use on ledger component,

retrieving, from the received instructions, at least one assigned behavior,

assigning the at least one assigned behavior to the token via the automatically generated second chaincode, and

detecting whether a token role is associated with the token within the received instructions, and upon detecting that no token role is assigned to the token, assigning each of a plurality of token roles to the token via the automatically generated second chaincode, the plurality of token roles comprising a minter role, a burner role, and a notary role.

Assignments (1)

Continuity (3)

References Cited (27)