| CPC G06Q 20/367 (2013.01) [G06F 16/1834 (2019.01); G06Q 20/0658 (2013.01); G06Q 20/3672 (2013.01); G06Q 20/389 (2013.01); G06Q 20/405 (2013.01); H04L 9/3236 (2013.01); H04L 63/20 (2013.01); G06Q 2220/00 (2013.01); H04L 9/50 (2022.05); H04L 2209/56 (2013.01)] | 24 Claims |

|
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.
|