Abstract: Methods and systems for an extensible, universal ledger. One of the methods includes receiving at a journal manager engine a register transaction type request for a first transaction type, the journal manager engine reading and writing to a journal that stores a history of object state and of code by which object state is changed, wherein the register transaction type request is based at least in part on a template and specifies at least one action that can be performed as part of the first transaction type; writing the transaction type request to the journal including an operation definition for the first transaction type; receiving a transaction request of the first transaction type; obtaining the operation definition from the journal; executing an operation in response to the transaction request to produce a transaction result; and recording the transaction result in the journal.

Abstract: Methods and systems for an extensible, universal ledger. One of the methods includes receiving at a journal manager engine a register transaction type request for a first transaction type, the journal manager engine reading and writing to a journal that stores a history of object state and of code by which object state is changed, wherein the register transaction type request is based at least in part on a template and specifies at least one action that can be performed as part of the first transaction type; writing the transaction type request to the journal including an operation definition for the first transaction type; receiving a transaction request of the first transaction type; obtaining the operation definition from the journal; executing an operation in response to the transaction request to produce a transaction result; and recording the transaction result in the journal.

Abstract: Methods and systems for storing multiple asset types with embedded rules to simplify storage and enable simple and friction-free transactions. One of the methods includes: representing a plurality of asset types using a plurality of standard asset ownership units, each standard asset ownership unit representing a specific asset type; using a roll-up node configured to group specified standard asset ownership units; embedding standard asset unit ownership rules in each standard asset ownership unit, the standard asset ownership unit rules describing permitted behaviors for a specified asset type; embedding roll-up rules in the roll-up node, the roll-up rules including specification of which standard asset ownership units are grouped into the roll-up node, the standard asset ownership unit rules and the role-up rules being based on rules templates; receiving a request for information; and in response to the request, providing information based at least in part on data from the roll-up node.

Abstract: Methods and systems for an extensible, universal ledger. One of the methods includes receiving at a journal manager engine a register transaction type request for a first transaction type, the journal manager engine reading and writing to a journal that stores a history of object state and of code by which object state is changed, wherein the register transaction type request is based at least in part on a template and specifies at least one action that can be performed as part of the first transaction type; writing the transaction type request to the journal including an operation definition for the first transaction type; receiving a transaction request of the first transaction type; obtaining the operation definition from the journal; executing an operation in response to the transaction request to produce a transaction result; and recording the transaction result in the journal.

Abstract: Methods and systems for storing multiple asset types with embedded rules to simplify storage and enable simple and friction-free transactions. One of the methods includes: representing a plurality of asset types using a plurality of standard asset ownership units, each standard asset ownership unit representing a specific asset type; using a roll-up node configured to group specified standard asset ownership units; embedding standard asset unit ownership rules in each standard asset ownership unit, the standard asset ownership unit rules describing permitted behaviors for a specified asset type; embedding roll-up rules in the roll-up node, the roll-up rules including specification of which standard asset ownership units are grouped into the roll-up node, the standard asset ownership unit rules and the role-up rules being based on rules templates; receiving a request for information; and in response to the request, providing information based at least in part on data from the roll-up node.

Abstract: Methods and systems for an extensible, universal ledger. One of the methods includes receiving at a journal manager engine a register transaction type request for a first transaction type, the journal manager engine reading and writing to a journal that stores a history of object state and of code by which object state is changed, wherein the register transaction type request is based at least in part on a template and specifies at least one action that can be performed as part of the first transaction type; writing the transaction type request to the journal including an operation definition for the first transaction type; receiving a transaction request of the first transaction type; obtaining the operation definition from the journal; executing an operation in response to the transaction request to produce a transaction result; and recording the transaction result in the journal.