Abstract: A computing system comprising: processor(s) and memory; at least one network interface communicatively coupled to the at least one processor and configured to communicate with at least one remotely located computing device; wherein the at least one network interface is configured to receive a plurality of public encryption keys from the at least one remotely located computing device; wherein the at least one processor is configured to: split at least one secret into a plurality of shares, wherein at least a subset of the plurality of shares is sufficient to reconstruct the at least one secret; encrypt each of the plurality of shares based on a different public encryption key of the plurality of public encryption keys to create a plurality of encrypted shares; wherein the at least one network interface is configured to communicate the encrypted shares to the at least one remotely located computing device.

Abstract: Systems and methods described herein generally relate to storing and verifying data. In some embodiments, reference levels are generated according to time intervals, where the first reference level comprises a predetermined number of the time intervals, and where each of the time intervals of the remaining reference levels is comprised of a predetermined number of the time intervals of a previous reference level. Hashes of data can be created at the first reference level by performing a hashing function on the data in a time-sequenced manner. First reference level time interval hashes may be generated by performing the hashing function on the hashes of the data at each of the time intervals of the first reference level. Hashes for remaining reference level time intervals can be generated by performing the hashing function on the hashes of each of the time intervals of the previous reference level.

Abstract: A system, includes at least one processor; and at least one memory communicatively coupled to the at least one processor. The at least one processor is configured to receive an order to execute a trade of at least one transactional item associated with a first account, wherein the order, the first account, and a second account are associated with a common identifier; generate a first transaction to transfer the at least one transactional item from the first account to the second account; generate a second transaction that includes the order; verify that the first transaction was authorized by a same party as the second transaction; and authorize placement of the order on an exchange if the first transaction was authorized by the same party as the second transaction.

Abstract: Methods and systems described herein create a first addressed account and a second addressed account that each have a common identifier and are each associated with a customer. The system can receive an order for exchanging digital transactional items associated with the first addressed account, where the order is associated with the common identifier. A private key associated with the first addressed account can be used to electronically sign a first transaction to transfer the digital transactional items from the first addressed account to the second addressed account, and the same private key can be used to sign a second transaction. After verifying that the first transaction was signed with the same private key as the first transaction, the system authorizes placement of the order on a cryptographic exchange.

Abstract: A network node includes at least one processor, at least one memory, and at least one network interface. 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. The network node is configured to be communicatively coupled to at least one remotely located computing device through the at least one network interface. The at least one processor is configured to determine a split ratio for a new split of security tokens held in at least one address of the distributed ledger. The at least one processor is also configured to store an indication of the split ratio without updating token balances for all of the at least one address in a list of addresses holding at least one of the security tokens.

Abstract: A network node that includes at least one processor, at least one memory, and at least one network interface. 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. The network node is communicatively coupled to at least one remotely located computing device through the at least one network interface. The at least one processor is configured to deploy a child smart contract, which is a subsequent version of a parent smart contract, on the distributed ledger. The at least one processor is also configured to set an upgraded address field in the parent smart contract to point to an address of the child smart contract. The parent smart contract remains deployed after the child smart contract is deployed.

Abstract: A network node that includes at least one processor, at least one memory, and at least one network interface is disclosed. 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. The network node is configured to be communicatively coupled to at least one remotely located computing device through the at least one network interface. The at least one processor is configured to receive, from a remotely located computing device, a request to transfer a security token. The at least one processor is also configured to 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.

Abstract: Methods and systems described herein prevent traders from using order intent and hardware solutions to advance their order position by obfuscating the order until execution and by using a digital ledger to assign priority of the orders. As described herein, using a series of cryptographic key pairs, one side of a transaction can be created, matched, and executed while a public record is recorded and maintained but obfuscated (i.e., not publicly transparent) until after the transaction is completed.

Abstract: Systems and methods described herein generally relate to storing and verifying data. In some embodiments, reference levels are generated according to time intervals, where the first reference level comprises a predetermined number of the time intervals, and where each of the time intervals of the remaining reference levels is comprised of a predetermined number of the time intervals of a previous reference level. Hashes of data can be created at the first reference level by performing a hashing function on the data in a time-sequenced manner. First reference level time interval hashes may be generated by performing the hashing function on the hashes of the data at each of the time intervals of the first reference level. Hashes for remaining reference level time intervals can be generated by performing the hashing function on the hashes of each of the time intervals of the previous reference level.

Abstract: Methods and systems described herein create a first addressed account and a second addressed account that each have a common identifier and are each associated with a customer. The system can receive an order for exchanging digital transactional items associated with the first addressed account, where the order is associated with the common identifier. A private key associated with the first addressed account can be used to electronically sign a first transaction to transfer the digital transactional items from the first addressed account to the second addressed account, and the same private key can be used to sign a second transaction. After verifying that the first transaction was signed with the same private key as the first transaction, the system authorizes placement of the order on a cryptographic exchange.