Abstract: A system, method, and apparatus for creating and managing smart contracts on a blockchain is provided. A method includes detecting, by the computing system, a code language of the smart contract code, wherein each of a plurality of code languages is associated with at least one of a plurality of blockchain platforms; determining, by the computing system, based at least partially on the code language of the smart contract code, an optimal blockchain platform to deploy the smart contract onto, the optimal blockchain platform being one of the plurality of blockchain platforms associated with the detected code language, the smart contract code capable of being deployed onto two or more blockchain platforms; compiling, by the computing system, the smart contract code based on the determination of the optimal blockchain platform so as to generate smart contract byte code and metadata; and deploying, by the computing system, the smart contract byte code to the optimal blockchain platform.

Abstract: A system, method, and apparatus for creating and managing smart contracts on a blockchain is provided. A method includes detecting, by the computing system, a code language of the smart contract code, wherein each of a plurality of code languages is associated with at least one of a plurality of blockchain platforms; determining, by the computing system, based at least partially on the code language of the smart contract code, an optimal blockchain platform to deploy the smart contract onto, the optimal blockchain platform being one of the plurality of blockchain platforms associated with the detected code language, the smart contract code capable of being deployed onto two or more blockchain platforms; compiling, by the computing system, the smart contract code based on the determination of the optimal blockchain platform so as to generate smart contract byte code and metadata; and deploying, by the computing system, the smart contract byte code to the optimal blockchain platform.

Abstract: A method performed by a processor of a financial institution computing system includes authorizing an account holder to execute transactions in an MBC from a financial account of the account holder that includes funds in a fiat currency. A transaction request is received, including a request to transfer a first amount of funds from the financial account to a recipient. The first amount is defined in MBC. The financial account is debited by a second amount, which is an amount of fiat currency equivalent to the first amount of MBC. A service call is transmitted to the MBC partner. The service call includes instructions to create a temporary account to hold the MBC, to exchange the second amount from fiat currency to MBC, to credit the temporary account with the funds exchanged to MBC, and to transfer the first amount in MBC from the temporary account to the recipient.

Abstract: A method performed by a processor of a financial institution computing system includes authorizing an account holder to execute transactions in an MBC from a financial account of the account holder that includes funds in a fiat currency. A transaction request is received, including a request to transfer a first amount of funds from the financial account to a recipient. The first amount is defined in MBC. The financial account is debited by a second amount, which is an amount of fiat currency equivalent to the first amount of MBC. A service call is transmitted to the MBC partner. The service call includes instructions to create a temporary account to hold the MBC, to exchange the second amount from fiat currency to MBC, to credit the temporary account with the funds exchanged to MBC, and to transfer the first amount in MBC from the temporary account to the recipient.

Abstract: Systems, methods, and apparatuses for storing verified identification information in a distributed database and for verifying entities to requestors are provided herein. Identity information relating to an entity is verified by a generally recognized identity provider (GRIP). Once verified, the GRIP populates a distributed database with an entry corresponding to the verified identity information. The distributed database is publically accessible such that identity requestors can see the entries in the distributed database. In some arrangements, the distributed database is write-protected such that only an authorized GRIP can modify the distributed database. An entity can provide information to a requestor to verify an identity attribute of the entity to the requestor. The requestor uses information provided by the entity to retrieve verified entity identification information from the distributed database and to confirm that the identity attribute was verified by an authorized GRIP.

Abstract: A method performed by a processor of a financial institution computing system includes authorizing an account holder to execute transactions in an MBC from a financial account of the account holder that includes funds in a fiat currency. A transaction request is received, including a request to transfer a first amount of funds from the financial account to a recipient. The first amount is defined in MBC. The financial account is debited by a second amount, which is an amount of fiat currency equivalent to the first amount of MBC. A service call is transmitted to the MBC partner. The service call includes instructions to create a temporary account to hold the MBC, to exchange the second amount from fiat currency to MBC, to credit the temporary account with the funds exchanged to MBC, and to transfer the first amount in MBC from the temporary account to the recipient.

Abstract: Systems, methods, and apparatuses for storing verified identification information in a distributed database and for verifying entities to requestors are provided herein. Identity information relating to an entity is verified by a generally recognized identity provider (GRIP). Once verified, the GRIP populates a distributed database with an entry corresponding to the verified identity information. The distributed database is publically accessible such that identity requestors can see the entries in the distributed database. In some arrangements, the distributed database is write-protected such that only an authorized GRIP can modify the distributed database. An entity can provide information to a requestor to verify an identity attribute of the entity to the requestor. The requestor uses information provided by the entity to retrieve verified entity identification information from the distributed database and to confirm that the identity attribute was verified by an authorized GRIP.

Abstract: A system, method, and apparatus for creating and managing smart contracts on a blockchain is provided. A method includes receiving smart contract code; detecting a code language of the smart contract code; determining an optimal blockchain platform to deploy the smart contract onto; compiling the smart contract code so as to generate smart contract byte code and metadata; storing the smart contract byte code and the metadata; deploying the smart contract byte code to the optimal blockchain platform; receiving an address of the smart contract deployed to the optimal blockchain platform; assigning a name to the address; and storing the assigned name and the address in a smart contract naming directory; wherein a smart contract computing system is configured to identify the address of the deployed smart contract in response to receiving the name from a user.

Abstract: A method includes generating a blockchain-based letter of credit (“BLC”) relating to a contract for a trade transaction between a seller and a buyer. The BLC defines documentary and supply chain flow payment trigger events. The BLC is stored and accessible via a blockchain. A plurality of documentary flow events related to the BLC are tracked and recorded on the blockchain, and are linked to the BLC. A plurality of supply chain flow events related to a physical status of a good involved in the trade transaction are tracked and recorded on the blockchain. Each of the plurality of supply chain flow events are linked to the BLC. Payment for the contract for the trade transaction is transferred to the seller in response to detecting occurrence of both of the documentary and supply chain flow events corresponding to the respective documentary and supply chain flow payment trigger events.