Managing digital blockchains via digital tokens, systems, methods, and apparatus

1 . A distributed computer-based digital token management system, comprising:

a first computer readable memory storing

(i) a primary digital notarized ledger instantiated in the first computer readable memory storing a digital token,

(ii) the digital token that includes a token address field having a first portion representative of an owner of the digital token and a second portion that is separate from the first portion and representative of a token state, and

(iii) software instructions;

at least one processor coupled with the first computer readable memory and that performs the following operations upon execution of the software instructions:

instantiating a target digital notarized ledger using a smart contract of the primary digital notarized ledger;

receiving a request to update the digital token, the request comprising digital token owner data and digital token state data representing actions on the target digital notarized ledger;

identifying the digital token based on a comparison of the digital token owner data with the first portion of the token address field;

generating a token state value based on the digital token state data;

updating the second portion of the token address field to include the token state value;

invoking the smart contract of the primary digital notarized ledger instantiated in the first computer readable memory storing the digital token according to at least the first portion of the token address field and the second portion of the token address field; and

responsive to invoking the smart contract, causing an update to the digital token, so that the token address field includes the token state value.

2 . The distributed computer-based digital token management system of claim 1 , wherein the operations further include:

receiving a second request, including at least one of: an address, a Health Object Identifier (HOI), a suffix, a prefix, a bit field, a record identifier, a patient-specific record, a ledger state, a URL, a pointer, or a file system address, to update a third portion of the digital token; and

updating the third portion of the digital token based on the second request.

3 . The distributed computer-based digital token management system of claim 2 , wherein the bit field further includes a permission that the digital token may give to the address assigned to the first portion of the token address field or object identifiers of: a block, a transaction, a ledger, a wallet, the smart contract, a second smart contract, or a second digital token, and wherein the permission enables the owner with the address to perform permitted actions to the target digital notarized ledger.

4 . The distributed computer-based digital token management system of claim 2 , wherein the bit field represents at least one of: how many times the target digital notarized ledger has been rebuilt, that a bug fix has been applied, that a patch has been applied, or that a new directory in a file system has been established.

5 . The distributed computer-based digital token management system of claim 2 , wherein the pointer is to a block, a transaction, the smart contract, a second smart contract, a second digital token, or a lookup table.

6 . The distributed computer-based digital token management system of claim 5 , wherein at least one of the block, the transaction, the second smart contract, or the second digital token is on the target digital notarized ledger or a different digital notarized ledger.

7 . The distributed computer-based digital token management system of claim 1 , wherein the first portion of the token address field representative of the owner of the digital token includes a unique owner identifier.

8 . The distributed computer-based digital token management system of claim 1 , wherein the token address field comprises a first unique owner identifier and a second unique owner identifier, wherein the second unique owner identifier is different from the first unique owner identifier.

9 . The distributed computer-based digital token management system of claim 1 , wherein the digital token comprises at least a third portion separate from the first portion of the token address field and the second portion of the token address field.

10 . The distributed computer-based digital token management system of claim 9 , wherein the third portion represents at least one of: an address, a Health Object Identifier (HOI), a suffix, a prefix, a bit field, a record identifier, a patient-specific record, a ledger state, a URL, a pointer, or a file system address.

11 . The distributed computer-based digital token management system of claim 9 , wherein the third portion is a different size than at least one of: the first portion of the token address field or the second portion of the token address field.

12 . The distributed computer-based digital token management system of claim 1 , wherein the first portion of the token address field is a different size than the second portion of the token address field.

13 . The distributed computer-based digital token management system of claim 1 , wherein the digital token further comprises at least a second token address field that is different from the token address field.

14 . The distributed computer-based digital token management system of claim 13 , wherein the second token address field comprises state information.

15 . The distributed computer-based digital token management system of claim 1 , wherein updating the second portion of the token address field further includes:

updating the second portion of the token address field independently of the first portion of the token address field.

16 . The distributed computer-based digital token management system of claim 1 , wherein updating the second portion of the token address field further includes:

updating the second portion based on updates or edits to the primary digital notarized ledger instantiated in the first computer readable memory that the digital token is on or the target digital notarized ledger instantiated in the first computer readable memory.

17 . The distributed computer-based digital token management system of claim 16 , wherein the updating the second portion is caused when at least one of the following occurs on the primary digital notarized ledger instantiated in the first computer readable memory or the target digital notarized ledger instantiated in the first computer readable memory: a block is added, a transaction is added, the primary digital notarized ledger instantiated in the first computer readable memory is turned off, the primary digital notarized ledger instantiated in the first computer readable memory is turned on, or the primary digital notarized ledger instantiated in the first computer readable memory has a state change.

18 . The distributed computer-based digital token management system of claim 17 , wherein the state change occurs when a state is created, updated, or deleted.

19 . The distributed computer-based digital token management system of claim 1 , wherein the operations further comprise:

updating the first portion of the token address field based on the second portion of the token address field.

20 . The distributed computer-based digital token management system of claim 1 , wherein updating the second portion of the token address field is performed when the first portion of the token address field is updated.

21 . The distributed computer-based digital token management system of claim 1 , wherein the first portion of the token address field represents a unique identifier of the owner of the digital token and does not change until at least the owner of the digital token or the owner of the target digital notarized ledger changes.

22 . The distributed computer-based digital token management system of claim 1 , wherein the second portion of the token address field of the token address field is used to store bits associated with at least one of: a multi-bit search trie, a value of a state machine, an index for a lookup table, additional instructions, or a next stage in a lookup.

23 . The distributed computer-based digital token management system of claim 22 , wherein the multi-bit search trie is used to store a primary ledger state.

24 . The distributed computer-based digital token management system of claim 1 , wherein the request to update the digital token is received when at least one of the following transactions takes place on the primary digital notarized ledger instantiated in the first computer readable memory or the target digital notarized ledger instantiated in the first computer readable memory: a mint transaction, a first transaction associated with an identified smart contract, a second transaction representing a change of ownership of the digital token, a third transaction representing a change of ownership of another digital token, a digital asset, or non-digital asset, a first file being saved, a second file being created, a third file being deleted, or a fourth file being saved by a particular user.

25 . The distributed computer-based digital token management system of claim 1 , wherein the request to update the digital token is received from a second smart contract on the primary digital notarized ledger or a different digital notarized ledger.

26 . The distributed computer-based digital token management system of claim 1 , wherein the digital token grants access rights to the smart contract.