Abstract: Systems and methods for managing digital identities. In some embodiments, a method is provided, comprising acts of: receiving a request to validate at least one statement about a user; identifying, from the request, a reference to a distributed ledger, the reference comprising an identifier for the distributed ledger and an identifier for a transaction recorded on the distributed ledger; identifying, based at least in part on the identifier for the distributed ledger, at least one node of a network of nodes managing the distributed ledger; and communicating with the at least one node to validate the at least one statement about the user.

Abstract: A decentralized investment fund operates according to consensus code on a shared ledger and raises capital by issuing ownership tokens on the shared ledger. The decentralized investment fund may hold digital assets in the consensus code and distribute profits to the token owners according to each owner's dividend preference. A token owner's dividend preference can include digital assets tracked by a different shared ledger, stabletoken digital assets pegged to the value of a digital asset, and cross-chain digital asset swaps. Token issuance may include a proof of accreditation requirement based on cryptographic proof on a shared ledger. The decentralized investment fund may distribute fund documents to the token holders by encrypting the document, first with a symmetric key common to all token holders, and second with an asymmetric key unique to each token holders and based on the token's holder's known public address on the shared ledger.

Abstract: Users of a multisignature wallet can customize keys to initiate various transactions. As a user specifies roles to customize keys, a smart contract is updated to associate the roles with the keys, where the customized keys are then associated with the user's multisignature wallet. The user may perform transactions by signing using the key or an address of the key, where a transaction can be processed upon verifying the key and its role. Additionally, a privacy service can facilitate blockchain transactions initiated using a key of a multisignature wallet. The privacy service receives a transaction signed by a key of the multisignature wallet and identifies a proxy wallet using the key. The privacy service validates and signs the transaction, which is then sent to a proxy wallet. The proxy wallet can cause a blockchain transaction to be executed.

Abstract: A system and a method are disclosed for using a client that is unsynchronized with a blockchain network to validate blockchain transactions for IoT devices, web apps, mobile apps, and other applications. The client retrieves a register of nodes (acting as information provider or validator) that are synchronized with the blockchain network, selects a node from the register, and transmits an information request to the selected node. The client receives a response to the request, the response including the requested information and validation indicia (e.g., proofs), and determines whether the response is valid based on the validation indicia. The client transmits, in response to determining that the response is valid, a confirmation to the IoT device, web app, mobile app or other applications.

Abstract: Systems and methods for providing a secure custodial service for managing a digital asset. The method comprises receiving a first value for use in decrypting at least one attribute value, receiving the at least one attribute value in encrypted form, and storing, on at least one storage device, the first value and the at least one attributed value in encrypted form, wherein at least one attribute value has been encrypted using a second value and a public key associated with secure hardware, and the second value corresponds to the first value.

Abstract: Systems and methods for validating transactions distributed ledger transactions. In some embodiments, a request may be received to validate a proposed transaction for layer 2 processing for a distributed ledger. In response, a cryptographic configuration involved in the proposed transaction may be identified, and the proposed transaction may be checked against one or more transaction rules of the cryptographic configuration. In response to successfully checking the proposed transaction against the one or more transaction rules of the cryptographic configuration, the proposed transaction may be signed as part of a joint signature process with a validation key associated with the cryptographic configuration.

Abstract: Users of a multisignature wallet can customize keys to initiate various transactions. As a user specifies roles to customize keys, a smart contract is updated to associate the roles with the keys, where the customized keys are then associated with the user's multisignature wallet. The user may perform transactions by signing using the key or an address of the key, where a transaction can be processed upon verifying the key and its role. Additionally, a privacy service can facilitate blockchain transactions initiated using a key of a multisignature wallet. The privacy service receives a transaction signed by a key of the multisignature wallet and identifies a proxy wallet using the key. The privacy service validates and signs the transaction, which is then sent to a proxy wallet. The proxy wallet can cause a blockchain transaction to be executed.

Abstract: The reliability of a second public key which is part of a second key pair generated in association with a first key pair is certified. A generating apparatus 210 provides certification data to a receiving apparatus 220 (S301). The receiving apparatus 220 transmits a certification request requesting a certification that the second public key PK2 is in a parent-child relationship with the first public key PKI to a certifying apparatus 230 (S302). In this example, the certification request includes the certification data, but if the certification data is provided directly from the generating apparatus 210 to the certifying apparatus 230, the certification request does not need to include the certification data. The certifying apparatus 230 verifies the certification data by calculating a verification formula for the certification data in response to the certification request (S303).

Abstract: Proving reliability of a second public key of a second key pair generated in association with a first key pair. A generator 210 calculates and stores x·H(n) which is proof data and ax·H(n), when the second public key ax·g1 which is of the second key pair is generated (S301). The generator 210 provides the calculated proof data to a receiving apparatus 220 (S302) which has received the proof data, transmits a proof request to the proving apparatus 230 for requesting a proof that the second public key ax·g1 is generated by an owner of the first public key a·g1 (S303). In response to the proof request, the proving apparatus 230 verifies the proof data by calculating a verification formula for the proof data (S304). The proving apparatus 230 transmits the verification result as a response to the proof request from the receiving apparatus 220 (S305).

Abstract: Systems and methods for managing digital identities. In some embodiments, a method is provided, comprising acts of: receiving a request to validate at least one statement about a user; identifying, from the request, a reference to a distributed ledger, the reference comprising an identifier for the distributed ledger and an identifier for a transaction recorded on the distributed ledger; identifying, based at least in part on the identifier for the distributed ledger, at least one node of a network of nodes managing the distributed ledger; and communicating with the at least one node to validate the at least one statement about the user.

Abstract: The disclosed embodiments provide a distributed transaction system including a group of validator nodes that are known to each other in a network but are indistinguishable to other network nodes. The validator nodes form a Committee including a Leader node and one or more Associate nodes configured to receive and process transaction requests and candidate requests, for example, to add new blocks to one or more blockchains. The Committee may be dynamically changed, such that new network nodes may be added to the Committee or may replace existing validator nodes. The Associate nodes also may coordinate with each other to select a new Leader node. The system may allow multiple request-fulfillment process to run simultaneously, thereby enhance the efficiency of the system.

Abstract: Systems and methods for managing digital identities. In some embodiments, a method is provided, comprising acts of: receiving a request to validate at least one statement about a user; identifying, from the request, a reference to a distributed ledger, the reference comprising an identifier for the distributed ledger and an identifier for a transaction recorded on the distributed ledger; identifying, based at least in part on the identifier for the distributed ledger, at least one node of a network of nodes managing the distributed ledger; and communicating with the at least one node to validate the at least one statement about the user.

Abstract: A method includes conveying a cryptocurrency transaction to a peer-to-peer network, wherein said cryptocurrency transaction having encoded therein an email address and to convey goods or services embodied in an electronic form to the email address in response to receipt of said cryptocurrency transaction on said peer-to-peer network. The conveying of goods or services includes transmitting over the Internet in conformance with an email protocol. The goods or services includes event admission tickets, music recordings, video, text, game content, live event broadcast, software, encryption keys or passwords.

Abstract: Systems and methods are provided for optimizing computer processing power in cloud computing systems. The method may include obtaining, by an interactive dynamic resizer application stored on non-volatile computer readable memory operatively connected to an administrator device, status information of a first server instance; accessing policy rule information for a first set of server instances associated with a first server; identifying a second server instance based on the status information and the policy rules information; automatically selecting the second server instance; generating resizing instructions based on the selected second server instance; and sending the resizing instructions to a cloud network.

Abstract: Systems and methods for performing a compliance check on a proposed transfer of one or more digital assets between a user and a counterparty. In some embodiments, one or more attribute values of the counterparty may be received, the one or more attribute values comprises a first attribute value indicating a status of a distributed ledger address of the counterparty. One or more corresponding attribute attestations may be accessed from a distributed ledger, and may be checked against the one or more attribute values. For instance, it may be checked whether each attribute attestation includes a cryptographic proof of the corresponding attribute value, and/or whether the cryptographic proof is electronically signed by a trusted entity. Additionally, or alternatively, it may be determined, based on the first attribute value indicating the status of the distributed ledger address of the counterparty, whether one or more compliance requirements are triggered.

Abstract: Determining data availability is disclosed, including: performing a data availability challenge with respect to a claimer node to determine whether the claimer node stores at least some elements included in a base layer in a digital tree corresponding to a data entity; and publishing a first set of elements associated with the base layer of the digital tree and the data availability challenge. Furthermore, encoding auditing is disclosed, including: obtaining a first set of elements associated with a base layer of a digital tree corresponding to a data entity; and generating an encoding validity determination of the digital tree based at least in part on whether the first set of elements is usable to recover a second set of elements associated with the base layer of the digital tree.

Abstract: The disclosed embodiments provide a distributed transaction system including a group of validator nodes that are known to each other in a network but are indistinguishable to other network nodes. The validator nodes form a Committee including a Leader node and one or more Associate nodes configured to receive and process transaction requests, for example, to add new blocks to one or more blockchains. The Committee may be dynamically changed, such that new network nodes may be added to the Committee or may replace existing validator nodes. The Associate nodes also may coordinate with each other to select a new Leader node. The disclosed embodiments reduce the distributed system's reliance on the stability of any particular node(s) in the network, as the validator nodes in the Committee may be changed at a sufficient frequency to remove unreliable, unavailable, or otherwise untrusted nodes.

Abstract: The disclosed embodiments provide a distributed transaction system including a group of validator nodes that are known to each other in a network but are indistinguishable to other network nodes. The validator nodes form a Committee including a Leader node and one or more Associate nodes configured to receive and process transaction requests and candidate requests, for example, to add new blocks to one or more blockchains. The Committee may be dynamically changed, such that new network nodes may be added to the Committee or may replace existing validator nodes. The Associate nodes also may coordinate with each other to select a new Leader node. The system may allow multiple request-fulfillment process to run simultaneously, thereby enhance the efficiency of the system.

Abstract: Signature handling for a block for which consensus was formed in blockchain network which requires signatures from plurality of nodes to form consensus for block adoption. After completion of the setup, first node 110 sends a first message including a generated block to N nodes (S301). Each node evaluates the validity of the block on basis of the rule for consensus formation (S302). If the block is valid, the node sends a second message which includes signature si, by secret key share f(xi), with respect to a hash value h of the block for which consensus is to be formed (S303-1). After k signatures are collected at jth node, the node merges these signatures to generate a signature corresponding to a public key PK (S304). A block for which consensus is to be formed has signature SK·h appended thereto and is added to blockchain of each node (S306).

Abstract: A system for “tagging” funds identified on a blockchain and associating a weight value therewith. The tagging profile is developed into a propagation profile wherein weight values are inherited from the tagging profile s. Propagation profile funds may be diluted by combining with non-tagged funds, similar to how ink dilutes through water. A spending history of funds of interest is developed based on replaying the funds of interest against the global transaction history of the blockchain. It is determined whether the spending history intersects with the propagation profile, thus determining how closely the two sources of funds are economically to one another. Intersection triggers actions including alert notifications or transfer of funds on the blockchain.