Self-enforcing security token implementing smart-contract-based compliance rules consulting smart-contract-based global registry of investors
A network node in a peer-to-peer network of nodes includes at least one processor, at least one memory, and at least one network interface. The at least one processor is configured to receive a request to transfer a security token and execute a plurality of compliance rules associated with the security token. At least one of the compliance rules is implemented using at least one smart contract. The at least one smart contract references a global registry. The at least one processor is also configured to transfer the security token based on the execution of the compliance rules. The global registry includes personally identifiable information (PII) hash(es) for each of at least one investor associated with the transfer of the security token. The hashes are committed to the distributed ledger and updated when PII of a respective one of the at least one investor changes.
1. A network node comprising:
at least one processor;
at least one memory communicatively coupled to the at least one processor;
at least one network interface communicatively couple to the at least one processor;
wherein the network node is configured to be within a plurality of network nodes communicatively coupled in a peer-to-peer network of network nodes implementing a distributed ledger; and
wherein the network node is configured to be communicatively coupled to at least one remotely located computing device through the at least one network interface;
wherein the at least one processor is configured to:
receive, from a remotely located computing device, a request to transfer a security token;
execute a plurality of compliance rules associated with the security token, wherein at least one of the plurality of compliance rules is implemented using at least one smart contract, wherein the at least one smart contract references a global registry; and
transfer the security token based on the execution of the plurality of compliance rules, wherein the global registry comprises at least one personally identifiable information (PII) hash for each of at least one investor associated with the transfer of the security token, wherein the at least one PII hash for each of the at least one investor is committed to the distributed ledger, wherein each of the at least one PII hash is updated when PII of a respective investor of the at least one investor changes.
2. The network node of claim 1 , wherein the security token is a cryptographic token that represents an external, tradeable asset.
3. The network node of claim 1 , wherein the global registry comprises indication of at least one of:
whether an offering of the security token qualifies under Securities and Exchange Commission (SEC) Regulation A;
whether at least one of the at least one investor qualifies under SEC Regulation D; or
whether the offering of the security token qualifies under SEC Regulation S.
4. The network node of claim 3 , wherein the global registry further comprises indication of at least one of:
whether anti-money laundering and know-your-customer (AML/KYC) checks have been performed for the at least one investor associated with the transfer of the security token; or
a length of time a particular security token has been owned by a particular investor.
5. The network node of claim 4 , wherein the global registry further comprises indication of at least one of:
whether a freeze has been placed on any of the at least one investor;
whether a freeze has been placed on the security token;
whether a freeze has been placed on a custodian associated with the transfer of the security token; or
whether a freeze has been placed on any broker dealer associated with the transfer of the security token.
6. The network node of claim 5 , further comprising at least one of:
wherein a freeze is placed on or removed from any of the at least one investor by modifying first attributes in an investor element in the global registry;
wherein a freeze is placed on or removed from the security token by modifying second attributes in a security token element in the global registry;
wherein a freeze is placed on or removed from the custodian by modifying third attributes in a custodian element in the global registry; or
wherein a freeze is placed on or removed from any broker dealer associated with the transfer of the security token by modifying fourth attributes in a broker dealer element in the global registry.
7. The network node of claim 5 , wherein the global registry comprises a data storage smart contract that stores at least one indication in the global registry.
8. The network node of claim 1 , wherein the security token stores a table that indicates a length of time a particular security token has been owned by a particular investor.
9. The network node of claim 1 , wherein the security token is implemented using an originating smart contract.
10. The network node of claim 1 , wherein a record of an issuance of the security token is recorded on the distributed ledger.
11. The network node of claim 1 , wherein a record of the transfer of the security token is committed to the distributed ledger.
12. The network node of claim 1 , wherein the request to transfer the security token is a request to transfer the security token from a first address to a second address, wherein the at least one processor is configured to:
before the request to transfer the security token is received, determine a split ratio for a new split of security tokens held in at least one address of the distributed ledger without updating token balances on the distributed ledger;
determine a split-updated token balance for at least the first address based on at least an indication of the split ratio; and
wherein the token balances on the distributed ledger are updated for at least the first address based on the split-updated token balance for at least the first address as part of a transaction associated with the transfer of the security token.
13. A computerized method for transferring a self-enforcing security token, wherein the computerized method is performed by a network node configured to be included within a plurality of network nodes in a peer-to-peer network of network nodes implementing a distributed ledger, wherein the network node is configured to be communicatively coupled to other network nodes in the peer-to-peer network, the computerized method comprising:
receiving, from a remotely located computing device, a request to transfer a security token;
executing a plurality of compliance rules associated with the security token, wherein at least one of the plurality of compliance rules is implemented using at least one smart contract, wherein the at least one smart contract references a global registry; and
transferring the security token based on the execution of the plurality of compliance rules, wherein the global registry comprises at least one personally identifiable information (PII) hash for each of at least one investor associated with the transfer of the security token, wherein the at least one PII hash for each of the at least one investor is committed to the distributed ledger, wherein each of the at least one PII hash is updated when PII of a respective investor of the at least one investor changes.
14. The computerized method of claim 13 , wherein the security token is a cryptographic token that represents an external, tradeable asset.
15. The computerized method of claim 13 , wherein the global registry comprises indication of at least one of:
whether an offering of the security token qualifies under Securities and Exchange Commission (SEC) Regulation A;
whether at least one of the at least one investor qualifies under SEC Regulation D; or
whether the offering of the security token qualifies under SEC Regulation S.
16. The computerized method of claim 13 , wherein the global registry further comprises indication of at least one of:
whether anti-money laundering and know-your-customer (AML/KYC) checks have been performed for at least one investor associated with the transfer of the security token; or
a length of time a particular security token has been owned by a particular investor.
17. The computerized method of claim 16 , wherein the global registry further comprises indication of at least one of:
whether a freeze has been placed on any of the at least one investor;
whether a freeze has been placed on the security token;
whether a freeze has been placed on a custodian associated with the transfer of the security token; or
whether a freeze has been placed on any broker dealer associated with the transfer of the security token.
18. The computerized method of claim 17 , further comprising at least one of:
wherein a freeze is placed on or removed from any of the at least one investor by modifying first attributes in an investor element in the global registry;
wherein a freeze is placed on or removed from the security token by modifying second attributes in a security token element in the global registry;
wherein a freeze is placed on or removed from the custodian by modifying third attributes in a custodian element in the global registry; or
wherein a freeze is placed on or removed from any broker dealer associated with the transfer of the security token by modifying fourth attributes in a broker dealer element in the global registry.
19. The computerized method of claim 17 , wherein the global registry comprises a data storage smart contract that stores at least one indication in the global registry.
20. The computerized method of claim 13 , wherein the security token stores a table that indicates a length of time a particular security token has been owned by a particular investor.
21. The computerized method of claim 13 , wherein the security token is implemented using an originating smart contract.
22. The computerized method of claim 13 , wherein a record of an issuance of the security token is recorded on the distributed ledger.
23. The computerized method of claim 13 , wherein a record of the transfer of the security token is committed to the distributed ledger.
24. The computerized method of claim 13 , wherein the request to transfer the security token is a request to transfer the security token from a first address to a second address, wherein the computerized method further comprises:
before the request to transfer the security token is received, determining a split ratio for a new split of security tokens held in at least one address of the distributed ledger without updating token balances on the distributed ledger;
determining a split-updated token balance for at least the first address based on at least an indication of the split ratio; and
wherein the token balances on the distributed ledger are updated for at least the first address based on the split-updated token balance for at least the first address as part of a transaction associated with the transfer of the security token.