Systemic extensible blockchain object model comprising a first-class object model and a distributed ledger technology

Abstract

A method for processing one or more message passing transactions sent from one or more client computers to one or more distributed ledger accounts, of one or more distributed ledgers, executed on one or more distributed ledger nodes, the message passing transactions processed by one or more class manager infrastructure intrinsics.

What is claimed is: 
     
       1. A computer-implemented method for processing one or more message passing transactions, said computer-implemented method comprising:
 creating a message passing transaction comprising; 
 transmitting the message passing transaction to one or more distributed ledger nodes; 
 identifying an account and an object instance within an account state space of at least one node of the one or more distributed ledger nodes based on a data element in the message passing transaction; 
 passing the message passing transaction and one or more arguments to the object instance by calling a class manager infrastructure intrinsic; 
 resolving the message passing transaction, by the class manager infrastructure intrinsic, to one or more method implementations implemented in a class or an ancestor class of the object instance; 
 performing object-oriented inheritance by recursively resolving the message passing transaction to the one or more method implementations to the ancestor class or the class; 
 receiving output data from calling the one or more method implementations and any changes to one or more account state spaces; 
 creating a processed transaction comprising: the output data and one or more verification values of the changes to the one or more account state spaces; and 
 adding the processed transaction to one or more distributed ledgers. 
 
     
     
       2. The computer-implemented method of  claim 1  wherein the message passing transaction comprises:
 a unique object identifier; 
 a message identifier, wherein the message identifier includes an account address, a class object instance reference, and a method reference; and 
 arguments for the message identifier by a client. 
 
     
     
       3. The computer-implemented method of  claim 2  wherein the unique object identifier comprises:
 a ledger account address; and 
 an object reference to an object instance in the one or more account state spaces. 
 
     
     
       4. The computer-implemented method of  claim 1  wherein the one or more method implementations of the classes are in a format of computer machine instructions, bytecode virtual machine instructions, interpretable script code, or references to the bytecode virtual machine instructions, to the bytecode virtual machine instructions, or to the interpretable script code. 
     
     
       5. The computer-implemented method of  claim 1  wherein the one or more verification values are a hash values over the changes to one or more account state spaces. 
     
     
       6. The computer-implemented method of  claim 2  wherein resolving the message to the one or more method implementations by the class manager infrastructure intrinsic comprises the message identifier combined with a list of data types of the arguments matched against a method name associate with the one or more method implementations and a list of data types associated with parameters of the one or more method implementations. 
     
     
       7. The computer-implemented method of  claim 1  wherein performing the object-oriented inheritance includes multiple inheritance by the class referencing a list of the ancestor class. 
     
     
       8. The computer-implemented method of  claim 1  wherein the changes to the one or more account state spaces may include creating one or more object instances. 
     
     
       9. One or more tangible non-transitory computer-readable mediums storing computer program code instructions and associated data that, when coupled to, read, and executed by one or more computer processors, causes the one or more computer processors to perform operations comprising:
 creating a message passing transaction comprising; 
 transmitting the message passing transaction to the one or more computer processors; 
 identifying an account and an object instance within an account state space of on one or more distributed ledgers based on a data element in the message passing transaction; 
 message passing transaction and one or more arguments to the object instance by calling a class manager infrastructure intrinsic; 
 resolving the message passing transaction, by the class manager infrastructure intrinsic to one or more method implementations implemented in a class or an ancestor class of the object instance; 
 performing object-oriented inheritance by recursively resolving the message passing transaction to the one or more method implementations to the ancestor class or the class; 
 receiving output data from calling the one or more method implementations and any changes to one or more account state spaces; 
 creating a processed transaction comprising: the output data, and one or more verification values of the changes to one or more account state spaces; and 
 adding the processed transaction to one or more distributed ledgers. 
 
     
     
       10. The one or more tangible non-transitory computer-readable mediums of  claim 9  wherein the message passing transaction comprises:
 a unique object identifier; 
 a message identifier, wherein the message identifier includes an account address, a class object instance reference, and a method reference; and 
 arguments for the message identifier by a client. 
 
     
     
       11. The one or more tangible non-transitory computer-readable mediums of  claim 10 , wherein the unique object identifier comprises:
 a ledger account address; and 
 an object reference to an object instance in the one or more account state spaces. 
 
     
     
       12. The one or more tangible non-transitory computer-readable mediums of  claim 9 , wherein the one or more method implementations of the classes are in a format of computer machine instructions, bytecode virtual machine instructions, interpretable script code, or references to the bytecode virtual machine instructions, to the bytecode virtual machine instructions, or to the interpretable script code. 
     
     
       13. The one or more tangible non-transitory computer-readable mediums of  claim 9 , wherein the one or more verification values are a hash values over the changes to one or more account state spaces. 
     
     
       14. The one or more tangible non-transitory computer-readable mediums of  claim 10 , wherein resolving the message identifier to the one or more method implementations by the class manager infrastructure intrinsic comprises the message identifier combined with a list of data types of the arguments and matched against a method name associate with the one or more method implementations and a list of data types associated with parameters of the one or more method implementations. 
     
     
       15. The one or more tangible non-transitory computer-readable mediums of  claim 9 , wherein performing the object-oriented inheritance includes multiple inheritance by the class referencing a list of the ancestor class. 
     
     
       16. The one or more tangible non-transitory computer-readable mediums of  claim 9  wherein the changes to the one or more account state spaces may include creating one or more object instances. 
     
     
       17. A system, comprising:
 one or more processors; and 
 one or more computer-readable storage devices coupled to the one or more processors and having computer program code instructions and data stored thereon which, when coupled to, read, and executed by the one or more processors cause the one or more processors to perform operations comprising: 
 creating a message passing transaction comprising: 
 transmitting the message passing transaction to the one or more processors; 
 identifying an account and an object instance within an account state space of one or more distributed ledgers based on a data element in the message passing transaction; 
 passing the message passing transaction and one or more arguments to the object instance by calling a class manager infrastructure intrinsic; 
 resolving the message passing transaction, by the class manager infrastructure intrinsic to one or more method implementations implemented in a class or an ancestor class of the object instance; 
 performing object-oriented inheritance by recursively resolving the message passing transaction to the one or more method implementations to the ancestor class or the class; 
 receiving output data from calling the one or more method implementations and any changes to one or more account state spaces; 
 creating a processed transaction comprising: the output data and one or more verification values of the changes to the one or more account state spaces; and 
 adding the processed transaction to one or more distributed ledgers. 
 
     
     
       18. The system of  claim 17  wherein the message passing transaction comprises:
 a unique object identifier; 
 a message identifier, wherein the message identifier includes an account address, a class object instance reference, and a method reference; and 
 arguments for the message identifier by a client. 
 
     
     
       19. The system of  claim 18  wherein the unique object identifier comprises:
 a ledger account address; and 
 an object reference to an object instance in the one or more account state spaces. 
 
     
     
       20. The system of  claim 18  wherein resolving the message to the one or more method implementations by the class manager infrastructure intrinsic comprises the message identifier combined with a list of data types of the arguments matched against a method name associate with the one or more method implementations and a list of data types associated with parameters of the one or more method implementations.