Patent Grant
11334883
This application is also a continuation in part of U.S. patent application Ser. No. 16/452,187, filed on Jun. 25, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MAKING PAYMENTS USING FIAT BACKED DIGITAL ASSETS, which claims the benefit of and priority to each of U.S. Provisional Application No. 62/689,563, filed on Jun. 25, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application Ser. No. 62/764,977, filed on Aug. 17, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; U.S. Provisional Patent Application Ser. No. 62/721,983, filed on Aug. 23, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; and U.S. Provisional Patent Application Ser. No. 62/728,441, filed on Sep. 7, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS, the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/452,187 is a continuation-in-part of U.S. patent application Ser. No. 16/437,841, filed on Jun. 11, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, which is a continuation in part of U.S. patent application Ser. No. 16/421,975, filed on May 24, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS, which is a continuation of U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS which claims the benefit of and priority to each of U.S. Provisional Application No. 62/638,679, filed on Mar. 5, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/647,353, filed on Mar. 23, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/660,655, filed on Apr. 20, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/683,412, filed on Jun. 11, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/689,563, filed on Jun. 25, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application Ser. No. 62/764,977, filed on Aug. 17, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; U.S. Provisional Patent Application Ser. No. 62/721,983, filed on Aug. 23, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; and U.S. Provisional Patent Application Ser. No. 62/728,441, filed on Sep. 7, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS, the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS” also claims priority as a continuation-in-part to U.S. patent application Ser. No. 16/036,469, filed on Jul. 16, 2018 and entitled “SYSTEM, METHOD, AND PROGRAM PRODUCT FOR DEPOSITING AND WITHDRAWING STABLE VALUE DIGITAL ASSETS IN EXCHANGE FOR FIAT”, which in turn is a continuation-in-part of U.S. patent application Ser. No. 16/020,534, filed on Jun. 27, 2018 and entitled “SYSTEM, METHOD, AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS”, which in turn is a continuation-in-part of U.S. patent application Ser. No. 15/960,040, filed on Apr. 23, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” which claims priority to and the benefit of each of U.S. Provisional Patent Application No. 62/660,655, filed on Apr. 20, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” U.S. Provisional Patent Application No. 62/647,353, filed on Mar. 23, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” and U.S. Provisional Patent Application No. 62/638,679, filed on Mar. 5, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS” also claims priority as a continuation-in-part to U.S. patent application Ser. No. 15/960,040, filed on Apr. 23, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” which claims priority to and the benefit of each of: U.S. Provisional Patent Application No. 62/660,655, filed on Apr. 20, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” U.S. Provisional Patent Application No. 62/647,353, filed on Mar. 23, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” and U.S. Provisional Patent Application No. 62/638,679, filed on Mar. 5, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS,” the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS” also claims priority as a continuation-in-part to U.S. patent application Ser. No. 16/020,534 filed on Jun. 27, 2018 and entitled “SYSTEM, METHOD, AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS”, which claims the benefit of and priority to each of U.S. Provisional Patent Application Ser. No. 62/689,563, filed on Jun. 25, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS” and U.S. Provisional Patent Application No. 62/683,412, filed Jun. 11, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS”, the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/036,469 also claims the benefit of and priority to each of U.S. Provisional Patent Application Ser. No. 62/689,563, filed on Jun. 25, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS” and U.S. Provisional Patent Application No. 62/683,412, filed Jun. 11, 2018 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS”, the entire content of each of which is hereby incorporated by reference herein.
U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled “SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS” also claims priority as a continuation-in-part to U.S. patent application Ser. No. 16/282,955, filed on Feb. 22, 2019 and entitled “SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR DEPOSITING, HOLDING, AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN” which in turn is a continuation-in-part to U.S. Non-Provisional patent application Ser. No. 16/280,788, filed Feb. 20, 2019 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR LOANING DIGITAL ASSETS AND FOR DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN, which in turn claims priority to U.S. Provisional Application Ser. No. 62/684,023 filed on Jun. 12, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR LOANING DIGITAL ASSETS; U.S. Provisional Application No. 62/680,775, filed on Jun. 5, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR LOANING DIGITAL ASSETS; U.S. Provisional Application No. 62/702,265, filed on Jul. 23, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR LOANING DIGITAL ASSETS AND FOR DEPOSITING, HOLDING, AND/OR DISTRIBUTING COLLATERAL AS A TOKEN ON AN UNDERLYING BLOCKCHAIN; U.S. Provisional Patent Application Ser. No. 62/764,978, filed on Aug. 17, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR GENERATING USER DEFINED SMART CONTRACTS AND DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN; and U.S. Provisional Patent Application Ser. No. 62/732,347, filed on Sep. 17, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR GENERATING USER DEFINED SMART CONTRACTS AND DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN, the entire content of each of each of which is hereby incorporated by reference herein.
U.S. Non-Provisional patent application Ser. No. 16/280,788 also claims priority as a continuation-in-part to U.S. Non-Provisional patent application Ser. No. 15/973,140, filed on May 7, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, which in turn claims priority to U.S. Provisional Patent Application Ser. No. 62/660,655, filed on Apr. 20, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, U.S. Provisional Patent Application Ser. No. 62/642,946, filed on Mar. 14, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, U.S. Provisional Patent Application Ser. No. 62/642,931, filed on Mar. 14, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, and U.S. Provisional Patent Application Ser. No. 62/629,417, filed on Feb. 12, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, the entire content of each of which is hereby incorporated by reference herein. U.S. Non-Provisional patent application Ser. No. 16/280,788 also claims priority as a continuation-in-part to U.S. Non-Provisional patent application Ser. No. 15/960,040, filed on Apr. 23, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, which in turn claims priority to U.S. Provisional Patent Application Ser. No. 62/660,655, filed on Apr. 20, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, and U.S. Provisional Patent Application Ser. No. 62/647,353, filed on Mar. 23, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS and U.S. Provisional Patent Application Ser. No. 62/638,679, filed on Mar. 5, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, the entire content of each of which is hereby incorporated by reference herein. U.S. Non-Provisional patent application Ser. No. 16/280,788 also claims priority as a continuation-in-part to U.S. Non-Provisional patent application Ser. No. 15/973,175, filed on May 7, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, which in turn claims priority to U.S. Provisional Patent Application No. 62/642,946, filed on Mar. 14, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, and U.S. Provisional Patent Application No. 62/642,931 filed on Mar. 14, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, and U.S. Provisional Patent Application Ser. No. 62/629,417, filed Feb. 12, 2018 entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, and U.S. Provisional Patent Application Ser. No. 62/660,655 filed on Apr. 20, 2018 and entitled SYSTEMS, METHODS, and PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS, the entire content of each of which is hereby incorporated by reference herein. U.S. Non-Provisional patent application Ser. No. 16/280,788 also claims priority as a continuation-in-part to U.S. Non-Provisional patent application Ser. No. 15/920,042, filed on Mar. 13, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, which in turn claims priority to U.S. Provisional Patent Application No. 62/629,417 filed Feb. 12, 2018 entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, the entire content of each of which is hereby incorporated by reference herein.
This application claims the benefit of and priority to each of U.S. Provisional Application No. 62/867,091, filed on Jun. 26, 2019 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN; U.S. Provisional Application No. 62/732,347, filed on Sep. 17, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR GENERATING USER DEFINED SMART CONTRACTS AND DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN; U.S. Provisional Application No. 62/728,441, filed on Sep. 7, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; U.S. Provisional Patent Application No. 62/721,983, filed on Aug. 23, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; U.S. Provisional Patent Application No. 62/764,978, filed on Aug. 17, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR GENERATING USER DEFINED SMART CONTRACTS AND DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN; U.S. Provisional Patent Application No. 62/764,977, filed on Aug. 17, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; and U.S. Provisional Patent Application No. 62/702,265, filed on Jul. 23, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR LOANING DIGITAL ASSETS AND FOR DEPOSITING, HOLDING AND/OR DISTRIBUTING COLLATERAL AS A TOKEN IN THE FORM OF DIGITAL ASSETS ON AN UNDERLYING BLOCKCHAIN, the entire content of each of which is hereby incorporated by reference herein.
The present invention also relates to a method, system, and program product for generating user defined smart contracts and depositing, holding and/or distributing collateral in the form of a stable value token for a security token based on the user defined smart contracts, the tokens being on the same underlying blockchain.
There is no technological solution for generating user defined smart contracts and depositing, holding, and/or distributing collateral in the form of a stable value token for a security token based on the user defined smart contract, the tokens being on the same underlying blockchain.
Traditionally, capital markets work by channeling savings typically held in banks into investments in exchange for interest on the use of such capital over a defined period of time in exchange for a defined interest rates. With government backed currencies (or fiat) like the U.S. dollar, central authorities, like the Federal Reserve in the U.S. for U.S. Dollars, are involved in established bench mark rates at which banks may lend or borrow funds. These rates may vary on the length of time at which such funds are to be lent or borrowed.
With the advent of digital assets and crypto-currencies, traditional banks are no longer involved with storage of such digital assets. Thus, in the new paradigm, digital assets are stored by holders in digital wallets are tracked and maintained on a peer-to-peer blockchain, with no central authority or bank involved. As a result, once value is stored in a digital asset, that value is taken out of the economy and remains idle. In other words, it is no longer available to loan or invest, and/or earn interest, while it is being securely stored in a digital wallet.
Thus, digital assets and the new blockchain technology create a technological challenge of how to continue to take advantage of the security and independence offered by peer-to-peer blockchain technologies, but still allow stored value in digital asset wallets to be invested so as to earn interest and support investment through capital markets.
Another technical problem arises in that current blockchain technology does not provide for a mechanism to deposit, hold and/or distribute collateral in the form of stable value digital assets for a security token based on a user defined smart contract, on the same underlying blockchain.
An object of the present invention is to address technological challenges that currently exist in providing user defined smart contracts based on user provided contract parameters on underlying blockchains as well as depositing, holding and/or distributing collateral in the form of a stable value token for a security token based on the user defined smart contract, the tokens being on the same underlying blockchain.
This and other objects shall be addressed by embodiments of the present invention as set forth herein.
The present invention relates to methods, systems, and program products for providing user defined smart contract parameters on underlying blockchains.
Systems, methods, and program products for use with custodial electronics wallets for ETPs holding digital assets, including digital math-based assets, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin to name a few, and other financial products or services based on the same, are disclosed.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the blockchain for the underlying digital asset, a second message comprising requests for the first smart contract to: (i) recalculate the second collateral amount based on the at least one collateral requirement and current benchmark information; (l) determining, by the first smart contract, a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (m) receiving, at the first smart contract address, the second additional collateral amount. In embodiments the second collateral amount is recalculated by the first user device. In embodiments, the administrator system sends the second message in response to receiving a request from the first user device. In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) monitoring, by the administrator system, the second contract address on the blockchain associated with the underlying digital asset; (l) determining, by the administrator system, the second additional collateral amount is not received by the first smart contract address; (m) generating, by the administrator system, a notification indicating that the second additional collateral amount is not received by the first smart contract address; (n) sending, by the administrator system, the notification to the first user device, the second user device and the first smart contract address; (o) generating, by the administrator system, a third message including a request to transfer the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions; and (p) sending, by the administrator system, the third message to the first smart contract address from the administrator public address via the blockchain, wherein, upon receipt of the third message, the first smart contract address transfers the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions.
In embodiments, the first contract information further comprises at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, prior to step (a), the method further comprises: (k) generating, by the administrator system, machine readable instructions comprising graphical user interface information including a graphical user interface with at least one prompt for the first user to provide the contract proposal; (l) sending, by the administrator system to the first user device, the machine readable instructions such that, upon receipt of the machine readable instructions, the first user device displays the graphical user interface; and (m) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the first smart contract is associated with a security token.
In embodiments, a third smart contract comprises the first smart contract and the stable value token smart contract.
In embodiments, a method comprises (a) receiving, from a first user device associated with a first user by an administrator system associated with an administrator of a digital asset database, a first contract proposal, wherein the first contract proposal includes: (i) first user information associated with the first user; and (ii) first contract information comprising at least the following contract parameters: (A) an inception date; (B) an inception value; (C) at least one benchmark; (D) a contract duration; (E) at least one collateral requirement; (F) a notional value of the smart contract; and (G) first side information comprising identification of a first leg of the first contract proposal, wherein the digital asset database is tied to a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network; and wherein the administrator system is associated with an administrator public address associated with the peer-to-peer network; (b) receiving, by the administrator system from a second user device associated with a second user, at least one indication of interest, wherein the at least one indication of interest includes at least: (i) a first user response comprising: (1) second user information associated with the second user; and (2) second side information comprising a second leg of the contract proposal; (c) matching, by the administrator system, the first contract information and the second side information; (d) generating a first module on the peer-to-peer network associated with a fiat-backed digital asset, wherein the module comprises first contract instructions associated with a first module address associated with the peer-to-peer network, wherein the smart contract instructions are saved in the peer-to-peer network and include: (i) first authorization instructions regarding creating fiat-backed digital assets; (ii) second authorization instructions regarding transferring fiat-backed digital assets; (iii) third authorization instructions regarding destroying fiat-backed digital assets; (iv) fourth authorization instructions regarding functions associated with the fiat-backed digital asset; (v) first trade instructions including execution instructions to execute a first trade between the first user and the second user, wherein the first trade is based on at least the following: 1. the first contract proposal; and 2. the first user response (vi) fifth authorization instructions regarding transferring security tokens; (vii) sixth authorization instructions regarding destroying security tokens; (viii) seventh authorization instructions regarding transferring fiat-backed digital assets from the first smart contract address; (ix) calculating instructions regarding calculating excess collateral; and (x) dispute instructions regarding disputed benchmark information received by the first smart contract address from an oracle; (e) sending, by the administrator system from the administrator public address to the module address via the peer-to-peer network, the first module and associated first contract instructions; (f) receiving, by the first module address, a first amount of collateral, wherein the first amount of collateral is a first amount of fiat-backed digital assets associated with the first user as collateral, and wherein the first amount of fiat-backed digital assets associated with the first user is based on the at least one collateral requirement; (g) receiving, by the first module address, a second amount of collateral, wherein the second amount of collateral is a second amount of fiat-backed digital assets associated with the second user as collateral, wherein the second amount of fiat-backed digital assets associated with the second user is based on the at least one collateral requirement; (h) receiving, by the first module address from an oracle public address associated with the oracle, a third amount of collateral, wherein the third amount of collateral is a third amount of fiat-backed digital assets associated with the oracle as collateral, wherein the third amount of fiat-backed digital assets associated with the oracle is based on the at least one collateral requirement, wherein the oracle public address is associated with the peer-to-peer network; (i) implementing, by the first module, the first trade instructions via the peer-to-peer network by the plurality of geographically distributed computer systems in the peer-to-peer network, wherein implementing comprises the following steps: (i) receiving, by the first module address from the oracle, a first benchmark message including: (1) first current benchmark information associated with the first contract information; (2) a digital signature associated with the oracle; and (3) a first timestamp; (ii) monitoring, by the administrator system, the first module address for a predetermined amount of time; and (iii) after the predetermined amount of time has elapsed, collecting, by the administrator system from the module address, excess collateral from the first trade, wherein the collecting includes steps of: (1) sending, by the administrator system via the peer-to-peer network, a first message comprising requests for the first smart contract to: (A) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (B) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (C) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (D) distribute the first excess collateral to a first user public address associated with the first user and associated with the peer-to-peer network; (E) distribute the second excess collateral to a second user public address associated with the second user associated with the peer-to-peer network; and (F) distribute the third excess collateral to the oracle public address.
In embodiments, monitoring the first module address for the predetermined amount of time further comprises: (1) receiving, by the first module address, a first dispute message disputing the first current benchmark information, wherein the first dispute message comprises: (A) the first digitally signed benchmark message; and (B) a second digitally signed benchmark message, wherein the second digitally signed benchmark message is digitally signed by the oracle and comprises: i. second current benchmark information; and ii. a second timestamp; (2) comparing, by the first module, the first digitally signed benchmark message to the second digitally signed benchmark message to determine: i. a first difference between the first current benchmark information and the second current benchmark information; and ii. a second difference between the first timestamp and the second time stamp; (3) in the case where the first difference is above a first predetermined threshold and the second difference is below a second predetermined threshold, performing the steps of: (A) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate, based on the dispute instructions, the first amount of collateral; (ii) recalculate, based on the dispute instructions, the second amount of collateral; (iii) recalculate, based on the dispute instructions, the third amount of collateral; (iv) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (v) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (vi) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (vii) distribute the first excess collateral for the first trade in accordance with the first module and the first trade instructions to the first user public address; (viii) distribute the second excess collateral for the first trade in accordance with the first module and the first trade instructions to the second user public address; and (ix) distribute the third excess collateral for the first trade in accordance with the first module and the first trades instructions to the oracle public address; (1) in the case where the first difference is above the first predetermined threshold and the second difference is above the second predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network; and (2) in the case where the first difference is below the first predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network. In embodiments, the first dispute message is received by the first module address from the first user public address. In embodiments, the first excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from the second user public address. In embodiments, the second excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from at least one of the following: (1) the first user public address; (2) the second user public address; and (3) the administrator public address. In embodiments, the first excess collateral comprises a first half of the third amount of collateral, wherein the second excess collateral comprises a second half of the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is verified by the administrator system. In embodiments, the first dispute message is verified by the first module.
In embodiments, receiving the first digitally signed benchmark message further comprises: (a) sending, from the first module address to the oracle public address, a digitally signed first transaction request; (b) receiving, from the oracle public address by the first module address, the first digitally signed benchmark message; and (c) storing, by the first module, the first digitally signed benchmark message.
In embodiments, the at least one collateral requirement comprises: (1) a user collateral requirement; and (2) an oracle collateral requirement.
In embodiments, the first contract information further comprises the following contract parameter: (H) a trusted oracle selection.
In embodiments, the first time stamp indicates the time at which the first current benchmark data was retrieved by the oracle.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated first collateral amount and the first collateral amount; and (m) receiving, at the first module address, the first additional collateral amount.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; (m) monitoring, by the administrator system, the first module address on the peer-to-peer network associated with the underlying digital asset; (n) determining, by the administrator system, the first additional collateral amount has not been received by the first contract address; (o) generating, by the administrator system, a default notification indicating that the first additional collateral amount was not received by the second contract address; (p) sending, by the administrator system, the default notification to the first user device, the second user device, and the first module address; (q) generating, by the administrator system, a third message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first contract instructions; and (r) sending, by the administrator system from the administrator public address to the first module address, the third message, wherein, upon receipt of the third message, the first module implements the first trade instructions via the peer-to-peer network by computer systems among the plurality of distributed computer systems in the peer-to-peer network.
In embodiments, the first trade instructions are implemented as a result of a second message sent by the administrator system from the administrator public address to the first module address via the peer-to-peer network.
In embodiments, the first user information further comprises the first user public address, wherein the first user public address corresponds to a first user private key that is mathematically related to the first user public address, wherein the second user information further comprises the second user public address, and wherein the second user public address corresponds to a second user private key that is mathematically related to the second user public address. In embodiments, the step of receiving the first amount of collateral further comprises sending, by the first user device via the underlying peer-to-peer network from the first user public address, a digitally signed first transaction request including a request to transfer the first amount of collateral from the first user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the first user private key. In embodiments, the step of receiving the second amount of collateral further comprises sending, by the second user device via the underlying peer-to-peer network from the second user public address, a digitally signed first transaction request including a request to transfer the second amount of collateral from the second user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the second user private key.
In embodiments, the step of receiving the third amount of collateral further comprises sending, by an electronic device associated with the oracle via the underlying peer-to-peer network from the oracle public address, a digitally signed first transaction request including a request to transfer the third amount of collateral from the oracle public address to the first module address, wherein the oracle public address corresponds to an oracle private key that is mathematically related to the oracle public address, and wherein the digitally signed first transaction request is digitally signed by the oracle private key.
In embodiments, the excess collateral is calculated by at least one of the following: (i) the administrator system; (ii) the first module; (iii) the second smart contract; (iv) the first user device; and (v) the second user device.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the second collateral amount based on the at least one collateral requirement and current benchmark information; (l) determining, by the first module, a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (m) receiving, at the first module address, the second additional collateral amount. In embodiments, the second collateral amount is recalculated by the first user device. In embodiments, the administrator system sends the second message in response to receiving a request from the first user device. In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) monitoring, by the administrator system, the second contract address on the peer-to-peer network associated with the underlying digital asset; (l) determining, by the administrator system, the second additional collateral amount is not received by the first module address; (m) generating, by the administrator system, a notification indicating that the second additional collateral amount is not received by the first module address; (n) sending, by the administrator system, the notification to the first user device, the second user device and the first module address; (o) generating, by the administrator system, a third message including a request to transfer the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions; and (p) sending, by the administrator system, the third message to the first module address from the administrator public address via the peer-to-peer network, wherein, upon receipt of the third message, the first module address transfers the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions.
In embodiments, the first contract information further comprises at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, prior to step (a), the method further comprising: (k) generating, by the administrator system, machine readable instructions comprising graphical user interface information including a graphical user interface with at least one prompt for the first user to provide the contract proposal; (l) sending, by the administrator system to the first user device, the machine readable instructions such that, upon receipt of the machine readable instructions, the first user device displays the graphical user interface; and (m) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the fiat-backed digital assets are pegged to a predetermined ratio associated with one or more types of fiat.
In embodiments, the fiat-backed digital assets are backed by a reserve of fiat maintained on behalf of an issuer of the fiat-backed digital assets.
In embodiments, a method comprises (a) receiving, from a first user device associated with a first user by an administrator system associated with an administrator of a digital asset database, a first contract proposal, wherein the first contract proposal includes: (i) first user information associated with the first user; and (ii) first contract information comprising at least the following contract parameters: (A) an inception date; (B) an inception value; (C) at least one benchmark; (D) a contract duration; (E) at least one collateral requirement; (F) a notional value of the smart contract; and (G) first side information comprising identification of a first leg of the first contract proposal, wherein the digital asset database is tied to a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network; and wherein the administrator system is associated with an administrator public address associated with the peer-to-peer network; (b) receiving, by the administrator system from a second user device associated with a second user, at least one indication of interest, wherein the at least one indication of interest includes at least: (i) a first user response comprising: (1) second user information associated with the second user; and (2) second side information comprising a second leg of the contract proposal; (c) matching, by the administrator system, the first contract information and the second side information; (d) generating a first module on the peer-to-peer network associated with a fiat-backed digital asset, wherein the module comprises first contract instructions associated with a first module address associated with the peer-to-peer network, wherein the smart contract instructions are saved in the peer-to-peer network and include: (i) first authorization instructions regarding transferring fiat-backed digital assets; (ii) second authorization instructions regarding functions associated with the fiat-backed digital asset; (iii) first trade instructions including execution instructions to execute a first trade between the first user and the second user, wherein the first trade is based on at least the following: 1. the first contract proposal; and 2. the first user response (iv) third authorization instructions regarding transferring security tokens; (v) fourth authorization instructions regarding destroying security tokens; (vi) fifth authorization instructions regarding transferring fiat-backed digital assets from the first smart contract address; (vii) calculating instructions regarding calculating excess collateral; and (viii) dispute instructions regarding disputed benchmark information received by the first smart contract address from an oracle; (e) sending, by the administrator system from the administrator public address to the module address via the peer-to-peer network, the first module and associated first contract instructions; (f) receiving, by the first module address, a first amount of collateral, wherein the first amount of collateral is a first amount of fiat-backed digital assets associated with the first user as collateral, and wherein the first amount of fiat-backed digital assets associated with the first user is based on the at least one collateral requirement; (g) receiving, by the first module address, a second amount of collateral, wherein the second amount of collateral is a second amount of fiat-backed digital assets associated with the second user as collateral, wherein the second amount of fiat-backed digital assets associated with the second user is based on the at least one collateral requirement; (h) receiving, by the first module address from an oracle public address associated with the oracle, a third amount of collateral, wherein the third amount of collateral is a third amount of fiat-backed digital assets associated with the oracle as collateral, wherein the third amount of fiat-backed digital assets associated with the oracle is based on the at least one collateral requirement, wherein the oracle public address is associated with the peer-to-peer network; (i) implementing, by the first module, the first trade instructions via the peer-to-peer network by the plurality of geographically distributed computer systems in the peer-to-peer network, wherein implementing comprises the following steps: (i) receiving, by the first module address from the oracle, a first benchmark message including: (1) first current benchmark information associated with the first contract information; (2) a digital signature associated with the oracle; and (3) a first timestamp; (ii) monitoring, by the administrator system, the first module address for a predetermined amount of time; and (iii) after the predetermined amount of time has elapsed, collecting, by the administrator system from the module address, excess collateral from the first trade, wherein the collecting includes steps of: (1) sending, by the administrator system via the peer-to-peer network, a first message comprising requests for the first smart contract to: (A) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (B) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (C) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (D) distribute the first excess collateral to a first user public address associated with the first user and associated with the peer-to-peer network; (E) distribute the second excess collateral to a second user public address associated with the second user associated with the peer-to-peer network; and (F) distribute the third excess collateral to the oracle public address.
In embodiments, monitoring the first module address for the predetermined amount of time further comprises: (1) receiving, by the first module address, a first dispute message disputing the first current benchmark information, wherein the first dispute message comprises: (A) the first digitally signed benchmark message; and (B) a second digitally signed benchmark message, wherein the second digitally signed benchmark message is digitally signed by the oracle and comprises: i. second current benchmark information; and ii. a second timestamp; (2) comparing, by the first module, the first digitally signed benchmark message to the second digitally signed benchmark message to determine: i. a first difference between the first current benchmark information and the second current benchmark information; and ii. a second difference between the first timestamp and the second time stamp; (3) in the case where the first difference is above a first predetermined threshold and the second difference is below a second predetermined threshold, performing the steps of: (A) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate, based on the dispute instructions, the first amount of collateral; (ii) recalculate, based on the dispute instructions, the second amount of collateral; (iii) recalculate, based on the dispute instructions, the third amount of collateral; (iv) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (v) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (vi) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (vii) distribute the first excess collateral for the first trade in accordance with the first module and the first trade instructions to the first user public address; (viii) distribute the second excess collateral for the first trade in accordance with the first module and the first trade instructions to the second user public address; and (ix) distribute the third excess collateral for the first trade in accordance with the first module and the first trades instructions to the oracle public address; (1) in the case where the first difference is above the first predetermined threshold and the second difference is above the second predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network; and (2) in the case where the first difference is below the first predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network. In embodiments, the first dispute message is received by the first module address from the first user public address. In embodiments, the first excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from the second user public address. In embodiments, the second excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from at least one of the following: (1) the first user public address; (2) the second user public address; and (3) the administrator public address. In embodiments, the first excess collateral comprises a first half of the third amount of collateral, wherein the second excess collateral comprises a second half of the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is verified by the administrator system. In embodiments, the first dispute message is verified by the first module.
In embodiments, receiving the first digitally signed benchmark message further comprises: (a) sending, from the first module address to the oracle public address, a digitally signed first transaction request; (b) receiving, from the oracle public address by the first module address, the first digitally signed benchmark message; and (c) storing, by the first module, the first digitally signed benchmark message.
In embodiments, the at least one collateral requirement comprises: (1) a user collateral requirement; and (2) an oracle collateral requirement.
In embodiments, the first contract information further comprises the following contract parameter: (H) a trusted oracle selection.
In embodiments, the first time stamp indicates the time at which the first current benchmark data was retrieved by the oracle.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated first collateral amount and the first collateral amount; and (m) receiving, at the first module address, the first additional collateral amount.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; (m) monitoring, by the administrator system, the first module address on the peer-to-peer network associated with the underlying digital asset; (n) determining, by the administrator system, the first additional collateral amount has not been received by the first contract address; (o) generating, by the administrator system, a default notification indicating that the first additional collateral amount was not received by the second contract address; (p) sending, by the administrator system, the default notification to the first user device, the second user device, and the first module address; (q) generating, by the administrator system, a third message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first contract instructions; and (r) sending, by the administrator system from the administrator public address to the first module address, the third message, wherein, upon receipt of the third message, the first module implements the first trade instructions via the peer-to-peer network by computer systems among the plurality of distributed computer systems in the peer-to-peer network.
In embodiments, the first trade instructions are implemented as a result of a second message sent by the administrator system from the administrator public address to the first module address via the peer-to-peer network.
In embodiments, the first user information further comprises the first user public address, wherein the first user public address corresponds to a first user private key that is mathematically related to the first user public address, wherein the second user information further comprises the second user public address, and wherein the second user public address corresponds to a second user private key that is mathematically related to the second user public address. In embodiments, the step of receiving the first amount of collateral further comprises sending, by the first user device via the underlying peer-to-peer network from the first user public address, a digitally signed first transaction request including a request to transfer the first amount of collateral from the first user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the first user private key. In embodiments, the step of receiving the second amount of collateral further comprises sending, by the second user device via the underlying peer-to-peer network from the second user public address, a digitally signed first transaction request including a request to transfer the second amount of collateral from the second user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the second user private key.
In embodiments, the step of receiving the third amount of collateral further comprises sending, by an electronic device associated with the oracle via the underlying peer-to-peer network from the oracle public address, a digitally signed first transaction request including a request to transfer the third amount of collateral from the oracle public address to the first module address, wherein the oracle public address corresponds to an oracle private key that is mathematically related to the oracle public address, and wherein the digitally signed first transaction request is digitally signed by the oracle private key.
In embodiments, the excess collateral is calculated by at least one of the following: (i) the administrator system; (ii) the first module; (iii) the second smart contract; (iv) the first user device; and (v) the second user device.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the second collateral amount based on the at least one collateral requirement and current benchmark information; (l) determining, by the first module, a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (m) receiving, at the first module address, the second additional collateral amount. In embodiments, the second collateral amount is recalculated by the first user device. In embodiments, the administrator system sends the second message in response to receiving a request from the first user device. In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) monitoring, by the administrator system, the second contract address on the peer-to-peer network associated with the underlying digital asset; (l) determining, by the administrator system, the second additional collateral amount is not received by the first module address; (m) generating, by the administrator system, a notification indicating that the second additional collateral amount is not received by the first module address; (n) sending, by the administrator system, the notification to the first user device, the second user device and the first module address; (o) generating, by the administrator system, a third message including a request to transfer the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions; and (p) sending, by the administrator system, the third message to the first module address from the administrator public address via the peer-to-peer network, wherein, upon receipt of the third message, the first module address transfers the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions.
In embodiments, the first contract information further comprises at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, prior to step (a), the method further comprising: (k) generating, by the administrator system, machine readable instructions comprising graphical user interface information including a graphical user interface with at least one prompt for the first user to provide the contract proposal; (l) sending, by the administrator system to the first user device, the machine readable instructions such that, upon receipt of the machine readable instructions, the first user device displays the graphical user interface; and (m) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the fiat-backed digital assets are pegged to a predetermined ratio associated with one or more types of fiat.
In embodiments, the fiat-backed digital assets are backed by a reserve of fiat maintained on behalf of an issuer of the fiat-backed digital assets.
Exemplary embodiments of the present invention will be described with references to the accompanying figures, wherein:
A digital math-based asset is a kind of digital asset based upon a computer generated mathematical and/or cryptographic protocol that may, among other things, be exchanged for value and/or be used to buy and sell goods or pay for services. A digital math-based asset may be a non-tangible asset that is not based upon a governmental rule, law, regulation, and/or backing. The Bitcoin system represents one form of digital math-based asset. The Ethereum system represents another form of digital math-based asset, which allows for smart contracts, as discussed below.
A bitcoin may be a unit of the Bitcoin digital math-based asset. An ether may be a unit of the Ethereum digital math-based asset. Other examples of digital math-based assets include Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin, to name a few. In embodiments, digital math-based assets, such as bitcoin, may be accepted in trade by merchants, other businesses, and/or individuals in many parts of the world.
Digital assets may also include “tokens,” which like other digital assets can represent anything from loyalty points to vouchers and IOUs to actual objects in the physical world. Tokens can also be tools, such as in-game items, for interacting with other smart contracts. A token is a “smart contract” running on top of a blockchain network (such as the Ethereum Blockchain, the Bitcoin Blockchain, to name a few). As such, it is a set of code with an associated database. In embodiments, the database may be maintained by an issuer. The code describes the behavior of the token, and the database is basically a table with rows and columns tracking who owns how many tokens.
In embodiments, a smart contract may be a computer protocol intended to digitally facilitate, verify, or enforce the negotiation or performance of credible transactions without third parties. In embodiments, smart contracts may also allow for the creation of tokens.
In embodiments, a digital math-based asset may be based on an open source mathematical and/or cryptographic protocol, which may exist on a digital asset network, such as a Bitcoin network or an Ethereum network. The network may be centralized, (e.g., run by one or more central servers) or decentralized (e.g., run through a peer-to-peer network). Digital math-based assets may be maintained, tracked, and/or administered by the network.
A digital math-based asset system may use a decentralized electronic ledger system, which may be maintained by a plurality of physically remote computer systems. Such a ledger may be a public transaction ledger, which may track asset ownership and/or transactions in a digital math-based asset system. The ledger may be a decentralized public transaction ledger, which can be distributed to users in the network (e.g., via a peer-to-peer sharing). Ledger updates may be broadcast to the users across the network. Each user may maintain an electronic copy of all or part of the ledger, as described herein. In embodiments, a digital asset system may employ a ledger that tracks transactions (e.g., transfers of assets from one address to another) without identifying the assets themselves.
In embodiments, a digital asset ledger, such as the Bitcoin blockchain or the Ethereum blockchain, can be used to achieve consensus and to solve double-spending problems where users attempt to spend the same digital assets in more than one transaction. In embodiments, before a transaction may be cleared, the transaction participants may need to wait for some period of time, e.g., a six-confirmation wait (typically one hour in the context of the Bitcoin network, 15 minutes in the context of the Litecoin network, to name a few), before feeling confident that the transaction is valid (e.g., not a double count). Each update to the decentralized electronic ledger (e.g., each addition of a block to the Bitcoin blockchain or the Ethereum blockchain) following execution of a transaction may provide a transaction confirmation. After a plurality of updates to the ledger (e.g., 6 updates), the transaction may be confirmed with certainty or high certainty.
In embodiments, a blockchain can be a public transaction ledger of the digital math-based asset that is maintained by a distributed network, such as the Bitcoin network or the Ethereum network. For example, one or more computer systems (e.g., miners) or pools of computer systems (e.g., mining pools) can solve algorithmic equations allowing them to add records of recent transactions (e.g., blocks), to a chain of transactions. In embodiments, such algorithmic equations may be using a cryptographic protocol like RSA, PKI, to name a few. In embodiments, miners or pools of miners may perform such services in exchange for some consideration such as an upfront fee (e.g., a set amount of digital math-based assets) and/or a payment of transaction fees (e.g., a fixed amount or set percentage of the transaction) from users whose transactions are recorded in the block being added. In embodiments, digital assets in the form of a digital asset token, such as Gas, may be used to pay such fees.
The digital asset network (e.g., Bitcoin network or Ethereum network) may timestamp transactions by including them in blocks that form an ongoing chain called a blockchain. In embodiments, the addition of a block may occur periodically, e.g., approximately every 15 seconds, every 2.5 minutes or every 10 minutes, to name a few. Such blocks cannot be changed without redoing the work that was required to create each block since the modified block. The longest blockchain may serve not only as proof of the sequence of events but also records that this sequence of events was verified by a majority of the digital asset network's computing power. The blockchain recognized by the nodes corresponding to the majority of computing power, or some other consensus mechanism will become the accepted blockchain for the network. In embodiments, confirmation of a transaction may be attained with a high degree of accuracy following the addition of a fixed number of blocks to the blockchain (e.g., six blocks) after a transaction was performed and first recorded on the blockchain. As long as a majority of computing power (or some other consensus mechanism) is controlled by nodes that are not cooperating to attack the network, they will generate the longest blockchain of records and outpace attackers.
There are a variety of consensus mechanisms (or protocols) that may be used to verify transactions recorded in a blockchain. A few non-limiting examples of these mechanisms are discussed below, however, other protocols may be used in accordance with exemplary embodiments of the present invention.
For example, the proof of control protocol is one example of a consensus mechanism and is used, for example, in the Bitcoin blockchain. A more detailed discussion of proof of control protocols can be found in co-pending U.S. patent application Ser. No. 15/920,042, filed Mar. 13, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, the entire content of which is hereby incorporated herein by reference.
The proof of stake protocol is another optional protocol that may be implemented by blockchains. In this type of protocol, the validator's stake is represented by the amount of digital assets held. Validators accept, reject or otherwise validate a block to be added to the blockchain based on the amount of digital assets held by the Validator on the blockchain. If the Validators are successful in validating and adding the block, such a protocol, in embodiments, will award successful Validators are a fee in proportion to their stake.
The delegated proof of stake protocol is another protocol that is available and is, for example, used by the EOS blockchain. In this protocol, blocks are produced in a fixed number in rounds (e.g., 21 for EOS). At the start of every such round, block producers are chosen. A number less than all of the producers (e.g., 20 in EOS) are automatically chosen while a corresponding number are chosen proportional to the number of their votes relative to other producers. In embodiments, the remaining producers may be shuffled using a pseudorandom number derived from the block time, for example. In embodiments, other forms of randomized selection may be used. To ensure that regular block production is maintained, in embodiments, block time is kept short (e.g., 3 seconds for EOS) and producers may be punished for not participating by being removed from consideration. In embodiments, a producer has to produce a minimal number of block, e.g., at least one block every 24 hours to be in consideration. All of the nodes will, by default, not switch to a fork which does not include any blocks not finalized by a sufficient majority (e.g., 15 of the 21 producers) regardless of chain length. Thus, in EOS, each block must gain 15 of 21 votes for approval to be considered a part of the chain.
In embodiments, a delegated byzantine fault tolerance protocol may be used as a consensus mechanism. For example, NEO uses this type of protocol. In this protocol, one of the bookkeeping nodes is randomly chosen as a “speaker.” The speaker then looks at all the demands of the “citizens,” (e.g., all of the holders of the digital asset), and creates a “law” (e.g., a rule governing the protocol). The speaker then calculates a “happiness factor” of these laws to see if the number is enough to satisfy the citizen's needs or not. The speaker then passes the happiness factor down to the delegates (e.g., the other bookkeeping nodes). The delegates may then individually check the speaker's calculations. If the speaker's number matches the delegate's number, then the delegates give their approval, and if not, then they give their disapproval. In embodiments, a sufficient majority (e.g., 66% in NEO) of the delegates need to give their approval for the law to pass, i.e. for the block to be added. If a sufficient majority is not obtained (e.g., less than 66% approval), then a new speaker is chosen and the process starts again.
Ripple uses an algorithm in which each server gathers all valid transactions that have not yet been applied and makes them public. Each server then amalgamates these transactions and votes on the veracity of each. Transactions that receive at least a minimum number of yes votes will move into another round of voting. A minimum of 80% approval is required before a transaction is applied.
These and other protocols may be used to generate a blockchain in accordance with exemplary embodiments of the present invention.
In embodiments, transaction messages can be broadcast on a best effort basis, and nodes can leave and rejoin the network at will. Upon reconnection, a node can download and verify new blocks from other nodes to complete its local copy of the blockchain.
In the exemplary Bitcoin system, a bitcoin is defined by a chain of digitally-signed transactions that began with its creation as a block reward through bitcoin mining. Each owner transfers bitcoin to the next by digitally signing them over to the next owner in a bitcoin transaction, which is published to and added onto a block on the blockchain. A payee can then verify each previous transaction, e.g., by analyzing the blockchain, to verify the chain of ownership.
Other examples of different types of blockchains noted above that are consistent with embodiments of present invention pose unique problems. Certain currencies present unique challenges in that transactions and/or wallets or digital asset addresses associated therewith may be shielded (e.g., not viewable by the public on the ledger). For example, Monero is based on the CryptoNight proof-of-work hash algorithm and possesses significant algorithmic differences relating to blockchain obfuscation. Monero provides a high level of privacy and is fungible such that every unit of the currency can be substituted by another unit. Monero is therefore different from public-ledger cryptocurrencies such as Bitcoin, where addresses with coins previously associated with undesired activity can be blacklisted and have their coins refused by others.
In embodiments, “proof of brain” may be a type of token reward algorithm used in social media blockchain systems that encourages people to create and curate content. In embodiments, proof of brain may enable token distribution by upvote and like-based algorithms, which may be integrated with websites to align incentives between application owners and community members to spur growth.
In particular, in Monero, ring signatures mix spender's address with a group of others, making it more difficult to establish a link between each subsequent transaction. In addition, Monero provides “stealth addresses” generated for each transaction which make it difficult, if not impossible to discover the actual destination address of a transaction by anyone else other than the sender and the receiver. Further, the “ring confidential transactions” protocol may hide the transferred amount as well. Monero is designed to be resistant to application-specific integrated circuit mining, which is commonly used to mine other cryptocurrencies such as Bitcoin, however, it can be mined somewhat efficiently on consumer grade hardware such as x86, x86-64, ARM and GPUs, to name a few.
Another example of a modified blockchain consistent with exemplary embodiments of the present invention discussed above is Darkcoin. Darkcoin adds an extra layer of privacy by automatically combining any transaction its users make with those of two other users—a feature it calls Darksend—so that it will be more difficult to analyze the blockchain to determine where a particular user's money ended up.
Yet another example of a modified blockchain consistent with embodiments of the present invention discussed above is Zcash. The Zcash network supports different types of transactions including: “transparent” transactions and “shielded” transactions. Transparent transactions use a transparent address (e.g., “t-address”). In embodiments, transactions between two t-addresses behave like Bitcoin transactions and the balance and amounts transferred are publicly visible on the Zcash blockchain. Unlike the Bitcoin Blockchain, the Zcash network may also support shielded transactions using a shield address (e.g., “z-address”). In embodiments, the “z-address” provides privacy via zero-knowledge succinct noninteractive arguments of knowledge (e.g., “zk-SNARKS” or “zero-knowledge proofs”). The balance of a z-address is not publicly visible on the Zcash blockchain—the amount transferred into and out of a z-address is private if between two z-addresses—but may be public if between a z-address and a t-address.
In embodiments, a digital asset based on a blockchain, may, in turn, include special programming, often referred to as “smart contracts”, which allow for the creation of “tokens”, which in turn are digital assets based on digital assets. In embodiments, tokens may be ERC-20 tokens, and used in conjunction with ERC-20 token standard as a programming language. In embodiments, other protocols may be used including but not limited to ERC-223 and ERC-721, to name a few. In embodiments, smart contracts may be written on other smart contracts to provide for increased functionality. One non-limiting example of this type of structure is the open source Cryptokittens game in which digital kittens are provided as ERC-721 tokens with a series of smart contracts provided to define how the kittens will interact with each other and with users. In embodiments, programming modules may be added to and/or transferred with programming modules associated with specific tokens. By way of illustration, a first token, e.g., a Cryptokitten Tiger, may purchase a second token, e.g., a digital “hat,” that will then become associated with the first token to be a Tiger with a hat, and remain with the first token when transferred. Thus, by way of illustration, in the context of example embodiments of the present invention, the first token could be, e.g., a security token, and the second token could be, e.g., an account holding tokens, or a right to request tokens from another account as discussed below. If the first token is transferred, the second token would transfer with the ownership of the first token.
For example, digital assets can include tokens, which like other digital assets that can represent anything from loyalty points to vouchers and IOUs to actual objects in the physical world. Tokens can also be tools, such as in-game items, for interacting with other smart contracts. A token is a smart contract running on top of a blockchain network (such as the Ethereum Blockchain, the Bitcoin Blockchain, to name a few). As such, it is a set of code with an associated database. In embodiments, the database may be maintained by an issuer. In embodiments, the database may be included as part of the blockchain. In embodiments, the ledger may be maintained in the first instance as a database in a sidechain by the issuer or agent of the issuer and subsequently published and stored as part of a blockchain. The code describes the behavior of the token, and the database may be a table with rows and columns tracking who owns how many tokens.
If a user or another smart contract within the blockchain network (such as the Ethereum Network) sends a message to that token's contract in the form of a “transaction,” the code updates its database.
In embodiments, an underlying blockchain, like the Bitcoin Block chain, may have limited or no smart contract capabilities.
In such embodiments, an overlying protocol, such as Omni Layer (https://www.omnilayer.org/) may also be used to create custom digital assets on such an underlying blockchain, like the Bitcoin blockchain, as described in https://github.com/OmniLayer/spec. In embodiments, a smart contract may be used for transactions involving Bitcoin through the use of a two way peg with side chain. The side chain can share miners with the Bitcoin blockchain and allows smart contracts to be run, such as contracts using the Ethereum virtual machine. When Bitcoin is to be used in the smart contract side chain, the Bitcoin is locked and an equal amount of side chain currency, an example of which is Super Bitcoin (SBTC), is assigned to the corresponding address. After the smart contract transaction is completed, the side chain currency is locked and the Bitcoin is unlocked. An example of such a side chain is Rootstock.
In embodiments, where the blockchain is the Bitcoin blockchain, and another protocol is used as a layer over the Bitcoin blockchain to provide for smart contract functionality. For example, the other protocol may be a two-way peg of stable value digital asset tokens to bitcoin and a sidechain that shares miners with the Bitcoin blockchain. In embodiments, the other protocol is an omni layer protocol.
So, for instance, as illustrated in
In step S6001, at the token issuer computer system, Security Tokens are created. In embodiments, each Stable Value Token may have a “ERC-20 Contract Wallet Address” (“Contract Address”) which is an address on the blockchain at which the code for the smart contract is stored. In embodiments, the smart contract may include instructions to perform at least: (1) token creation, (2) token transfer, (3) token destruction; and (4) updating smart contract coding.
In embodiments of the present invention, the minimal specification for a Token, such as a Stable Value Token, may include instructions to perform at least: (1) a “total Supply” function, which when called, will respond with a count of the number of tokens in existence; (2) a “balanceOf” function, which when called with a specific account (address) as a parameter, responds with the count of the number of tokens owned by that account; and (3) a “transfer” function, which is an example of a state modifying function, that, when called, given one or more target accounts and corresponding transferred amounts as parameters, the transfer function will decrease the balance of the caller account by the corresponding transfer amounts, and increase the target accounts by the target amounts (or fail if the caller account has insufficient amounts or if there are other errors in the parameters).
In embodiments, a Stable Value Token may be created with a fixed supply of tokens at the time of its creation. For example, a Stable Value Token may be created with a supply of 21 million tokens and set Address 1 (mathematically associated with a private key 1) as the owner of all 21 million tokens. Thereafter, private key 1 will be required to generate a call to the transfer function in order to assign some portion of the 21 million tokens with a second Address 2 (mathematically associated with a private key 2) or any other Address (also mathematically associated with a corresponding private key).
In embodiments, a Stable Value Token may be created with a variable supply of tokens which can be set to increase or decrease after original creation. In such embodiments, the minimum functions required will also include: (4) a “print” function, which is another example of a state modifying function, that when called allows for the creation of additional Stable Value Tokens into the total Supply of Stable Value Tokens; and (5) a “burn” function, which is also another example of a state modifying function, that when called allows for the destruction of previously created Stable Value Token from the total Supply of the Stable Value Tokens. As discussed below in greater detail, in embodiments, the print and burn function may include limits on the Addresses that are allowed to call those functions.
Currently, due to the immutable nature of the Ethereum blockchain, once a smart contract is written to a specific Contract Address it cannot be changed. However, in embodiments, the various functions called for in the Contract Address may be associated with specific authorized key pairs of public keys (or “addresses”) and corresponding private keys (which are mathematically associated with public keys). In embodiments, one or more private keys may be stored off-line in, what is sometimes referred to as, a designated cold storage wallet associated with the token issuer. In such embodiments, keys may be generated, stored, and managed onboard hardware security modules (HSMs). For example, HSMs, e.g., each a “signer,” should have achieved a rating of FIPS PUB 140-2 Level 3 (or higher). In embodiments, one or more private keys may be stored on-line in, what is sometimes referred to as a designated hot storage wallet associated with the token issuer. In embodiments, the Contract Address may include instructions which are associated with authorizing one or more designated key pairs stored off-line in, e g., one or more cold storage wallets on one or more air-gapped computer systems associated with the token issuer, but may also give at least some permission to perform operations by one or more designated key pairs stored on-line, in, e.g., one or more hot wallets associated with the token issuer and/or a token administrator on behalf of the token issuer on one or more computer systems connected to the digital asset computer system. In embodiments, the on-line computer systems would be co-located with the digital asset computer systems. In embodiments, the Stable Value Tokens may be created in batches (for example, 100,000 SVCoins worth $100,000 U.S. dollars) by a designated key pair (such as an off-line designated key pair) authorized by smart contract and assigned by such a key pair to a designated address associated with on on-line public key for transactions as necessary.
In embodiments, a Stable Value Token database is maintained in a blockchain, such as the Ethereum blockchain, for example. In embodiments, the ledger may be maintained, in the first instance, as a database in a sidechain by the issuer or agent and subsequently published and stored as part of a blockchain.
In embodiments, a Stable Value Token database is maintained in a blockchain, such as the Ethereum blockchain, for example. In embodiments, the ledger may be maintained in the first instance as a database in a sidechain by the issuer or agent and subsequently published and stored as part of a blockchain.
In embodiments, Stable Value Tokens may be generated on the fly, however, in this case, the contract code, which is the executable code that is stored at the Contract Address location on the blockchain, may designate one or more public addresses corresponding to one or more on-line private keys held in, e.g., a hot wallet(s), or one or more public addresses corresponding on one or more off-line public keys held in, e.g., a cold wallet(s), or some combination thereof, as the authorized caller of some functionality. A more detailed discussion of hot wallets and cold wallets is presented in U.S. Pat. No. 9,892,460 issued Feb. 13, 2018 entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR OPERATING EXCHANGE TRADED PRODUCTS HOLDING DIGITAL MATH-BASED ASSETS, the entire content of which is incorporated herein by reference. In embodiments, Contract Wallets may be maintained by the token issuer and which would hold the private key associated with the token on an associated device. In embodiments, Contract Wallets may be provided on a user computer device and hold the private key associated with the token. In such embodiments, a user computer device may include a software application to provide secure access to the token issuer such that the user can engage in transactions.
By way of illustration, an ERC-20 Contract can include the following representative type of functions as shown in Table 1 in its programming of a Smart Contract associated with a particular token, such as a security token:
Some of the tokens may include further information describing the token contract such as shown in Table 2:
In embodiments, a more elaborate smart contract can be set up to allow token issuers to have hybrid control over which key pairs have authority to affect the token supply and distribution. In embodiments, a hybrid combination of on-line and off-line key pairs can be used to control the supply and distribution of tokens.
For example, in embodiments, a smart contract may include a state-changing function such as limitedPrint, where the authorized caller of such function would be authorized only to print (or issue) a specific limited amount of tokens. In embodiments, the limitedPrint function may be used with an on-line key pair (e.g., hot wallet), to allow for fast and efficient token creation, but limit risk of unauthorized takeover of the on-line key pair to the set limit.
In conjunction with a limitedPrint command, a separate state-changing function of raiseCeiling can be used to increase the authority for the on-line key pair using a different key pair, such as an off-line key pair (e.g., cold wallet), which is considered to be more secure.
In embodiments, using a limitedPrint function with a set limit that can be implemented by one or more designated on-line key pairs (e.g., hot wallets), and a raiseCeiling function which may change that limit under the authority of a different set of one or more designated off-line key pairs (e.g., cold wallets), the automated increases in the token supply through on-line control will only continue up until the ceiling is reached, at which point further intervention through off-line control is required.
One should consider the difference between the current token supply and the supply ceiling as part of the tokens at risk. If the current token supply has decreased through the use of burn, then the effective funds at risk could have increased without a corresponding decrease in the supply ceiling. The ceiling can be lowered by on-line control, through a function called lowerCeiling. This allows for relinquishing some portion of what has been granted through off-line control to limit the effective funds at risk through compromise of on-line key management systems. In embodiments, a limit on number of tokens that can be burned may also be included.
In embodiments, as illustrated in
In the context of a ERC20 compliant token on the Ethereum blockchain, there is one, and will only ever be one instance of ERC20Proxy 6410. This is the smart contract that users of the token treat as the token contract. Thus, ERC20Proxy 6410 can be considered the permanent face of interacting with the token on the Ethereum blockchain.
However, in embodiments, ERC20Proxy 6410 may have almost no code and does not keep any state information itself. Instead, in embodiments, ERC20Proxy 6410 has one or more implementations (e.g., ERC20 Impl 6420, ERC20 Impl (1) 6440, ERC20 Impl (2), to name a few) that executes the logic of the token. S6412 impl represents a delegation from ERC20 Proxy 6410 to ERC20Impl 6420. Thus, the instance of ERC20Impl 6420 executes the specific delegated functions. ERC20Impl 6420 may further limit the authority to implement to the specific delegated functions to only specified trusted callers (e.g., as shown in
In embodiments, state information, such as token balances, may be maintained in a. separate instance, e.g., ERC20Store 6430, a “backing store.” In such embodiments, ERC20Store 6430 would own the delegated state of the token. S6422 store illustrates the delegation of state information from ERC20Impl 6420 to ERC20Store 6430. In embodiments, the instance of ERC20Store 6430 may execute updates to the state of the token, such as updates to token balances that occur during a token transfer to one or more designated key sets. S6424 impl represents the address that the ERC20Store 6430 will permit to invoke the update functions. In embodiments, that address is the “Contract Address” of the active version of ERC20Impl 6420.
This separation of duties—public face, logic, and storage, for ERC20Proxy 6410, ERC20Impl 6420, and ERC20Store 6430, respectively—provides the ability for token issuer to replace the logic of the system at a later date. In embodiments, the logic may be replaced by changing the impl arrows (e.g., S6412 impl and S6424 impl).
Turning to
In embodiments, a fourth type of contract, Custodian 6450, may also be implemented. A Custodian 6450 is logic which designates which key pair (e.g., an Off-Line Keyset 6462), is authorized to control other contracts in the system (e.g., ERC20Proxy 6410). Contracts cooperate with Custodian 6450 by awaiting an approval from Custodian 6450 before executing certain actions. In turn, such approval will require a message from an authorized key pair (e.g., Off-Line Keyset 6462) authorizing the action (e.g., print tokens, limit tokens, transfer tokens, to name a few).
In embodiments, Custodian 6450 may include a range of control coding. In embodiments, control coding may include the requirement that at least two designated keysets authorize a specific action (e.g., print token). In embodiments, at the least two keysets may be a subset of a larger group of keysets (e.g., two of three designated keysets, or two of six designated keysets, or three of five designated keysets, to name a few). In embodiments, when a higher degree of security is desired, the keysets may be maintained off-line. In embodiments, when a high degree of automation or speed to access is required, the keysets may be maintained on-line, such as in a co-located, but separate computer system that is operatively connected to a customer facing digital asset system.
In embodiments, Custodian 6450 may also exercise control over various security operations of ERC20Proxy 6410 (e.g., time locking and revocation, to name a few).
In embodiments, Custodian 6450 may have custodianship of the proxy which grants exclusive power to replace the implementation for ERC20Proxy 6410 from its current implementation (e.g., ERC20Impl 6420 (version 1)) to a new implementation (e.g., ERC20Impl 6420A (version 2)), as illustrated in
In embodiments, Custodian contracts with their own respective authorized designated keysets can be set up for other contracts, such as ERC20Store 6430 as also shown in
In embodiments, custodianship of the proxy and store also grants exclusive power to pass custodianship to a new instance of Custodian. Thus, one of the technical computer problems associated with the immutability of ERC20 smart contracts on the Ethereum blockchain has been solved, thus allowing for a self-upgrade of custodianship. In embodiments, since a set of signers for a given instance of a Custodian is fixed, a change to the off-line keyset may be implemented instead having a current Custodian authorize itself to be replaced by a new instance of Custodian with a new set of signers.
Referring now to
To swap out the current ERC20Impl 6420 (version 1) with an updated ERC20Impl 6420 (version 2), as shown in
Next, the implementation pointer from ERC20Proxy 6410 which is currently set at S6412 (impl) to point to ERC20Impl 6420 (Version 1), needs to be reset to be S6412B impl to point to ERC20Impl 6420A (version 2) instead. This change requires the authorization of Custodian 6450, which in turn requires two signatures from keys in its designated keyset (e.g., Off-Line Keyset 6462) sent to it on the blockchain.
Table 3 represents an exemplary embodiment of the steps used to implement this process:
Referring to Table 3, in step 1, a request must be made to ERC20Proxy to change its instance of ERC20Impl. This request may come from any address, and when the request is made, the function returns a unique lockId that anyone can use to look up that request.
Next, in step 2, to confirm the pending request, the Custodian contract 6450 for ERC20 Proxy 6410 calls requestUnlock and passes as arguments the lockId generated for the change request, and the function in ERC20Proxy 6410 the Custodian 6450 needs to call to confirm the change request. This generates a request, which is a unique identifier for this unlock request.
In step 3, to complete the unlocking of Custodian and therefore propagate the change to ERC20Proxy 6410, the digital asset system operated by the token issuer uses its off-line key storage infrastructure to sign the request with the previously approved designated key sets. In this example, two signatures are required (signature 1 and signature 2), but other combinations of signatures may be used consistent with embodiments of the present invention.
In step 4, those signatures are passed into the Custodian's completeUnlock function along with the initial request. Once the request is validated against the signatures, completeUnlock parses the content of the request and issues the command. In this case, it calls ERC20Proxy's confirmImplChange using the lockId generated in the initial ERC20Impl change request.
As shown in
In embodiments, a similar process may also be used to upgrade the active Custodian 6450. Instead of the pair of functions requestImplChange and confirmImplChange, the pair of functions requestCustodianChange and confirmCustodianChange are used instead.
Referring to
In the context of
Thus, to print an unbounded amount of tokens, signatures from keys in Off-Line Key Set 6462 need to be sent through the blockchain, to Custodian 6450, which, in turn, then calls through the blockchain, PrintLimiter 6460, which then, in turn, calls through the blockchain ERC20Impl 6420 to confirm the print request.
Referring to
The total supply ceiling can only be raised by Off-Line Key Set 6462. In embodiments, it can be lowered, however, by that On-Line Key Set 6464 or Off-Line Key Set 6462.
Table 4 illustrates exemplary embodiments of code used in smart contracts on the Ethereum blockchain which implement a cooperative relationship with an external account or contract that exerts custodianship over the contract following the pattern.
A contract following the pattern is capable of carrying out some action—a portion of the desired operations; however, rather than executing the action directly, the action is first requested, with a unique ‘lock identifier’ returned as the result of the request. The pending action is stored in the contract state, storing the data necessary to execute the action in the future, and with the lock identifier as the lookup key to retrieve the pending action. If the contract is called by its custodian, receiving a lock identifier as an argument, then the associated pending action, if any, is retrieved and executed.
In embodiments, as illustrated in Table 4, the contracts may include multiple inheritances, so for the purposes of code reuse, a function for generating unique lock identifiers is implemented in the contract LockRequestable.
In embodiments, the function generateLockId returns a 32-byte value to be used as a lock identifier, which is a hash of the following three components: (1) The blockhash of the Ethereum block prior to the block that included the Ethereum transaction that executed this function; (2) The deployed address of the instance of the contract that inherits from LockRequestable; and (3) The current value of the count of all invocations of generateLockId (within ‘this’ contract).
Component three plays the role of a nonce (in cryptography, a nonce is an arbitrary number that can be used just once) ensuring that a unique lock identifier is generating no matter how many invocations of generateLockId there are within a single Ethereum transaction or a single Ethereum block.
Component two ensures that the lock identifier is unique among the set of cooperating contracts that use this identifier generation scheme. A noncooperative contract authored by a third party may choose to generate identifiers that overlap, but that is expected not to impact operation.
Finally, component three uses the relative previous blockhash to make future lock identifiers unpredictable.
Table 5 illustrates embodiments of code which uses LockRequestable in a template consistent with embodiments of the present invention.
The function requestAction generates a fresh lock identifier and captures the request parameters as a pending action, storing it in a mapping associated with the lock identifier.
The function confirmAction is callable only by the designated custodian. The given lock identifier is used to retrieve the associated pending action from the contract storage, if it exists, otherwise the function reverts. The pending action is deleted from storage, which ensures that the action will be executed at most once. Finally the logic of the action is executed.
In embodiments, there are two requirements to the confirmAction callback function: (1) The function does not have a return value; and (2) The function must only revert if there is no pending action associated with the lock identifier.
In these embodiments, the custodian receives a failure signal only when it called with an invalid lock identifier. Any failure cases that may occur in the execution of the action logic must be signaled by means other than return values or reversions (including abortive statements such as throw).
Programming consistent with Tables 4 and 5 may be used to implement a wide variety of functions in the context of a token including, by way of example:
In embodiments, other limits or controls may also be built into the smart contract functionality of the token. For example, in embodiments, it may be necessary for the token issuer to adjust the token ledger to account for regulatory activity. For example, there may be a court order seizure of funds, or a security issue that may require reversing transactions during a compromised period, to name a few
In embodiments, the administrator may send instructions to modify the token supply for one or more particular accounts. For example, the smart contract may include instructions to pause a transfer. The pause function may be a permanent pause, e.g., for a compromised account, a time limited pause, e.g., for 24 hours or 2 days, or a temporary pause which requires another instruction to reactivate the account, to name a few. Such a function could be included as an upgrade feature in a new Impl contract, or built into the smart contract to be activated when an authorized account, e.g., one or more off-line keys call upon the smart contract to implement the pause functionality, with appropriate parameters.
In embodiments, the administrator may send instructions to rebalance the token supply of one or more particular accounts. For example, the smart contract may include instructions to adjust a token balance in a designated account, e.g., by raising the balance in the designated account, lowering the balance in the designated account, or transferring some or all of the tokens in one designated account to one or more other designated accounts. Such a function could be included as an upgrade feature in a new Impl contract, or built into the smart contract to be activated when an authorized account, e.g., one or more off-line keys, call upon the smart contract to implement the pause functionality, with appropriate parameters.
In embodiments, the Stable Value Token may be embodied in the form of a token on the Ethereum Blockchain, referred to as a Gemini Dollar token, as illustrated in the exemplary dashboard of
In embodiments, creation and redemption of the Gemini Dollar tokens may be made simple to promote usability and encourage adoption. In embodiments, Gemini Dollar tokens are redeemed or “destroyed” at the time of deposit into a digital asset exchange. Exchange customers may exchange Gemini Dollar tokens for U.S. dollars at a 1:1 exchange rate by depositing Gemini Dollar tokens into their exchange account. The U.S. dollar amount of Gemini Dollar tokens will be credited to the customer's exchange account balance at the time of deposit.
Referring back to
In Step S6004, when miners on the blockchain network receive the transaction request directed to the contract wallet or associated digital asset address, with the request message, miners on the blockchain network will confirm the transaction, including verifying that the message was properly signed by Alice. In Step S1004-b, the miners may verify that Alice has a sufficient amount of tokens to perform the requested transaction, for example, by comparing Alice's balance against Alice's token balance as indicated on the blockchain. In Step S1004-c, the validity of Bob's digital asset address (the Destination Address) may also be confirmed by the miners. The miners may also compare the request with smart contract coding and instructions included in the Contract Address. The transaction fee discussed above is paid to the miners for confirming the transaction as noted above.
In Step S6006, if the request is verified the transaction is published in the Security Token database of the blockchain reflecting a debit against Alice's token holdings and a corresponding credit to Bob's token holdings (less any applicable fees).
In Step S6008, response messages to the digital asset addresses of both Alice and Bob may be sent to reflect that the transaction was successfully processed. In embodiments, such messages may include information including: (i) the source digital asset address; (ii) the destination digital asset address; (iii) the amount of tokens transferred; and/or (iv) the new balances for each digital asset address or associated digital wallet. In embodiments, the message may include a proposed fee amount and/or fee proposal including a limit in e.g., Gas. In embodiments, Alice, Bob, and/or third parties may view the balances and transaction information based on the information stored in the blockchain, by, e.g., viewing token balances at websites like etherscan.io, to name a few.
In contrast to tokens, a blockchain based digital asset (such as ether) is hard coded into the blockchain (e.g., the Ethereum Blockchain) itself. It is sold and traded as a cryptocurrency, and it also powers the network (e.g., the Ethereum Network) by allowing users to pay for smart contract transaction fees. (In some networks, transactions fees may be paid for in digital assets, such as tokens (e.g., Gas) or blockchain based digital assets (e.g., bitcoin). In the Ethereum Network, all computations typically have a cost based on other digital assets, such as Gas.
In embodiments, when tokens are sent to or from a Contract Address, for example, a fee may be charged for that transaction (in this case, a request to the token's contract to update its database) in, e.g., some form of digital asset, such as ether, bitcoin, Gas, to name a few. In embodiments, the message may include a proposed fee amount and/or fee proposal including a limit in digital asset, e.g., ether, bitcoin or Gas. This payment is then collected by a miner who confirms the transaction in a block, which then gets added to the blockchain.
As can be seen in
An exemplary embodiment of a digital asset network is illustrated in
In the exemplary embodiment, user devices 105a, 105b1 . . . 105N can each run a digital asset client 110, e.g., a Bitcoin client, which can comprise digital asset source code 120 and an electronic transaction ledger 115. The source code 120 can be stored in processor readable memory, which may be accessed by and/or run on one or more processors. The electronic transaction ledger 115 can be stored on the same and/or different processor readable memory, which may be accessible by the one or more processors when running the source code 120. In embodiments, the electronic transaction leger 115a (contained on a user device 105a) should correspond with the electronic transaction ledgers 115b . . . 115N (contained on user devices 105b . . . 105N), to the extent that the corresponding user device has accessed the Internet and been updated (e.g., downloaded the latest transactions). Accordingly, the electronic transaction ledger may be a public ledger. Exemplary embodiments of digital asset clients 110 for the Bitcoin network (Bitcoin clients) include Bitcoin-Qt and Bitcoin Wallet, to name a few. In embodiments, some of the transactions on the public ledger may be encrypted or otherwise shielded so that only authorized users may access ledger information about such transactions or wallets.
In addition, a digital asset network, such as a Bitcoin network, may include one or more digital asset exchange 130, such as Bitcoin exchanges (e.g., BitFinex, BTC-e). Digital asset exchanges may enable or otherwise facilitate the transfer of digital assets, such as bitcoin, and/or conversions involving digital assets, such as between different digital assets and/or between a digital asset and non-digital assets, currencies, to name a few. The digital asset network may also include one or more digital asset exchange agents 135, e.g., a Bitcoin exchange agent. Exchange agents 135 may facilitate and/or accelerate the services provided by the exchanges. Exchanges 130, transmitters 132, and/or exchange agents 135 may interface with financial institutions (e.g., banks) and/or digital asset users. Transmitters 132 can include, e.g., money service businesses, which could be licensed in appropriate geographic locations to handle financial transactions. In embodiments, transmitters 132 may be part of and/or associated with a digital asset exchange 130. Like the user devices 105, digital asset exchanges 130, transmitters 132, and exchange agents 135 may be connected to the data network 125 through wired, wireless, or other connections. They may be connected directly and/or indirectly to each other and/or to one or more user device 105 or other entity participating in the digital asset system.
Digital assets may be sub-divided into smaller units or bundled into blocks or baskets. For example, for bitcoin, subunits, such as a Satoshi, as discussed herein, or larger units, such as blocks of bitcoin, may be used in exemplary embodiments. Each digital asset, e.g., bitcoin, may be subdivided, such as down to eight decimal places, forming 100 million smaller units. For at least bitcoin, such a smaller unit may be called a Satoshi. Other forms of division can be made consistent with embodiments of the present invention.
In embodiments, the creation and transfer of digital math-based assets can be based on an open source mathematical and/or cryptographic protocol, which may not be managed by any central authority. Digital assets can be transferred between one or more users or between digital asset accounts and/or storage devices (e.g., digital wallets) associated with a single user, through a network, such as the Internet, via a computer, smartphone, or other electronic device without an intermediate financial institution. In embodiments, a single digital asset transaction can include amounts from multiple origin accounts transferred to multiple destination accounts. Accordingly, a transaction may comprise one or more input amounts from one or more origin digital asset accounts and one or more output amounts to one or more destination accounts. Origin and destination may be merely labels for identifying the role a digital asset account plays in a given transaction; origin and destination accounts may be the same type of digital asset account.
In embodiments, a digital math-based asset system may produce digital asset transaction change. Transaction change refers to leftover digital asset amounts from transactions in digital asset systems, such as Bitcoin, where the transactions are comprised of one or more digital inputs and outputs. A digital asset account can store and/or track unspent transaction outputs, which it can use as digital inputs for future transactions. In embodiments, a wallet, third-party system, and/or digital asset network may store an electronic log of digital outputs to track the outputs associated with the assets contained in each account. In digital asset systems such as Bitcoin, digital inputs and outputs cannot be subdivided. For example, if a first digital asset account is initially empty and receives a transaction output of 20 BTC (a bitcoin unit) from a second digital asset account, the first account then stores that 20 BTC output for future use as a transaction input. To send 15 BTC, the first account must use the entire 20 BTC as an input, 15 BTC of which will be a spent output that is sent to the desired destination and 5 BTC of which will be an unspent output, which is transaction change that returns to the first account. An account with digital assets stored as multiple digital outputs can select any combination of those outputs for use as digital inputs in a spending transaction. In embodiments, a digital wallet may programmatically select outputs to use as inputs for a given transaction to minimize transaction change, such as by combining outputs that produce an amount closest to the required transaction amount and at least equal to the transaction amount.
In embodiments, the present invention can be used to be compatable with the Libra Network and the Move Programming language as described in the following disclosures, each of which is hereby incorporated by reference herein: (1) Move: A Language With Programmable Resources (available at: https://developers.libra.org/docs/move-paper); (2) The Libra White Paper (available at: https://libra.org/en-US/white-paper/); (3) The Libra Reserve (available at: https://libra.org/en-US/about-currency-reserve/); (4) The Libra Association (available at: https://libra.org/en-US/association-council-principles/); (5) State Machine Replication in the Libra Blockchain (available at: https://developers.libra.org/docs/state-machine-replication-paper); (6) Moving Toward Permissionless Consensus (available at: https://libra.org/en-US/permissionless-blockchain/); and (7) The Libra Blockchain (available at: https://developers.libra.org/docs/the-libra-blockchain-paper).
Referring again to
In embodiments, the processing of digital asset transactions, e.g., bitcoin transactions, can be performed by one or more computers over a distributed network, such as digital asset miners 145, e.g., bitcoin miners, and/or digital asset mining pools 150, e.g., bitcoin mining pools. In embodiments, mining pools 150 may comprise one or more miners 145, which miners 145 may work together toward a common goal. Miners 145 may have source code 120′, which may govern the activities of the miners 145. In embodiments, source code 120′ may be the same source code as found on user devices 105. These computers and/or servers can communicate over a network, such as an internet-based network, and can confirm transactions by adding them to a ledger 115, which can be updated and archived periodically using peer-to-peer file sharing technology. For example, a new ledger block could be distributed on a periodic basis, such as approximately every 10 minutes. In embodiments, the ledger may be a blockchain. Each successive block may record transactions that have occurred on the digital asset network. In embodiments, all digital asset transactions may be recorded as individual blocks in the blockchain. Each block may contain the details of some or all of the most recent transactions that are not memorialized in prior blocks. Blocks may also contain a record of the award of digital assets, e.g., bitcoin, to the miner 145 or mining pool 150 who added the new block, e.g., by solving calculations first.
A miner 145 may have a calculator 155, which may solve equations and/or add blocks to the blockchain. The calculator 155 may be one or more computing devices, software, or special-purpose device, to name a few. In embodiments, in order to add blocks to the blockchain, a miner 145 may be required to map an input data set (e.g., the blockchain, plus a block of the most recent transactions on the digital asset network, e.g., transactions on the Bitcoin network, and an arbitrary number, such as a nonce) to a desired output data set of predetermined length, such as a hash value. In embodiments, mapping may be required to use one or more particular cryptographic algorithms, such as the SHA-256 cryptographic hash algorithm or scrypt, to name a few. In embodiments, to solve or calculate a block, a miner 145 may be required to repeat this computation with a different nonce until the miner 145 generates a SHA-256 hash of a block's header that has a value less than or equal to a current target set by the digital asset network. In embodiments, each unique block may only be solved and added to the blockchain by one miner 145. In such an embodiment, all individual miners 145 and mining pools 150 on the digital asset network may be engaged in a competitive process and may seek to increase their computing power to improve their likelihood of solving for new blocks. In embodiments, successful digital asset miners 145 or mining pools 150 may receive an incentive, such as, e.g., a fixed number of digital assets (e.g., bitcoin) and/or a transaction fee for performing the calculation first and correctly and/or in a verifiable manner.
In embodiments, the cryptographic hash function that a miner 145 uses may be one-way only and thus may be, in effect, irreversible. In embodiments, hash values may be easy to generate from input data, such as valid recent network transaction(s), blockchain, and/or nonce, but neither a miner 145 nor other participant may be able to determine the original input data solely from the hash value. Other digital asset networks may use different proof of work algorithms, such as a sequential hard memory function, like scrypt, which may be used for Litecoin. As a result, generating a new valid block with a header less than the target prescribed by the digital asset network may be initially difficult for a miner 145, yet other miners 145 can easily confirm a proposed block by running the hash function at least once with a proposed nonce and other identified input data. In embodiments, a miner's proposed block may be added to the blockchain once a defined percentage or number of nodes (e.g., a majority of the nodes) on the digital asset network confirms the miner's work. A miner 145 may have a verifier 160, which may confirm other miners' work. A verifier 160 may be one or more computers, software, or specialized device, to name a few. A miner 145 that solved such a block may receive the reward of a fixed number of digital assets and/or any transaction fees paid by transferors whose transactions are recorded in the block. “Hashing” may be viewed as a mathematical lottery where miners that have devices with greater processing power (and thus the ability to make more hash calculations per second) are more likely to be successful miners 145. In embodiments, as more miners 145 join a digital asset network and as processing power increases, the digital asset network may adjust the complexity of the block-solving equation to ensure that one newly-created block is added to the blockchain approximately every ten minutes. Digital asset networks may use different processing times, e.g., approximately 2.5 minutes for Litecoin, approximately 10 minutes for Bitcoin, to name a few.
In addition to archiving transactions, a new addition to a ledger can create or reflect creation of one or more newly minted digital assets, such as bitcoin. In embodiments, new digital math-based assets may be created through a mining process, as described herein. In embodiments, the number of new digital assets created can be limited. For example, in embodiments, the number of digital assets (e.g., bitcoin) minted each year is halved every four years until a specified year, e.g., 2140, when this number will round down to zero. At that time no more digital assets will be added into circulation. In the exemplary embodiment of bitcoin, the total number of digital assets will have reached a maximum of 21 million assets in denomination of bitcoin. Other algorithms for limiting the total number of units of a digital math-based asset can be used consistent with exemplary embodiments of the present invention. For example, the Litecoin network is anticipated to produce 84 million Litecoin. In embodiments, the number of digital assets may not be capped and thus may be unlimited. In embodiments, a specified number of coins may be added into circulation each year, e.g., so as to create a 1% inflation rate.
In embodiments, the mining of digital assets may entail solving one or more mathematical calculations. In embodiments, the complexity of the mathematical calculations may increase over time and/or may increase as computer processing power increases. In embodiments, result of solving the calculations may be the addition of a block to a blockchain, which may be a transaction ledger, as described further below. Solving the calculations may verify a set of transactions that has taken place. Solving the calculations may entail a reward, e.g., a number of digital math-based assets and/or transaction fees from one or more of the verified transactions.
Different approaches are possible for confirming transactions and/or creating new assets. In embodiments, a digital asset network may employ a proof of work system. A proof of work system may require some type of work, such as the solving of calculations, from one or more participants (e.g., miners 145) on the network to verify transactions and/or create new assets. In embodiments, a miner 145 can verify as many transactions as computationally possible. A proof of work system may be computationally and/or energy intensive. In embodiments, the network may limit the transactions that a miner 145 may verify.
In embodiments, a digital asset network may employ a proof of stake system. In a proof of stake system, asset ownership may be tied to transaction verification and/or asset creation. Asset ownership can include an amount of assets owned and/or a duration of ownership. The duration of ownership may be measured linearly as time passes while a user owns an asset. In an exemplary embodiment, a user holding 4% of all digital assets in a proof of stake system can generate 4% of all blocks for the transaction ledger. A proof of stake system may not require the solution of complex calculations. A proof of stake system may be less energy intensive than a proof of work system. In embodiments, a hybrid of proof of work and proof of stake systems may be employed. For example, a proof of work system may be employed initially, but as the system becomes too energy intensive, it may transition to a proof of stake system.
Proof or work and proof of stake are both examples of consensus algorithms. Such consensus algorithms have as their goal providing a method of reaching consensus to improve the system whether it be on ways of improving transactions, upgrading the network, etc.
In embodiments, asset creation and/or transaction confirmation can be governed by a proof of stake velocity system. Proof of stake velocity may rely upon asset ownership where the function for measuring duration of ownership is not linear. For example, an exponential decay time function may ensure that assets more newly held correspond to greater power in the system. Such a system can incentivize active participation in the digital math-based asset system, as opposed to storing assets passively.
In embodiments, a proof of burn system may be employed. Proof of burn may require destroying assets or rendering assets unspendable, such as by sending them to an address from which they cannot be spent. Destroying or rendering assets unusable can be an expensive task within the digital math-based asset system, yet it may not have external costs such as the energy costs that can be associated with mining in a proof of work system.
Blockchains can include a consensus generating protocol through which the network determines whether a transaction is valid, included in the ledger and in what order each transaction should be included. Examples of such facilities, can include mining, proof of work, proof of stake protocols, to name a few.
In embodiments, a stable value digital asset token, or Stable Value Token (“SVCoin”) may operate on a blockchain based network, such as the Ethereum network, a decentralized virtual currency and blockchain network with a programming language that can automatically facilitate, verify, and enforce the terms of a digital contract entered into by human or computer counterparties. In embodiments, the SVCoin may conform with the ERC-223 token standard, making it available for a variety of uses within the Ethereum Network. In embodiments, the SVCoin may conform to the ERC-721 token standard. However, unlike other types of cryptocurrencies currently available on the Ethereum Network or the virtual currency ecosystem generally, the SVCoin will be strictly pegged to a fiat currency, such as the U.S. Dollar, and a custodian, such as a trusted entity like a digital asset exchange or bank, to name a few, will hold an equal value in fiat (e.g., one (1) SVCoin is pegged to be equal to one (1) USD or one hundred (199(SVCoin is pegged to equal one (1) USD, to name a few).
In embodiments, a digital asset exchange, such as a regulated digital asset exchange, like Gemini, may be the sole issuer of the SVCoin. In embodiments, especially in the context of a regulated digital asset exchange, in order to obtain freshly minted SVCoin, customers must first register with the digital asset exchange and create an exchange account to allow access to the digital asset exchange platform. Customers may deposit fiat (e.g., USD) with the digital asset exchange, via, e.g., Fedwire, ACH, Swift, to name a few, into the customers respective exchange account, or convert into fiat some or all of existing digital assets held at the digital asset exchange. SVCoin may be held in the customer's exchange account or may be transferred via the blockchain, such as via the Ethereum Network. In embodiments, the SVCoin issuer may be a digital asset exchange, a bank, a trust or some other trusted entity, to name a few.
In embodiments, regardless of whether the SVCoin is stored in the customer's exchange account or transferred via the blockchain such as the Ethereum Network, the digital exchange will continue to hold sufficient fiat to maintain the total value of SVCoin based on a notional pegged rate (e.g., one USD for every one SVCoin issued). In embodiments, the value of the SVCoin is pegged to the fiat in a fixed proportion, for example 1:1. In embodiments, fiat will be held in a segregated, omnibus bank account at one or more federally insured depository institution. In embodiments, the fiat may be held in other secure and non-volatile financial instruments, such as invested in treasury bills or other liquid, interest bearing financial instruments.
In embodiments, customers wishing to redeem their SVCoin for fiat may do so through the digital asset platform. Customers that have transferred their SVCoin to the blockchain will be able to transfer their SVCoin back to their exchange account, and subsequently redeem them for fiat through the digital exchange platform, such as via Fedwire, ACH or SWIFT to the customer's registered bank account, to name a few. For each fiat redeemed with the digital exchange, a corresponding SVCoin will be removed from circulation. As mentioned above, exemplary embodiments of such transactions are discussed below in connection with the descriptions of
In embodiments, the Stable Value Token may be implemented as a token on the Ethereum blockchain, following the open standard known as ERC20 adopted by the Ethereum community. In embodiments, the Stable Value Token may be a system of smart contracts. In embodiments, the Stable Value Token may be a triplet of smart contracts on the Ethereum blockchain, which may be referred to as ‘Proxy’, ‘Impl’, and ‘Store’.
In embodiments, the smart contract known as ‘Proxy’ is the permanent and public face of the Stable Value Token and provides the interface to interact with the token to allow token holders transfer their tokens and view token balances. In embodiments, however, this contract contains neither the code nor the data that comprises the behavior and state of the Stable Value Token.
In embodiments, the ‘Proxy’ contract delegates to the contract known as ‘Impl’ authority to execute the logic that governs token transfers, issuance, and other core features. In embodiments, ‘Impl’ does not directly own the data that is the ledger of the Stable Value Token, the mapping of token holders to their balances, but instead delegates this to the smart contract known as ‘Store’.
In embodiments, the arrangement of ‘Proxy’, ‘Impl’, and ‘Store’ provides for future change and flexibility. While ‘Proxy’ may be the permanent address of the Stable Value Token on the Ethereum blockchain, and ‘Store’ is the external storage of the token ledger, the ‘Impl’ contract is designed to be replaced, if need be. Utilizing this architecture to implement the Stable Value Token provides for the following advantages:
In embodiments, each of these three contracts has a custodian: an actor in the system that has the sole authority to authorize important actions. In embodiments, the custodianship role varies for each of ‘Proxy’, ‘Impl’, and ‘Store’. In embodiments, the custodian of ‘Proxy’ can redirect the delegation to the active token implementation, the specific ‘Impl’ contract. In embodiments, matching this arrangement, the ‘Store’ contract may only accept updates to its ledger from a single trusted source, the active token implementation, the specific ‘Impl’ contract. In embodiments, these two custodial actions on ‘Proxy’ and ‘Store’ provide the upgrade feature where a new ‘Impl’ displaces the prior version by the custodian of ‘Proxy’ redirecting the delegation in ‘Proxy’; and a new ‘Impl’ displaces the prior version by the custodian of ‘Store’ updating the trusted caller of ‘Store’. In embodiments, the custodians of ‘Proxy’ and ‘Store’ can also pass custodianship to new custodians.
In embodiments, the primary custodial action on the ‘Impl’ contract is different. In embodiments, an important aspect of the Stable Value Tokens is governing the increase to the token supply since at all times the system must ensure that there are at least as many U.S. Dollars as there are Stable Value Tokens in circulation. In embodiments, the ‘Impl’ contract contains the logic to increase the token supply, and the custodian of ‘Impl’ has the sole authority to invoke it. In embodiments, custodianship can also be passed.
In embodiments, an auxiliary contract is a contract to fulfil the custodian role, which we will refer to here as ‘Custodian’. In embodiments, this contract is designed around several security principles:
This provides strong security control on custodianship, which is appropriate for the critical and infrequent system actions of replacing the ‘Impl’ contract (“the upgrade feature”) and passing custodianship. In embodiments, however, for the action of increasing the token supply, an action expected to occur frequently, using ‘Custodian’ as the custodian of ‘Impl’ introduces an undue operational burden.
In embodiments, a second auxiliary contract, is referred to as ‘PrintLimiter’. In embodiments, the purpose of the ‘PrintLimiter’ smart contract is to govern the increases to the supply of Stable Value Tokens, specifically by a hybrid of online and offline control. While ‘Custodian’ is the custodian of the contracts ‘Proxy’ and ‘Store’, the ‘PrintLimiter’ contract is the custodian of ‘Impl’, and in turn, ‘Custodian’ is the custodian of ‘PrintLimiter’. In embodiments, this doubly-layered custodianship relationship still reserves ultimate control to ‘Custodian’, however, the ‘PrintLimiter’ contract grants limited permission to increase the token supply (“print” new tokens) to a key in online control (an automated, networked computer system), which we will refer to as ‘printer’. In embodiments, the ‘printer’ key can increase the token supply in response to user demand to withdraw U.S. dollars as Stable Value Tokens, but only up until a ceiling. In embodiments, further expansion of the supply is disallowed by ‘PrintLimiter’ once the ceiling is reached. In embodiments, increasing the ceiling is an action reserved for the custodian, and the custodian of ‘PrintLimiter’ is ‘Custodian.’ In embodiments, the ‘printer’ can reduce the ceiling thus reducing its own grant. In embodiments, offline control can increase the grant to online control; online control can decrease its own grant. In embodiments, the arrangement discussed herein achieves a hybrid of online and offline control over the supply of Stable Value Tokens. In embodiments, tokens can be issued in an efficient and timely manner, while the risk of inflation of the supply of Stable Value Tokens without backing U.S. Dollars is bounded.
In embodiments, as noted above, multiple signatures may be required for certain transactions such as those requiring intervention of the Custodian 1350. In embodiments, as noted above, changing the implementation pointer from ERC20Proxy 1310 which is currently set at S1312 (impl) to point to ERC20Impl 1320 (Version 1), requires resetting S1312B “impl” to point to ERC20Impl 1320A (version 2). In embodiments, a request is made to ERC20Proxy to change its instance of ERC20Impl. When the request is made, a unique lockId is generated. In embodiments, the Custodian contract 1350 for ERC20 Proxy 1310 calls requestUnlock and passes as arguments the lockId generated for the change request, and the function in ERC20Proxy 1310 the Custodian 1350 needs to call to confirm the change request. This generates a request, which is a unique identifier for this unlock request.
In embodiments, to complete the unlocking of Custodian and therefore propagate the change to ERC20Proxy 1310, the digital asset system operated by the token issuer uses its off-line key storage infrastructure to sign the request with the previously approved designated key sets. This may require the use of two or more key sets.
In embodiments, those signatures are passed into the Custodian's completeUnlock function along with the initial request. Once the request is validated against the signatures, completeUnlock parses the content of the request and issues the command. In this exemplary case, it calls ERC20Proxy's confirmImplChange using the lockId generated in the initial ERC20Impl change request.
In embodiments, the arrangement discussed herein achieves a hybrid of online and offline control over the supply of Stable Value Tokens. In embodiments, tokens can be issued in an efficient and timely manner, while the risk of inflation of the supply of Stable Value Tokens without backing U.S. Dollars is bounded. In embodiments, pending actions may be revoked, allowing for the nullification of erroneous or malicious actions before being executed.
In embodiments, a digital asset in the form of a token (“Security Token”) may be issued to represent inventory, equity interests in a venture, real estate, rights in intellectual property such music, videos, pictures, to name a few. When used as a security, appropriate filings with a regulatory authority may be necessary to comply with local law. In the case of a security, investors may exchange fiat or other digital assets (such as bitcoin or ether, to name a few) in exchange for Security Tokens. Typically, Security Tokens may issue using a smart contract written on another digital asset (such as ether or bitcoin, to name a few), and tracked in a separate database stored in a distributed peer to peer network in the form of a blockchain. In an example, the blockchain is the Ethereum Blockchain and includes all Security Tokens, the respective address associated therewith, wherein maintenance of the blockchain is controlled by contract instructions stored in the form of a smart contract at the Contract Address. In embodiments, the Secure Token database maintained on the blockchain may be viewed via etherscan.io. In embodiments, the Security Token ledger may be maintained as a sidechain in a separate database off chain and published periodically or aperiodically to the blockchain. Each Security Token may also be associated with a specific digital asset address on the network associated with the underlying digital asset (e.g., the Ethereum Network when ether is the underlying digital asset, or the Bitcoin Network, when bitcoin is the digital asset, to name a few). Generally, the same blockchain will be used for the SVCoin and the Security Token.
Digital assets may be associated with a digital asset account, which may be identified by a digital asset address. A digital asset account can comprise at least one public key and at least one private key, e.g., based on a cryptographic protocol associated with the particular digital asset system, as discussed herein. One or more digital asset accounts may be accessed and/or stored using a digital wallet, and the accounts may be accessed through the wallet using the keys corresponding to the account.
A digital asset account identifier and/or a digital wallet identifier may comprise a public key and/or a public address. Such a digital asset account identifier may be used to identify an account in transactions, e.g., by listing the digital asset account identifier on a decentralized electronic ledger (e.g., in association with one or more digital asset transactions), by specifying the digital asset account identifier as an origin account identifier, and/or by specifying the digital asset account identifier as a destination account identifier, to name a few. The systems and methods described herein involving public keys and/or public addresses are not intended to exclude one or the other and are instead intended generally to refer to digital asset account identifiers, as may be used for other digital math-based asset. A public key may be a key (e.g., a sequence, such as a binary sequence or an alphanumeric sequence) that can be publicly revealed while maintaining security, as the public key alone cannot decrypt or access a corresponding account. A public address may be a version of a public key. In embodiments, a public key may be generated from a private key, e.g., using a cryptographic protocol, such as the Elliptic Curve Digital Signature Algorithm (“ECDSA”).
In exemplary embodiments using bitcoin, a public key may be a 512-bit key, which may be converted to a 160-bit key using a hash, such as the SHA-256 and/or RIPEMD-160 hash algorithms. The 160-bit key may be encoded from binary to text, e.g., using Base58 encoding, to produce a public address comprising non-binary text (e.g., an alphanumeric sequence). Accordingly, in embodiments, a public address may comprise a version (e.g., a shortened yet not truncated version) of a public key, which may be derived from the public key via hashing or other encoding. In embodiments, a public address for a digital wallet may comprise human-readable strings of numbers and letters around 34 characters in length, beginning with the digit 1 or 3, as in the example of 175tWpb8K1S7NmH4Zx6rewF9WQrcZv245 W. The matching private key may be stored in a digital wallet or mobile device and protected by a password or other techniques and/or devices for providing authentication.
In embodiments, other cryptographic algorithms may be used such as:
In other digital asset networks, other nomenclature mechanisms may be used, such as a human-readable string of numbers and letters around 34 characters in length, beginning with the letter L for Litecoin or M or N for Namecoin or around 44 characters in length, beginning with the letter P for PPCoin, to name a few.
A private key in the context of a digital math-based asset, such as bitcoin, may be a sequence such as a number that allows the digital math-based asset, e.g., bitcoin, to be transferred or spent. In embodiments, a private key may be kept secret to help protect against unauthorized transactions. In a digital asset system, a private key may correspond to a digital asset account, which may also have a public key or other digital asset account identifier. While the public key may be derived from the private key, the reverse may not be true.
In embodiments related to the Bitcoin system, every Bitcoin public address has a matching private key, which can be saved in the digital wallet file of the account holder. The private key can be mathematically related to the Bitcoin public address and can be designed so that the Bitcoin public address can be calculated from the private key, but importantly, the same cannot be done in reverse. In the event that a transaction is sent to a Bitcoin public address and signed by a private key that does not match, such transaction will not be processed by the Bitcoin blockchain.
A digital asset account, such as a multi-signature account, may require a plurality of private keys to access it. In embodiments, any number of private keys may be required. An account creator may specify the number of required keys (e.g., 2, 3, 5, to name a few) when generating a new account. More keys may be generated than are required to access and/or use an account. For example, 5 keys may be generated, and any combination of 3 of the 5 keys may be sufficient to access a digital asset account. Such an account setup can allow for additional storage and security options, such as backup keys and multi-signature transaction approval, as described herein.
Because a private key provides authorization to transfer or spend digital assets such as bitcoin, security of the private key can be important. Private keys can be stored via electronic computer files, but they may also be short enough that they can be printed or otherwise written on paper or other media. An example of a utility that allows extraction of private keys from an electronic wallet file for printing purposes is Pywallet. Other extraction utilities may also be used consistent with the present invention.
In embodiments, a private key can be made available to a program or service that allows entry or importing of private keys in order to process a transaction from an account associated with the corresponding public key. Some wallets can allow the private key to be imported without generating any transactions while other wallets or services may require that the private key be swept. When a private key is swept, a transaction is automatically broadcast so that the entire balance held by the private key is sent or transferred to another address in the wallet and/or securely controlled by the service in question.
In embodiments, using Bitcoin clients, such as BlockChain.info's My Wallet service and Bitcoin-QT, a private key may be imported without creating a sweep transaction.
In embodiments, a private key, such as for a Bitcoin account, may be a 256-bit number, which can be represented in one or more ways. For example, a private key in a hexadecimal format may be shorter than in a decimal format. For example, 256 bits in hexadecimal is 32 bytes, or 64 characters in the range 0-9 or A-F. The following is an example of a hexadecimal private key:
In embodiments, nearly every 256-bit number is a valid private key. Specifically, any 256-bit number between 0x1 and 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4141 is a valid private key. In embodiments, the range of valid private keys can be governed by the secp256k1 ECDSA standard used by Bitcoin. Other standards may also be used.
In embodiments, a shorter form of a private key may be used, such as a base 58 Wallet Import format, which may be derived from the private key using Base58 and/or Base58Check encoding. The Wallet Import format may be shorter than the original private key and can include built-in error checking codes so that typographical errors can be automatically detected and/or corrected. For private keys associated with uncompressed public keys, the private key may be 51 characters and may start with the number 5. For example, such a private key may be in the following format:
In embodiments, private keys associated with compressed public keys may be 52 characters and start with a capital L or K.
In embodiments when a private key is imported, each private key may always correspond to exactly one Bitcoin public address. In embodiments, a utility that performs the conversion can display the matching Bitcoin public address.
The Bitcoin public address corresponding to the sample above is:
In embodiments, a mini private key format can be used. Not every private key or Bitcoin public address has a corresponding mini private key; they have to be generated a certain way in order to ensure a mini private key exists for an address. The mini private key is used for applications where space is critical, such as in QR codes and in physical bitcoin. The above example has a mini key, which is:
In embodiments, any bitcoin sent to the designated address 1CC3X2gu58d6wXUWMffpuzN9JAfTUWu4Kj can be transferred or spent by anybody who knows the private key in any of the three formats (e.g., hexadecimal, base 58 wallet format, or mini private key). That includes bitcoin presently at the address, as well as any bitcoin that are ever sent to it in the future. The private key is only needed to transfer or spend the balance, not necessarily to see it. In embodiments, the bitcoin balance of the address can be determined by anybody with the public Block Explorer at http://www.blockexplorer.com/address/1CC3X2gu58d6wXUWMffpuzN9JAfTUWu4Kj—even if without access to the private key.
In embodiments, a private key may be divided into segments, encrypted, printed, and/or stored in other formats and/or other media, as discussed herein.
In embodiments, digital math-based assets can be stored and/or transferred using either a website or software, such as downloaded software. The website and/or downloadable software may comprise and/or provide access to a digital wallet. Each digital wallet can have one or more individual digital asset accounts (e.g., digital asset addresses) associated with it. Each user can have one or more digital wallets to store digital math-based assets, digital crypto-currency, assets and the like and/or perform transactions involving those currencies or assets. In embodiments, service providers can provide services that are tied to a user's individual account.
Digital wallets and/or the digital asset accounts associated with and/or stored by a digital wallet may be accessed using the private key (which may be used in conjunction with a public key or variant thereof). Accordingly, the generation, access, use, and storage of digital asset accounts is described herein with respect to generation, access, use, and storage of digital wallets. Such descriptions are intended to be representative of digital asset accounts and not exclusive thereof.
A digital wallet can be generated using a digital asset client 110 (e.g., a Bitcoin client). In embodiments, a digital wallet can be created using a key pair system, such as an asymmetric key pair like a public key and a private key. The public key can be shared with others to designate the address of a user's individual account and/or can be used by registries and/or others to track digital math-based asset transactions involving a digital asset account associated with the digital wallet. Such transactions may be listed or otherwise identified by the digital wallet. The public key may be used to designate a recipient of a digital asset transaction. A corresponding private key can be held by the account holder in secret to access the digital wallet and perform transactions. In embodiments, a private key may be a 256-bit number, which can be represented by a 64-character hexadecimal private key and/or a 51-character base-58 private key. As discussed herein, private keys of other lengths and/or based on other numbering systems can be used, depending upon the user's desire to maintain a certain level of security and convenience. Other forms of key pairs, or security measures can be used consistent with embodiments of the present invention.
In embodiments, a digital wallet may store one or more private keys or one or more key pairs which may correspond to one or more digital asset accounts.
In embodiments, a digital wallet may be a computer software wallet, which may be installed on a computer. The user of a computer software wallet may be responsible for performing backups of the wallet, e.g., to protect against loss or destruction, particularly of the private and/or public key. In embodiments, a digital wallet may be a mobile wallet, which may operate on a mobile device (e.g., mobile phone, smart phone, cell phone, iPod Touch, PDA, tablet, portable computer, to name a few). In embodiments, a digital wallet may be a website wallet or a web wallet. A user of a web wallet may not be required to perform backups, as the web wallet may be responsible for storage of digital assets. Different wallet clients may be provided, which may offer different performance and/or features in terms of, e.g., security, backup options, connectivity to banks or digital asset exchanges, user interface, and/or speed, to name a few.
In embodiments, a digital wallet may be a custodial digital wallet. Further, the custodial digital wallet may be a segregated custodial wallet or a commingled custodial wallet. Segregated custodial digital wallets hold digital assets for the benefit of a single customer or entity. Commingled custodial accounts hold digital assets for multiple users or customers of the custodian. Segregated custodial wallets are useful for institutional clients, mutual funds and hedge funds, for example.
While many digital asset holders may hold their digital assets in their own wallets, various custodial services, like Gemini custodial services exist. In embodiments, the present invention may be used with custodial wallets. In embodiments, custodial wallets may be commingled custodial wallets which commingle digital assets from more than one client. In embodiments, custodial wallets may be segregated custodial wallets, in which digital assets for a specific client is held using one or more unique digital asset addresses maintained by the custodial service. For segregated custodial wallets, the amount of digital assets held in such wallet(s) may be verified and audited on their respective blockchain. In embodiments, segregated custodial accounts may be used for digital asset holders such as hedge funds, mutual funds, exchange traded funds, to name a few. Proof of control as described herein may be implemented to verify the amount of assets held in custodial wallets, including both segregated custodial wallets and commingled custodial wallets.
A transaction may require, as a precondition to execution, a digital asset signature generated using a private key and associated public key for the digital asset account making the transfer. In embodiments, each transaction can be signed by a digital wallet or other storage mechanism of a user sending a transaction by utilizing a private key associated with such a digital wallet. The signature may provide authorization for the transaction to proceed, e.g., authorization to broadcast the transaction to a digital asset network and/or authorization for other users in a digital asset network to accept the transaction. A signature can be a number that proves that a signing operation took place. A signature can be mathematically generated from a hash of something to be signed, plus a private key. The signature itself can be two numbers such as r and s. With the public key, a mathematical algorithm can be used on the signature to determine that it was originally produced from the hash and the private key, without needing to know the private key. Signatures can be either 73, 72, or 71 bytes long, to name a few.
In embodiments, the ECDSA cryptographic algorithm may be used to ensure that digital asset transactions (e.g., bitcoin transactions) can only be initiated from the digital wallet holding the digital assets (e.g., bitcoin). Alternatively, or in addition, other algorithms may be employed.
In embodiments, a transaction from a multi-signature account may require digital asset signatures from a plurality of private keys, which may correspond to the same public key and/or public address identifying the multi-signature digital asset account. As described herein, a greater number of private keys may be created than is necessary to sign a transaction (e.g., 5 private keys created and only 3 required to sign a transaction). In embodiments, private keys for a multi-signature account may be distributed to a plurality of users who are required to authorize a transaction together. In embodiments, private keys for a multi-signature account may be stored as backups, e.g., in secure storage, which may be difficult to access, and may be used in the event that more readily obtainable keys are lost. As noted above, there are a variety of cryptographic algorithms that may be used.
A digital asset market place, such as a Bitcoin market place, can comprise various participants, including users, vendors, exchanges, exchange agents, and/or miners/mining pools. The market contains a number of digital asset exchanges, which facilitate trade of digital assets using other currencies, such as United States dollars. Exchanges may allow market participants to buy and sell digital assets, essentially converting between digital assets (e.g., bitcoin) and currency, legal tender, and/or traditional money (e.g., cash). In embodiments, a digital asset exchange market can include a global exchange market for the trading of digital assets, which may contain transactions on electronic exchange markets. In embodiments, a digital asset exchange market can also include regional exchange markets for the trading of digital assets, which may contain transactions on electronic exchange markets. In accordance with the present invention, exchanges and/or transmitters may also be used to facilitate other transactions involving digital assets, such as where digital assets are being transferred from differently denominated accounts or where the amount to transfer is specified in a different denomination than the digital asset being transferred, to name a few. Gemini Trust Company LLC (“Gemini”) at (www.gemini.com) is an example of a digital asset exchange 130. By example, registered users of Gemini may buy and sell digital assets such as Bitcoin and Ether in exchange for fiat such as U.S. dollars or other digital assets, such as Ether and Bitcoin, respectively. A Bitcoin exchange agent 135 can be a service that acts as an agent for exchanges, accelerating the buying and selling of bitcoin as well as the transfer of funds to be used in the buying and/or selling of bitcoin. Coinbase is an example of a company that performs the role of a Bitcoin exchange agent 135. Coinbase engages in the retail sale of bitcoin, which it obtains, at least in part, from one or more exchanges.
In addition to the services that facilitate digital asset transactions and exchanges with cash, digital asset transactions can occur directly between two users. In exemplary uses, one user may provide payment of a certain number of digital assets to another user. Such a transfer may occur by using digital wallets and designating the public key of the wallet to which funds are being transferred. As a result of the capability, digital assets may form the basis of business and other transactions. Digital math-based asset transactions may occur on a global scale without the added costs, complexities, time and/or other limits associated with using one or more different currencies.
Vendors 140 may accept digital assets as payment. A vendor 140 may be a seller with a digital wallet that can hold the digital asset. In embodiments, a vendor may use a custodial wallet. In embodiments, a vendor 140 may be a larger institution with an infrastructure arranged to accept and/or transact in digital assets. Various vendors 140 can offer banknotes and coins denominated in bitcoin; what is sold is really a Bitcoin private key as part of the coin or banknote. Usually, a seal has to be broken to access the Bitcoin private key, while the receiving address remains visible on the outside so that the bitcoin balance can be verified. In embodiments, a debit card can be tied to a Bitcoin wallet to process transactions.
In embodiments, one form of trusted entity that may be an issuer of tokens or an agent of the issuer is a digital asset exchange or bank. In embodiments, the trusted entity may maintain a token database on a blockchain. In embodiments, the trusted entity may maintain the token database off chain as a sidechain which may be periodically or aperiodically published to a blockchain as discussed elsewhere.
In some embodiments, the trusted entity may be a digital asset exchange. A digital asset exchange, such as a digital math-based asset exchange, may allow users to sell digital assets in exchange for any other digital assets or fiat currency and/or may allow users to sell fiat currency in exchange for any digital assets. Accordingly, an exchange may allow users to buy digital assets in exchange for other digital assets or fiat currency and/or to buy fiat currency in exchange for digital assets. In embodiments, a digital asset exchange may integrate with a foreign exchange market or platform. A digital asset exchange may be configured as a centralized exchange or a decentralized exchange, as discussed herein.
In embodiments, the issuer of the SVCoin may be a digital asset exchange, a bank, a trust, or other trusted entity. In the context where a digital asset exchange may act as an issuer for token, or as an agent of the issuer, a digital asset exchange computer system may maintain a ledger as one or more databases associated with the token. Such a database may include an electronic log of all transactions, including the source wallet, the destination wallet, the timestamp of the transaction, the amount of the transaction (e.g., the number of tokens), and/or the balance in each wallet before and/or after the transaction. In embodiments, the database may include a list of wallet addresses and balances in each wallet of the token. In embodiments, the issuer may maintain the database by using a smart contract in association with a Contract Digital Address as part of a blockchain network, such as the Ethereum Network. In embodiments, the ledger may be maintained in a database as a sidechain which is periodically, or aperiodically, published to a blockchain such as the Ethereum blockchain. In embodiments, the ledger may be maintained directly on the blockchain.
In embodiments, users may connect to the exchange through one or more user electronic devices 3202 (e.g., 3202-1, 3202-2, . . . , 3202-N), such as computers, laptops, tablet computers, televisions, mobile phones, smartphones, and/or PDAs, to name a few. A user electronic device 3202 may access, connect to, and/or otherwise run one or more user digital wallets 3204. In embodiments, buyers and/or sellers may access the exchange using their own electronic devices and/or through a digital asset kiosk. A digital asset enabled kiosk can receive cash, including notes, coins or other legal tender, (of one or more fiat currencies) from a buyer to use in buying a quantity of digital assets. A digital asset kiosk may dispense cash (of one or more fiat currencies) to a seller of digital assets. In embodiments, a digital asset kiosk may receive funds from and/or dispense funds to a card, such as a prepaid or reloadable card, or digital asset address associated with a digital wallet, or electronic account. In embodiments, a digital wallet may be stored on a user electronic device, such as a mobile electronic device, or other computing device.
Users may also have user bank accounts 3208 (e.g., 3208-1, 3208-2, . . . , 3208-N) held at one or more banks 3206 (e.g., 3206-1, 3206-2, . . . , 3206-N). In embodiments, users may be able to access their bank accounts from a user electronic device 3202 and/or from a digital wallet 3204 or digital address associated therewith.
A digital asset exchange computer system 3210 can include software running on one or more processors, as discussed herein, as well as computer-readable memory comprising one or more database. A digital asset exchange can include one or more exchange digital wallets 3212, e.g., digital wallet 3212-A. Exchange digital wallets may be used to store digital assets in one or more denominations from one or more parties to a transaction. In embodiments, exchange digital wallets may store digital assets owned by the exchange, which may be used where an exchange is a counter-party to an exchange transaction, which can allow exchange transactions to occur even when a buyer and a seller are not otherwise both available and in agreement on transaction terms.
A digital asset exchange may have one or more bank accounts, e.g., bank account 3216-A, held at one or more banks 3214, such as exchange banks or exchange partner banks, which are banks associated with and/or in partnership with the exchange. In embodiments, exchanges may access other repositories for fiat currency. An exchange bank account may be a pass-through account that receives fiat currency deposits from a digital asset buyer and transfers the fiat currency to a digital asset seller. The exchange bank account may hold money in escrow while an exchange transaction is pending. For example, the exchange bank account may hold a digital asset buyer's fiat currency until a digital asset seller transfers digital assets to the buyer, to an exchange, or to an authorized third party. Upon receipt by the appropriate recipient of the requisite amount of digital assets, the exchange may authorize the release of the fiat currency to the digital asset seller. In embodiments, an exchange may hold, e.g., as custodian, fiat in bank accounts and digital assets in digital wallets at associated digital asset addresses. In embodiments, instead of using bank accounts, other stable investment instruments such as money market mutual funds, treasury bills, certificates of deposits, low risk bonds, to name a few, may be used.
The exchange may employ an electronic ledger system to track customer digital assets and/or customer fiat holdings. Such a system may allow rapid electronic transactions among exchange customers and/or between exchange customers and the exchange itself using its own digital asset and fiat holdings or those of its sponsor or owner. In embodiments, the electronic ledger system may facilitate rapid computer-based automated trading, which may comprise use by one or more computer systems of a trading API provided by the exchange. The electronic ledger system may also be used in conjunction with cold storage digital asset security systems by the exchange. Fiat (e.g., USD) and digital assets (e.g., bitcoin or ether) can be electronically credited and/or electronically debited from respective (e.g., fiat and digital asset) electronic ledgers. Clearing of transactions may be recorded nearly instantaneously on the electronic ledgers. Deposits of fiat with the exchange and withdrawals from the exchange may be recorded on the electronic fiat ledger, while deposits and withdrawals of digital assets may be recorded on the electronic digital asset ledger. Electronic ledgers may be maintained using one or more computers operated by the exchange, its sponsor and/or agent, and stored on non-transitory computer-readable memory operatively connected to such one or more computers. In embodiments, electronic ledgers can be in the form of a database.
A digital asset exchange computer system can include one or more software modules programmed with computer-readable electronic instructions to perform one or more operations associated with the exchange. Each module can be stored on non-transitory computer-readable memory operatively connected to such one or more computers. An exchange may have a user on-boarding module to register users with the exchange and/or create accounts for new and/or existing exchange users. The exchange may employ systems and methods to ensure that the identity of exchange customers is verified and/or the destination of fiat currency and/or digital assets is known. Accordingly, the exchange may require new exchange customers to provide valid (e.g., complying with certain types, such as a driver's license or passport, or complying with certain characteristics) photo identification, a current address, a current bill, such as a utility bill, biometric information (e.g., a fingerprint or hand scan), and/or bank account information. A user on-boarding module can include back-end computer processes to verify and store user data as well as a front-end user interface by which a user can provide information to the exchange, select options, and/or receive information (e.g., through a display). The user on-boarding module can provide the front-end interface to one or more user devices and/or platforms, such as a computer, mobile phone (e.g., running an exchange-related mobile application), and/or digital asset kiosk, to name a few.
In embodiments, an exchange computer system may calculate different fees for a market maker. The fee calculation may vary with market conditions, such as price, digital asset supply (e.g., sell orders), and digital asset demand (e.g., buy orders). In embodiments, transaction fees charged by an exchange may be different for purchase and sale transactions. Fees may be based upon a user's identity, a user's transaction history, the quantity of digital assets and/or fiat currency associated with a user account, a rate schedule associated with a particular account or account type (e.g., there could be different rates for institutional or foreign users), time of day, and/or whether the user is operating as a market maker or a market taker for a given transaction, to name a few.
As shown in
An account activities log 5114 may track all user requests received by the exchange computer system. The computer system may generate usage statistics and/or analyze user activity for patterns, e.g., to detect fraudulent behavior.
In embodiments, the risk management module 5126 may analyze user activity logs (e.g., access logs, transaction logs, user electronic requests, website navigation logs, mobile application usage logs, to name a few) to identify behavioral patterns, anomalies, and/or potential fraudulent activity (such as fraudulent electronic requests).
In embodiments, an exchange may conduct user or account verification procedures. In embodiments, these user or account verification procedures may comprise participating with third-party vendors in connection with certain Know Your Customer services. In embodiments, an exchange may implement alternative anti-money laundering (AML) measures. In embodiments, AML measures may include monitoring each transaction on the digital asset exchange for particular factors (e.g., amounts of transaction, location of transaction, volume of activity, to name a few). In the United States, the exchange may provide a user on-boarding mechanism that receives a user registration request, receives a user domicile (e.g., a state of domicile), and/or directs the user to an anti-money laundering user interface based upon the domicile. In embodiments, this interface may be generated at a user device using display data transmitted from the exchange computer system.
A matching engine 5128 may apply a continuous order book price time priority matching algorithm. In embodiments, matching engine 5128 may apply option points at low and/or high frequencies.
As shown in
A web server 5152 may provide display data to one or more user device 102, e.g., user device 102-1. Display data may comprise website content (e.g., HTML, JavaScript, and/or other data from which a user device can generate and/or render one or more webpages) and/or application content, such as mobile application content, to be used in generating or providing display content for one or more software application. In embodiments, the web server 5152 may authenticate a user account by verifying a received username and password combination.
An authenticator computer system 5154 may perform authentication of user login credentials, multi-factor authentication, and/or compare users against databases, such as government databases, for compliance with anti-money laundering laws and/or regulations.
A matching engine computer system 5156 may match buy (purchase) orders with sell orders, receive orders, and/or update an electronic order book, to name a few.
An electronic ledger computer system 5158 may track and/or store account balances, update account balances, compute account balances, report account balances, and/or place holds on account funds while transactions are in progress (e.g., set an account hold indicator), to name a few.
A risk management computer system 5160 may perform processes to detect fraudulent transactions and/or security breaches. Such a sub-system may monitor access data describing access of the exchange (e.g., IP addresses, accounts, times of access, to name a few), monitor trading data, analyze trading data, determine patterns, determine anomalies, and/or determine violations of pre-programmed security rules, to name a few.
A digital wallet computer system 5162 may generate digital wallets with associated digital asset addresses, generate instructions for digital wallet key storage and/or retrieval, allocate digital assets among digital wallets, track digital assets, store digital asset, and/or transfer digital assets, to name a few.
The digital wallets may include both hot wallets and cold wallets. In embodiments, sufficient digital assets will be stored in one or more hot wallets to allow for liquidity. The amount of digital assets stored in the one or more hot wallets may be determined based on historical averages of trading on the exchange. In embodiments, remaining digital assets will preferably be held in cold wallets. A more detailed discussion of hot wallets and cold wallets is presented in U.S. Pat. No. 9,892,460, issued Feb. 13, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR OPERATING EXCHANGE TRADED PRODUCTS HOLDING DIGITAL MATH-BASED ASSETS, the entire content of which is incorporated herein by reference.
A fiat account computer system 5164 may manage omnibus or pooled accounts for holding customer funds. The fiat account computer system may process receipts of funds, e.g., from a bank, via a wire transfer, via a credit card or ACH transfer, and/or via check, to name a few. Accordingly, the fiat account computer system may communicate with one or more external systems, such as a bank computer system. In embodiments, the fiat account computer system may process withdrawals. In embodiments, the omnibus or pooled accounts for holding fiat are maintained in a bank or other institution such that these accounts are eligible for insurance under the Federal Deposit Insurance Corporation (FDIC). In order to qualify for FDIC insurance, an account must typically be associated with specific user identification information, e.g., a user name, address and social security number, by way of example, to name a few. Accordingly, in embodiments, fiat accounts may be associated with individuals who are positively identified.
Referring to the account creation process shown in
Referring to the identity verification process shown in
Referring to the fiat account funding process shown in
Referring to the digital asset account funding process shown in
Referring to
In a step S4812, the exchange computer system can transmit a fund transfer request to a bank where the customer has a fiat bank account. Accordingly, the exchange computer system may transmit to an exchange partner bank an electronic funding request comprising the funding amount and the user bank account identifier.
In a step S4814, the exchange computer system can update an exchange fiat electronic ledger with the funding transaction information. In a step S4816, the exchange computer system can receive an electronic indication that the funding amount was transferred from the customer's fiat bank account to an exchange fiat account, e.g., at a partner bank. In a step S4818, the exchange computer system can monitor the exchange fiat account to determine the availability of funds in an exchange account associated with the user. In embodiments, the exchange computer system may generate and/or provide an electronic notification to one or more user devices associated with a user account that funds are available for use on the exchange. In embodiments, the notification may indicate a current balance of a user account (e.g., in fiat currency and/or digital asset quantities).
Referring to
A digital asset exchange can include additional systems, which may include software modules, for performing various functions of the exchange. For example, an exchange can include an account management system, which may comprise a user account registration system for new users and/or an existing user account management system. The exchange can include a trading system, which may comprise an interactive trading interface system, an automated trading interface system, a trade confirmation notification system, and/or a trade transaction fee processing system. A fund transfer system can include a fiat account funding and redemption system, a digital asset accounting funding and redemption system, and an account funding and redemption fee processing system. An exchange can also include a trade settlement system. A customer service system can include a trade dispute resolution interface system and a customer account management assistance system. A customer reporting system can include a gain an loss reporting system and a transaction history system. A fraud analysis system can monitor transactions to detect fraudulent and/or unauthorized transactions.
Deposited customer fiat may be held in a pooled fiat account maintained in a partner bank. Meanwhile, digital assets held by the exchange may be maintained in pooled digital addresses associated with pooled digital wallets, such as aggregated custodial wallets. The exchange may store digital assets using any of the security and/or storage systems and methods discussed herein. The exchange can employ any combination of varying levels of secure storage for its wallets. For example, portions of digital assets held by the exchange may be maintained in cold storage with neither the wallet's private nor public keys ever having been exposed to a digital asset network or other external network, such as the Internet. Other digital assets may be stored in air-gapped hot wallets, which may be wallets generated off-line with transactions generated off-line, e.g., on an isolated computer, and transferred to a networked computer via a temporary physical connection or manual transfer. Isolated computer systems are physically and operationally isolated from other computer systems. For example, an isolated computer system may be an air gapped computer system. Other digital assets may be maintained in hot wallets, e.g., to satisfy withdrawals from the exchange. The exchange may determine the amount of assets to hold in hot wallets, which may be based on historical exchange activity and/or anticipated need. A hot wallet liquidity module may analyze and predict the amount of assets per wallet and/or during a time period required to meet anticipated need and may also initiate transfers of assets to or from hot wallets to maintain desired levels. For example, a hot wallet liquidity module could determine that it is desirable to maintain digital assets in certain defined amounts (e.g., 0.5 bitcoin), and/or certain defined fiat amounts (e.g., $100 worth of bitcoin) and/or of certain defined quantities sufficient to cover transactions anticipated during a defined period (e.g., the day's transaction). In embodiments, initiating an electronic transfer may comprise electronically generating and providing an electronic notification to devices associated with one or more exchange administrators of a need to transfer assets and/or an amount of assets to transfer. The exchange may designate one or more wallets for receiving incoming digital assets only. For example, the exchange may employ a single digital wallet for each receipt of digital assets, e.g., from exchange users. The receiving wallet may be destroyed after the received assets are transferred to one or more other wallets.
The exchange may employ any of a number of different exchange digital wallet systems. As discussed herein, the exchange may operate a pooled or omnibus digital wallet system, e.g., as part of a centralized exchange system. The pooled system may use an electronic ledger to track digital asset ownership for each exchange customer. Customers may transfer digital assets from their own digital wallets to an exchange address in order to fund their digital asset account on the exchange. The ledger can track (e.g., record) such funding events, as well as withdrawal events. Transfers of digital assets among customers can also be accounted for using the ledger. With a pooled wallet system, internal transactions on the exchange (e.g., transactions that do not entail transferring funds to or from the exchange or exchange wallets but rather transactions between exchange wallets) can be settled without delay, since the transfer can be logged through electronic ledger updates and does not have to otherwise be processed by a digital asset network.
In another embodiment, the exchange digital wallet system may comprise exchange operated wallets for each exchange customer. These exchange operated wallets may be maintained in trust by the exchange for each customer as associated digital asset addresses. Transactions may be processed by the digital asset network, e.g., the Bitcoin network. The keys to each customer wallet may be held by the customer and/or by the exchange. Transactions may be settled via the digital asset network in real-time (with any corresponding confirmation period) as they occur, or transactions may be settled in a batch, which may entail broadcasting a plurality of transactions to the network at a particular time or periodically throughout a day.
In another embodiment of an exchange digital wallet system, the exchange customers may own and/or manage their own wallets, e.g., as part of a decentralized exchange system. The exchange would not hold any customer digital assets, and customers would hold the private keys to their wallets with associated digital asset addresses. The exchange may match customers, as described herein, so that a digital asset seller can transfer digital assets from the seller's digital wallet to a digital wallet corresponding to a digital asset buyer.
In embodiments, the digital wallet may be a custodial digital wallet. The custodial digital wallet may be segregated, that is, unique to a particular customer or commingled, including digital assets of multiple customers. In such an embodiment, the custodian holds digital assets in the custodial wallet for the benefit of its customers. The custodian would hold the private key to each custodial wallet whether it be segregated or commingled. Transactions may be made between different custodial wallets or between custodial wallets and exchange customer wallets in the manner described above.
In embodiments, the exchange may hold customer fiat currency and/or digital assets in centralized, pooled accounts or wallets. As discussed herein, the exchange may maintain an electronic ledger to record transactions among users of the exchange. Separate electronic fiat account ledgers and electronic digital asset ledgers may be maintained. Maintaining a ledger may involve electronically updating the ledger to reflect pending transactions and/or completed transactions, which may involve debiting assets from a user's account and/or crediting assets to a user's account. Broadcast to a digital asset network and confirmation from a digital asset network may not be performed for transactions within the exchange, e.g., transactions between a digital asset seller selling digital assets that are stored by the exchange and a buyer paying with fiat currency that is held in an exchange bank account, such as a pooled account.
In embodiments, for both a decentralized and a centralized exchange the exchange may provide the ability for customers to purchase digital assets from the exchange and/or sell digital assets to the exchange such that the exchange operator or owner is the counter-party to the transaction. Transaction amount limits may be place on such transactions and/or additional fees may be charged.
In embodiments, a digital asset exchange may require users to open designated accounts associated with the user in order to participate in the exchange. Each user may have a digital math-based asset account to record and maintain such user's digital math-based assets and a fiat account to record and maintain such user's fiat assets. In embodiments, the fiat assets recorded in the fiat account may be U.S. Dollars held in one or more omnibus bank accounts with one or more FDIC-insured depository institutions or banks. In embodiments, a digital math-based asset computer system of a digital asset exchange may record in an electronic ledger information associated with a user account, such as digital math-based asset purchase orders, digital math-based asset sell orders, digital math-based asset purchase offers, digital math-based asset sell offers. In embodiments, digital math-based asset purchase offers and digital math-based asset sell offers may be converted into digital math-based asset purchase orders and digital math-based asset sell orders, respectively, according to a user's instructions, if certain user-specified factors are met (e.g., digital math-based assets are within a given price, quantity, period of time, to name a few). In embodiments, when the digital math-based asset computer system matches an electronic digital math-based asset purchase order with an electronic digital math-based asset sell order, the digital math-based asset computer system may record the trade in an electronic ledger, effectively transferring ownership of the seller's traded digital math-based assets to the buyer, and ownership of the related purchase price in fiat currency from the buyer to the seller. In embodiments, the changes in a user's ownership of digital math-based assets and fiat currency recorded in the electronic ledger are reflected in a user's digital math-based asset account and fiat account.
In embodiments, a digital asset exchange may accept payment methods (e.g., credit card transactions; Automated Clearing House (ACH) debits, wire transfers, digital asset transactions, to name a few) for purchases of digital assets.
In embodiments, users may utilize sub-accounts subordinate to the master account. In embodiments, sub-accounts can be used as entities for traders, or can be used by machines associated with an owner, as discussed in U.S. patent application Ser. No. 15/071,902, filed Mar. 16, 2016 and entitled AUTONOMOUS DEVICES, which is expressly incorporated herein by reference.
In embodiments, a digital asset exchange may hold digital math-based assets and/or fiat currency in trust for users before, during and after a trade. Fiat currency may be maintained in accounts with a state or federally chartered bank and may be eligible for FDIC insurance, subject to compliance with applicable federal regulation. In embodiments, a digital asset exchange may also operate a digital math-based asset storage system, in which users may deposit digital math-based assets. In embodiments, fiat currency may be transmitted to a digital asset exchange's omnibus account. In embodiments, the exchange may transmit fiat currency back to a user upon receiving a request from a user.
In embodiments, a digital asset exchange may comply with relevant laws and regulations whereby the exchange may operate in a highly regulated banking environment and permit necessary supervision by relevant legal authorities.
In embodiments, when a user commences an electronic digital math-based asset purchase order to acquire digital math-based assets, the user may either have fiat currency in an associated user account or the buyer may send fiat currency to the digital asset exchange's omnibus account at the applicable bank. In embodiments, when a seller commences an electronic digital math-based asset sell order to sell digital math-based assets, the seller may either have digital math-based assets in an associated user account or may send digital math-based assets to a digital math-based asset account. In embodiments, the seller may send digital math-based assets to one or more of digital wallets held by the exchange. In embodiments, exchange transactions may only be completed after the digital math-based asset computer system verifies that the digital math-based asset accounts and fiat accounts associated with the users involved in the transaction at least equal the quantities required by the transaction.
In embodiments, the exchange may permit trading twenty-four hours a day, seven days a week. In embodiments, the exchange may shut down for scheduled maintenance periods. In embodiments, the exchange may prohibit users from transferring fiat currency outside of normal business hours, in order to comply with applicable laws and regulations. In embodiments, the exchange may allow users to deposit and withdraw digital math-based assets outside of normal business hours. In embodiments, the exchange may permit users to sell digital math-based assets for fiat currency or buy digital math-based assets with fiat currency if the user holds sufficient fiat currency in its associated account prior to initiating the transaction.
In embodiments, as discussed herein, exchange customers looking to buy digital assets may be matched to customers looking to sell digital assets, which matching may be performed by an exchange trading engine. Transaction volumes and prices may be based at least in part upon bids and asks that are received by the trading engine from the customers.
In embodiments, a digital asset exchange (such as a regulated exchange) can be used to exchange SVCoin for fiat and fiat for SVCoin. Since SVCoin is a stable value token, each token will be pegged to a stable value of fiat (e.g., 1 SVCoin=1 USD or 1 SVCoin=1 EUR, to name a few). An example of a SVCoin could be Gemini Dollar. In embodiments, when fiat is provided to a digital asset exchange to purchase SVCoin, a sufficient amount of fiat to cover the notional value of the SVCoin will be set aside and held until the SVCoin is redeemed. Similarly, when SVCoin is redeemed the corresponding amount of fiat associated with the notional value of the SVCoin will be taken from such reserves to cover the redemption.
In embodiments, each time SVCoins are purchased, redeemed and/or traded, transaction fees may be charged by the SVCoin issuer, and/or others involved in the transaction, such as miners on the digital asset network. Such transaction fees may be charged in fiat, SVCoin and/or other digital assets (e.g, Gas, bitcoin, ether, to name a few). For example, a purchaser may pay $1.01 USD for 1 SVcoin (that has a redemption value of $1.00 USD).
In embodiments, the SVCoin issuer may provide a discount to a purchaser of SVCoin, which may be reflected in fiat, SVCoin and/or other digital assets (e.g., Gas, bitcoin, ether, to name a few). For example, a purchaser may pay $0.99 USD for 1 SVCoin (that has a redemption value of $1.00 USD).
In embodiments, transaction fees and/or discounts can be incurred and/or paid at the time of transfer or at another time.
In embodiments, the SVCoin may be pegged to another stable value token. In embodiments, the SVCoin may be pegged to the value of another asset, other than fiat. In embodiments, the SVCoin may be pegged to the value of a security, for example, a certificate of stock in a particular company. In embodiments, a purchaser of the SVCoin may deposit or otherwise provide to the digital asset exchange, a share of stock and will receive an SVCoin token in return. In embodiments, the digital asset exchange will hold the share of stock, in a custodial account, for example, until it is redeemed. In embodiments, rather than deposit a share of stock, a purchaser of SVCoin may deposit a sum of fiat, or other assets, sufficient to purchase a share of stock. In embodiments, the digital asset exchange may acquire a share of stock on the market using the assets deposited by the purchaser and then hold the share of stock until the SVCoin is redeemed.
In embodiments, the SVCoin may be pegged to the value of a commodity. In embodiments, a purchaser of SVCoin may deposit a sum of fiat, or other assets, sufficient to purchase a quantity of a commodity. In embodiments, the digital asset exchange may hold an amount of the commodity, in a custodial account, for example, until the SVCoin is redeemed. In embodiments, the digital asset exchange may acquire the quantity of the commodity on the market using the assets deposited by the purchaser and then hold the commodity until the SVCoin is redeemed.
In embodiments, the SVCoin may be pegged to a derivative product of a stock, commodity and/or another digital asset to name a few.
In embodiments, when a user (such as a registered user of a regulated digital asset exchange) commences a purchase order to acquire SVCoin for fiat, the user may have fiat currency in an associated user account. Alternatively, the user may send fiat currency to the exchange's account, such as an omnibus account, at the applicable bank. In embodiments, when a seller sells SVCoin, the seller may have the SVCoin in an associated user account or may send SVCoin to a digital asset account. Specifically, the seller may send SVCoin to one or more of digital asset addressed, typically associated with digital wallets held by the exchange. In embodiments, exchange transactions may only be completed after the verification that the digital asset accounts and fiat accounts associated with the users involved in the transaction at least equal the quantities of each required by the transaction.
In embodiments, as shown in
Similarly,
In embodiments, a registered user may purchase SVCoins in exchange for fiat. Referring to
In S6604, the user selects the purchase SVCoin option, and specifies the amount of SVCoins the user seeks to obtain. In embodiments, the user may be requested to provide a digital asset address, typically associated with a digital wallet, such as a digital asset address associated with a blockchain digital asset, like ether. In embodiments, the amount of SVCoins to be purchased may be specified by number of SVCoins, or by an amount of fiat. Since the SVCoins are pegged to the fiat in a stable amount (e.g., 1 SVCoin=1 USD), the system can automatically convert and display the requested amount of SVCoin into fiat, or requested amount of fiat into SVCoin.
In S6606, the digital asset exchange system will analyze and verify that the request can be properly processed. In step S6606-a, the digital asset exchange system, as the SVCoin issuer, may verify that the user has sufficient fiat currency maintained at the digital asset exchange to cover the transaction, including a sufficient amount of fiat to cover the amount of SVCoin being acquired, as well as any transaction fees that may be charged. If the user does not have sufficient fiat in the system, the transaction may be terminated for insufficient funds. In embodiments, the user may be provided an opportunity to obtain sufficient funds, by, e.g., selling digital assets maintained by the user on the digital asset exchange or by making a deposit of additional fiat. In step S6606-b, the digital asset exchange system, may also verify that the digital asset address provided is a valid digital asset address. In step S6608-c, the digital asset exchange system, may also publish transactions to blockchain.
In S6608, after the digital asset exchange system has confirmed that the user has sufficient fiat to cover the transaction, the digital asset exchange system may initiate the process of generating the requested SVCoin. In embodiments, where SVCoins were previously generated, then S6608 may be replaced with an alternative process S9908′ as discussed below.
Returning to S6608, in S6608-a, the digital asset exchange system may debit the designated fiat funds from a fiat ledger associated with the user account, and credit a corresponding amount of fiat to the SVCoin fiat ledger to be held in trust by the Exchange.
In S6608-b, the digital asset exchange system shall generate the requested SVCoin tokens. As part of this step, or as an additional step, the digital asset exchange system will update the SVCoin ledger to reflect the creation of the newly generated SVCoins and to indicate the digital asset address associated with these newly generated SVCoins.
In S6608-c, the digital asset exchange system shall publish to the blockchain network (e.g., the Ethereum Network) the transaction to be recorded by the blockchain network. In embodiments, a transaction fee may be required by, e.g., a miner, to process and add the requested transaction on the blockchain.
As noted, when a reserve of SVCoin had been previously created but not yet distributed by the digital asset exchange system, S6608′ may be implemented instead of S6608. At step S6608-a′, digital asset exchange computer system may debit the designated fiat funds from a fiat ledger associated with the user account, and credit a corresponding amount of fiat to the SVCoin fiat ledger to be held in trust by the Exchange.
In step S6608-b′, the digital asset exchange computer system may determine an appropriate amount of SVCoin from the reserve to satisfy the request.
In step S6608-c′, the digital asset exchange computer system updates the SVCoin ledger to change the address associated with the portion of the reserve determined in step S6608b′ to the address associated with the user.
In S6610, the digital asset exchange computer system may send a message to the registered user, and/or the designated digital asset address to reflect that the transaction was successfully processed. In embodiments, such messages may include information including: (i) digital asset address; (ii) the amount of tokens generated; and/or (iii) the new balances for the digital asset address.
In embodiments, a registered user may redeem SVCoins in exchange for fiat. Referring to
In S6654, the user selects the redeem SVCoin option, and specifies the amount of SVCoins the user seeks to redeem. In embodiments, the user may be requested to provide a digital wallet address, such as a digital wallet address associated with a blockchain digital asset, like ether. In embodiments, the amount of SVCoins may be specified by number of SVCoins, or by an amount of fiat. Since the SVCoins are pegged to the fiat in a stable amount (e.g., 1 SVCoin=1 USD, or 100 SVCoin=1 USD, to name a few), the system can automatically convert the requested amount of SVCoin to fiat, or requested amount of fiat into SVCoin.
In S6656, the digital asset exchange system will analyze and verify that the request can be properly processed. In step S6656-a, the digital asset exchange system, as the SVCoin issuer, may verify that the user has sufficient SVCoin to cover the transaction as well as any transaction fees that may be charged. In embodiments, the digital asset exchange system may perform verification of the SVCoin balance by checking the token balance of the digital asset address against the SVCoin Token ledger as maintained by the digital asset blockchain. For example, a balance for a token issued based on the Ethereum Network may be checked at www.etherscan.io. If the user does not have sufficient SVCoin and/or an insufficient amount for transaction fees and/or provided an invalid digital asset address, to name a few, the transaction may be terminated.
In embodiments, SVCoin transactions may be published and recorded in a SVCoin token side ledger that is separate from an underlying blockchain (e.g., the Ethereum Blockchain). Such a side ledger may be provided using a sidechain, for example, a plasma chain, which is separate from the underlying digital asset blockchain that is maintained on the distributed network. In embodiments, this sidechain is used to record all transactions involving the SVCoin token and is maintained by the token issuer or another trusted entity on behalf of the token issuer. These transactions may then be subsequently published to the underlying digital asset blockchain periodically or aperiodically such that all transactions are publicly viewable and confirmable. In embodiments, with a blockchain supporting shielded transactions, the transactions in the SVCoin token may potentially be shielded and only viewable by authorized token holders. In embodiments, transactions on the sidechain may be consolidated prior to publication on the digital asset blockchain to increase speed of processing and reduce transaction costs.
The use of a sidechain in conjunction with a blockchain can provide certain technical advantages not otherwise available by either alone. For example, since all transactions on the sidechain are inevitably published to the digital asset blockchain, these transaction records enjoy the same benefit of immutability provided to all other transactions on the digital asset blockchain. However, use of a sidechain reduces both transaction costs and transaction times overall. Recording the transactions on the sidechain first can be accomplished more rapidly than transactions that are published directly to the digital asset blockchain, which must be confirmed prior to being added to the digital asset blockchain. In embodiments, the sidechain may simply be a database that records all transactions such that there is no need for miners to verify each transaction, and thus, no need to pay miners for this service. In this case, transaction costs are only incurred for the periodic or aperiodic publication of transfers from the sidechain to the underlying digital asset blockchain.
In embodiments, the database for the SVCoin tokens may be maintained as a separate side chain from the database for each Security token. In embodiments, one or more security tokens may be maintained in the same side chain as the SVCoin tokens, and/or by the same trusted entity system as used to maintain the SVCoin token database.
In S6658, after the digital asset exchange system may confirm that the user has sufficient SVCoin to cover the transaction, as well as any other designated criteria, the digital asset exchange system may initiate the process of redeeming the designated SVCoin.
In S6658-a, the digital asset exchange system redeems the designated SVCoin tokens, including updating the SVCoin token ledger database to reflect the debiting and cancelling of the designated tokens and debiting the corresponding digital wallet address associated with such redeemed SVCoin tokens. In embodiments, this process may be performed by generating a transaction on the digital asset exchange network from a contract digital wallet address or other authorized digital wallet address under the relevant SVCoin smart contract programming, to be sent in S6658-c, discussed below.
In S6658-b, the digital asset exchange system credits the designated fiat funds to a fiat ledger associated with the user account, and debit a corresponding amount of fiat from the SVCoin fiat ledger being held in trust by the exchange.
In S6658-c, the digital assert exchange system publishes to the blockchain network (e.g., the Ethereum Network) the transaction to be recorded by the blockchain network. In embodiments, a transaction fee (such as Gas) may be required by, e.g., a miner, to process and add the requested transaction on the blockchain. In embodiments, the transaction fee may be specified as an amount and/or an amount limit to facilitate the transaction being processed by a miner.
In S6660, the digital asset exchange computer system may send a message to the registered user, and/or the designated digital asset addresses to reflect that the transaction was successfully processed. In embodiments, such messages may include information including: (i) digital asset address; (ii) the amount of tokens redeemed; and/or (iii) the new balances for the digital asset address or digital wallet associated therewith.
In embodiments, a digital asset exchange may employ systems and methods to manage and/or reduce digital asset transaction change. Digital asset transaction change refers to leftover digital asset amounts from transactions in digital asset systems, such as Bitcoin, where the transactions are comprised of one or more digital inputs and outputs. A wallet stores unspent transaction outputs, which it can use as digital inputs for future transactions. In embodiments, a wallet or third-party system may store an electronic log of digital outputs to track the outputs associated with the assets contained in each wallet. In digital asset systems such as Bitcoin, digital inputs and outputs cannot be subdivided. For example, if a first wallet is initially empty and receives a transaction output of 20 BTC from a second wallet, the first wallet then stores that 20 BTC output for future use as a transaction input. To send 15 BTC, the first wallet must use the 20 BTC as an input, 15 BTC of which will be a spent output that is sent to the desired destination and 5 BTC of which will be an unspent output, which is transaction change that returns to the first wallet. A wallet with digital assets stored as multiple digital outputs can select any combination of those outputs for use as digital inputs in a spending transaction.
For transactions involving sending digital assets from exchange wallets to non-exchange wallets (e.g., when a user requests a withdrawal of digital assets from the user's exchange account), a digital asset exchange may employ systems and methods to reduce transaction change, e.g., to avoid a temporary decrease in liquidity due to the unavailability of funds during a transaction confirmation period, to which the change in systems such as Bitcoin is subject.
To manage and/or reduce transaction change, in embodiments, an exchange may maintain wallets containing varying sized digital outputs so that an output or combination of outputs can be selected as digital input for a transaction, where the total input amount can have a size either equal to or greater than but close to the transaction amount. Accordingly, the exchange may employ a wallet balancing module running one or more balancing algorithms on one or more processors to distribute digital assets to wallets in digital outputs of various sizes and various quantities of each size. These output sizes and quantities thereof may be pre-determined and programmed into the wallet balancing module and/or may be adjusted algorithmically to better reduce transaction change in light of actual current or historical exchange transaction activity. Wallet balancing operations may be performed continuously, periodically throughout a day, once a day (e.g., at midnight), once a week, at some other interval, as balancing is required for one or more transactions, and/or as the wallet balancing module determines a wallet imbalance that exceeds a threshold tolerable imbalance. In embodiments, an exchange wallet balancing module may perform balancing operations after receiving a digital asset withdrawal request from a user and before transferring the digital assets to the user.
An exchange may also reduce transaction change by programming multiple outputs for a single transaction. In embodiments, digital asset withdrawals may be processed only at specified times or periodically, e.g., in the morning and in the evening. Such a system may facilitate batch processing of withdrawals using multiple digital transaction outputs. In embodiments, digital asset storage or protection services, such as insurance or storage warranties, may be offered through a digital asset exchange. Transaction insurance or warranties may also be offered, e.g., to guarantee an exchange transaction for a particular volume at a particular price.
In embodiments of a digital asset exchange in accordance with the present invention, one or more types of order books may be used. For example, in embodiments, a digital asset exchange may feature central limit order books that follow a price-time priority model.
In embodiments, a continuous order book and/or auction order book may be used with any pair of digital assets and/or digital asset and fiat currency. For example, in embodiments the following trading pairs and order books may be available:
In the above example, BTC/USD is a pairing of Bitcoin with U.S. dollars, ETH/USD is a pairing of Ethers and U.S. Dollars and ETH/BTC is a pairing of Ethers and Bitcoin.
In embodiments, both a continuous order book and an auction order book may not be available, for example, an auction order book may not be available for an ETH/BTC pairing. In embodiments, however, an auction could be provided based on digital currency to digital currency pairings, such as ETH/BTC. In embodiments, other pairings may also be available such as other digital assets with other fiat currencies, or other digital asset pairs.
In embodiments, a digital asset exchange may operate during limited hours, or may operate 24 hours a day, seven days a week, except for brief maintenance periods.
In embodiments, clients may submit as many orders as desired with any of the execution options described below. Alternatively, in embodiments, the number of orders may be restricted.
In embodiments, a digital asset exchange may be a full reserve exchange in which all orders are fully funded. In full reserve exchange embodiments, a client's outstanding interest on orders books of the digital asset exchange cannot exceed their account balance at any time and all open orders reduce a client's available balance until such orders are fulfilled or canceled. In other embodiments, a digital set exchange may offer margin trading.
In embodiments, a digital asset exchange may support the following order types and execution options:
In embodiments, the digital asset exchange may also support an order type that initiates a block trading workflow to source liquidity for large block quantities.
It will be appreciated that in embodiments, different combinations of order types may be available and in embodiments, additional order types may be available and some order types may not be available. In embodiments, order types may differ for pairings of digital assets and/or fiat currencies.
In embodiments, a digital asset exchange may have a continuous book. The continuous book may support market orders and/or limit orders.
In embodiments, a continuous order book may be implemented, by way of example, in accordance with the following:
1. Alice places a limit order to buy 16.65 BTC at a price of 5885.65 USD.
2. Bob places a limit order to sell 21.84 BTC at a price of 5924.85 USD.
3. Both orders rest on continuous order book.
In embodiments, limit orders have a side, a limit price in fiat (e.g. USD) and a quantity in digital asset (e.g., Bitcoin or Ether). Example:
In embodiments, continuous book limit orders support the following execution options:
Option 1: Standard (Good until canceled)
The order may be filled in part or fully before being booked. The order will rest on the book until complete filled or cancelled.
Option 2: Immediate or Cancel
The order never rests on the book. The order is filled to the extent possible based on existing orders on the order book, and any remainder is cancelled.
Option 3: Market or Cancel
The order rests on the book to add liquidity. The order will be cancelled if any part of it would be filled immediately.
In embodiments, a continuous book may offer market buys. Market buys may be placed with a gross notional value in fiat (e.g., USD). A fee may be deducted from the gross amount. Market buys are filled against resting orders on the book. Any remainder to the order is cancelled when filled. As a circuit breaker, in embodiments, a threshold may be applied to a market buy, e.g., filling up a market buy up to a fixed percentage (e.g., 20%) or an aggregate amount (e.g., x digital assets or y fiat) against the market at time of order, with the remainder of the order being cancelled.
In embodiments, market buys in the continuous book may be implemented, by way of example, in accordance with the following:
1. Charlie wants to buy 5000 USD worth of bitcoin. He places a market buy order that is immediately filled against Bob's resting limit order to sell 21.849 BTC at a price of 5924.98 USD.
2. Charlie receives 0.84177499 BTC which his 4987.50 USD worth of BTC at the current market price of 5924.98 USD. 4968.50 USD is the net notional value of Charlie's market buy, which is the 5000 USD gross notional value of the market buy less his 12.50 USD fee.
3. Bob's limit sell continues to rest on the books with a remaining quantity of 21.007225 BTC.
In embodiments, a continuous book may offer market sells. Market sells are placed with a quantity in digital assets. As a circuit breaker, in embodiments, a threshold may be applied to a market sell, e.g., filing up a market sell up to a fixed percentage (e.g., 20%) or an aggregate amount (e.g., x digital assets or y fiat) against the market at time of order, with the remainder of the order being cancelled.
In embodiments, market sells in the continuous book may be implemented, by way of example, in accordance with the following:
1. David wants to sell 3 BTC at whatever the market price is. He places a market sell order that immediately crosses with Alice's resting limit order to buy 16.65 BTC at a price of 5885.65 USD.
2. David nets 17,612.81 USD form his market sell. 17,656.95 USD less his 44.14 USD fee.
3. Alice's limit buy continues to rest on the books with a remainder quantity of 13.65 BTC.
In embodiments, the priority of matching orders resting on the books may be filled in using price time priority.
In embodiments, priority of matching orders resting on the books filled in using price time priority may be implemented, by way of example, in accordance with the following:
At T1: Alice places a limit order to buy 2 BTC at 5788.52 USD.
At T2: Charlie places a limit order to buy 0.5 BTC at 5788.58 USD
At T3: Bob places a limit order to buy 3 BTC at 5788.52 USD
At T4: David places a limit order to sell 5.25 BTC at 5788.50 USD
David's order then completely fills, crossing first with Charlie then Alice and then partially filling Bob's order, which was placed last time at an acceptable price. Because of price improvement, David's order fills at a higher price than his limit price.
In embodiments, resting limit order could also be filled on a continuous book in price-time priority.
In embodiments, resting limit order filled on a continuous book in price-time priority may be implemented, by way of example, in accordance with the following:
1. At time X+1, Charlie's resting limit buy order for 0.5 BTC at $5,786.55 is filled.
2. At time X, Alice's resting limit buy order for 2 BTC at 5788.52 USD is completely filed.
3. At time X+2, Bob's resting limit buy order for 3 BTC at 5788.52 US is partially filed for 2.75 BTC, 0.25 BTC remains resting on the book.
In embodiments, a digital asset exchange may have an auction order book. In embodiments, the auction order book is blind but the public auction events contain information that allows market participants to understand when there is an imbalance of buy or sell interest. In embodiments, the auction order book supports auction-only (AO) market and limit orders. These orders rest until the auction runs, at which time the orders will be either filled or cancelled. In general, self-trading should not be not allowed. An incoming order that would cross with a resting order on the auction book from the same account is cancelled.
In embodiments, a digital asset exchange in accordance with the present invention may conduct auctions for certain trading pairs periodically (e.g., every day (including weekends and holidays)) and/or aperiodically (e.g., a specific announced times, which may be irregular). Such auctions offer a technical advantage of fostering moments of elevated liquidity and price discovery.
In embodiments, auctions may be implemented, by way of example, in accordance with the following representative schedules:
In embodiments, the auction order book may have time constraints, so that auction order windows may only be placed within a specified time window. Thus, the auction order book for a given auction may open a set time period in advance of the auction (e.g., 8 hours before the auction begins), as the opening of the auction order window. For example, if an auction is set to begin at 4:00 p.m. Eastern Standard Time, the Auction could begin at 8:00 a.m. Eastern Standard Time, as illustrated above.
In embodiments, once an auction window opens, auction-only order may not be cancelled after the final indicated price has been published, e.g., one minute before the auction runs. In the above example, that would be 3:59 p.m.
In embodiments, auction-only orders may be accepted up until the auction runs.
In embodiments, auction only orders placed outside of the auction order window may be rejected.
In embodiments, at a set time period before the auction begins, e.g., 10 minutes, an indicative auction event window may be opened. An indicative auction event is a simulation of what would happen if the auction ran at that point in time. In embodiments, an indicative auction uses the same pricing algorithm as the final auction price determination. In embodiments, although the auction order book is blind, indicative auction events show when there is a buy/sell interest imbalance so participants may adjust their orders.
During an indicative auction window, indicative results may be published at set time intervals, such as once a minute, twice a minute, four times a minute, to name a few, and will continue to be published until the indicative auction window closes. In embodiments, the indicative auction window will not close until the auction is run.
In the example above, for an auction beginning at 4:00 p.m. Eastern Standard Time, an indicative auction window may be opened 10 minutes prior at 3:50 p.m. Eastern Standard Time. Indicate results are published once a minute starting at the opening of the indicative auction window at 3:50 p.m. Eastern Standard Time, 10 minutes before the 4:00 p.m. auction. Starting at one minute before the auction window, 3:59 p.m. Eastern Standard Time, the indicative price may be published every 15 seconds. An indicative auction window will close when the auction window opens at 4:00 p.m., with the last indicative price published at 3:59:45 p.m. Eastern Time. Of course, other time periods can be used to set the opening and closing of the indicative auction windows and one or more intervals of publication can be used in that windows.
In embodiments, the final auction run at a final auction run time, e.g., 4:00 p.m. Eastern Standard Time in the above examples. In embodiments, at the final auction run time, no more orders on the continuous or auction order books are accepted. In embodiments, the midpoint of the best bid and best ask from the auction price will be taken as the auction collar price. In embodiments, an index value may be taken as the auction collar price.
The final auction price for every auction is established as the price that executes the greatest aggregate quantity and minimizes the imbalance between buy and sell orders across both the auction and continuous order books. The imbalance is defined as the absolute value of the difference between total buy orders and total sell orders at a given price across both the auction and continuous order books. Other pairings and timings may be used in accordance with the embodiments of the present invention.
Within this auction design, the market is open to accepting orders until the time the auction algorithm runs.
In embodiments, limits order may be placed in auctions. Typically, limit orders have a side (e.g., buy or sell), a limit price in fiat (e.g., USD), and a quantity in digital asset (e.g., BTC).
In embodiments, once a limit order is placed for an auction, the order will rest until the auction runs and the auction window closes.
In embodiments, if the auction succeeds, limit orders will be filled based on:
1. Price-time priority
2. If the auction price is equal to the limit price or a price improvement (auction price is lower than the limit buy order or higher than the limit sell order).
In embodiments, auction-only market buys and sells are like their continuous book counterparts except that they will rest on the book until they are cancelled or the auction runs. If the auction succeeds, auction-only market orders may be filled according to time priority, unlike in the continuous book where market orders are filled immediately. Although uncommon, auction-only market orders may be partially filled or even unfilled. This can happen when the auction has an unusually large buy-sell interest imbalance.
In the example below, there are two prices, $99 and $100, that will execute the greatest aggregate quantity across both the auction and continuous order books, which is 30. However, at the $99 price, the imbalance between buy and sell orders is greater than it is at the $100 price. As a result, the final auction price will be $100 because this price executes the greatest aggregate quantity and minimizes the imbalance between buy and sell orders across both the auction and continuous order books.
In embodiments, all limit orders at the same specified price are treated equally and executed in the order in which they were received. Partially filled resting limit orders retain their priority until canceled.
In embodiments, a Walrasian auction that seeks to identify the price with the greatest aggregate quantity may be employed. In such embodiments, each possible price is tested summing up buy and sell quantities. The price that would execute the greatest possible “wins” may be selected. In embodiments, in the event of a tie between two or more prices that would execute the same quantity, the exchange may select the price that minimizes the imbalance between the buy and sell orders across the auction order book and/or the auction and continuous order books. In embodiments, in the event of a tie between two or more adjacent prices that would execute the same quantity, the auction price may be the midpoint of the two adjacent prices. In embodiments, in the event of a tie between two or more adjacent prices that would execute the same quantity, the auction price may be the price that is closest to the collar price. In the event that the two prices are equally close to the collar price, the auction price may be the midpoint of the two prices.
In embodiments, the auction price is established as the price that executes the greatest aggregate quantity (i.e. auction quantity) across both the auction-only and continuous order books. It is possible that there is not an exact match between buy and sell interest at this price, and so some orders will partially filled or not be filled at all. Auction-only market orders may be filled by time priority. To avoid time conflicts, the market may be paused for a brief period (e.g., milliseconds) while the final price, quantity, and controls are calculated.
In embodiments, in order to provide the most liquidity to the marketplace, resting limit orders on the continuous order book may be used in the auction price and quantity calculations. In embodiments, for a resting limit order to be eligible for inclusion, the auction price must be equal to or better than the resting limit price (less than or equal to for bids, or greater than or equal to for asks). Resting limit orders on the continuous order book may be filled according to time priority and are subject to improvements in price.
In embodiments, the auction may fail if an equilibrium cannot be achieved, for example, if the auction quantity is zero. A zero auction quantity could occur when no auction orders are received, or if only one-way auction orders are received (e.g., buy only or sell only orders). In embodiments, a collar may also be placed on the auction. For example, a collar may be placed on the auction price, by using fixed percentage (e.g., 1 percent, 5 percent, 10 percent) of a benchmark against the continuous book price at given time period or set of time period. In embodiments, the benchmark could be a midpoint of the spot price of the continuous book price at the given time period—e.g., auction price. In embodiments, the benchmark could be a weighted average (such as a time weighted average, volume weighted average, or time and volume weighted average) of the continuous book during a pre-set window (e.g., 10 minutes for before auction, 1 hour before the auction, 12 hours before the auction, 24 hours before the auction, to name a few).
In embodiments, digital asset exchange computer system 3230 may set a collar for the auction trade, including a collar minimum and a collar maximum. First, the digital asset exchange computer system 3230 may access, from at least a first database stored on a computer readable medium operatively connected to the digital asset computer system, pricing data associated with the first pair at a predefined time associated with a time of the auction trade order. In embodiments, pricing data can include a spot price. In embodiments, a pricing data may be based on the last transaction immediately prior to the auction. In embodiments, a pricing data may be based on an average of the most recent bid/ask price for the digital asset. In embodiments, the pricing data may be set based on a blended digital asset price as discussed elsewhere herein. For example, a single exchange digital asset price could be determined based on a volume weighted average and/or time weighted average of recent digital asset pricing. In embodiments, a blended digital asset price may be based on a pricing from digital assets taken from a plurality of exchanges (such as qualified exchanges). In embodiments, pricing data may be a blended digital asset price comprising a plurality of digital asset exchanges (e.g., 4) executing trade data for a fixed period of time (e.g., a 10 minute period) using a volume weighting with a fixed percentage (e.g., 5%) of the highest priced trades and a second fixed percentage (e.g., 5%) of the lowest priced trades removed. The digital asset exchange computer system 3230 may calculate a collar minimum for the auction based on the pricing data less an amount equal to a first percentage of the pricing data, and a collar maximum for the auction based on the pricing data plus an amount equal to the first percentage of the pricing data. Thus, a collar may be based on a spot price at the time for the auction, plus or minus a defined range, such as a percentage of the spot price or other pricing data. In embodiments, the collar could be set using percentages such as 1%, 2%, 3%, 5%, 10% of the spot price or other pricing data, to name a few. By way of illustration, if a 5% collar is used with a spot price of 1 BTC=USD$10,000, the collar would be set at between USD$9,500 and USD$10,500.
Accordingly, in embodiments, in substep S5604a, the digital asset exchange computer system 3230 may retrieve a current pricing information (e.g., bid/ask price) from continuous trading order book 5702a associated with a first digital asset pairing and establish a spot price for the first digital asset pairing. As noted above, in embodiments, the spot price may be the average of the current bid/ask price or may be the price used in the last transaction in the continuous trading book, to name a few. In embodiments, the spot price may be a blended digital asset price, in which one or more different order books from one or more digital asset exchanges or index databases may be required to be access to obtain such price. In embodiments, the blended digital asset price may be obtained by being calculated and/or by accessing a blended digital asset price database (not shown). In substep S5604b, the digital asset exchange computer system may establish the collar, for example, based on adding and/subtracting a fixed percentage of the spot price to the spot price as discussed above, for example.
In embodiments, the collar may be a blended digital asset price consisting of 4 digital asset exchanges' executed trade data for a 10 minute period volume weighted with 5% of the highest priced trades and 5% of the lowest priced trades removed.
In embodiments, the digital asset exchange computer system 3230 may determine whether the price in the auction is within the limits of the collar determined above (e.g., at or above the collar minimum and at or below the collar maximum).
In embodiments, if the final auction price falls outside the collar, the auction may also fail.
In embodiments, in the event auction fails, the exchange may cancel all the auction-only orders unfilled, close the auction and/or publish as market data for the auction that it failed, either with or without a reason for such failure. In embodiments, where the auction fails because the final auction price falls outside the collar, the price and quantity of the auction that would have otherwise been executed may be published as part of the market data, with an indication that the auction failed.
In embodiments, if the event auction succeeds, the digital asset exchange may fill all eligible auction only and/or continuous book order by strict time priority. In embodiments, continuous book orders may not be filled. The digital asset exchange may also notify the market participants whose orders were filled, such as through the alert system discussed herein. In embodiments, the digital asset exchange may also notify the market participants whose orders were not filled, such as through the alert system discussed herein. The digital asset exchange may also cancel all remaining unfilled and partially filled auction-only orders to the extent such partially filled auction-only orders remain unfiled. The digital asset exchange may then close the auction order book for this auction window. In embodiments, the digital asset exchange may published a market data auction event showing the outcome of the auction, through, e.g., an API or other electronic publication. In embodiments, historical trades may show a bulk trade event for the auction volume. In embodiment, normal operations, such as continuous order book trading, may resume once the auction process is completed.
In embodiments, in addition to publishing the final auction price and whether or not it failed, the collar price may also be published as part of an API or other electronic publication.
In embodiments, marketplace controls may be put in place in an effort to foster a fair and orderly market. Examples of marketplace controls can include one or more of the following:
In embodiments, other controls may be put in place consistent with the present invention.
A digital asset exchange may, in embodiments, declare a transaction null and void when it is determined to be clearly erroneous.
Errors or disruptions may occur on an exchange during the order entry, order matching, or trading process. In embodiments, if any such errors or disruptions occur, the digital asset exchange may cancel any order and/or reverse any trade, in whole or in part.
In embodiments, the results of each auction may be made available as pricing data for a digital asset though, e.g., an API. In general, an API is a set of routines or subroutines, protocols and tools for building software applications, which facilitate communications between various software components. An API may be for a web-based system, operating system, database system, computer hardware or software library. An API specification can take many forms, but often includes specifications for routines, data structures, object classes, variables or remote calls. POSIX, Windows API and ASPI are examples of different forms of APIs. Documentation for the API is usually provided to facilitate usage.
In embodiments, auction order book data may not be publically available. In embodiments, auction order book data may be available with a time delay after each auction completes through, e.g., an API. In embodiments, auction data, like other digital asset pricing data, may be used an input to a blended digital asset price, or other index or benchmark.
In embodiments, a digital asset exchange may publish market data using APIs, such as public REST APIs and private REST APIs. Public REST APIs may provide market data such as: current order book, recent trading activity and/or trade history, to name a few. Private REST APIs allows participants to manage both orders and funds, by for example, placing and/or cancelling orders, viewing active orders, viewing trading history and/or trade volume, retrieving available balances, to name a few.
In embodiments, individual auction-only and continuous order book market participants may be notified their order has been filled via an email, sms, push notification, or other message and/or a status update on their activity feed. In embodiments, the same alerting system may be used for continuous order book execution.
In a step S3152, the exchange computer system may receive from the digital asset buyer authorization to transfer funds from the digital asset buyer's account in an amount based at least in part upon the accepted digital asset price.
In a step S3156, the exchange computer system may receive from a bank, a notification of funds transferred to an exchange bank account from the digital asset buyer.
In a step S3158, the exchange computer system may provide to a digital asset seller a notification of funds transferred to the exchange bank account from the digital asset buyer.
In a step S3160, the exchange computer system may provide to a digital asset seller, an instruction to transfer digital assets to a digital wallet associated with the seller in an amount based at least in part upon the accepted digital asset quantity. In embodiments, the digital asset seller may transfer digital assets to a digital wallet associated with (e.g., owned by and/or operated by) the exchange. The exchange may hold such funds in escrow until the buyer's payment is received, e.g. into a bank account (for fiat currencies) or into a digital wallet (for other digital assets).
In a step S3164, the exchange computer system may receive from the digital asset buyer a notification of received digital assets from the digital asset seller.
In a step S3166, the exchange computer system may provide to the bank, an instruction to release the digital asset buyer's funds to the digital asset seller.
In another embodiment, the exchange can act as a counter-party to transactions where digital assets are bought and/or sold for a differently denominated digital asset or a fiat currency. In embodiments, the system illustrated in
The present invention relates to methods, systems and program products for lending digital assets, such as crypto currency, and related products.
The present invention creates a process where digital assets may be lent for a set period of time (“loan duration” or “duration”) based on an agreed interest rate (“interest rate”) through a competitive bidding process. In embodiments, rather than using an agreed interest rate, an agreed payment amount for the loan may be used. In embodiments, examples of loan duration may include, e.g., 1 day, 1 week, 2 weeks, 1 month, 3 month, 6 month, 12 month, periods to name a few. Other loan durations may also be selected consistent with exemplary embodiments of the present invention.
In order to define a market for loaning of digital assets, one or more order books may be set up on a digital asset exchange, such as Gemini, Coinbase, to name a few. In embodiments, a regulated digital asset exchange may be preferred. In embodiments, the digital asset exchange, or other platform, may be maintained by as a trust company, a regulated trust company, a bank, a broker dealer, or some other form of entity, to name a few. In embodiments, the computer systems operated by entities involved in the process may be provided at the same data center and/or may have fast interconnections to provide for more efficient and timely transactions. In embodiments, a FIX order message system, cross connect message system and/or a third party order management system provider, to name a few, may be used to send and enter orders.
In embodiments, the use of surveillance technologies, such as NASDAQ Smart surveillance technologies, such as used by Gemini, is also preferred.
In embodiments, order books may take various forms, such as continuous order books, auction order books, block trading order books, to name a few. For a detailed description of such order books, please see U.S. patent application Ser. No. 15/920,042, filed Mar. 13, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR VERIFYING DIGITAL ASSETS HELD IN A CUSTODIAL DIGITAL ASSET WALLET, U.S. patent application Ser. No. 15/973,175, filed May 7, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS and U.S. patent application Ser. No. 15/973,140, filed May 7, 2018 and entitled SYSTEMS, METHODS, AND PROGRAM PRODUCTS FOR EXCHANGING DIGITAL ASSETS FOR FIAT AND/OR OTHER DIGITAL ASSETS, which are hereby incorporated by reference as if fully set forth herein.
In embodiments, a digital asset computer system may be used to lend digital assets. In embodiments, digital assets may be lent via a digital asset computer system using a continuous order book. In other embodiments, digital assets may be lent via a digital asset computer system using an electronic auction. In alternate embodiments, digital assets may be lent via a digital asset computer system using a block trade order book. In embodiments an over the counter (OTC) order book may be used.
In embodiments, digital assets may be lent via a digital asset computer system using a continuous order book.
In a step S6101, the digital asset computer system receives, a deposit of digital assets to at least a first respective exchange account, from a first digital asset account, through use of a first digital asset account identifier associated with the first respective exchange account, where the deposit is recorded on the decentralized electronic ledger.
In a step S6102, the digital asset computer system provides a loan order database associated with a first digital asset and a first duration period, stored on the non-transitory computer-readable memory comprising at least a digital asset borrow order information comprising for each borrow order: borrow order identification information, borrow order digital asset quantities and corresponding borrow order interest rates and digital asset lend order information comprising for each lend order: lend order identification information, lend order digital asset quantities and corresponding lend order interest rates. In embodiments, the borrow order information and/or lend order information may include user identifications information, a time stamp, a credit score associated with the borrower or lender, margin information related to the borrower or lender and account balance information, to name a few.
In a step S6103, the digital asset computer system provides an electronic ledger comprising digital asset account balance data for each of the exchange accounts.
In a step S6104, the digital asset computer system receives, from a first user electronic device associated with a first user associated with a first exchange account, a first electronic digital asset borrow order comprising first borrow order information comprising a first borrow order digital asset quantity and a corresponding first borrow order interest rate.
As shown in
In a step 6106, the digital asset computer system receives, from a second user electronic device associated with a second user associated with a second exchange account, a first electronic digital asset lend order comprising first lend order information comprising a lend order digital asset quantity from the deposit of digital assets and a corresponding lend order interest rate. In embodiments, step S6106 may occur either before or after step S6104. Thus, by way of example, in embodiments, a lend order may be received before a borrow order or a borrow order may be received before a lend order. Similarly, in embodiments, more than one lend order may be received before more than one borrow order, and vis-versa. Further, in embodiments, more than one lend order and/or more than one borrow order may be received in any order prior to matching in Step S6109, as discussed below. Thus, in embodiments, the digital asset system may store the first electronic asset lend order in the loan order database in step S6105.
In a step S6107, the digital asset computer system verifies that the first digital asset account balance data indicating a first digital asset account balance of a lender digital asset account associated with the second exchange account at least equals the lend order digital asset quantity.
In embodiments, the digital asset computer system may allow lenders to lend assets on margin. For example, the lender may be permitted to lend digital assets that are not already included in its account on the lender. In such case, the digital asset computer system may verify that the lender has sufficient assets to cover the value of the digital assets to be lent, wherein the assets may include fiat, digital assets or any other asset. In embodiments, the digital asset computer system, may verify the lender has sufficient credit, even without holding sufficient assets in the digital asset computer system, to go forward with the transaction.
In a step S6108, the digital asset computer system stores the first electronic digital asset lend order information in the loan orders database. In the case where the lend order is received before the borrow order, the first electronic digital asset borrow order may be stored in the loan order database at step S6108.
In embodiments, the digital asset computer system may receive a plurality of electronic digital asset lend orders and a plurality of electronic digital asset borrow orders. In embodiments the electronic digital asset lend order information and the electronic digital asset borrow order information from the plurality of borrow orders and lend orders is stored in the loan order database.
In a step S6109, the digital asset computer system matches the first electronic digital asset loan order with the first electronic digital asset lend order. In embodiments, where digital asset computer system may receive a plurality of electronic digital asset lend orders and a plurality of electronic digital asset borrow orders, a borrow order may be matched with one or more lend order and/or a lend order may be matched with one or more borrow orders.
In a step S6110, the digital asset computer system generates first machine-readable transaction instructions for a first loan transaction having a first transaction digital asset quantity satisfying the first electronic digital asset borrow order and the first electronic digital asset lend order.
In a step S6111, the digital asset computer system executes the first machine-readable transaction instructions by updating the electronic ledger by decreasing, by the first transaction digital asset quantity, the first digital asset account balance data corresponding to the lender digital asset account and increasing, by the first transaction digital asset quantity, second digital asset account balance data corresponding to a first borrower digital asset account associated with the first exchange account.
In embodiments, the digital asset computer system may send electronic transfer confirmations to one or both of the first and second user electronic devices at the completion of the transaction. The digital asset computer system may also send electronic transaction confirmations to a computer system associated with an institution associated with the exchange institutional account.
In embodiments the interest rate or lending rate may be used as a benchmark for a financial instrument. In embodiments, the financial instrument may be an exchange traded product. In embodiments the digital asset may be a derivative product of a type selected from the group consisting of: an exchange traded derivative product, a fund, a company, an exchange traded fund, a note, an exchange traded note, a security, a debt instrument, a convertible security, an instrument comprising a basket of assets including one or more digital math-based assets and an over-the-counter product, to name a few.
In embodiments, the first digital asset may be a digital math-based asset. In embodiments the digital asset may be Bitcoin, Ether, Litecoin, Bitcoin Cash or Zcash, to name a few. In embodiments, the digital asset may be a token, such as a stable value token.
In embodiments, the user authentication data may comprise a username and password. The user authentication data may also comprise multi-factor authentication data.
In embodiments, digital assets may be lent via a digital asset computer system using an auction.
In a step S6200, a digital asset computer system generates a first electronic auction loan order book for the first digital asset for the first duration, on or after a first time associated with opening the electronic auction until a second time associated with closing the electronic auction. Part of this step includes a step S6201, of a digital asset computer system receiving a first plurality of auction loan orders associated with the first digital asset from a first plurality of user devices associated with a first plurality of users wherein each auction loan order may include characteristics representing the asset type of the first digital asset, the respective quantity of units of the first digital asset, a respective side of the transaction (borrow or lend), the duration of the loan and a respective interest rate on the loan. Another part of this step includes a step S6202, of a digital asset computer system verifying that each of the first plurality of auction loan orders is qualified based on the steps of the digital asset computer system verifying that the order characteristics of the respective loan order are valid auction order characteristics and, in the cases where the side of the transaction is lend, the digital asset computer system verifying that the respective user has sufficient amounts of the first digital asset to cover the first auction loan order if filled in full.
If step S6202 results in successful verification, the next step of step S6200 is step S6203, comprising a first step S6204 of the digital asset computer system updating each respective lender user account associated with each respective lender to set aside sufficient reserves in the first digital asset, sufficient to cover each respective auction loan order which has been successfully verified if filled in full and the step S6205, of the digital asset computer storing in the first electronic auction loan order book (on or more computer readable systems) each representative auction loan order which has been successfully verified.
In embodiments, in optional step S6206, the digital asset computer system may publish, at set time intervals starting with a third time and continuing until the second time, respective indicative results of the first auction loan order book if the auction were to close at the end of each respective time interval. The respective indicative results may comprise a respective indicative interest rate which is calculated by the digital asset computer system determining using the first auction loan order book, a respective indicative auction interest rate in terms of the first digital asset that will execute the greatest quantity of the first digital assets being transacted for the interest rate and in the case where more than one respective indicative auction interest rate is identified as having the same greatest quantity of the first digital assets being transacted, selecting as the respective indicative auction interest rate based on the midpoint of the two adjacent indicative auction interest rates identified for the fourth time. In embodiments, other tie breaking criteria may be used to select the indicative auction interest rate, exampled of which are discussed below. The respective indicative results also comprise a respective auction quantity, which is determined by the digital asset computer system, as the quantity of units of the first digital asset to be loaned at the respective indicative interest rate as of the fourth time.
In step S6207, the digital asset computer system closes the first auction loan order book, at the second time, and stops accepting new auction loan orders to be added to the first auction order book
In step S6208, the digital asset computer system calculates final results of the first auction loan order book. The final results comprise a final auction price interest rate at the second time which is calculated by the digital asset computer system determining, using the first auction loan order book at the second time, a final auction interest rate in term of the first digital asset that will execute the greatest quantity of first digital assets being transacted and in the case where more than one respective final auction interest rate is identified as having the same greatest quantity of the first digital assets being transacted, selecting as the respective final auction interest rate based on the midpoint of the two adjacent indicative auction interest rates identified for the fourth time. In embodiments, when the more than one respective final auction interest rate is identified as having the same greatest quantity of the first digital assets being transacted, the final auction interest rate may be selected by some other tie breaking criteria, including lowest imbalance, the lower rate, the higher rate, the rate closest to the U.S. treasury rate for the same duration, the rate closest to a benchmark crypto asset rate at the same duration. the rate closer to LIBOR at the same duration, the rate closer to the continuous order book at the time of the auction, and the rate closer to a predetermined index rate at the time of the auction, to name a few. The final results also comprise a final auction quantity, which is determined by the digital asset computer system, as the quantity of units of the first digital asset which match the final auction interest rate as of the second time.
In embodiments, the order book data may be used to create a benchmark to be used in a financial product. In embodiments, the financial product may be, by way of illustration, an exchange traded product, a fund, an exchanged traded note, an exchange traded product, a call, a put, an option, an exchange traded derivative product, a fund, a company, an exchange traded fund, a note, an exchange traded note, a security, a debt instrument, a convertible security, an instrument comprising a basket of assets including one or more digital math-based assets and an over-the-counter product, an interest rate future, a future on swaps, an option on interest rate futures, an interest rate swap, a bond forward, a floating rate agreement (FRA), a structured, product such as a note bond or bill, a foreign exchange future, a foreign exchange forward, a foreign exchange listed option, a currency linked note and a currency swaption, to name a few.
In embodiments, the first digital asset may be a digital math-based asset. In embodiments the digital asset may be Bitcoin, Ether, Litecoin, Bitcoin Cash or Zcash. In embodiments, the digital asset may be a token, to name a few.
In embodiments, other forms of order books may be used to lend digital assets, such as block trade order books and limited order books, to name a few. In embodiments, requests for quotes (RFQs) or OTC voice transactions may be used to lend digital assets.
In embodiments, a method for lending digital assets by a digital asset computer system includes: (a) providing, by the digital asset computer system comprising one or more computers, the digital asset computer system being operatively connected to a decentralized digital asset network that uses a decentralized electronic ledger in the form of a blockchain maintained by a plurality of physically remote computer systems to track at least one of asset ownership or transactions in a digital asset system, one or more exchange account databases stored on non-transitory computer-readable memory and comprising for a plurality of exchange accounts the following information: (i) digital asset account information for a respective exchange account; (ii) user authentication data; (b) receiving, by the digital asset computer system, a deposit of digital assets to at least a first respective exchange account, from a first digital asset account, through use of a first digital asset account identifier associated with the first respective exchange account, where the deposit is recorded on the decentralized electronic ledger; (c) providing, by the digital asset computer system, a loan order database associated with a first digital asset and a first duration period, stored on the non-transitory computer-readable memory comprising at least the following information: (i) digital asset borrow order information comprising for each borrow order: borrow order identification information, borrow order digital asset quantities and corresponding borrow order interest rates; (ii) digital asset lend order information comprising for each lend order: lend order identification information, lend order digital asset quantities and corresponding lend order interest rates; (d) providing, by the digital asset computer system, an electronic ledger comprising, for each of the plurality of exchange accounts, digital asset account balance data; (e) receiving, by the digital asset computer system from a first user electronic device associated with a first user associated with a first exchange account, a first electronic digital asset borrow order comprising first borrow order information comprising a first borrow order digital asset quantity and a corresponding first borrow order interest rate; (f) storing, by the digital asset computer system in the loan orders database, the first electronic digital asset borrow order information; (g) receiving, by the digital asset computer system, from a second user electronic device associated with a second user associated with a second exchange account, a first electronic digital asset lend order comprising first lend order information comprising a lend order digital asset quantity from the deposit of digital assets and a corresponding lend order interest rate; (h) verifying, by the digital asset computer system, that first digital asset account balance data indicating a first digital asset account balance of a lender digital asset account associated with the second exchange account at least equals the lend order digital asset quantity; (i) storing, by the digital asset computer system in the loan orders database, the first electronic digital asset lend order information; (j) matching, by the digital asset computer system, the first electronic digital asset loan order with the first electronic digital asset lend order; (k) generating, by the digital asset computer system, first machine-readable transaction instructions for a first loan transaction having: (i) a first transaction digital asset quantity satisfying the first electronic digital asset borrow order and the first electronic digital asset lend order; and (l) executing, by the digital asset computer system, the first machine-readable transaction instructions by updating the electronic ledger according to the following steps: (i) decreasing, by the first transaction digital asset quantity, the first digital asset account balance data corresponding to the lender digital asset account; and (ii) increasing, by the first transaction digital asset quantity, second digital asset account balance data corresponding to a first borrower digital asset account associated with the first exchange account. The method of claim 1, wherein the first digital asset is a digital math-based asset.
In embodiments, the first digital asset may be one or more of Bitcoin, Ether, Litecoin, Bitcoin Cash, Zcash or a token.
In embodiments, a method for conducting an electronic auction to loan a first digital asset for a first duration, on a digital asset computer system, includes: (a) on or after a first time associated with opening the electronic auction until a second time associated with closing the electronic auction, generating, by the digital asset computer system, a first electronic auction loan order book for the first digital asset for the first duration, comprising: (i) receiving, by a digital asset computer system from a first plurality of user devices associated with a first plurality of users, a first plurality of auction loan orders associated with the first digital asset, wherein each auction loan order specifies order characteristics comprising: (1) the first digital asset as digital asset type; (2) a respective quantity of units of the first digital asset; (3) a respective side of the transaction, where the side is either borrow or lend; (4) the first duration as the duration for the loan; and (5) a respective interest rate on the loan; (ii) for each of the first plurality of auction loan orders, verifying, by the digital asset computer system, each respective first auction loan order is qualified, based on the steps of: (1) verifying, by the digital asset computer system, the order characteristics of the respective loan order are valid auction order characteristics; (2) in the case where the side of the transaction is lend, verifying, by the digital asset computer system, the respective user has sufficient amounts of the first digital asset to cover the first auction loan order if filled in full; (iii) upon successful verification of each respective auction loan order in step (a)(ii), the steps of: (1) updating, by the digital asset computer system, each respective lender user account associated with each respective lender to set aside sufficient reserves in the first digital asset, sufficient to cover each respective auction loan order which has been successfully verified if filled in full; and (2) storing in first electronic auction loan order book, by the digital asset computer system on one or more computer readable mediums, each respective auction loan order which has been successfully verified; (b) starting with a third time and continuing until the second time, electronically publishing, by the digital asset computer system, at set time intervals between the third time and the second time, respective indicative results of the first auction loan order book if the auction were to close at the end of each respective time interval, wherein the respective indicative results comprise: (i) a respective indicative interest rate, which is calculated, as of a respective fourth time, by: (1) determining, by the digital asset computer system, using the first auction loan order book, a respective indicative auction interest rate in terms of the first digital asset that will execute the greatest quantity of the first digital assets being transacted for the interest rate; and (2) in the case where more than one respective indicative auction interest rate is identified as having the same greatest quantity of the first digital assets being transacted, selecting as the respective indicative auction interest rate by applying the following order of priority: (A) the midpoint of the two adjacent indicative auction interest rates identified for the fourth time; and (ii) a respective auction quantity, which is determined by the digital asset computer system, as the quantity of units of the first digital asset to be loaned at the respective indicative price interest rate as of the fourth time; (c) at the second time, closing the first auction loan order book, by the digital asset computer system, and stop accepting new auction loan orders to be added to the first auction order book; (d) after step (c), calculating, by the digital asset computer system, final results of the first auction loan order book, wherein the final results comprise: (i) a final auction price interest rate at the second time, which is calculated by: (1) determining, by the digital asset computer system, using the first auction loan order book at the second time, a final auction interest rate in term of the first digital asset that will execute the greatest quantity of first digital assets being transacted; and (2) in the case where more than one respective final auction interest rate is identified as having the same greatest quantity of the first digital assets being transacted, selecting as the respective final auction price interest rate by applying the following order of priority: (A) the midpoint of the two adjacent indicative auction interest rates identified for the fourth time; and (ii) a final auction quantity, which is determined by the digital asset computer system, as the quantity of units of the first digital asset which match the final auction interest rate as of the second time; and (e) publishing, by the digital asset computer system, for the first auction loan order book, auction results comprising: the first digital asset, the first duration, the final auction interest rate and final auction quantity.
In embodiments, the first digital asset may be one or more of a digital math-based asset, Bitcoin, Ether, Litecoin, Bitcoin Cash, a token and Zcash.
In embodiments, the loan may be collateralized by a stable value digital asset (e.g. Gemini Dollar, TrueUSD, USD Tether, Paxos Standard, and/or Bitcoin Air, to name a few) a fiat backed digital asset (e.g. Libra), and/or a commodity-backed digital asset (e.g. Digix Gold Tokens).
In embodiments, the third time is 10 minutes prior to the second time.
In embodiments, the plurality of fourth times are one minute apart from each other.
In embodiments, digital assets held in, e.g., a custodial account may be used in a return swap. In a return swap, a return on a first asset may be swapped or exchanged for the return on a second asset for a period of time. Conventionally, the owner of an asset with a volatile return will swap or exchange this return for a less volatile return.
In the context of digital assets, technological challenges are created due to the nature of the digital assets, being tied to a blockchain, and having high level of volatility.
In embodiments, in a step S6300, a digital asset computer system that includes one or more computer, provides an electronic ledger that includes user account information associated with each user of a plurality of users. The user account information includes at least user identification information and user collateral information indicating a value of collateral associated with each user of the plurality of users. In embodiments, the user collateral information may include a value of digital assets in accounts associated with the user, a quantity of digital assets in accounts associated with the user, a value of fiat in accounts associated with the user and/or a value of other assets in accounts associated with the user, to name a few. In embodiments, the user account information may also include obligation information associated with each user's payment obligations to others.
As step S6301, the digital asset computer system provides to a first user device associated with a first user and a second user device associated with a second user, swap transaction information that includes details regarding the swap. In embodiments, the swap transaction information includes swap information, a swap duration, at least one fixing date, and at least one benchmark rate. In embodiments, the swap information identifies the assets involved in the swap and preferably includes at least one digital asset and may include another digital asset, fiat, or any other asset, to name a few. In embodiments, the at least one fixing date is a date on which an agreed to interest rate, discussed below, is applied to determine the payment owed on both sides of the swap. In embodiments, there may be additional fixing dates which may apply to one or both sides of the swap. In embodiments, the swap information may also include a swap quantity which identifies the quantity of assets that are involved in the swap. In embodiments, each swap may include a quantity of one with users entering into multiple swaps if they wish to swap quantities of more than one.
In step 6302, the digital asset computer system receives from a first user device, associated with the first user of the plurality of users, swap bid information including first user side information and a first interest rate. In embodiments, the first user side information indicates whether the first user is buying protection or selling protection in the swap. Users who are buying protection are generally trading the return on a digital asset such as bitcoin which is unknown, for example, for another predetermined return. In embodiments, a benchmark rate such as LIBOR may be used as a basis for the predetermined return. In embodiments, the predetermined return may be based on LIBOR plus some additional percentage. The two returns are swapped for the swap duration. In embodiments, the first interest rate is the first user's proposal for an interest rate and may be expressed in terms of a benchmark rate (LIBOR, for example) plus a predetermined percentage. This is the rate which the protection buyer would like to get. In embodiments, the first interest rate may be based on a notional value of the assets relative to each other. In embodiments, for example, where the swap is bitcoin for U.S. dollars, the notional value of a bitcoin in U.S. dollars is $10,000. The return rate may be set at a percentage that is based on the performance of bitcoin. In this case, the owner of a bitcoin may exchange the potential return on a bitcoin for the swap duration for a set return rate, for example 10% of the notional value of the bitcoin. In embodiments, as noted above, the interest rate may be set as a percentage of a benchmark rate or a benchmark rate plus a percentage. In such a case, the bitcoin owner is referred to as a buyer of protection.
In step S6302a, the digital asset computer system receives, from the second user device, associated with the second user of the plurality of users a swap ask request including second user side information and a second interest rate. In embodiments, the second user side information indicates whether the second user is buying protection or selling protection. The second interest rate is the interest rate proposed by the second user for the swap. In embodiments, the second interest rate may be presented as a benchmark rate plus a predetermined percentage. In embodiments, the benchmark rate is one of the first benchmark rate and the second benchmark rate. Where the second user is a protection seller, the second interest rate is the rate which the second user is willing to pay in exchange for the potential return of the protection buyer's asset.
At step S6303, the digital asset computer system calculates margin requirements based on margin considerations. The margin requirements apply to both the first user and the second user (buyer and seller). In embodiments, an initial margin requirement is based on the margin considerations, including the swap pair information, continuous order book market data and/or one of more reference indexes. In embodiments, both the protection buyer and protection seller must provide sufficient collateral to cover at least a portion of the total value of the swap, which corresponds to the initial margin.
At step S6304, the digital asset computer system verifies that the value of collateral associated with each of the first user and the second user is equal to or greater than the initial margin requirement.
As shown in
At step S6306, the digital asset computer system matches the first user side information with the second user side information where a match is achieved when the first user side information indicates a side opposite that of the second user side information.
At step S6306a, the digital asset computer system matches the first interest rate with the second interest rate where a match is achieved when the first interest rate is the same as the second interest. In embodiments, if there is no match, the digital asset computer system may continue to wait until there is a match, or at some point in time (as may be defined by the system) terminate the process.
At step S6307 the digital asset computer system generates transaction instructions in accordance with the swap transaction information, the first side user information, the second side user information and the matched first interest rate and second interest rate to transact the swap.
In step 6308, the digital asset computer system, updates the electronic ledger to change the account information of the first user and second user to reflect a decrease in the amount of collateral associated with the first user and second user in an amount equal to the initial margin. The digital asset computer system also updates the electronic ledger to change the obligation information of the first user and the second user in accordance with the swap transaction information and the matched first interest rate and second interest rate.
In step S6309, the digital asset computer system transmits a confirmation of the transaction to at least the first user device associated with the first user and the second user device associated with the second user.
In step 6309a, the digital asset computer system may publish the matched first interest rate and second interest rate.
As shown in
At step 6311, the digital asset computer system may determine whether the recalculated margin exceeds the collateral of the first user or the second user. If so, in embodiments, the digital asset computer system may issue an alert to the first user or second user to increase their account balance to meet the recalculate margin. In embodiments, the first user and second user are provided a set period of time to increase their collateral prior to the computer asset computer system transferring collateral from the account of the first user or second user to the account of the other of the first user and the second user.
In embodiments, a Swap Token tied to an underlying blockchain, such as the Ethereum Blockchain may be provided.
By way of illustration and referring to the exemplary block diagram of
In embodiments, the Swap Contract may include such terms as a duration.
In Step S6702, a Stable Value Token (such as SVCoin) is provided as discussed previously, with its own Contract Address, (e.g., svt), on an underlying Blockchain (e.g., the Ethereum Blockchain). In embodiments, the Stable Value Token will have its own smart contract (e.g., SV Coin Contract), using one or more contract addresses, consistent with embodiments otherwise described herein.
In Step S6704, a Swap Token is provided with its own Contract Address, (e.g., swapt) on the same underlying Blockchain. In embodiments, the Swap Token will have its own smart contract (e.g., Swap Contract), using one or more contract addresses, consistent with embodiments otherwise described herein. In embodiments, the Swap Contract may include instructions providing for:
In Step S6706, User 1 and User 2 agree to a trade, which the swap admin is aware of it. In embodiments, Step S6706 may be performed through an order book, such as a continuous order book or an auction order book, as discussed above.
In Step S6708, the swap admin calls a function on the smart contract ‘swapt’ to set up the trade (e.g., ‘setupTrade’ function). The setupTrade function may include as parameters, the parties to the trade (e.g., User 1 and User 2), the addresses of the participants in the trade (e.g., User Public Address 1 and User Public Address 2), the side of each party to the contract (e.g., buy or sell), as well as the other parameters, such as how much collateral is required, (e.g., 101), to name a few. The ‘setupTrade’ function returns some unique identifier (e.g., ‘trade001’), to identify this particular trade and notifies User 1 and User 2 of the identifier ‘trade001’. At the end of Step S6708, the trade is in an unfunded state.
In Step S6710, User 1 and User 2 will fund their collateral requirements for the trade (trade001) using the stable value token. In embodiments, this amount may be from a preexisting account (e.g., User Public Address 1 for User 1 and User Public Address 2 for User 2). In embodiments, each user's balance may be checked by using a function such as check balance function against the svt contract address (e.g., svt.balnceOf(User Public Address 1), and svt.balanceOf (User Public Address 2). In embodiments, one or more users may need to purchase new stable value tokens to fund the collateral requirement, in accordance with embodiments elsewhere discussed. Before the next step (Step S6710a), both users will have to have sufficient balances of stable value tokens in their respective public addresses to support the collateral requirements of the sap transaction.
In Step S6710a, User 1 will send to the svt contract address a message to fund the swapt contract address with the required collateral amount (e.g., 101 SVCoins). In embodiments, User 1 sends the transaction from User Public Address 1 to svt Contract Address with message instruction the transfer of the SVCoins from user's public address to the swap contract address (e.g., ‘svt.approve(swapt, 101)’). This message would be signed by User 1, using User Private Key 1. Assuming User Public Address has a sufficient balance, and User Private Key 1 is authorized to sign for the transfer, the Stable Value Token Contract should approve and record the transfer.
In Step S6710b, User 1 makes a second transaction to fund the trade by, e.g., calling a fundTrade Function in the swap contract, including reference to the unique identifier of the trade (e.g., trade001). In this example, User 1 would send to the underlying blockchain, a transaction from User Public Address 1 to swapt Contract Address, with a message such as ‘swap.fundTrade(trade001)’. In response, the swap contract, executing the ‘fundTrade’ function, may internally call ‘svt.transferFrom(User Public Address 1, swap, 101)’ to transfer the previously approved tokens to itself (otherwise failing if User Public Address 1 did not approve the required tokens to fund the trade) and, if successful, marks trade001 in its datastore as being funded by User 1's side of the trade. At this point, trade001 has been half funded by User 1.
In Steps S6710c and S6710d, User 2 will need to carry out comparable steps as S6710a and S6710b for User 2's SVCoin tokens in User Public Address 2 and to support User 2's collateral obligations for its side of the trade (e.g., trade001).
In Step S6710c, User 2 will send to the svt contract address a message to fund the swapt contract address with the required collateral amount (e.g., 101 SVCoins). In embodiments, User 2 sends the transaction from User Public Address 2 to svt Contract Address with message instruction the transfer of the SVCoins from user's public address to the swap contract address (e.g., ‘svt.approve(swapt, 101)’). This message would be signed by User 2, using User Private Key 2. Assuming User Public Address has a sufficient balance, and User Private Key 2 is authorized to sign for the transfer, the Stable Value Token Contract should approve and record the transfer.
In Step S6710d, User 2 makes an additional transaction to fund the trade by, e.g., calling a fundTrade Function in the swap contract, including reference to the unique identifier of the trade (e.g., trade001). In this example, User 2 would send to the underlying blockchain, a transaction from User Public Address 2 to swapt Contract Address, with a message such as ‘swap.fundTrade(trade001)’. In response, the swap contract, executing the ‘fundTrade’ function, may internally call ‘svt.transferFrom(User Public Address 2, swap, 101)’ to transfer the previously approved fiat currency to itself (otherwise failing if User Public Address 2 did not approve the required tokens to fund the trade) and, if successful, marks trade001 in its datastore as being funded by User 2's side of the trade.
At this point, trade001 has been fully funded by User 1 and User 2, and should be in a fully funded state. At a later point in time, in embodiments, either User 1 or User 2 may send a call request to the swapt contract address to collect from the posted collateral in trade001 if appropriate conditions have been met, using, e.g., a ‘withdrawal’ command.
In embodiments, a method for performing a return swap using a digital asset includes: (a) providing, by the digital asset computer system comprising one or more computers, an electronic ledger including user account information for a plurality of users, the user account information for each user of the plurality of users including: 1. user identification information; 2. collateral information; and 3. obligation information; (b) providing, from the digital asset computer system to a first user device associated with a first user and a second user device associated with a second user, swap transaction information including: 1. swap information; 2. a swap duration; 3. a t least one fixing date; and 4. at least one benchmark rate; (c) receiving, by the digital asset computer system from the first user device associated with the first user, a swap bid request, the swap bid request including: 1. first user side information; and 2. a first interest rate; (d) receiving, by the digital asset computer system from the second user device associated with the second user, a swap ask request, the swap ask request including: 1. second user side information; and 2. a second interest rate; (e) calculating, by the digital asset computer system, an initial margin amount based on margin consideration wherein the margin considerations include: 1. the swap information; 2. continuous order book market data; and 3. index information; (f) verifying, by the digital asset computer system, that an amount of collateral for the first user and for the second is greater than or equal to the sum of the initial margin; (g) where the digital asset computer system verifies that an amount of collateral for the first user and the second user is greater than or equal to the initial margin, storing the swap bid request and the swap ask request; (h) matching, by the digital asset computer system, the first user side swap information with the second user side swap information, where a match is achieved where the first user side information identifies a side opposite that identified by the second user side information; (i) matching, by the digital asset computer system, the first interest rate with the second interest rate, where a match is achieved where the first interest rate is the same as the second interest rate; (j) generating, by the digital asset computer system, transaction instructions in accordance with the swap transaction information, the first user side information, the second user side information and the matched first interest rate and second interest rate; (k) updating, by the digital asset computer system, the electronic ledger to: 1. change the account information of the first user and the second user to decrease the amount of collateral associated with the first user and second user in an amount equal to the initial margin; and 2. change the obligation information associated with the first use and second user to reflect their obligations including the swap transaction information and the matched first rate and second rate; (l) transmitting, by the digital asset computer system, a confirmation of the transaction to at least the first user device and the second user device; and (m) publishing, by the digital asset computer system, the matched first interest rate and second interest rate.
In embodiments, the method further includes the steps of: (n) recalculating, by the digital asset computer system, the margin; and (o) determining, by the digital asset computer system, whether the recalculated margin exceeds the collateral of the first user and the second user and issuing an alert to the first user and the second user to increase their collateral when the recalculated margin exceeds the collateral of the first user and the second user.
The present invention also relates to methods, systems and program products for depositing, holding and/or distributing collateral in the form of a stable value token for a security token, the tokens being on the same underlying blockchain.
In embodiments, each of systems 6801, 8609 and user devices 105a, 105b 105N may communicated with and/or among each other directly and/or indirectly, e.g., through a data network 15, such as the Internet. In embodiments, encryption and/or other security protocols may be used. In embodiments, data network 15, may be a wide area network, a local area network, a telephone network, dedicated access lines, a proprietary network, a satellite network, a wireless network, a mesh network, or through some other form of end-user to end-user interconnection, which may transmit data and/or other information. Any participants in a digital asset network may be connected directly or indirectly, as through the data network 15, through wired, wireless, or other connections.
In embodiments, issuer of the security token may be one or more entities. In embodiments, the issuer of the stable value token may be one or more entities. In embodiments, the issuer of the security token and the issuer of the stable value token may be the same or different entity. In embodiments, one or more administrators may operate the security token administrator system 6801 on behalf of the issuer of the stable value token. In embodiments, the same or different administrators may operate the stable value token administrator system 6809. In embodiments, the issuers and/or administrators may be a trust company, a regulated trust company, a bank, a broker dealer, or some other form of entity, to name a few.
In embodiments, the administrator system 6801 may access one or more databases stored on non-volatile computer readable memory including contract parameters data base 6801B, key information data 6801C and smart contract information 6801D. As further illustrated in
As illustrated in
As illustrated in
In embodiments, the create security token module 6918 may include one or more authorization instructions related to creating security tokens. Such instructions may specify one or more authorized key pairs or contract addresses that may be authorized to create security tokens under specified conditions. In embodiments, the create security module 6918 may include instructions on increasing the token supply. In embodiments, the create security token module 6918 may include instructions on how to create new tokens within pre-approved token supply limits and how to assign newly created or “minted” tokens to specific designated public addresses or contract addresses on the underlying blockchain.
In embodiments, the transfer tokens module 6920, in embodiments, may include authorization instructions related to transferring security tokens. In embodiments, such transfer instructions may include rules by which certain transfer are allowed or blocked and may specify one or more key pair or contract addresses that may be authorized to perform one or more types of transfer operations. In embodiments the transfer tokens module 6920 may include authorization instructions related to transferring stable value tokens to smart contract address 6805A. In embodiments, the transfer tokens module 6920 may include authorization instructions related to transferring stable value tokens from smart contract address 6805A.
In embodiments, the destroy security tokens module 6922 may include authorization instructions related to destroying security tokens, including, in embodiments, instructions on when, and with whose authority, security tokens associated with one or more specified addresses shall be destroyed or “burned”, and thus removed from the security token supply.
The access data module 6924, in embodiments, may include authorization instructions related to accessing data supplied by a first authorized third party database (i.e. administrator system 6801), as discussed in further detail elsewhere.
The authorize instructions module 6926 may further include instructions to authorize the transfer of stable value tokens from the second contract address 6805B.
The generate collateral information message module 6930, in embodiments, may include instructions to generate a collateral confirmation message to the administrator system 6801 confirming receipt of at least one of a first amount of collateral and a second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments, the send collateral information message module 6932 may include instructions to send the collateral confirmation message to the administrator system 6801 confirming receipt of at least one of a first amount of collateral and a second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
As illustrated in
In embodiments, the create stable value token module 6934 may include authorization instructions related to creating stable value tokens.
The transfer stable value token module 6936, in embodiments, may include authorization instructions related to transferring stable value tokens.
In embodiments, the destroy stable value token module 6938 may include authorization instructions related to destroying stable value tokens.
In embodiments, the authorization instruction module 6940 may include authorization instructions related to functions associated with the stable value tokens. In embodiments, authorization instructions module 6940 may also include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts.
While security token 6805 is described as a security token, in embodiments, the security token may reflect other types of tokens, such as tokens associated with a security, a bond, a financial instrument, a contract, and stock, to name a few. Similarly, while the SVCoin token 6807 is describe a stable value token, in embodiments, the SVCoin token 6807, may reflect other kinds of token which may not necessarily reflect a stable value, e.g., Gas tokens, and/or some other kind of token which the parties to the transaction reflect as an appropriate collateral.
Referring to
In embodiments, a contract request may be from more than one user. In embodiments, a first user and second user may agree in advance, as to contract parameters, and one or the other may send a contract request that includes first user identification information associated with a first user device that is associated with a first user as well as second used identification information associated with a second user device that is associated with a second user. The first user device, in embodiments, may be User device 105a. In embodiments, the second user device may be User device 105b. The contract request, in embodiments, may include a smart contract generation request. The smart contract generation request, in embodiments, is a request from a user device to an administrator system to generate a smart contract.
In embodiments, the contract request may be for a contract where the parameters are already agreed upon by more than two users (i.e. User device 105a, User device 105b . . . User device 105n). For example, where the contract parameters are already agreed upon by more than two users, the contract request may include user information for each of the users of which have already agreed upon the parameters of the requested contract. The contract request, in embodiments, may also include a smart contract generation request.
Once a contract request is received by the administrator system, at step S7304, the administrator system may generate graphical user interface (GUI) information including at least one prompt for the first user to provide contract parameters related to the smart contract to be generated. For example, the administrator system may generate graphical user interface information to provide a GUI similar to that shown in
Once the GUI information is generated, at step S7306, the administrator system may send the GUI information to the first user device. In embodiments, once received by the first user device, the first user device may use the GUI information to display a GUI, which may be similar to GUI shown in connection with
In embodiments, once the GUI information is received by the first user device, the first user device may receive one or more inputs which may include contract information including the contract parameters. For example, the user device may receive inputs that indicate an inception date 7104, inception value 7106, benchmark data 7108, contract duration data 7110, collateral requirement 7112, notional value 7114, early termination rules 7130, and second benchmark data 7132, to name a few. In embodiments, where the GUI information is sent to more than one device, for example, where the GUI information is sent to a first user device and a second user device, at least one of the user devices may receive inputs which may include contract information including the contract parameters. The contract information including the contract parameters may, in embodiments, be sent from the first and or second user devices to the administrator system.
At a step S7308, the administrator system may receive, from the first user device, in response to the at least one prompt included in the graphical user interface information, contract information including the contract parameters of the contract to be generated. In embodiments, such as embodiments where the contract parameters are already agreed upon by more than one user, the administrator system may receive contract information including the contract parameters of the contract to be generated from at least one of the first user device and the second user device. In embodiments, such as embodiments where the parameters are already agreed upon by more than two users, the administrator system may receive contract information including the contract parameters of the contract to be generated from at least one of the user devices associated with the users that have already agreed upon the contract parameters.
Once the contract information is received by the administrator system, at a step S7310, the administrator system may store the contract information including the contract parameters in memory operably connected to the administrator system. In embodiments, the contract information may be stored in smart contract information database 6801D.
In embodiments, the contract parameters provided in the process described in connection with
The steps of the process described in connection with
In embodiments, the process of
A more detailed description of contract parameters and collateral requirements associated with an oracle is located below in connection with the descriptions of
In embodiments, the oracle fee may be a fee associated with using an oracle. The fee, in embodiments, may be applied to the first user and second user equally (e.g. if the fee is 2 Gemini Dollars, the first user pays 1 Gemini Dollar and the second user pays 1 Gemini Dollar). In embodiments, the fee may be applied to the user who proposed an incorrect settlement amount. In embodiments, the oracle fee may be waived if the first user and/or the second user use an SV Coin (e.g. Gemini Dollar) to collateralize the published contract. In embodiments, the fee may be waived if the first user and/or second user collateralize the published contract with the same digital asset type as the digital asset type used by the oracle to collateralize the published contract (e.g. if the oracle uses Bitcoin and the first or second user also use Bitcoin). In embodiments, the fee may be waived for one or more of the users (e.g. only the first user, only the second user, or both the first user and the second user). In embodiments, the fee may be waived by the administrator system 6801.
In embodiments, other values and parameters may be included consistent with embodiments of the present invention. In embodiments, these other values and parameters may include information that may be used to determine the contract parameters discussed above, and/or other parameters including: (1) asset identification information; (2) a current (spot) price; (3) a type of derivative; (4) a side (buy/sell); (5) a call/put designation, (6) an expiration date or term, (7) a strike price; (8) pricing model information, and (10) volatility information, to name a few. In embodiments, user input of certain information may prompt requests for additional information. In one example, input of an identification of a particular type of derivative may require user identification of other information, such as upper or lower price limit, to name a few.
In embodiments, the type of derivative may be any one of: vanilla, fx hedge, flexi forward, knock out, knock in, double knockout, double knock in, no touch, one touch, double no touch, double one touch, digital, digital knockout, digital knockin, digital double knockout, digital double knockin, compound, sequential—kiko & kiki, koki—no sequential, digital sequential, average (Asian), fader, digital accrual, accrual, accumulator, accumulator KO, accumulator KI, cas, dcd vanilla, dcd knockout, dcd knockin, average forward, euro-american KO, target redemption forward, dual-strike tarf, kockin tarf, pivot tarf, variance swap, volatility swap and forward volatility agreement, to name a few.
In embodiment, the pricing model may be any one of: black-scholes, vanna-volga, heston, local vol, stoch-local vol, stochastic, to name a few.
In embodiments, the smart contract parameters database may further include: (10) early termination rule data 6914; and/or (11) second benchmark data 6916, to name a few. In embodiments, early termination rule data 6914 may include rules that charge a fee associated with a user terminating the smart contract before the contract duration is completed. Second benchmark data 6916 in some embodiments may be different than benchmark data 6906. The published contract, in embodiments, may include a GUI with such information as shown in connection with
Referring to
In embodiments, the first indication of interest may further include additional information such as, a first user public address and/or first collateral information, to name a few. In embodiments, such additional information may not be necessary to include in the indication of interest because it may be included in the contract parameters as published and thus implied. First collateral information may be in stable value digital asset tokens (SVCoins). For example, referring to
In embodiments, the second indication of interest may be a second user response sent from a second user device 105b to administrator system 6801. In embodiments, the second user device 105b may be associated with a second user (e.g. Bob). The second indication of interest (e.g. second indication of interest 7150 described in connection with
In embodiments, step S7004 may further include the administrator system may receive a third and fourth user responses from a fourth user device and a fifth user device, for example. The third user response, in some embodiments, may include fourth user identification information associated with the fourth user. In embodiments, the third user response may also include third side information comprising identification of the first leg of the contract. In embodiments, the third user response may be similar to first indication of interest 7134 described in connection with
The fourth user response may include fifth user identification information associated with the fifth user. In embodiments, the fourth user response may also include fourth side information comprising identification of the second leg of the contract, the fourth side information being different than the third side information. In embodiments, the fourth user response may be similar to first indication of interest 7134 described in connection with
Referring back to
In embodiments, such as the embodiments where a third user response and fourth user response are received by the administrator system, the third user response may be matched with the fourth user response.
In a step S7008, a stable value token smart contract associated with a stable token 6807 and first smart contract instructions 6807B associated with a first contract address 6807A associated with the blockchain 6803 for the underlying digital asset are provided. In embodiments, the first smart contract instructions 6807B are saved in the blockchain 6803 for the underlying digital asset. In embodiments, the first smart contract instructions 6807B may include the stable value token smart contract instructions 6807B described in connection with
Referring back to
In embodiments, the second smart contract instructions 6805B may also include oracle instructions associated with the oracle (e.g. dispute instructions module 6942). A more detailed description of oracle instructions is located below in connection with the description of
In embodiments, the mathematical solution may correspond to a mathematical puzzle, which may be generated by one or more of: the first user device, the second user device, the administrator, and/or the oracle, to name a few. In embodiments, the administrator 6801 (e.g. digital asset exchange computer system 3230, a trusted entity, the digital asset exchange computer system described in connection with
The algorithm, in embodiments, may be applied to a puzzle seed that is obtained by the digital asset exchange computer system. In embodiments, the puzzle seed may be a randomly generated series of numbers, letters, and/or characters. Alternatively, in embodiments, the puzzle seed may be a semi-randomly generated series of numbers and/or letters based on at least one of the following: (1) a first user public address; (2) a second user public address; (3) a public key associated with the digital asset exchange computer system; (4) a public key associated with the first user; (5) the oracle address; (6) a public key associated with the oracle’ (7) a private key associated with the oracle; (8) a private key associated with the first user; (9) a private key associated with the second user; and/or (10) a private key associated with the digital asset exchange computer system, to name a few. In embodiments, the first user public address may be a public address on blockchain 6803 and associated with the first user. The first user public address may be associated with a first user public key. In embodiments, the first user public key may correspond to a first user private key—which combined may be a first user key pair. In embodiments, the second user public address may be a public address on blockchain 6803 and associated with the second user. The second user public address may be associated with a second user public key. In embodiments, the second user public key may correspond to a second user private key—which combined may be a second user key pair.
In embodiments, one or more processor(s) of the digital asset exchange computer system may apply an algorithm to a puzzle seed to generate a first mathematical puzzle. Continuing the example, the algorithm may be applied to the first mathematical puzzle. The result of the second application of the algorithm may be the corresponding first mathematical solution. In embodiments, the algorithm may be applied a plurality of times, resulting in a plurality of mathematical puzzles and corresponding solutions. Thus, in embodiments, the first mathematical puzzle may be a plurality of mathematical puzzles. Similarly, the corresponding first mathematical solution may be a plurality of mathematical solutions. The below table is an example of an overly simplified algorithm applied to a puzzle seed, resulting in a plurality of mathematical puzzles and corresponding solutions, merely for exemplary purposes. For the purposes of the example in the below table, (1) the puzzle seed is 123456; and (2) the algorithm applied is X*4+5, where X represents the puzzle seed. Thus, the first puzzle may be (123456)*4+5, or in other words, 493829.
As another example, below is a second table illustrating an exemplary generation of puzzle sequences for a sequence of length 5.
Table 1-B, in embodiments, may be an example of an asymmetric puzzle. An asymmetrical puzzle sequence, for example, may refer to a puzzle sequence including N puzzles, where the Nth puzzle is generated first, based off the seed. Continuing the example, the second puzzle in the puzzle sequence, the N−1 puzzle, may be generated second based of the Nth puzzle. This may continue until the first puzzle is generated. The below diagram, in embodiments, may illustrate the order in which an asymmetric puzzle sequence is generated.
Asymmetrical Puzzle Sequence Diagram
As shown in the above diagram, the seed is hashed to create the Nth puzzle, which is hashed to create the N−1 Puzzle which continues until the Second Puzzle is hashed to create the First Puzzle. Hashed, as used herein, may refer to the application of a hash algorithm.
In practice, the algorithm and seeds used to generate the puzzle and solution will be more complex, and each layer may potentially use a different algorithm to increase complexity and avoid reserve engineering of puzzle solutions. In embodiments, by building a nested puzzle/solution basis, where the current solution to the current puzzle is the next puzzle, the process can be more efficient.
As shown in the above table the first mathematical solution may correspond to the second mathematical puzzle. Similarly, the second mathematical solution may correspond to the third mathematical puzzle. Moreover, the third mathematical solution may correspond to the fourth mathematical puzzle. Furthermore, the fourth mathematical solution may correspond to the fifth mathematical puzzle. In embodiments, the digital asset exchange computer system may continue applying the algorithm, generating dozens, hundreds, thousands, millions, and/or billions of puzzle/solution combinations. In embodiments, each puzzle/solution combination may be unrelated. In embodiments, a first user device associated with the first user and/or a second user device associated with the second user may generate the first mathematical puzzle and corresponding solution.
The corresponding first solution to the first mathematical puzzle may be used to protect the first user, the second user, and/or the digital asset exchange computer system in the event of a security incident or breach (e.g. a data breach; a data incident; untrustworthy actions on behalf of the first user, second user, and/or the digital asset exchange computer system, and/or a system crash, to name a few—a data security incident or breach response is described more fully below in connection with
In embodiments, the generated puzzle may be transmitted to one or more of the first user public address, the second user public address, a public address associated with the administrator 6801 and/or the oracle address, to name a few. In embodiments, the generated puzzle may be transmitted by the party that generated the puzzle and corresponding solution (e.g. the first user, the second user, the administrator 6801, and/or the oracle, to name a few).
In embodiments, step S7008 and step S7010 may be performed before step S7002, step S7004, and step S7006.
Referring back to
Referring to
In a step S7018, the administrator system 6801 may generate first hashed trade instructions, the first hashed trade instructions being generated by applying a hash algorithm to the first trade instructions. Examples of hash algorithms include MD 5, SHA 1, SHA 256, RIPEMD, and Keccak-256 to name a few. Hash algorithms take an input of any length and create an output of fixed length, allowing the trade instructions to be detectable and usable by administrators and users on the underlying blockchain. However, applying a hash algorithm is not always necessary if trade instructions are published ahead of time
In a step S7020, the administrator system 6801 sends a first transaction request from an administrator public address associated with the administrator system 6801 to the second contract address 6805A via the underlying blockchain 6803. In embodiments, the first transaction request, includes a first message which may include: (1) the first hashed trade instructions; (2) a request to assign a first trade identification to a first trade associated with the hashed trade instructions. In embodiments, the first message may include requests to assign a first trade identification to the first trade associated with the hashed trade instructions and include the first trade identification associated with the first hashed trade instructions. In embodiments, the first transaction request may further include first transaction fee information. The first transaction fee information, in embodiments, may be for miners on the blockchain 6803 to process the first transaction request. The first transaction request may also be electronically signed by an administrator private key. The administrator private key may be mathematically related to the administrator public address.
The process may continue with step S7022. In step S7022, the administrator system 6801 obtains the first trade identification of the first trade. In embodiments, the administrator system 6801 may determine the first trade identification, as calculated by the security token smart contract, by monitoring transactions on the blockchain 6803 (as shown in connection with a step S7024 of
In embodiments, as shown in a step S7030, the first user device 105a may send a second transaction request from a first user public address (the first user public address being associated with the first user and the first user device 105a) to the first contract address 6807A via the underlying blockchain 6803. The second transaction request may include a second message, the second message including requests to the stable value token smart contract 6807B regarding a first transfer of a first amount of collateral. In embodiments, the second message may include the first trade information. In embodiments, the second transaction request may include second transaction fee information. The second transaction fee information may be for miners on the blockchain 6803 to process the second transaction request. In embodiments, the second message may also include a transfer request to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens 6807 from the first user public address to the second contract address 6805A. The transfer request, in embodiments, will be executed upon receipt of a first collateral request from the second contract address 6805A. In embodiments, the transfer request included in the second message may be executed upon receipt of a first collateral request from the administrator system 6801. The second transaction request is also electronically signed by a first user private key. The first user private key may be mathematically related to the first user public address.
In embodiments, the process described in
The process may continue with a step S70121. In a step S7034, the administrator system 6801 monitors transactions of the stable value digital asset tokens 6807 on the blockchain 6803 to determine that the second contract address 6805A has received at least the following: (1) the first amount of collateral in stable value digital asset tokens from the first user (e.g. the user associated with user device 105a); and (2) the second amount of collateral in stable value digital asset tokens from the second user (e.g. the user associated with user device 105b). In embodiments, the administrator system 6801 may further monitor the first contract address 6807A to determine whether the first amount of collateral is received at the second contract address 6805A and whether the second amount of collateral is received at the second contract address 6805A (as shown in connection with a step S7036 of
Alternatively, the administrator system 6801 may receive a collateral confirmation message confirming that the first amount of collateral and the second amount of collateral are received by the second contract address 6805A (as shown in connection with a step S7040 of
In embodiments, the administrator system 6801 may also determine the second contract address 6805A has also received the oracle collateral. In embodiments, the administrator system 6801 may further monitor the first contract address 6807A to determine whether the oracle collateral is received at the second contract address 6805A. Alternatively, the administrator system 6801 may receive a collateral confirmation message confirming that the oracle collateral was received by the second contract address 6805A (similar to the step illustrated as shown in connection with a step S7040 of
Upon determining that the first amount of collateral from the first user (e.g. the user associated with user device 105a), the second amount of collateral from the second user (e.g. the user associated with user device 105b), and/or the oracle collateral have been received by the second contract address 6805A, in a step S7042, the administrator system 6801 may send a fourth transaction request from the administrator public address to the second contract address 6805A via the underlying blockchain 6803. The fourth transaction request may include a fourth message including the first trade instructions and the first trade identification. In embodiments, the fourth transaction request may further include fourth transaction fee information. The fourth transaction fee information, in embodiments, may be for miners on the blockchain 6803 to process the fourth transaction request. The fourth transaction request may also be electronically signed by the administrator private key.
In embodiments, the second contract address 6805A may further include modules with instructions to: (1) generate a first collateral request when the third message is received by the second contract address 6805A; (2) send the first collateral request to the first contract address 6807A associated with the stable value token smart contract; (3) generate a second collateral request when the third message is received by the first contract address 6807A; (4) send the first collateral request to the first contract address 6807A associated with the stable value digital asset token smart contract; confirming that the first amount of collateral from the first user (e.g. a user associated with user device 105a) and the second amount of collateral from the second user (e.g. a user associated with user device 105b) has been received by the second contract address; and (5) sending a collateral confirmation message to the administrator public address.
Upon receiving the confirmation message, the administrator system 6801 may send a fourth transaction request from the administrator public address to the second contract address 6805A via the underlying blockchain 6803. The fourth transaction message may include a fourth message comprising first trade instructions and the first trade identification.
Referring to
In embodiments, as shown in a step S7044, the first user device 105a may then send a second transaction request from a first user public address (the first user public address being associated with the first user and the first user device 105a) to the first contract address 6807A via the underlying blockchain 6803. The second transaction request may include a second message, the second message authorizing the stable value token smart contract 6807B to accept a request to transfer a first amount of collateral from the first user public address to the second contract address 6805A. In embodiments, the second transaction request may further include second transaction fee information. The second transaction fee information, in embodiments, may be for miners on the blockchain 6803 to process the second transaction request. The second transaction request may be electronically signed by the first user private key. The first user private key is mathematically related to the first user public address.
The process may continue at step S7046. At a step S7046, the second user device may send a third transaction request from a second user public address (associated with the second user and the second user device 105b) to the second contract address 6805A via the underlying blockchain 6803. The third transaction request may include a third message authorizing the stable value digital asset smart contract 6807B to accept a request to transfer a second amount of collateral from the second user public address to the second contract address 6805A. In embodiments, the third transaction request may further include third transaction fee information. The third transaction fee information, in embodiments, may be for miners on the blockchain 6803 to process the third transaction request. The third transaction request may be electronically signed by the second user private key. The second user private key is mathematically related to the second user public address.
In step S7048, the administrator system 6801 may send a fourth transaction request from the administrator public address to the first contract address 6807A via the underlying blockchain 6803. The fourth transaction request may include a fourth message including requests to: (1) transfer of the first amount of collateral of stable value digital asset tokens from the first user public address to the second contract address 6805A; and (2) transfer of a second amount of collateral of stable value digital asset tokens 6807 from the second user public address to the second contract address 6805A. The fourth transaction request may also be electronically signed by the administrator private key.
Alternatively, the second contract address 6805A may send a fourth transaction request to the first contract address 6807A via the underlying blockchain 6803. The fourth transaction request may similarly include a fourth message including requests to: (1) transfer of the first amount of collateral of stable value digital asset tokens 6807 from the first user public address to the second contract address 6805A; and (2) transfer of a second amount of collateral of stable value digital asset tokens from the second user public address to the second contract address 6805A.
In alternative embodiments, steps S7010 and S7012 (and accompanying substeps described above in connection with
The second smart contract instructions 6805B may include one or more of the following: (1) first trade instructions for the security token smart contract; (2) fifth authorization instructions regarding transferring security tokens (which may be included in the transfer security tokens module 6920); (3) sixth authorization instructions regarding destroying security tokens (which may be included in the destroy security tokens module 6922); (4) seventh authorization instructions regarding transferring stable value tokens to the second contract address (which may be included in the authorize instructions module 6926); (5) eighth authorization instructions regarding transferring stable value tokens from the second contract address (which may be included in the authorize instructions module 6926); (6) calculating instructions regarding calculating excess collateral (which may be included in the calculate excess collateral module 6928); (7) generating collateral information instructions regarding excess collateral (which may be included in the generate collateral information message module 6930); and (8) sending collateral information message instructions regarding excess collateral (which may be included in the send collateral information message module 6932). In embodiments, the first trade instructions may include execution instructions to execute a first trade between the first user and the second user. The first trade, in embodiments, may be based on at least (1) the contract request or proposal and (2) the first user response.
In embodiments, once the security token contract is generated by an administrator 6801, the administrator 6801 may send the security token smart contract and associated second smart contract instructions 6805B to the second smart contract address 6805A via the blockchain 6803 for the underlying digital asset.
In embodiments, the first trade instructions may be implemented via the blockchain 6803 for the underlying digital asset by computers systems among the plurality of geographically distributed computer systems in the peer-to-peer network.
Referring back to
Referring to
In response to the requests contained in the fifth message, as shown in step S7052, the security token smart contract 6805B sends a sixth transaction request from the second contract address 6805A to an oracle address associated with an oracle smart contract on the blockchain 6803 associated with an oracle interface in contact with a trusted third party database. The sixth transaction request, in embodiments, may include a sixth message to obtain first benchmark data from the trusted third party database. In response to sending the sixth transaction request, in step S7054, the security token smart contract 6805B may receive a callback message from the oracle interface including the first benchmark information. In embodiments, access to the trusted third party database through the oracle smart contract may be limited to certain authorized or approved addresses on the blockchain. In embodiments, as described further below, a whitelist of authorized (or approved) requesting addresses may be provide in which the first benchmark information is provided only in response to requests from an authorized address. In embodiments, the whitelist of authorized requesting addresses may be updated. In embodiments, the administrator system may update the whitelist of authorized requesting addresses to reflect the address of the security token contract that is provided using the process of the present application.
In embodiments, the whitelist of authorized addresses may be included at the oracle smart contract address. In embodiments, the oracle smart contract address may include authorization instructions to request the first contract address only when the requester address is one of the addresses on the whitelist. In embodiments, the oracle smart contract may include authorization instructions related to an update key pair for updating the whitelist of authorized addresses to allow for the white list to be updated.
In embodiments, the whitelist of authorized addresses may be provided in memory element associated with the trusted third party database. In embodiments, the trusted third party database will not provide the first benchmark information to the oracle contract unless the requester address is included in the whitelist of authorized addresses.
In response to receiving a callback message, in step S7056, the security token smart contract 6805B executes instructions to: (1) store the first benchmark information and (2) calculate the excess collateral for the first user (e.g. the user associated with user device 105a) and the second excess collateral for the second user (e.g. the user associated with user device 105b) by using the first trade instructions and the first benchmark information. In embodiments, the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value, to the extent it is greater than zero. In embodiments, the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information, to the extent it is greater than zero.
To the extent that the first excess collateral is greater than zero or the second excess collateral is greater than zero, in step S7058, the security token smart contract 6805B sends a seventh transaction request from the second contract address 6805A to the first contract address 6807A via the underlying blockchain 6803. The seventh transaction request, in embodiments, may include a seventh message requesting the stable value token smart contract 6807B to transfer: (1) the first excess collateral in stable value digital asset token from the second contract address 6805A to the first user public address (associated with the first user and user device 105a), to the extent the first excess collateral is greater than zero; and (2) the second excess collateral in stable value digital asset token from the second contract address 6805A to the second user public address (associated with the second user and user device 105b).
Referring to
The process in
In response to the requests contained in the sixth message, in step S7014′D, the security token smart contract 6805B executes instructions via the blockchain 6803 to calculate first excess collateral for the first user (e.g. a user associated with user device 105a) and second excess collateral for the second user (e.g. a user associated with user device 105b) using the first trade instructions and the first benchmark information. In embodiments, the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value, to the extent it is greater than zero. In embodiments, the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information, to the extent it is greater than zero.
To the extent that the first excess collateral is greater than zero or the second excess collateral is greater than zero, in step S7014′E, the security token smart contract 6805B sends a seventh transaction request from the second contract address 6805A to the first contract address 6807A via the underlying blockchain 6803. The seventh transaction request, in embodiments, may include a seventh message requesting the stable value token smart contract 6807B to transfer: (1) the first excess collateral in stable value token from the second contract address 6805A to the first user public address (associated with the first user and user device 105a), to the extent the first excess collateral is greater than zero; and (2) the second excess collateral in stable value token from the second contract address 6805A to the second user public address (associated with the second user and user device 105b). As in step S7014E, if there is excess collateral, the second contract address 6805A sends the excess collateral to the user of which that excess collateral belongs.
In embodiments, such as the embodiments where a third user response and fourth user response are received by the administrator system and matched, the administrator system may set up a second trade between the fourth user and the fifth user. This process of setting up a trade between two users may be similar to the process described in connection with
In embodiments, the steps within the process described above in connection with
In embodiments, a separate security token smart contract may be generated and published to the underlying blockchain for each separate trade.
For example, in embodiments, generating a security token smart contract between a first user and a second user may be implemented, in accordance with the following example. In embodiments, generating a security token smart contract between a first user and a second user may begin with an administrator system associated with an administrator 6809 of a security token smart contract receiving a contract proposal. In embodiments, the security token smart contract is maintained on a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network in the form of a blockchain 6803 of an underlying digital asset. In embodiments the underlying digital asset may be a digital math-based asset, Ether, or Neo, to name a few. In embodiments the contract proposal includes: first user information associated with a first user device 105a that is associated with a first user; and first contract information including at least the following contract parameters 6801B: an inception date 6902; an inception value 6904; at least one benchmark 6906; a contract duration 6908; at least one collateral requirement 6910; a notional value of the smart contract 6912; and first side information including identification of a first leg of the contract (e.g. the side information including a leg of a contract described in
In embodiments, the method continues with the administrator system receiving at least one indication of interest (e.g., second indication of interest 7150 described above in reference to
In embodiments, the method continues with the administrator system matching the first contract information and the first user response. Matching, by the administrator system, may be similar to S7006 of
In embodiments, the method continues with an administrator system providing a stable value token smart contract associated with a stable value token 6807 and first smart contract instructions 6807B for a digital asset token. The digital asset token, in embodiments, may be associated with a first smart contract address 6807A that may be associated with the blockchain 6803 for the underlying digital asset. In embodiments, the first smart contract instructions 6807B are saved in the blockchain 6803 for the underlying digital asset. In embodiments, the first smart contract instructions 6807B include: first authorization instructions regarding creating stable value tokens (which may be included in the create stable value token module 6934); second authorization instructions regarding transferring stable value tokens (which may be included in the transfer stable value token module 6936); third authorization instructions regarding destroying stable value tokens (which may be included in the destroy stable value token module 6938); and fourth authorization instructions regarding functions associated with the stable value token (which may be included in the authorization instruction module 6940). In embodiments the first smart contract instructions of the first stable value smart contract are associated with more than one smart contract address. For example, Smart Contract Address 6807A may may be associated with a plurality of smart contract addresses associated with the blockchain 6803 for the underlying digital asset.
In embodiments, the method continues with the administrator system generating the security token smart contract, which may be associated with a security token 6805 and second smart contract instructions 6805B which may be associated with a second smart contract address 6805A which may be associated with the blockchain for the underlying digital asset. In embodiments, the second smart contract instructions 6805B are saved in the blockchain 6803 for the underlying digital asset. In embodiments, the second smart contract instructions 6805B include: first trade instructions for the security token smart contract (which may be similar to step S7016 described above in reference to
In embodiments, the method continues with the administrator system sending the security token smart contract and associated second smart contract instructions. In embodiments, the security token smart contract and associated second smart contract instructions 6805B may be sent via the blockchain 6803 for the underlying digital asset to the second smart contract address 6805A.
In embodiments, the method may continue with the second smart contract address 6805A receiving a first amount of collateral. In embodiments the first amount of collateral may be a first amount of stable value tokens associated with the first user as collateral. In embodiments the first amount of stable value tokens associated with the first user is based on the at least one collateral requirement 6910. In embodiments, the first user device 105a may send a first message. The first message may include a request to transfer the first amount of collateral from the first user public address to the second smart contract address. In embodiments the first message may be sent via the underlying blockchain 6803 from the first user public address associated with the underlying blockchain 6803 to the first smart contract address 6807A associated with the underlying blockchain 6803. In embodiments the first user device 105a may send a second message to the first smart contract address 6807A. The second message may include authorization for the security token smart contract to request a transfer of the first amount of collateral. In embodiments the administrator system may send a third message including instructions to send a request from the second smart contract address 6805A to the first smart contract address 6807A. The request, in embodiments, may be for the first amount of collateral to be transferred from the first user public address to the second smart contract address 6805A. In embodiments, the third message is sent by the administrator system via the underlying blockchain 6803 to the second smart contract address 6805A.
In embodiments, the method may continue with the second smart contract address 6805A receiving a second amount of collateral. In embodiments the second amount of collateral may be a second amount stable value tokens associated with the second user as collateral. In embodiments the second amount of stable value tokens associated with the second user is based on the at least one collateral requirement 6910. In embodiments the second user device 105b may send a fourth message including a request. In embodiments, the request may be to transfer the second amount of collateral from the second user public address to the second smart contract address 6805A. In embodiments the fourth message may be sent via the underlying blockchain 6803 from the second user public address associated with the underlying blockchain 6803 to the first smart contract address 6807A associated with the underlying blockchain 6803. In embodiments the second user device 105b may send a fifth message to the first smart contract address 6807A. The fifth message, in embodiments, may include authorization for the security token smart contract to request a transfer of the second amount of collateral via the blockchain 6803. In embodiments, the administrator system may send a sixth message. The sixth message, in embodiments, may include instructions to send a request. The request, in embodiments, may be for the second amount of collateral to be transferred from the second user public address to the second smart contract address 6805A. In embodiments, the sixth message is sent via the underlying blockchain 6803 to the second smart contract address 6805A.
In embodiments, the first trade instructions are implemented via the blockchain for the underlying digital asset by computer systems among the plurality of geographically distributed computer systems in the peer-to-peer network. In embodiments, the first trade instructions are implemented as a result of a message sent from the administrator system via the blockchain 6803 to the second smart contract address 6805A.
In embodiments, the method may continue with the first collateral amount being recalculated based on the at least one collateral requirement 6910 and current benchmark information (this may be similar to steps S6310 and S6311, both described above in reference to
In embodiments, the method may continue with the second collateral amount being recalculated based on the at least one collateral requirement 6910 and current benchmark information (this may be similar to steps S6310 and S6311, both described above in reference to
In embodiments, the method may include the administrator system determining, at the end of the contract duration, a payout amount based on at least the first trade instructions. The payout instructions may be generated by the administrator system. In embodiments, the payout instructions may be based at least on the first side information and the second side information (e.g. the first and/or second side information including a leg of a contract described in
In embodiments, the method may include the administrator system collecting excess collateral from the first trade (this may be similar to S7014 described above in reference to
In embodiments, the administrator system may return the remaining collateral from the first trade (this may be similar to S7014 described above in reference to
In embodiments, a first benchmark value 6906 may be determined. The first benchmark value 6906 may be determined by the security token smart contract sending, via the blockchain 6803 for the underlying digital asset, a request. The request may be sent from the second smart contract address 6805A to an oracle smart contract at a third contract address associated with the blockchain 6803 for the underlying digital asset (this may be similar to S7014 described above in reference to
In the case where the first excess collateral is greater than zero the first excess collateral may be calculated for the first user (this may be similar to S7014 described above in reference to
In embodiments, the smart contract may pull data from a trusted third party by using a query function, examples of which include Oraclize, etc. The query from the smart contract may include the address of the web API to be queried and the data requested. The third party service then accesses data through web APIs and provides this data to the smart contract through a callback response. The data obtained from web APIs may be parsed to provide data that is compatible with the smart contract, examples of such parsing including JSON, XML and HTML parsing, to name a few. The authenticity of the data provided by the third party may be verified by a cryptographic proofing service, examples of which can include TLSNotary Proofs, Android Proofs and Ledger Proofs, to name a few. In embodiments, the third party service may provide a pointer to an uploaded proof rather than provide the proof itself in order to limit the amount of data provided to the smart contract.
In embodiments, data may be pushed to a smart contract from an external intermediary. In embodiments, the external intermediary may be automated or manually controlled. The external intermediary may be identified in the smart contract as a trusted address. In embodiments, the external intermediary may push data to the smart contract that is representative of a value used by the smart contract. The data may be a copy of data that the external intermediary obtains through a web API. In other embodiments, the data may be derived from one or more sources of data, for example a blended price value based on data from multiple exchanges, as discussed elsewhere. In embodiments, the external intermediary may be a service that provides price information for one or more digital assets. In embodiments, the external intermediary may be hosted by an exchange or other digital asset computer system that provides price information for one or more digital assets. In embodiments, the external intermediary may be the administrator computer system or a digital asset exchange computer system.
In embodiments, the smart contract may pull data from a decentralized network of oracles. Queries for the same data may be sent to multiple oracles and the data returned by the oracles may be compared in order to establish the veracity of the data. In embodiments, the decentralized network of oracles may be an opinion market, examples of which include Auger and Gnosis, to name a few.
In embodiments, an oracle contract ‘c’ may be accessible to other smart contracts. That is, the address of oracle contract ‘c’ may already be used by other smart contracts. One or more of these other smart contracts may call the oracle contract ‘c’ to invoke its function. Inside the implementation of the oracle contract ‘c’, the contract may make a call to the oracle (as a trusted source) with a query, e.g. oracle.query( . . . ). In embodiments, however, some function of contract ‘c’ may be called in order to trigger the call to the oracle. In embodiments, the parameters to query the function may include: (1) an identifier for the data source; (2) a timestamp; (3) additional parameters to specify the query to the data source, to name a few. In embodiments, the call may return a unique identifier (such as ‘id’) to identify the query that was made to the oracle, as the oracle query does not directly return a query result.
In embodiments, contract ‘c’ may include smart contract instructions that include a callback function, for example, function callback(bytes 32 queryId, string result)
In embodiments, information may be retrieved from outside the blockchain. When the trusted intermediary has completed the execution of the query outside the blockchain, accessing whatever external datasource is required, it may send the query result back to the blockchain with a transaction that calls back to the contract ‘c’ as follows:
TO: ‘c’
FROM: CallbackAddress
DATA: _callback(id, “query_result_data_ . . . ”)
Thereafter, the contract ‘c’ may store the result data at the callback address for use as appropriate.
In embodiments, the above model may be used where the domain of query-able things is not known ahead of time or where the domain of query results is far larger than desirable to pre-emptively load into the blockchain. For example, where the query is related to a time series of market data with very granular time precision, it would be impractical to store all of this information in the blockchain. In contrast, the above model is suitable where a small, targeted value out of a large data set is needed. In embodiments, a simpler model may be used where the datasource is fixed ahead of time (e.g. Gemini BTC auction) and domain cardinality is small (e.g. one value per day, one value per week, one value per month, to name a few).
In embodiments, an oracle model may include two smart contracts, the ‘oracle’ and some contract ‘c’ using it. When the contract ‘c’ calls the oracle's query function, the query result is returned directly (as opposed to the query id in the model discussed above) and there is no need for a callback.
In embodiments, when such a push model is used, a transaction must first occur targeting contract ‘c’ to query the ‘oracle’, and thus may be considered a “pull” of data instigated by ‘c’. However, data is generally not pulled into the blockchain. Instead, in embodiments utilizing the pull model discussed above, a second transaction occurs from the trusted intermediary (such as the Oraclize service), which sends the desired result to contract ‘c’ via the callback, and thus, is really a push.
In embodiments, using a small oracle model, in a first transaction, the operator, such as the administrator system, pushes data, such as an auction result, in a transaction so that it is stored in the oracle. Later transactions may occur based on calls to contracts that may then query the oracle to fetch that auction result, which may be considered a lookup, (or a pull). Thus, this model uses a push followed by a pull.
In embodiments, another variation of the model may utilize a subscribe and publish model. In embodiments, the subscribe and publish model may be used for a query that is a one-time action, for a datasource, or a datastream, such as periodically occurring events like the Gemini auction. In embodiments, instead of a call with parameters that specify a single results such as: oracle.query( . . . ) the contract ‘c’ may make a call with parameter that specifies a stream of future events that it wishes to receive, such as: oracle.subscribe( . . . ). In this case, when the operator pushes a new event to the oracle (say an auction result) then the oracle may call each of its subscribers on their respective callback functions to broadcast the event. This model may be considered pull, push, push, push, etc.
In embodiments, access to oracle information may be limited. In embodiments using the small oracle model discussed above, as the query result is returned directly to the query function itself, to limit access, an authorization check of the message sender against a whitelist of permitted callers may be used. The oracle operator may maintain such a whitelist to enable contracts to use its oracle.
In embodiments, there may not be an authorization (in the oracle contract) that is required to restrict which contracts may interact with the oracle. In embodiments, while any contract may query the oracle, the service or operator may decide if and when to push the requested data via the callback, and it may elect to drop queries if the calling contract is deemed not to be authorized. Of course, the oracle could also adhere to a whitelist and reject any query from an unauthorized sender.
In the subscription and publication module discussed above, subscriptions may be gated by a whitelist to limit access. Alternatively, the publish step may only target those contracts that are authorized, similarly to restrictions discussed above.
In embodiments, a method for holding collateral in a smart contract on an underlying blockchain includes: (a) publishing, by an administrator system associated with an administrator, contract information comprising at least the following contract terms: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (b) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a first user device associated with a first user, the first user response including: (i) first user identification information associated with the first user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a second user device associated with a second user, the second user response including: (i) second user identification information associated with the second user; and (ii) second side information comprising identification of a second leg of the contract wherein the second leg is different than the first leg; (c) matching, by the administrator system, the first user response with the second user response; (d) providing, on the underlying blockchain, a stable value token smart contract having a first contract address on the underlying blockchain for a stable value digital asset token comprising instructions to: (1) create stable value tokens; (2) transfer stable value tokens; (3) destroy stable value tokens; and (4) authorization instructions; (e) providing, on the underlying blockchain, a security token smart contract having a second contract address on the underlying blockchain comprising instructions to: (1) create security tokens; (2) transfer security tokens; (3) destroy security tokens; (4) access data supplied by a first authorized third party database; (5) authorize instructions to transfer of stable value token to the second contract address; (6) authorize instructions to transfer of stable value token from the second contract address; and (7) calculate excess collateral; (f) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract on the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address on the underlying blockchain associated with the first user and a second user public address on the underlying blockchain associated with the second user, wherein the first trade is based at least on: (i) the contract terms; (ii) the first user response; and (iii) the second user response; (2) generating, by the administrator system, hashed trade instructions by applying a hash algorithm to the first trade instructions; (3) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the first transaction request includes a first message including: (i) the hashed trade instructions; and (ii) request to assign a first trade identification to a first trade associated with the hashed trade instructions, wherein the administrator public address on the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address, and wherein the first transaction request is signed by the administrator private key; (4) obtaining, by the administrator system, the first trade identification of the first trade; (5) sending, by the administrator system, the first trade identification to the first user device associated with the first user; (6) sending, by the administrator system, the first trade identification to the second user device associated with the second user; (7) monitoring, by the system administrator, transactions of stable value digital asset tokens on the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the first user; and (ii) a second amount of collateral in stable value digital asset tokens from the second user; (8) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the second transaction request includes a second message including: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction is signed by the administrator private key; and (g) collecting, by the administrator system from the security token smart contract, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, the third transaction request including a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions, and wherein the third transaction is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the third message, a fourth transaction request from the second contract address on the underlying blockchain to an oracle address on the underlying blockchain, wherein the oracle address is associated with an oracle interface, and wherein the fourth transaction request includes a sixth message to obtain first benchmark data; (3) receiving, by the security token smart contract from the oracle interface, a callback message; (4) executing, by the security token smart contract in response to receiving the callback message, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (5) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain, a fifth transaction request, from the second contract address on the underlying blockchain to the first contract address on the underlying blockchain, wherein the fifth transaction request including a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address on the underlying blockchain to the first user public address on the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address on the underlying blockchain to the second user public address on the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments, the contract further includes: (7) early termination rules; and (8) a second benchmark.
In embodiments the first user response further includes: (iii) a first user public address on the underlying blockchain; and (iv) first collateral information in stable value tokens.
In embodiments, the second user response further comprises: (iii) a second user public address on the underlying blockchain; and (iv) second collateral information in stable value token.
In embodiments the first transaction request further includes first transaction fee information. In embodiments the second transaction request further includes second transaction fee information.
In embodiments, the first trade identification further includes: (i) monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract.
In embodiments, the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further includes monitoring, by the administrator system, the first contract address on the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address on the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address on the underlying blockchain.
In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further includes monitoring, by the administrator system, the first contract address on the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address on the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address on the underlying blockchain. In embodiments, the second contract address further includes instructions to: (8) generate a collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received; and (9) send the collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value.
In embodiments the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information.
In embodiments the first user public address has a corresponding first user private key which is mathematically related to the first user public address.
In embodiments, the second user public address has a corresponding second user private key which is mathematically related to the second user public address.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token on the underlying blockchain, a sixth transaction is sent by the first user device via the underlying blockchain, from the first user public address on the underlying blockchain to the first contact address on the underlying blockchain, wherein the sixth transaction request comprises a sixth message including requests to the stable value token smart contract regarding a first transfer of the first amount of collateral, wherein the first user public address has a corresponding first user private key which is mathematically related to the first user public address; and wherein the sixth transaction request is signed by the first user private key.
In embodiments, the sixth transaction request further includes third transaction fee information.
In embodiments, the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address on the underlying blockchain to the second contract address on the underlying blockchain.
In embodiments, the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address on the underlying blockchain to the second user public address on the underlying blockchain are executed upon receipt of a first collateral request from the second contract address.
In embodiments, the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address on the underlying blockchain to the second user public address on the underlying blockchain are executed upon receipt of a first collateral request from the administrator system.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token on the underlying blockchain, a seventh transaction is sent by the second user device via the underlying blockchain, from the second user public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the seventh transaction request comprises a seventh message including requests to the stable value token smart contract regarding a second transfer of the second amount of collateral, wherein the second user public address has a corresponding second user private key which is mathematically related to the second user public address, and wherein the seventh transaction request is signed by the second user private key.
In embodiments, the seventh transaction request includes fourth transaction fee information.
In embodiments, the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address on the underlying blockchain to the second contract address on the underlying blockchain.
In embodiments, the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address on the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from the second contract address on the underlying blockchain.
In embodiments, the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address on the underlying blockchain to the second contract address on the underlying blockchain are executed upon receipt of a second collateral request from the second administrator system.
In embodiments, the step of collecting the excess collateral occurs in response to the security token smart contract verifying the first trade instructions against the hashed instructions.
In embodiments, a method for holding collateral in a smart contract on an underlying blockchain, the method includes: (a) publishing, by an administrator system associated with an administrator, contract information comprising at least the following contract terms: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (b) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a first user device associated with a first user, the first user response comprising: (i) first user identification information associated with the first user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a second user device associated with a second user, the second user response including: (i) second user identification information associated with the second user; and (ii) second side information comprising identification of a second leg of the contract wherein the second leg is different than the first leg; (c) matching, by the administrator system, the first user response with the second user response; (d) providing, on the underlying blockchain, a stable value token smart contract having a first contract address on the underlying blockchain for a stable value digital asset token including instructions to: (1) create stable value tokens; (2) transfer stable value tokens; (3) destroy stable value tokens; and (4) authorization instructions; (e) providing, on the underlying blockchain, a security token smart contract having a second contract address on the underlying blockchain including instructions to: (1) create security tokens; (2) transfer security tokens; (3) destroy security tokens; (4) access data supplied by a first authorized third party database; (5) authorize instructions to transfer stable value tokens to the second contract address; (6) authorize instructions to transfer stable value tokens from the second contract address; and (7) calculate excess collateral; (f) setting up, by the administrator system, a first trade between the first user and the second user using the security token smart contract, the step of setting up further comprising: (1) sending, by the administrator system via the underlying blockchain a first transaction request, from an administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the first transaction request comprises a first message including requests to create a first trade between a first user public address on the underlying blockchain associated with the first user device and a second user public address on the underlying blockchain associated with the second user device in accordance with the security token smart contract, wherein the administrator public address has a corresponding administrator private key which is mathematically related to the administrator public address, and wherein the first transaction request is signed by the administrator private key; (2) sending, by the administrator system via the underlying blockchain a second transaction request from the administrator public address on the underlying blockchain to the first contract address on the underlying blockchain, the second transaction request comprising a second message including requests to: (i) transfer of a first amount of collateral of stable value digital asset tokens from the first user public address to the second contract address; and (ii) transfer of a second amount of collateral of stable value digital asset tokens from the second user public address to the second contract address; wherein the second transaction request is signed by the administrator private key; and (g) collecting, by the administrator system from the security token smart contract, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, the third transaction request including a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and wherein the third transaction request is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the requests contained in the third message, a fourth transaction request from the second contract address on the underlying blockchain to an oracle address on the underlying blockchain, wherein the oracle address is associated with an oracle interface; and wherein the fourth transaction request includes a fourth message to obtain first benchmark data; (3) receiving, by the security token smart contract from the oracle interface, a callback message; (4) executing, by the security token smart contract in response to receiving the callback message, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (5) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract, via the underlying blockchain, a fifth transaction request, from the second contract address on the underlying blockchain to the first contract address on the underlying blockchain, wherein the fifth transaction request including a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address on the underlying blockchain to the first user public address on the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address on the underlying blockchain to the second user public address on the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments, a method for holding collateral in a smart contract on an underlying blockchain, the method including: (a) publishing, by an administrator system associated with an administrator, contract information including at least the following contract terms: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (b) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a first user device associated with a first user, the first user response comprising: (i) first user identification information associated with the first user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a second user device associated with a second user, the second user response comprising: (i) second user identification information associated with the second user; and (ii) second side information comprising identification of a second leg of the contract wherein the second leg is different than the first leg; (c) matching, by the administrator system, the first user response with the second user response; (d) providing, on the underlying blockchain, a stable value token smart contract having a first contract address on the underlying blockchain for a stable value digital asset token comprising instructions to: (1) create stable value tokens; (2) transfer stable value tokens; (3) destroy stable value token; and (4) authorization instructions; (e) providing, on the underlying blockchain, a security token smart contract having a second contract address on the underlying blockchain comprising instructions to: (1) create security tokens; (2) transfer security tokens; (3) destroy security tokens; (4) access data supplied by a first authorized third party database; (5) authorize instructions to transfer stable value tokens to the second contract address; (6) authorize instructions to transfer stable value tokens from the second contract address; and (7) calculate excess collateral; (f) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract on the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address on the underlying blockchain associated with the first user and a second user public address on the underlying blockchain associated with the second user, wherein the first trade is based at least on: (i) the contract terms; (ii) the first user response; and (iii) the second user response; (2) generating, by the administrator system, hashed trade instructions by applying a hash algorithm to the first trade instructions; (3) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the first transaction request includes a first message comprising: (i) the hashed trade instructions; and (ii) instructions to assign a first trade identification to a first trade associated with the hashed trade instructions, wherein the administrator public address on the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address, and wherein the first transaction request is signed by the administrator private key; (4) obtaining, by the administrator system, the first trade identification of the first trade; (5) sending, by the administrator system, the first trade identification to the first user device associated with the first user; (6) sending, by the administrator system, the first trade identification to the second user device associated with the second user; (7) monitoring, by the system administrator, transactions of stable value digital asset tokens on the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the first user; and (ii) a second amount of collateral in stable value digital asset tokens from the second user; (8) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the second transaction request includes a second message including: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction request is signed by the administrator private key; and (g) collecting, from the security token contract, first trade excess collateral, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain a third transaction request from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the third transaction request includes a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with security token smart contract and the first trade instructions; wherein the third transaction request is signed by the administrator private key; (2) executing, by the security token smart contract in response to receiving the requests contained in the third message, instructions to calculate first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (3) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain a fourth transaction request from the second contract address on the underlying blockchain to the first contract address on the underlying blockchain, the fourth transaction request comprising a fourth message including requests for the stable value token smart contract to transfer: (i) the first excess collateral, if the first excess collateral is greater than zero, in stable value token from the second contract address on the underlying blockchain to the first user public address on the underlying blockchain; and (ii) the second excess collateral, if the second excess collateral is greater than zero, in stable value token from the second contract address on the underlying blockchain to the second user public address on the underlying blockchain.
In embodiments, obtaining the first trade identification further includes (i) monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract.
In embodiments, a method for holding collateral in a smart contract on an underlying blockchain, the method including: (a) publishing, by an administrator system associated with an administrator, contract information comprising at least the following contract terms: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (b) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a first user device associated with a first user, the first user response comprising: (i) first user identification information associated with the first user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a second user device associated with a second user, the second user response comprising: (i) second user identification information associated with the second user; and (ii) second side information comprising identification of a second leg of the contract wherein the second leg is different than the first leg; (c) matching, by the administrator system, the first user response with the second user response; (d) providing, on the underlying blockchain, a stable value token smart contract having a first contract address on the underlying blockchain for a stable value digital asset token comprising instructions to: (1) create stable value tokens; (2) transfer stable value tokens; (3) destroy stable value tokens; and (4) authorization instructions; (e) providing, on the underlying blockchain, a security token smart contract having a second contract address on the underlying blockchain comprising instructions to: (1) create security tokens; (2) transfer security tokens; (3) destroy security token; (4) access data supplied by a first authorized third party database; (5) authorize instructions to transfer stable value tokens to the second contract address on the underlying blockchain; (6) authorize instructions to transfer stable value tokens from the second contract address on the underlying blockchain; and (7) calculate excess collateral; (f) setting up, by the administrator system, a first trade between the first user and the second user using the security token smart contract, the step of setting up further comprising: (1) sending, by the administrator system via the underlying blockchain a first transaction request, from an administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the first transaction request comprises a first message including requests to create a first trade between a first user public address on the underlying blockchain associated with the first user device and a second user public address on the underlying blockchain associated with the second user device in accordance with the security token smart contract; wherein the administrator public address has a corresponding administrator private key which is mathematically related to the administrator public address on the underlying blockchain; and wherein the first transaction request is signed by the administrator private key; (2) sending, by the administrator system via the underlying blockchain a second transaction request from the administrator public address on the underlying blockchain to the first contract address on the underlying blockchain, the second transaction request comprising a second message including requests to: (i) transfer of a first amount of collateral of stable value digital asset tokens from the first user public address to the second contract address on the underlying blockchain; and (ii) transfer of a second amount of collateral of stable value digital asset tokens from the second user public address to the second contract address on the underlying blockchain; wherein the second transaction request is signed by the administrator private key; and (g) collecting, from the security token contract, first trade excess collateral, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain a third transaction request from the administrator public address on the underlying blockchain to the second contract address on the underlying blockchain, wherein the third transaction request includes a third message comprising requests to the security token smart contract to: (i) determine excess collateral for the first trade in accordance with security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with security token smart contract and the first trade instructions; wherein the third transaction request is signed by the administrator private key; (2) executing, by the security token smart contract in response to receiving the requests contained in the third message, instructions to calculate first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (3) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain a fourth transaction request from the second contract address on the underlying blockchain to the first contract address on the underlying blockchain, the fourth transaction request comprising a fourth message including requests for the stable value token smart contract to transfer: (i) the first excess collateral, if the first excess collateral is greater than zero, in stable value token from the second contract address on the underlying blockchain to the first user public address on the underlying blockchain; and (ii) the second excess collateral, if the second excess collateral is greater than zero, in stable value token from the second contract address on the underlying blockchain to the second user public address on the underlying blockchain.
In embodiments, a method is disclosed which includes: (a) receiving, by an administrator system associated with an administrator of a security token smart contract, a contract proposal. In embodiments, the security token smart contract is maintained on a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network in the form of a blockchain of an underlying digital asset. In embodiments the contract proposal includes: (i) first user information associated with a first user device that is associated with a first user; and (2) first contract information including at least the following contract parameters: (A) an inception date; (B) an inception value; (C) at least one benchmark; (D) a contract duration; (E) at least one collateral requirement; (F) a notional value of the smart contract; and (G) first side information including identification of a first leg of the contract. In embodiments, the method continues with (b) receiving, by the administrator system at least one indication of interest. In embodiments, the at least one indication of interest includes at least: (i) a first user response, from a second user device associated with a second user, the first user response including: (1) second user information associated with the second user; and (2) second side information including identification of a second leg of the contract. In embodiments, the method continues with (c) matching, by the administrator system, the first contract information and the first user response. In embodiments, the method continues with (d) providing a stable value token smart contract associated with a stable value token and first smart contract instructions for a digital asset token associated with a first smart contract address associated with the blockchain for the underlying digital asset. In embodiments, the first smart contract instructions are saved in the blockchain for the underlying digital asset and include: (i) first authorization instructions regarding creating stable value tokens; (ii) second authorization instructions regarding transferring stable value tokens; (iii) third authorization instructions regarding destroying stable value tokens; and (iv) fourth authorization instructions regarding functions associated with the stable value token. In embodiments, the method continues with (e) generating, by the administrator system, the security token smart contract associated with a security token and second smart contract instructions associated with a second smart contract address associated with the blockchain for the underlying digital asset. In embodiments the second smart contract instructions are saved in the blockchain for the underlying digital asset and include: (i) first trade instructions for the security token smart contract, wherein the first trade instructions include execution instructions to execute a first trade between the first user and the second user, the first trade is based on at least the following: 1 the contract proposal; and 2 the first user response; (ii) fifth authorization instructions regarding transferring security tokens; (iii) sixth authorization instructions regarding destroying security tokens; (iv) seventh authorization instructions regarding transferring stable value tokens to the second contract address; (v) eighth authorization instructions regarding transferring stable value tokens from the second contract address; and (vi) calculating instructions regarding calculating excess collateral. In embodiments, the method continues with (f) sending, by an administrator system via the blockchain for the underlying digital asset to the second smart contract address, the security token smart contract and associated second smart contract instructions. In embodiments, the method may continue with (g) receiving, by the second contract address, a first amount of collateral. In embodiments, the first amount of collateral is a first amount of stable value tokens associated with the first user as collateral. In embodiments the first amount of stable value tokens associated with the first user is based on the at least one collateral requirement. In embodiments, the method may continue with (h) receiving, by the second contract address, a second amount of collateral. In embodiments the second amount of collateral is a second amount stable value tokens associated with the second user as collateral. In embodiments the second amount of stable value tokens associated with the second user is based on the at least one collateral requirement. In embodiments, the first trade instructions are implemented via the blockchain for the underlying digital asset by computers systems among the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the first trade instructions are implemented as a result of a message sent from the administrator system via the blockchain to the second smart contract address.
In embodiments, the first user information further includes a first user public address associated with the blockchain of the underlying digital asset. In embodiments the first user public address corresponds to a first user private key that is mathematically related to the first user public address. In embodiments, the second user information further includes a second user public address associated with the blockchain of the underlying digital asset. In embodiments the second user public address corresponds to a second user private key that is mathematically related to the second user public address.
In embodiments, the step of receiving a first amount of collateral further includes sending, by the first user device via the underlying blockchain from the first user public address associated with the underlying blockchain to the first smart contract address associated with the underlying blockchain, a first message including a request to transfer the first amount of collateral from the first user public address to the second smart contract address.
In embodiments, the first user device sends a second message to the first smart contract address including authorization for the security token smart contract to request a transfer of the first amount of collateral. In embodiments, the administrator system sends a third message via the underlying blockchain to the second smart contract address with instructions to send a request from the second smart contract address to the first smart contract address for the first amount of collateral to be transferred from the first user public address to the second smart contract address. In embodiments, the step of receiving a second amount of collateral further includes sending, by the second user device via the underlying blockchain from the second user public address associated with the underlying blockchain to the first smart contract address associated with the underlying blockchain, a fourth message including a request to transfer the second amount of collateral from the second user public address to the second smart contract address. In embodiments, the second user device sends a fifth message to the first smart contract address including authorization for the security token smart contract to request a transfer of the second amount of collateral via the blockchain, and the administrator system sends a sixth message via the underlying blockchain to the second smart contract address with instructions to send a request for the second amount of collateral to be transferred from the second user public address to the second smart contract address.
In embodiments, the method further includes (i) recalculating the first collateral amount based on the at least one collateral requirement and current benchmark information; (j) determining a first additional collateral amount based on a difference between the recalculated first collateral amount and the first collateral amount; and (k) receiving, at the second smart contract address, the first additional collateral amount. In embodiments the recalculating step is performed by the first user device. In embodiments the recalculating step is performed by the administrator system, and further includes: (i) generating, by the administrator system, an alert including the first additional collateral amount; and (ii) sending, by the administrator system, to the first user device, the alert. In embodiments, the method further includes: (l) monitoring, by the administrator system, the second contract address on the blockchain associated with the underlying digital asset; (m) determining, by the administrator system, whether the first additional collateral amount is received by the second contract address; (n) generating, by the administrator system, a default notification when the administrator system determines that the first additional collateral amount is not received by the second contract address; (o) sending, by the administrator system, the default notification to the first user device, the second user device and the second smart contract address; (p) generating, by the administrator system, a seventh message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first trade instructions; and (q) sending, by the administrator system, the seventh message to the second smart contract address, where transfers of the first collateral amount and the second collateral amount are implemented by the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the method further includes (i) recalculating the second collateral amount based on the at least one collateral requirement and current benchmark information; (j) determining a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (k) receiving, at the second smart contract address, the second additional collateral amount. In embodiments, the recalculating step is performed by the second user device. In embodiments the recalculating step is performed by the administrator system, and further includes: (i) generating, by the administrator system, an alert to the second user including the second additional collateral amount; and (ii) sending, by the administrator system, to the second user device, the alert. In embodiments, the method further includes: (l) monitoring, by the administrator system, the second contract address on the blockchain associated with the underlying digital asset; (m) determining, by the administrator system, whether the second additional collateral amount is received by the second contract address; (n) generating, by the administrator system, a default notification when the administrator system determines that the second additional collateral amount is not received by the second contract address; (o) sending, by the administrator system, the default notification to the first user device, the second user device and the second smart contract address; (p) generating, by the administrator system, an eighth message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first trade instructions; and (q) sending, by the administrator system, the eighth message to the second smart contract address, where transfers of the first collateral amount and the second collateral amount are implemented by the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the method further includes: (i) determining, by the administrator system, at the end of the contract duration, a payout amount based on at least the first trade instructions; (j) generating, by the administrator system, payout instructions based at least on the first side information and the second side information; and (k) sending, by the administrator system, the payout instructions to the second contract address via the blockchain to provide the payout amount to one of the first user public address and the second user public address, wherein the payout instructions are implemented by the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the method further includes: (i) collecting, by the administrator system from the security token, excess collateral from the first trade. In embodiments, the collecting step includes: (1) sending, by the administrator system via the blockchain for the underlying digital asset, a ninth message including first requests for the security token to: (A) determine first excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; (B) determine second excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; (C) distribute the first excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions to the first user address; and (D) distribute the second excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions to the second user address.
In embodiments, the method further includes: (i) returning, by the administrator system from the security token smart contract, remaining collateral from the first trade. In embodiments returning includes: (1) sending a tenth message including requests for the security token smart contract to: (A) determine first remaining collateral for the first trade in accordance with the security token smart contract and the first trade instructions; (B) determine second remaining collateral for the first trade in accordance with the security token smart contract and the first trade instructions; (C) distribute the first remaining collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (D) distribute the second remaining collateral for the first trade in accordance with the security token smart contract and the first trade instructions.
In embodiments, the method further includes: (i) determining a first benchmark value. In embodiments, determining the first benchmark value includes: (1) sending, by the security token smart contract via the blockchain for the underlying digital asset, a request from the second contract address to an oracle smart contract at a third contract address associated with the blockchain for the underlying digital asset, wherein the oracle smart contract is associated with an oracle interface in contact with an authorized third party database, wherein the message includes an eleventh message to obtain first benchmark information; (2) receiving, by the security token smart contract from the oracle smart contract, the first benchmark information; and (3) executing, by the security token in response to receiving the first benchmark information, instructions to: (A) store the first benchmark information. In embodiments, in the case where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, the method further includes: (j) calculating the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (k) sending, from the second smart contract address to the first smart contract address, a twelfth message including a request for the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address to the first user public address, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address to the second user public address, if the second excess collateral is greater than zero.
In embodiments, the step 1(a), receiving a contract proposal, further includes: (i) generating, by the administrator system, graphical user interface information including at least one prompt for the first user to provide the contract proposal; (ii) sending, by the administrator system to the first user device, the graphical user interface information; and (iii) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the first contract information further includes at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, the first contract information further includes: (H) first collateral information in stable value tokens.
In embodiments, the first contract information further includes: (H) second collateral information in stable value tokens.
In embodiments, the first contract information includes first transaction fee information.
In embodiments, the underlying digital asset is a digital math-based asset.
In embodiments, the underlying digital asset is Ether.
In embodiments, the underlying digital asset is Neo.
In embodiments, the first smart contract instructions of the first stable value smart contract are associated with more than one smart contract address.
In embodiments, a method for generating a smart contract on an underlying blockchain includes: (a) receiving, at an administrator system associated with an administrator, a contract request, the contract request including: (1) first user information associated with a first user device that is associated with a first user; and (2) a smart contract generation request; (b) generating, by the administrator system, graphical user interface information including at least one prompt for the first user to provide contract parameters related to the smart contract to be generated; (c) sending, by the administrator system, the graphical user interface information to the first user device; (d) receiving, from the first user device, in response to the at least one prompt, contract information related to the contract parameters of the contract to be generated; (e) storing, in a memory operably connected to the administrator system, the contract information; (f) publishing, by the administrator system, the contract information, wherein the contract information comprises at least the following contract parameters: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (g) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a second user device associated with a second user, the first user response comprising: (i) second user identification information associated with the second user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a third user device associated with a third user, the second user response comprising: (i) third user identification information associated with the third user; and (ii) second side information comprising identification of a second leg of the contract, wherein the second leg information is different than the first leg information; (h) matching, by the administrator system, the first user response with the second user response; (i) providing a stable value token smart contract associated with a stable value token and first smart contract instructions associated with a first contract address associated with the blockchain for the underlying digital asset, wherein the first smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating stable value tokens; (2) authorization instructions related to transferring stable value tokens; (3) authorization instructions related to destroying stable value tokens; and (4) authorizing instructions related to functions associated with stable value tokens; (j) providing a security token smart contract associated with a security token and second contract instructions associated with a second smart contract address associated with the blockchain for the underlying digital asset, wherein the second smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating of security tokens; (2) authorization instructions related to transferring security tokens; (3) authorization instructions related to destroying security tokens; (4) authorization instructions related to accessing data supplied by a first authorized third party database; (5) authorization instructions related to transferring stable value tokens to the second contract address; (6) authorization instructions related to transferring stable value tokens from the second contract address; and (7) calculating instructions relating to calculating excess collateral; (k) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address associated with the underlying blockchain associated with the second user and a second user public address associated with the underlying blockchain associated with the third user, wherein the first trade is based at least on: (i) the contract parameters; (ii) the first user response; and (iii) the second user response; (2) generating, by the administrator system, hashed first trade instructions by applying a hash algorithm to the first trade instructions; (3) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the first transaction request includes a first message comprising: (i) the hashed first trade instructions; and (ii) a request to assign a first trade identification to a first trade associated with the hashed first trade instructions; wherein the administrator public address associated with the underlying blockchain has a corresponding administrator private key, the administrator private key being mathematically related to the administrator public address; and wherein the first transaction request is signed by the administrator private key; (4) obtaining, by the administrator system, a first trade identification of the first trade; (5) sending, by the administrator system, the first trade identification to the first user device associated with the first user; (6) sending, by the administrator system, the first trade identification to the second user device associated with the second user; (7) sending, by the administrator system, the first trade identification to the third user device associated with the second user; (8) monitoring, by the system administrator, transactions of stable value digital asset tokens associated with the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the second user; and (ii) a second amount of collateral in stable value digital asset tokens from the third user; (9) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the second transaction request includes a second message comprising: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction is signed by the administrator private key; and (1) collecting, by the administrator system from the security token, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, the third transaction request including a third message comprising requests for the security token to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and wherein the third transaction is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the third message, a fourth transaction request from the second contract address associated with the underlying blockchain to an oracle smart contract at a third contract address associated with the underlying blockchain, wherein the oracle smart contract is associated with an oracle interface in contact with the authorized third party database; and wherein the fourth transaction request includes a fourth message to obtain first benchmark information; (3) receiving, by the security token smart contract from the oracle smart contract, the first benchmark information; (4) executing, by the security token in response to receiving the callback message, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the second user and second excess collateral for the third user by using the first trade instructions and the first benchmark information; and (5) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token via the underlying blockchain, a fifth transaction request, from the second contract address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the fifth transaction request includes a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the second user public address associated with the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the third user public address associated with the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments, the contract parameters may further include at least one of: (7) derivative type information; (8) early termination rules; (9) a second benchmark; (10) asset identification information; (11) pricing model information; and (12) volatility information.
In embodiments, the first user response may further include: (iii) a first user public address associated with the underlying blockchain; and (iv) first collateral information in stable value tokens.
In embodiments, the second user response may further include: (iii) a second user public address associated with the underlying blockchain; and (iv) second collateral information in stable value token.
In embodiments, the first transaction request may include first transaction fee information.
In embodiments, obtaining the first trade identification further comprises: monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract.
In embodiments, the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises monitoring, by the administrator system, the first contract address associated with the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address associated with the underlying blockchain.
In embodiments, the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises receiving, from the second contract address associated with the underlying blockchain, a collateral confirmation message confirming that: (i) the first amount of collateral has been received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral has been received at the second contract address associated with the underlying blockchain.
In embodiments the second contract address is associated with instructions including: (8) authorization instructions related to generating a collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received; and (9) authorization instructions related to sending the collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments, the second transaction request further includes second transaction fee information.
In embodiments, the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value.
In embodiments the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information.
In embodiments the second user public address has a corresponding second user private key which is mathematically related to the second user public address.
In embodiments the third user public address has a corresponding third user private key which is mathematically related to the third user public address.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a sixth transaction is sent by the second user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the sixth transaction request comprises a sixth message including requests to the stable value token smart contract regarding a first transfer of the first amount of collateral; wherein the second user public address has a corresponding second user private key which is mathematically related to the second user public address; and wherein the sixth transaction request is signed by the second user private key. In embodiments, the sixth transaction request further includes third transaction fee information. In embodiments, the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract associated with the underlying blockchain are executed upon receipt of a first collateral request from the second contract address. In embodiments, the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a first collateral request from a fourth contract address associated with the second contract address. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a first collateral request from the administrator system.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a seventh transaction is sent by the fourth user device via the underlying blockchain, from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the seventh transaction request comprises a seventh message including requests to the stable value token smart contract regarding a second transfer of the second amount of collateral; wherein the third user public address has a corresponding third user private key which is mathematically related to the fourth user public address; and wherein the seventh transaction request is signed by the third user private key. In embodiments the seventh transaction request includes fourth transaction fee information. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to a fourth contract address related to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a second collateral request from the second administrator system.
In embodiments the step of collecting the excess collateral occurs in response to the security token smart contract verifying the first trade instructions against the hashed instructions. In embodiments the step (g) further comprises receiving: (3) a third user response, from a fourth user device associated with a fourth user, the third user response comprising: (i) third user identification information associated with the fourth user; and (ii) third side information comprising identification of the first leg of the contract; and (4) a fourth user response, from a fifth user device associated with a fifth user, the fourth user response comprising: (i) fourth user identification information associated with the fifth user; and (ii) fourth side information comprising identification of the fourth leg of the contract, wherein the fourth side information is different than the third side information. In embodiments, the matching step (h) further comprises matching the third user response with the fourth user response. In embodiments, in the event that there is no match the process may terminate and/or wait until there is a match to proceed. In embodiments the process further includes: (m) setting up, by the administrator system, a second trade between the fourth user and the fifth user, the second trade using the security token smart contract associated with the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, second trade instructions for the security token smart contract, the second trade instructions including instructions to execute the second trade between a fourth user public address associated with the underlying blockchain associated with the fourth user and a fifth user public address associated with the underlying blockchain associated with the fifth user, wherein the second trade is based at least on: (i) the contract parameters; (ii) the third user response; and (iii) the fourth user response; (2) generating, by the administrator system, hashed second trade instructions by applying the hash algorithm to the second trade instructions (3) sending, by the administrator system via the underlying blockchain, a sixth transaction request, from an administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the sixth transaction request includes a sixth message comprising: i. the hashed second trade instructions; and ii. a request to assign a second trade identification to the second trade; wherein the administrator public address associated with the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address; and wherein the sixth transaction request is signed by the administrator private key; (4) obtaining, by the administrator system, the second trade identification of the second trade; (5) sending, by the administrator system, the second trade identification to the first user device associated with the first user; (6) sending, by the administrator system, the second trade identification to the fourth user device associated with the third user; (7) sending, by the administrator system, the second trade identification to the fifth user device associated with the fourth user; (8) monitoring, by the system administrator, transactions of stable value digital asset tokens associated with the underlying blockchain to determine that the second contract address has received at least the following: (i) a third amount of collateral in stable value digital asset tokens from the third user; and (ii) a fourth amount of collateral in stable value digital asset tokens from the fourth user; (9) sending, by the administrator system via the underlying blockchain, a seventh transaction request, from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the seventh transaction request includes a seventh message comprising: (i) the second trade instructions; and (ii) the second trade identification; and wherein the seventh transaction request is signed by the administrator private key; and (n) collecting, by the administrator system from the security token smart contract, excess collateral from the second trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, an eight transaction request from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, the eight transaction request including an eight message comprising requests for the security token smart contract to: (i) determine excess collateral for the second trade in accordance with the security token smart contract and the second trade instructions; and (ii) distribute excess collateral for the second trade in accordance with the security token smart contract and the second trade instructions; and wherein the eight transaction request is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the eight message, a ninth transaction request from the second contract address associated with the underlying blockchain to the oracle smart contract at the third contract address associated with the underlying blockchain, wherein the oracle smart contract is associated with the oracle interface in contact with the authorized third party database; and wherein the ninth transaction request includes a ninth message to obtain second benchmark information; (3) receiving, by the security token smart contract from the oracle interface, the second benchmark information; (4) executing, by the security token smart contract in response to receiving the callback message, instructions to: (i) store the second benchmark information; and (ii) calculate the third excess collateral for the fourth user and fourth excess collateral for the fifth user by using the second trade instructions and the second benchmark information; and (5) in the cases where at least one of the third excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain, a tenth transaction request, from the second contract address associated with the underlying blockchain to the fourth contract address associated with the underlying blockchain, wherein the tenth transaction request includes an eleventh message requesting the stable value token smart contract to transfer: (i) the third excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the fourth user public address associated with the underlying blockchain, if the third excess collateral is greater than zero; and (ii) the fourth excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the fifth user public address associated with the underlying blockchain, if the fourth excess collateral is greater than zero.
In embodiments the fourth message further comprises the second contract address and the oracle smart contract only provides the first benchmark information to the second contract address when the second contract address is included in a list of approved contract addresses.
In embodiments the list of approved contract addresses may be modified periodically.
In embodiments the list of approved contract addresses may be modified aperiodically.
In embodiments, a method for generating a smart contract on an underlying blockchain includes: (a) receiving, at an administrator system associated with an administrator, a contract request, the contract request including: (1) first user information associated with a first user device that is associated with a first user; (2) second user information associated with a second user device that is associated with a second user; and (3) a request to generate the smart contract; (b) generating, by the administrator system, graphical user interface information including at least one prompt for the first user to provide contract parameters related to the smart contract to be generated; (c) sending, by the administrator system, the graphical user interface information to the first user device and the second user device; (d) receiving, from at least one of the first user device and the second user device, contract information related to contract parameters of the smart contract to be generated; (e) storing, in a memory operably connected to the administrator system, the contract information; (f) publishing, by the administrator system, the contract information, wherein the contract information comprises at least the following contract parameters: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; (6) a notional value of the contract; (7) first leg information associated with the first user; and (8) second leg information associated with the second user; (g) providing a stable value token smart contract associated with a stable value token and first smart contract instructions associated with a first contract address associated with the blockchain for the underlying digital asset, wherein the first smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating stable value tokens; (2) authorization instructions related to transferring stable value tokens; (3) authorization instructions related to destroying stable value tokens; and (4) authorizing instructions related to functions associated with stable value tokens; (h) providing a security token smart contract associated with a security token and second contract instructions associated with a second smart contract address associated with the blockchain for the underlying digital asset, wherein the second smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating security tokens; (2) authorization instructions related to transferring security tokens; (3) authorization instructions related to destroying security tokens; (4) authorization instructions related to accessing data supplied by a first authorized third party database; (5) authorization instructions related to transferring stable value tokens to the second contract address; (6) authorization instructions related to transferring stable value tokens from the second contract address; and (7) calculating instructions relating to calculating excess collateral; (i) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract associated with the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address associated with the underlying blockchain associated with the first user and a second user public address associated with the underlying blockchain associated with the second user, wherein the first trade is based at least on the contract parameters; (2) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the first transaction request includes a first message comprising a request to assign a first trade identification to a first trade; wherein the administrator public address associated with the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address; and wherein the first transaction request is signed by the administrator private key; (3) obtaining, by the administrator system, the first trade identification of the first trade; (4) sending, by the administrator system, the first trade identification to the first user device associated with the first user; (5) sending, by the administrator system, the first trade identification to the second user device associated with the second user; (6) monitoring, by the administrator system, transactions of stable value digital asset tokens on the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the first user; and (ii) a second amount of collateral in stable value digital asset tokens from the second user; (8) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the second transaction request includes a second message comprising: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction is signed by the administrator private key; and (j) collecting, by the administrator system from the security token smart contract, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, the third transaction request including a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and wherein the third transaction is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the third message, a fourth transaction request from the second contract address associated with the underlying blockchain to an oracle smart contract associated with a third contract address associated with the underlying blockchain to retrieve first benchmark information, wherein the oracle smart contract is associated with an oracle interface in contact with the authorized third party database; and wherein the fourth transaction request includes a fourth message to obtain first benchmark information; (3) receiving, by the security token smart contract from the oracle smart contract, the first benchmark information; (4) executing, by the security token smart contract in response to receipt of the first benchmark information, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (5) in the case where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain, a fifth transaction request, from the second contract address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the fifth transaction request including a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the first user public address associated with the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the second user public address associated with the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments the contract parameters further comprise at least one of: (7) derivative type information; (8) early termination rules; (9) a second benchmark; (10) asset identification information; (11) pricing model information; and (12) volatility information.
In embodiments, the first user response further comprises: (iii) a first user public address associated with the underlying blockchain; and (iv) first collateral information in stable value tokens.
In embodiments, the second user response further comprises: (iii) a second user public address associated with the underlying blockchain; and (iv) second collateral information in stable value token.
In embodiments, the first transaction request further includes first transaction fee information. In embodiments obtaining the first trade identification further comprises: (i) monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract.
In embodiments, the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises monitoring, by the administrator system, the first contract address associated with the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address associated with the underlying blockchain.
In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises receiving, from the second contract address associated with the underlying blockchain, a collateral confirmation message confirming that: (i) the first amount of collateral has been received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral has been received at the second contract address associated with the underlying blockchain.
In embodiments the second contract address is associated with instructions including: (8) authorization instructions related to generating a collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received; and (9) authorization instructions related to sending the collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments, the second transaction request further includes second transaction fee information.
In embodiments the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value.
In embodiments, the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information.
In embodiments the first user public address has a corresponding first user private key which is mathematically related to the first user public address.
In embodiments the second user public address has a corresponding second user private key which is mathematically related to the second user public address.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a sixth transaction is sent by the second user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the sixth transaction request comprises a sixth message including requests to the stable value token smart contract regarding a first transfer of the first amount of collateral; wherein the second user public address has a corresponding second user private key which is mathematically related to the second user public address; and wherein the sixth transaction request is signed by the second user private key. In embodiments the sixth transaction request further includes third transaction fee information. In embodiments, the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from the second contract address. In embodiments, the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from a fourth contract address associated with the second contract address. In embodiments, the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from the administrator system.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a seventh transaction is sent by the third user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the seventh transaction request comprises a seventh message including requests to the stable value token smart contract regarding a second transfer of the second amount of collateral; wherein the third user public address has a corresponding third user private key which is mathematically related to the third user public address; and wherein the seventh transaction request is signed by the third user private key. In embodiments the seventh transaction request includes fourth transaction fee information. In embodiments, the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to a fourth contract address related to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from the second contract address associated with the underlying blockchain. In embodiments, the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a second collateral request from the second administrator system. In embodiments, the step of collecting the excess collateral occurs in response to the security token smart contract verifying the first trade instructions against the hashed instructions.
In embodiments, the fourth message further comprises the second contract address and the oracle smart contract only provides the first benchmark information to second contract address when the second contract address is included in a list of approved contract addresses.
In embodiments the list of approved contract addresses may be modified periodically.
In embodiments the list of approved contract addresses may be modified aperiodically.
In embodiments, a method for generating a smart contract on an underlying blockchain includes: (a) receiving, at an administrator system associated with an administrator, a contract request, the contract request including: (1) first user information associated with a first user device that is associated with a first user; and (2) a request to generate a contract; (b) generating, by the administrator system, graphical user interface information including at least one prompt for the first user to provide contract parameters related to the smart contract to be generated; (c) sending, by the administrator system, the graphical user interface information to the first user device; (d) receiving, from the first user device, in response to the at least one prompt, contract information related to the contract parameter of the contract to be generated; (e) storing, in a memory operably connected to the administrator system, the contract information; (f) publishing, by the administrator system, the contract information, wherein the contract information comprises at least the following contract parameters: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; (6) a notional value of the contract; and (7) first leg information associated with the first user; (g) receiving, by the administrator system, at least one indication of interest, the at least one indication of interests including at least: (1) a first user response, from a second user device associated with a second user, the second user response comprising: (i) second user identification information associated with the second user; and (ii) second leg information associated with the second user, wherein the second leg information is different from the first leg information; (h) matching, by the administrator system, the first user response with the contract request of the first user based at least on the first leg information and the second leg information; (i) providing a stable value token smart contract associated with a stable value token and first smart contract instructions associated with a first contract address associated with the blockchain for the underlying digital asset, wherein the first smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating stable value tokens; (2) authorization instructions related to transferring stable value tokens; (3) authorization instructions related to destroying stable value tokens; and (4) authorizing instructions related to functions associated with stable value tokens; (j) providing a security token smart contract associated with a security token and second contract instructions associated with a second smart contract address associated with the blockchain for the underlying digital asset, wherein the second smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating security tokens; (2) authorization instructions related to transferring security tokens; (3) authorization instructions related to destroying security tokens; (4) authorization instructions related to accessing data supplied by a first authorized third party database; (5) authorization instructions related to transferring stable value tokens to the second contract address; (6) authorization instructions related to transferring stable value tokens from the second contract address; and (7) calculating instructions relating to calculating excess collateral; (k) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract associated with the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address associated with the underlying blockchain associated with the first user and a second user public address associated with the underlying blockchain associated with the second user, wherein the first trade is based at least on the contract parameters and the first user request; (2) generating, by the administrator system, hashed first trade instructions by applying a hash algorithm to the first trade instructions; (3) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the first transaction request includes a first message comprising: (i) the hashed first trade instructions; and (ii) a request to assign a first trade identification to a first trade associated with the hashed trade instructions; wherein the administrator public address associated with the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address; and wherein the first transaction request is signed by the administrator private key; (3) obtaining, by the administrator system, the first trade identification of the first trade; (4) sending, by the administrator system, the first trade identification to the first user device; (5) sending, by the administrator system, the first trade identification to the second user device; (6) monitoring, by the system administrator, transactions of stable value digital asset tokens on the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the first user; and (ii) a second amount of collateral in stable value digital asset tokens from the second user; (7) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the second transaction request includes a second message comprising: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction is signed by the administrator private key; and (1) collecting, by the administrator system from the security token smart contract, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, the third transaction request including a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and wherein the third transaction is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the third message, a fourth transaction request from the second contract address associated with the underlying blockchain to an oracle smart contract associated with a third contract address associated with the underlying blockchain, wherein the oracle smart contract is associated with an oracle interface in contact with the authorized third party database; and wherein the fourth transaction request includes a sixth message to obtain first benchmark information; (3) receiving, by the security token smart contract from the oracle interface, the first benchmark information; (4) executing, by the security token smart contract in response to receiving the first benchmark information, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (5) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain, a fifth transaction request, from the second contract address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the fifth transaction request includes a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the first user public address associated with the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the second user public address associated with the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments the contract parameters further comprise at least one of: (7) derivative type information; (8) early termination rules; (9) a second benchmark; (10) asset identification information; (11) pricing model information; and (12) volatility information.
In embodiments the first user response further comprises: (iii) a first user public address associated with the underlying blockchain; and (iv) first collateral information in stable value tokens.
In embodiments the second user response further comprises: (iii) a second user public address associated with the underlying blockchain; and (iv) second collateral information in stable value token.
In embodiments the first transaction request further includes first transaction fee information.
In embodiments obtaining the first trade identification further comprises: (i) monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract.
In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises monitoring, by the administrator system, the first contract address associated with the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address associated with the underlying blockchain.
In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises receiving, from the second contract address associated with the underlying blockchain, a collateral confirmation message confirming that: (i) the first amount of collateral has been received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral has been received at the second contract address associated with the underlying blockchain.
In embodiments the second contract address is associated with instructions including: (8) authorization instructions related to generating a collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received; and (9) authorization instructions related to sending the collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments the second transaction request further includes second transaction fee information.
In embodiments the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value.
In embodiments the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information.
In embodiments, the first user public address has a corresponding first user private key which is mathematically related to the first user public address.
In embodiments the second user public address has a corresponding second user private key which is mathematically related to the second user public address.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a sixth transaction is sent by the second user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the sixth transaction request comprises a sixth message including requests to the stable value token smart contract regarding a first transfer of the first amount of collateral; wherein the second user public address has a corresponding second user private key which is mathematically related to the second user public address; and wherein the sixth transaction request is signed by the second user private key. In embodiments the sixth transaction request further includes third transaction fee information. In embodiments the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from the second contract address. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from a fourth contract address associated with the second contract address. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the third user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from the administrator system.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token associated with the underlying blockchain, a seventh transaction is sent by the third user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the seventh transaction request comprises a seventh message including requests to the stable value token smart contract regarding a second transfer of the second amount of collateral; wherein the third user public address has a corresponding third user private key which is mathematically related to the third user public address; and wherein the seventh transaction request is signed by the third user private key. In embodiments the seventh transaction request includes fourth transaction fee information. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to a fourth contract address related to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the third user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a second collateral request from the second administrator system. In embodiments the step of collecting the excess collateral occurs in response to the security token smart contract verifying the first trade instructions against the hashed instructions.
In embodiments the fourth message further comprises the second contract address and the oracle smart contract only provides the first benchmark information to second contract address when the second contract address is included in a list of approved contract addresses.
In embodiments the list of approved contract addresses may be modified periodically.
In embodiments the list of approved contract addresses may be modified aperiodically.
A method for holding collateral in a smart contract on an underlying blockchain may include: (a) publishing, by an administrator system associated with an administrator, contract information comprising at least the following contract parameters: (1) an inception date; (2) an inception value; (3) at least one benchmark; (4) a contract duration; (5) at least one collateral requirement; and (6) a notional value of the contract; (b) receiving, by the administrator system, a plurality of indications of interests, wherein the plurality of indications of interests include at least: (1) a first user response, from a first user device associated with a first user, the first user response comprising: (i) first user identification information associated with the first user; and (ii) first side information comprising identification of a first leg of the contract; and (2) a second user response, from a second user device associated with a second user, the second user response comprising: (i) second user identification information associated with the second user; and (ii) second side information comprising identification of a second leg of the contract wherein the second leg is different than the first leg; (c) matching, by the administrator system, the first user response with the second user response; (d) providing a stable value token smart contract associated with a stable value token and first smart contract instructions associated with a first contract address associated with the blockchain for the underlying digital asset, wherein the first smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating stable value tokens; (2) authorization instructions related to transferring stable value tokens; (3) authorization instructions related to destroying stable value tokens; and (4) authorizing instructions related to functions associated with stable value tokens; (e) providing a security token smart contract associated with a security token and second contract instructions associated with a second smart contract address associated with the blockchain for the underlying digital asset, wherein the second smart contract instructions are saved in the blockchain for the underlying digital asset and include: (1) authorization instructions related to creating security tokens; (2) authorization instructions related to transferring security tokens; (3) authorization instructions related to destroying security tokens; (4) authorization instructions related to accessing data supplied by a first authorized third party database; (5) authorization instructions related to transferring stable value tokens to the second contract address; (6) authorization instructions related to transferring stable value tokens from the second contract address; and (7) calculating instructions relating to calculating excess collateral; (f) setting up, by the administrator system, a first trade between the first user and the second user, the first trade using the security token smart contract associated with the underlying blockchain with collateral in the form of stable value digital asset tokens, the step of setting up further comprising: (1) generating, by the administrator system, first trade instructions for the security token smart contract, the first trade instructions including instructions to execute the first trade between a first user public address associated with the underlying blockchain associated with the first user and a second user public address associated with the underlying blockchain associated with the second user, wherein the first trade is based at least on: (i) the contract terms; (ii) the first user response; and (iii) the second user response; (2) generating, by the administrator system, hashed trade instructions by applying a hash algorithm to the first trade instructions; (3) sending, by the administrator system via the underlying blockchain, a first transaction request, from an administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the first transaction request includes a first message comprising: (i) the hashed trade instructions; and (ii) request to assign a first trade identification to a first trade associated with the hashed trade instructions; wherein the administrator public address on the underlying blockchain has a corresponding administrator private key, wherein the administrator private key being mathematically related to the administrator public address; and wherein the first transaction request is signed by the administrator private key; (4) obtaining, by the administrator system, the first trade identification of the first trade; (5) sending, by the administrator system, the first trade identification to the first user device associated with the first user; (6) sending, by the administrator system, the first trade identification to the second user device associated with the second user; (7) monitoring, by the system administrator, transactions of stable value digital asset tokens on the underlying blockchain to determine that the second contract address has received at least the following: (i) a first amount of collateral in stable value digital asset tokens from the first user; and (ii) a second amount of collateral in stable value digital asset tokens from the second user; (8) sending, by the administrator system via the underlying blockchain, a second transaction request, from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the second transaction request includes a second message comprising: (i) the first trade instructions; and (ii) the first trade identification; and wherein the second transaction is signed by the administrator private key; and (g) collecting, by the administrator system from the security token smart contract, excess collateral from the first trade, wherein collecting comprises: (1) sending, by the administrator system via the underlying blockchain, a third transaction request from the administrator public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, the third transaction request including a third message comprising requests for the security token smart contract to: (i) determine excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and (ii) distribute excess collateral for the first trade in accordance with the security token smart contract and the first trade instructions; and wherein the third transaction is signed by the administrator private key; (2) sending, by the security token smart contract via the underlying blockchain in response to the instructions contained in the third message, a fourth transaction request from the second contract address associated with the underlying blockchain to an oracle smart contract associated with a third contract address associated with the underlying blockchain, wherein the oracle smart contract is associated with an oracle interface in contact with the authorized third party; and wherein the fourth transaction request includes a sixth message to obtain first benchmark data; (3) receiving, by the security token smart contract from the oracle smart contract, the first benchmark information; (4) executing, by the security token smart contract in response to receiving the callback message, instructions to: (i) store the first benchmark information; and (ii) calculate the first excess collateral for the first user and second excess collateral for the second user by using the first trade instructions and the first benchmark information; and (5) in the cases where at least one of the first excess collateral is greater than zero or the second excess collateral is greater than zero, sending, by the security token smart contract via the underlying blockchain, a fifth transaction request, from the second contract address associated with the underlying blockchain to the first contract address associated with the underlying blockchain, wherein the fifth transaction request including a fifth message requesting the stable value token smart contract to transfer: (i) the first excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the first user public address associated with the underlying blockchain, if the first excess collateral is greater than zero; and (ii) the second excess collateral in stable value tokens from the second contract address associated with the underlying blockchain to the second user public address associated with the underlying blockchain, if the second excess collateral is greater than zero.
In embodiments the contract parameters further comprise at least one of: (7) early termination rules; and (8) a second benchmark.
In embodiments the first user response further comprises: (iii) a first user public address on the underlying blockchain; and (iv) first collateral information in stable value tokens.
In embodiments the second user response further comprises: (iii) a second user public address on the underlying blockchain; and (iv) second collateral information in stable value token.
In embodiments the first transaction request further includes first transaction fee information.
In embodiments, obtaining the first trade identification further comprises: (i) monitoring, by the administrator system, transactions on the underlying blockchain to determine the first trade identification as calculated by the security token smart contract. In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises monitoring, by the administrator system, the first contract address on the underlying blockchain to determine: (i) the first amount of collateral is received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral is received at the second contract address associated with the underlying blockchain. In embodiments the step of monitoring transactions of the stable value digital asset token on the underlying blockchain further comprises receiving, from the second contract address associated with the underlying blockchain, a collateral confirmation message confirming that: (i) the first amount of collateral has been received at the second contract address associated with the underlying blockchain; and (ii) the second amount of collateral has been received at the second contract address associated with the underlying blockchain. In embodiments the second contract instructions include: (8) authorization instructions that relate to generating a collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received; and (9) authorization instructions that relate to sending the collateral confirmation message to the administrator system confirming receipt of at least one of the first amount of collateral and the second amount of collateral when at least one of the first amount of collateral and the second amount of collateral is received.
In embodiments the second transaction request further includes second transaction fee information.
In embodiments the first excess collateral is the first amount of collateral less the difference between the first benchmark information and the inception value.
In embodiments the second excess collateral is the second amount of collateral less the difference between the inception value and the first benchmark information.
In embodiments the first user public address has a corresponding first user private key which is mathematically related to the first user public address.
In embodiments the second user public address has a corresponding second user private key which is mathematically related to the second user public address.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token on the underlying blockchain, a sixth transaction request is sent by the first user device via the underlying blockchain, from the first user public address associated with the underlying blockchain to the first contact address associated with the underlying blockchain, wherein the sixth transaction request comprises a sixth message including requests to the stable value token smart contract regarding a first transfer of the first amount of collateral; wherein the first user public address has a corresponding first user private key which is mathematically related to the first user public address; and wherein the sixth transaction request is signed by the first user private key. In embodiments the sixth transaction request further includes third transaction fee information. In embodiments the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value token smart contact regarding the first transfer of the first amount of collateral include requests to the a second contract address associated with the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from the second contract address. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second user public address associated with the underlying blockchain are executed upon receipt of a first collateral request from a third contract address associated with the second contract address. In embodiments the requests to the stable value smart contract to transfer the first amount of collateral in the form of stable value digital asset tokens from the first user public address associated with the underlying blockchain to the second user public address associate with the underlying blockchain are executed upon receipt of a first collateral request from the administrator system.
In embodiments, prior to the step of monitoring transactions of the stable value digital asset token on the underlying blockchain, a seventh transaction is sent by the second user device via the underlying blockchain, from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain, wherein the seventh transaction request comprises a seventh message including requests to the stable value token smart contract regarding a second transfer of the second amount of collateral; wherein the second user public address has a corresponding second user private key which is mathematically related to the second user public address; and wherein the seventh transaction request is signed by the second user private key. In embodiments the seventh transaction request includes fourth transaction fee information. In embodiments the requests regarding transfer of the second amount of collateral include requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address are executed upon receipt of a second collateral request from a third contract address associated with the second contract address associated with the underlying blockchain. In embodiments the requests to the stable value smart contract to transfer the second amount of collateral in the form of stable value digital asset tokens from the second user public address associated with the underlying blockchain to the second contract address associated with the underlying blockchain are executed upon receipt of a second collateral request from the second administrator system.
In embodiments the step of collecting the excess collateral occurs in response to the security token smart contract verifying the first trade instructions against the hashed instructions.
In embodiments the fourth message further comprises the second contract address and the oracle smart contract only provides the first benchmark information to second contract address when the second contract address is included in a list of approved contract addresses.
In embodiments the list of approved contract addresses may be modified periodically.
In embodiments the list of approved contract addresses may be modified aperiodically.
The process of
In embodiments, the contract proposal may include one or more contract parameters of contract parameters database 6801B. In embodiments, the contract proposal may include one or more of the following parameters: (1) inception date data 6902; (2) inception value data 6904; (3) benchmark data 6906; (4) contract duration data 6908; (5) collateral requirements data 6910; and (6) notional value data 6912; (7) a trusted oracle selection 6917 (e.g. oracle 6811); (8) an oracle address (e.g. oracle public address 6813); (9) an oracle collateral requirement; and/or (10) an oracle fee, to name a few. A trusted oracle selection 6917 may be one or more oracles that the first user would like to use for their contract proposal. An oracle address may be one or more public addresses associated with the one or more trusted oracle selections 6917. The oracle collateral requirement, in embodiments, may be an amount of stable value tokens which the oracle deposits into a contract—the amount of which may be lost by the oracle if the oracle is found to be giving unreliable information (e.g. unreliable benchmark information). An oracle fee, in embodiments, may refer to the amount the oracle 6811 is paid to provide reliable information. Step S9504 may be similar to step S7308, described above in connection with
After receiving the contract proposal from the first user device, in embodiments, the administrator system may publish the received contract proposal, which may be similar to the published contracts described above in connection with
In embodiments where the at least one collateral requirement requires an oracle to provide collateral, the calculation of the oracle collateral may be performed by one or more of the following: (1) the oracle; (2) the administrator system 6801; (3) a third party; and/or (4) one or more parties associated with the published contract (e.g. the first user, the second user, to name a few), to name few. In embodiments, the administrator system 6801 may calculate the oracle collateral requirement and send it to the oracle address. In embodiments, the administrator system 6801 may receive the oracle collateral requirement at a public address associated with the administrator system 6801 from the oracle address. In embodiments, after receiving the oracle collateral requirement, the administrator system 6801 may calculate the oracle collateral requirement to verify the received oracle collateral requirement. If the receipt of the oracle collateral is not verified, the administrator system 6801, may, in embodiments, impose a penalty fee; generate and send a notification indicating the verification failure, stop the process of
The process of
In embodiments, the administrator system 6801 may also receive one or more indications of interest from one or more oracles. As described above, the received contract proposal may be transmitted by the administrator system 6801 to the one or more selected oracles of trusted oracle selection 6917. In embodiments, in response to receiving the contract proposal, one or more oracles that received the contract proposal may send an indication of interest to the administrator system 6801. For example, an oracle may send an indication of interest including one or more of the following: (1) an identifier unique to the contract proposal; (2) an oracle collateral requirement; (3) an inception date; (4) an inception value; (5) benchmark data; (6) second benchmark data; (7) a user collateral requirement (e.g. collateral requirement 7126); (8) a notional value of the contract; (9) early termination rules; and/or (10) dispute rules, to name a few. Dispute rules are described more fully below in connection with step S9512, the description of which applying herein. In embodiments, the administrator system 6801 may receive indications of interest from oracles not of the selected oracles of the contract proposal. In embodiments, an indication of interest from an oracle may be similar to the indications of interest described in connection with
The process of
In embodiments, after the administrator system 6801 matches the first user and the second user based on the received first trade information and the second side information, the administrator system 6801 may publish the second smart contract at the second smart contract address (e.g. step S9512).
The process of
In embodiments, the first smart contract may be associated with a digital asset token. The digital asset token, in embodiments, may be a fiat-backed digital asset token (e.g. Libra). The fiat-backed digital asset token, may be similar to the fiat-backed digital asset described throughout, the description of which applying herein. For example, the fiat-backed digital asset token may be backed by a reserve of fiat and/or governmental bonds. The reserve, in embodiments, may be maintained by or on behalf of the issuer that created the fiat-backed digital asset token. In embodiments, the digital asset may be a stable value token (e.g. Gemini Dollar). In embodiments, the first smart contract instructions may be associated with the blockchain for the underlying digital asset.
The process of
Referring to
In embodiments, the benchmark information received from the oracle may be disputed. For example, in embodiments, the oracle may be associated with multiple published contracts and be tasked to provide each of those smart contracts with current benchmark data. In embodiments, the oracle may provide second current benchmark data 9628 to a third smart contract address (e.g. not the second smart contract) that differs from the first current benchmark data 9618 provided to the second smart contract address. The first current benchmark data 9618, for example, may be transmitted to the second smart contract address at the same or substantially same time (e.g. the difference in time does not materially affect the benchmark data) as the second current benchmark data 9628 was transmitted to the third smart contract address. In embodiments, any party to the second smart contract may dispute the benchmark data provided by the oracle. In embodiments, the dispute instructions module 6942 may include wait period instructions, that allow for a predetermined wait period (e.g. 10 minutes, 1 hour, 5 hours, 1 day, 5 days, and/or a week, to name a few) for a party to the contract to dispute the current benchmark data provided by the oracle. The dispute instructions module 6942, in embodiments, may set requirements for a dispute message. Referring to
In embodiments, the dispute message 9602 may be analyzed to determine whether a penalty fee is warranted—the description of which is located below in connection with steps S9528, S9530, and S9532, described below in connection with
The second smart contract instructions 6805B, in embodiments, may also include instructions to settle based on the benchmark data supplied by the oracle, even if the oracle pays the penalty fee. Alternatively, in embodiments, the second smart contract instructions 6805B may, in the case where the oracle pays the penalty fee, include instructions for the second smart contract 6805 to refund the collateral associated with the first user to the first user and refund the collateral associated with the second user to the second user. In embodiments, in the case where the oracle pays the fee, the second smart contract instructions 6805B may include instructions for the second smart contract 6805 to query an additional oracle to settle the published contract.
In embodiments, the first benchmark information may, as mentioned above, be different and/or substantially different from benchmark information associated with a similar contract associated with the oracle address. In the case where the first benchmark information is different and/or substantially different from benchmark information associated with a similar contract, as mentioned above, the oracle may be required to pay a penalty fee. In the case where the first benchmark information is not different or substantially different from benchmark information associated with a similar contract, an additional transaction request may be generated by the administrator system 6801 (and/or the oracle) and sent to the second smart contract address 6805A. The second smart contract instructions, in embodiments, may require the additional transaction request: (1) be sent after a predetermined amount of time after the oracle sends the first benchmark information; (2) include a ledger of contracts the oracle address is associated with; (3) include the amount of oracle collateral; and/or (4) include a digital signature of the oracle (e.g. the private key associated with the oracle). The second smart contract address 6805A, upon receipt of the additional transaction request, may verify the transaction request by determining whether the one or more requirements associated with the additional transaction request and the second smart contract instructions 6805B are met. If the requirements are met, in embodiments, the second smart contract address 6805B may execute the additional transaction request, resulting in the oracle collateral being returned to the oracle address from the second smart contract address 6805A. If the requirements are not met, in embodiments, the second smart contract instructions 6805B may require the oracle to lose the collateral and be required to pay the penalty fee. In embodiments, if the requirements are not met, the second smart contract instructions 6805B may cause the second smart contract 6805 to generate and send a notification to the oracle address indicating that the additional transaction request was rejected because the requirements were not met.
In embodiments, the first smart contract and the second smart contract may be one smart contract and/or module. In embodiments, a third smart contract and/or module may include the first smart contract and the second smart contract. In embodiments, the first smart contract address and the second smart contract address may be the same smart contract address. In embodiments, the third smart contract address may be the first smart contract address and/or the second smart contract address.
Referring to
In embodiments, the first transaction request may be generated by the first user device and digitally signed by the first user private key. The first transaction request, in embodiments, may include a request to transfer the first amount of collateral in the digital asset token from the first user public address to the second smart contract address. In embodiments, once generated and signed, the first transaction request may be transmitted by the first user device from the first user public address to the first smart contract address via the underlying blockchain. The first transaction request may be verified and executed by the first smart contract, causing the first amount of collateral to be transferred from the first user public address to the second smart contract address.
In embodiments, the second amount of collateral may be received by the second smart contract address as a result of a second transaction request sent by the second user device. In embodiments, the second transaction request may be generated by the second user device and digitally signed by the second user private key. The second transaction request, in embodiments, may include a request to transfer the second amount of collateral in the digital asset token from the second user public address to the second smart contract address. In embodiments, once generated and signed, the second transaction request may be transmitted by the second user device from the second user public address to the first smart contract address via the underlying blockchain. The second transaction request may be verified and executed by the first smart contract, causing the second amount of collateral to be transferred from the second user public address to the second smart contract address.
In embodiments, the third amount of collateral may be received by the second smart contract address as a result of a third transaction request sent by the oracle 6811. In embodiments, the third transaction request may be generated by the oracle 6811 and digitally signed by a private key associated with the oracle 6811 and the oracle public address 6813 first user private key. The first transaction request, in embodiments, may include a request to transfer the third amount of collateral in the digital asset token from the oracle public address to the second smart contract address. In embodiments, once generated and signed, the third transaction request may be transmitted by the oracle from the oracle public address to the first smart contract address via the underlying blockchain. The third transaction request may be verified and executed by the first smart contract, causing the third amount of collateral to be transferred from the oracle public address to the second smart contract address.
In embodiments, the administrator system 6801 and/or a third party may monitor the second smart contract address to confirm that the first, second, and third amount of collateral have been received by the second smart contract. If any of the first, second, or third amount of collateral is not received by the second smart contract and/or partially not received by the second smart contract, the administrator system 6801, in embodiments, may generate a notification indicating that the collateral amount is not received by the second smart contract address; The generated notification, in embodiments, may be sent by the administrator system 6801 to the first user device, the second user device, the first smart contract address, and/or the oracle, to name a few. In embodiments, after the notification is sent, the administrator system 6801 may wait for a predetermined amount of time, allowing the deficient party to cure the collateral defect. In embodiments, the administrator system 6801 may generate and send a third message to the second smart contract address. The third message, in embodiments, may include a request to transfer the first amount of collateral, the second amount of collateral, and/or the third amount of collateral in accordance with the first trade instructions. The disbursement of the collateral when one or more parties to the second smart contract have not transferred sufficient collateral may be controlled by the first trade instructions. In embodiments, the disbursement may include a penalty fee to the deficient party or parties. In embodiments, each party may receive a refund of their collateral.
In embodiments, the administrator system 6801 may receive a request to update the second smart contract based on new benchmark data and recalculate the first amount of collateral and the second amount of collateral. The request, in embodiments, may be received from one or more of: the first user device, the second user device, and/or the oracle 6811. In embodiments, in response to receiving the request (and/or in accordance with the first trade instructions) the administrator system 6801 may generate and send a message to the second smart contract. The message, in embodiments, may request the second smart contract to recalculate the first collateral amount and the second collateral amount based on current benchmark data. In embodiments, the current benchmark data may be retrieved by the second smart contract generating and sending a request to the oracle public address 6813. In embodiments, the current benchmark data may be retrieved by the administrator system 6801, first user device, and/or second user device generating and sending a request to the oracle public address 6813. The oracle, in response, may return the current benchmark data (e.g. first digitally signed benchmark message 9604).
In embodiments, the request to update the second smart contract may be sent directly to the second smart contract via the blockchain from one or more of the following: the first user public address, the second user public address, the oracle public address 6813, and/or the administrator public address, to name a few.
Once the message is received by the second smart contract address, the second smart contract may recalculate the excess collateral. Recalculating excess collateral, in embodiments, may be similar to step S7014, described above in connection with
In embodiments, the administrator system 6801 and/or a third party may monitor the second smart contract address to confirm that the additional collateral has been received by the second smart contract. If any of the additional collateral is not received by the second smart contract, the administrator system 6801, in embodiments, may generate a notification indicating that the additional collateral amount is not received by the second smart contract address; The generated notification, in embodiments, may be sent by the administrator system 6801 to the first user device, the second user device, the first smart contract address, and/or the oracle, to name a few. In embodiments, after the notification is sent, the administrator system 6801 may wait for a predetermined amount of time, allowing the deficient party to cure the collateral defect. In embodiments, the administrator system 6801 may generate and send a third message to the second smart contract address. The third message, in embodiments, may include a request to transfer the first amount of collateral, the second amount of collateral, and/or the third amount of collateral in accordance with the first trade instructions. The disbursement of the collateral when one or more parties to the second smart contract have not transferred sufficient collateral may be controlled by the first trade instructions. In embodiments, the disbursement may include a penalty fee to the deficient party or parties. In embodiments, each party may receive a refund of their remaining collateral.
The process of
In embodiments, the oracle may send the first digitally signed benchmark message 9604 in response to receiving directions to send the current benchmark information. In embodiments, the directions may be received by one or more of: the first user, the second user, the administrator 6801, the first smart contract, and/or the second smart contract, to name of few. For example, the second smart contract may generate a transaction request, signed by a private key associated with the second smart contract. The generated transaction request may include a request to retrieve current benchmark information (e.g. first current benchmark data 9618) and send the current benchmark information to the second smart contract address. The generated transaction request, in embodiments, may be transmitted from the second smart contract address to the oracle public address 6813. In response to receiving the generated transaction request, the oracle may verify the transaction request (e.g. verify the digital signature), retrieve the current benchmark data, and generate a benchmark message (e.g. first digitally signed benchmark message 9604). The generated benchmark message, in embodiments, may be digitally signed by the oracle private key and sent from the oracle public address 6813 to the second smart contract address. The received benchmark message, in embodiments, may be verified and/or stored on the blockchain by the second smart contract address, and/or sent to another public address (e.g. the first smart contract address, the administrator public address, the first user public address, and/or the second user public address, to name a few) for verification and/or storage. The generated transaction request, in embodiments, may be generated by one or more of the following: the first user device, the second user device, the first smart contract, and/or the administrator, to name a few. The generated transaction message may be sent to the oracle public address 6813 and/or a computer system associated with the oracle 6811 from one or more of the following: the first user device via network 15, the second user device via network 15, the administrator via network 15, the first user public address via the blockchain, the second user public address via the blockchain, and/or the administrator public address via the blockchain, to name a few.
In embodiments, when the current benchmark data is received, the second smart contract may publish the current benchmark data on the blockchain.
The process of implementing the first trade instructions may continue with step S9520. At step S9520, the administrator system monitors the second smart contract for a predetermined amount of time. In embodiments, the predetermined amount of time may correspond to the amount of time allotted by the dispute instructions module 6942 to dispute the benchmark information received from the oracle. In embodiments, a trusted third party, e.g. a watchtower, may monitor the second smart contract address. In embodiments, no dispute message is received, and the second smart contract may continue implementing the first trade instructions (e.g. continued with step S9522). However, in embodiments, the information received by the oracle 6811 may be disputed. In embodiments, a dispute message is received by the second smart contract address. In embodiments, a process for receiving and processing dispute messages is illustrated in connection with
Referring to
In embodiments, the second smart contract may verify the dispute message 9602. In embodiments, the second smart contract address may transmit the dispute message 9602, for verification purposes, to one or more of: the administrator system 6801, the first smart contract, the first user device, and/or the second user device, to name a few. To verify the dispute message 9602, in embodiments, the data within the dispute message 9602 may be verified. For example, one or more of the following may be compared to determine if they are the same, and thus verified: (1) the first oracle identification 9616, the second oracle identification 9624, and the oracle 6811; (2) the first current benchmark data 9608 and the first current benchmark data 9618; (3) the first time stamp 9610 and the first time stamp 9620; (4) the second current benchmark data 9612 and the second current benchmark data 9626; (5) the second time stamp 9614 and the second time stamp 9628; and/or (6) the first oracle digital signature 9622 and the second oracle digital signature 9630. In embodiments, if the above respective information does not match its respective counterpart, the dispute message 9602 may not be verified. In embodiments, if the dispute message 9602 is not verified, a penalty fee may be imposed on the user(s) which submitted the dispute message 9602. In embodiments, if the dispute message is not verified, the predetermined amount of time will continue to toll, and, when the predetermined amount of time has elapsed, the process may continue with step S9522.
In embodiments, if the administrator system 6801 (and/or the first smart contract, the first user device, and/or the second user device) receives and verifies the dispute message 9602, the administrator system 6801 may generate and send a message to the second smart contract address from the administrator public address via the blockchain. The message, in embodiments, may indicate whether the dispute message was verified.
Continuing the process of
Continuing the process of
Continuing the process of
In embodiments, a successful dispute may require the first difference to be above a first predetermined threshold and/or the second difference to be below a second predetermined threshold. The first predetermined threshold may require that the difference between the first current benchmark data 9618 and the second current benchmark data 9626 be above a certain amount. The second predetermined threshold may require that the first current benchmark data 9618 and the second current benchmark data 9626 be retrieved by the oracle 6811 within a time period that did not materially affect the benchmark data. The first and second predetermined thresholds, in embodiments, may be static thresholds or dynamic, based on the asset associated with the second smart contract (e.g. the volatility of the asset).
In embodiments, the determination of whether the differences exceed the predetermined thresholds may be performed by one or more of: the second smart contract, the administrator system 6801, the first smart contract, the second smart contract, the first user device, and/or the second user device, to name a few.
If, in embodiments, the first difference is below the first predetermined threshold and/or the second difference is above the second predetermined threshold, the dispute may be unsuccessful, and the predetermined amount of time will continue to toll. When, in embodiments, the predetermined amount of time has elapsed, the process may continue with step S9522.
In embodiments, the first difference is above a first threshold and the second difference is below a second threshold and the process of
The second message, in embodiments, may include a request to recalculate the collateral based on the dispute instructions. The dispute instructions, as mentioned above, may impose a penalty fee to the oracle 6811 if the benchmark information received from the oracle 6811 is confirmed to be inaccurate, incorrect, and/or unreliable. In embodiments, the penalty fee may be the entire amount of the collateral from the oracle (e.g. the third amount of collateral). In embodiments, the third amount of collateral may be transferred to the sender of the dispute message 9602 and/or split between the first user and the second user. In embodiments, the fee may be predetermined, or dynamic based on the degree of unreliability or incorrectness of the information received from the oracle 6811. In embodiments, the recalculation of the excess collateral may set the oracle's excess collateral (e.g. the third amount of excess collateral) to zero.
Continuing the process of
After a successful, or unsuccessful dispute, the process of implementing the first trade instructions may continue. In embodiments, if there is a successful dispute, the predetermined amount of time may default to ending—the predetermined amount of time being for disputes, the dispute being completed. In embodiments, if the dispute is unsuccessful, the predetermined amount of time will continue to toll until the predetermined amount of time has elapsed. Referring to
The excess collateral, in embodiments, may be recalculated based on one or more of the following: the at least one collateral requirement; the first current benchmark data 9618, the second current benchmark data 9626, benchmark data gathered from an additional oracle, and/or a complete refund of the first amount of collateral and the second amount of collateral. In embodiments, a successful dispute may indicate that the first current benchmark data 9618 is unreliable. If the first current benchmark data 9618 is unreliable, the second smart contract may implement the first trade instructions based on the at least one collateral requirement and one or more of the following: first current benchmark data 9618; second current benchmark data 9626; benchmark data gathered from an additional oracle, and/or a complete refund of the first amount of collateral and the second amount of collateral. The aforementioned options may be preselected and defined by the first trade instructions—e.g. if the second current benchmark data 9626 is more accurate, use the more accurate benchmark data. The aforementioned options may be agreed upon as a dispute occurs—e.g. the data was completely wrong—refund the collateral and give the first user and the second user the penalty fee from the oracle 6811.
The process of implementing the first trade instructions may continue with step S9524. At step S9524, the excess collateral is distributed. In embodiments, step S9524 may be similar to step S7014 described in connection with
The steps of the processes described in connection with
In embodiments, a method comprises (a) receiving, from a first user device associated with a first user by an administrator system associated with an administrator of a digital asset database, a first contract proposal, wherein the first contract proposal includes: (i) first user information associated with the first user; and (ii) first contract information comprising at least the following contract parameters: (A) an inception date; (B) an inception value; (C) at least one benchmark; (D) a contract duration; (E) at least one collateral requirement; (F) a notional value of the smart contract; and (G) first side information comprising identification of a first leg of the first contract proposal, wherein the digital asset database is tied to a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network; and wherein the administrator system is associated with an administrator public address associated with the peer-to-peer network; (b) receiving, by the administrator system from a second user device associated with a second user, at least one indication of interest, wherein the at least one indication of interest includes at least: (i) a first user response comprising: (1) second user information associated with the second user; and (2) second side information comprising a second leg of the contract proposal; (c) matching, by the administrator system, the first contract information and the second side information; (d) generating a first module on the peer-to-peer network associated with a fiat-backed digital asset, wherein the module comprises first contract instructions associated with a first module address associated with the peer-to-peer network, wherein the smart contract instructions are saved in the peer-to-peer network and include: (i) first authorization instructions regarding creating fiat-backed digital assets; (ii) second authorization instructions regarding transferring fiat-backed digital assets; (iii) third authorization instructions regarding destroying fiat-backed digital assets; (iv) fourth authorization instructions regarding functions associated with the fiat-backed digital asset; (v) first trade instructions including execution instructions to execute a first trade between the first user and the second user, wherein the first trade is based on at least the following: 1. the first contract proposal; and 2. the first user response (vi) fifth authorization instructions regarding transferring security tokens; (vii) sixth authorization instructions regarding destroying security tokens; (viii) seventh authorization instructions regarding transferring fiat-backed digital assets from the first smart contract address; (ix) calculating instructions regarding calculating excess collateral; and (x) dispute instructions regarding disputed benchmark information received by the first smart contract address from an oracle; (e) sending, by the administrator system from the administrator public address to the module address via the peer-to-peer network, the first module and associated first contract instructions; (f) receiving, by the first module address, a first amount of collateral, wherein the first amount of collateral is a first amount of fiat-backed digital assets associated with the first user as collateral, and wherein the first amount of fiat-backed digital assets associated with the first user is based on the at least one collateral requirement; (g) receiving, by the first module address, a second amount of collateral, wherein the second amount of collateral is a second amount of fiat-backed digital assets associated with the second user as collateral, wherein the second amount of fiat-backed digital assets associated with the second user is based on the at least one collateral requirement; (h) receiving, by the first module address from an oracle public address associated with the oracle, a third amount of collateral, wherein the third amount of collateral is a third amount of fiat-backed digital assets associated with the oracle as collateral, wherein the third amount of fiat-backed digital assets associated with the oracle is based on the at least one collateral requirement, wherein the oracle public address is associated with the peer-to-peer network; (i) implementing, by the first module, the first trade instructions via the peer-to-peer network by the plurality of geographically distributed computer systems in the peer-to-peer network, wherein implementing comprises the following steps: (i) receiving, by the first module address from the oracle, a first benchmark message including: (1) first current benchmark information associated with the first contract information; (2) a digital signature associated with the oracle; and (3) a first timestamp; (ii) monitoring, by the administrator system, the first module address for a predetermined amount of time; and (iii) after the predetermined amount of time has elapsed, collecting, by the administrator system from the module address, excess collateral from the first trade, wherein the collecting includes steps of: (1) sending, by the administrator system via the peer-to-peer network, a first message comprising requests for the first smart contract to: (A) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (B) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (C) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (D) distribute the first excess collateral to a first user public address associated with the first user and associated with the peer-to-peer network; (E) distribute the second excess collateral to a second user public address associated with the second user associated with the peer-to-peer network; and (F) distribute the third excess collateral to the oracle public address.
In embodiments, monitoring the first module address for the predetermined amount of time further comprises: (1) receiving, by the first module address, a first dispute message disputing the first current benchmark information, wherein the first dispute message comprises: (A) the first digitally signed benchmark message; and (B) a second digitally signed benchmark message, wherein the second digitally signed benchmark message is digitally signed by the oracle and comprises: i. second current benchmark information; and ii. a second timestamp; (2) comparing, by the first module, the first digitally signed benchmark message to the second digitally signed benchmark message to determine: i. a first difference between the first current benchmark information and the second current benchmark information; and ii. a second difference between the first timestamp and the second time stamp; (3) in the case where the first difference is above a first predetermined threshold and the second difference is below a second predetermined threshold, performing the steps of: (A) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate, based on the dispute instructions, the first amount of collateral; (ii) recalculate, based on the dispute instructions, the second amount of collateral; (iii) recalculate, based on the dispute instructions, the third amount of collateral; (iv) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (v) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (vi) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (vii) distribute the first excess collateral for the first trade in accordance with the first module and the first trade instructions to the first user public address; (viii) distribute the second excess collateral for the first trade in accordance with the first module and the first trade instructions to the second user public address; and (ix) distribute the third excess collateral for the first trade in accordance with the first module and the first trades instructions to the oracle public address; (1) in the case where the first difference is above the first predetermined threshold and the second difference is above the second predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network; and (2) in the case where the first difference is below the first predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network. In embodiments, the first dispute message is received by the first module address from the first user public address. In embodiments, the first excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from the second user public address. In embodiments, the second excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from at least one of the following: (1) the first user public address; (2) the second user public address; and (3) the administrator public address. In embodiments, the first excess collateral comprises a first half of the third amount of collateral, wherein the second excess collateral comprises a second half of the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is verified by the administrator system. In embodiments, the first dispute message is verified by the first module.
In embodiments, receiving the first digitally signed benchmark message further comprises: (a) sending, from the first module address to the oracle public address, a digitally signed first transaction request; (b) receiving, from the oracle public address by the first module address, the first digitally signed benchmark message; and (c) storing, by the first module, the first digitally signed benchmark message.
In embodiments, the at least one collateral requirement comprises: (1) a user collateral requirement; and (2) an oracle collateral requirement.
In embodiments, the first contract information further comprises the following contract parameter: (H) a trusted oracle selection.
In embodiments, the first time stamp indicates the time at which the first current benchmark data was retrieved by the oracle.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated first collateral amount and the first collateral amount; and (m) receiving, at the first module address, the first additional collateral amount.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; (m) monitoring, by the administrator system, the first module address on the peer-to-peer network associated with the underlying digital asset; (n) determining, by the administrator system, the first additional collateral amount has not been received by the first contract address; (o) generating, by the administrator system, a default notification indicating that the first additional collateral amount was not received by the second contract address; (p) sending, by the administrator system, the default notification to the first user device, the second user device, and the first module address; (q) generating, by the administrator system, a third message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first contract instructions; and (r) sending, by the administrator system from the administrator public address to the first module address, the third message, wherein, upon receipt of the third message, the first module implements the first trade instructions via the peer-to-peer network by computer systems among the plurality of distributed computer systems in the peer-to-peer network.
In embodiments, the first trade instructions are implemented as a result of a second message sent by the administrator system from the administrator public address to the first module address via the peer-to-peer network.
In embodiments, the first user information further comprises the first user public address, wherein the first user public address corresponds to a first user private key that is mathematically related to the first user public address, wherein the second user information further comprises the second user public address, and wherein the second user public address corresponds to a second user private key that is mathematically related to the second user public address. In embodiments, the step of receiving the first amount of collateral further comprises sending, by the first user device via the underlying peer-to-peer network from the first user public address, a digitally signed first transaction request including a request to transfer the first amount of collateral from the first user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the first user private key. In embodiments, the step of receiving the second amount of collateral further comprises sending, by the second user device via the underlying peer-to-peer network from the second user public address, a digitally signed first transaction request including a request to transfer the second amount of collateral from the second user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the second user private key.
In embodiments, the step of receiving the third amount of collateral further comprises sending, by an electronic device associated with the oracle via the underlying peer-to-peer network from the oracle public address, a digitally signed first transaction request including a request to transfer the third amount of collateral from the oracle public address to the first module address, wherein the oracle public address corresponds to an oracle private key that is mathematically related to the oracle public address, and wherein the digitally signed first transaction request is digitally signed by the oracle private key.
In embodiments, the excess collateral is calculated by at least one of the following: (i) the administrator system; (ii) the first module; (iii) the second smart contract; (iv) the first user device; and (v) the second user device.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the second collateral amount based on the at least one collateral requirement and current benchmark information; (l) determining, by the first module, a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (m) receiving, at the first module address, the second additional collateral amount. In embodiments, the second collateral amount is recalculated by the first user device. In embodiments, the administrator system sends the second message in response to receiving a request from the first user device. In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) monitoring, by the administrator system, the second contract address on the peer-to-peer network associated with the underlying digital asset; (l) determining, by the administrator system, the second additional collateral amount is not received by the first module address; (m) generating, by the administrator system, a notification indicating that the second additional collateral amount is not received by the first module address; (n) sending, by the administrator system, the notification to the first user device, the second user device and the first module address; (o) generating, by the administrator system, a third message including a request to transfer the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions; and (p) sending, by the administrator system, the third message to the first module address from the administrator public address via the peer-to-peer network, wherein, upon receipt of the third message, the first module address transfers the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions.
In embodiments, the first contract information further comprises at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, prior to step (a), the method further comprising: (k) generating, by the administrator system, machine readable instructions comprising graphical user interface information including a graphical user interface with at least one prompt for the first user to provide the contract proposal; (l) sending, by the administrator system to the first user device, the machine readable instructions such that, upon receipt of the machine readable instructions, the first user device displays the graphical user interface; and (m) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the fiat-backed digital assets are pegged to a predetermined ratio associated with one or more types of fiat.
In embodiments, the fiat-backed digital assets are backed by a reserve of fiat maintained on behalf of an issuer of the fiat-backed digital assets.
In embodiments, a method comprises (a) receiving, from a first user device associated with a first user by an administrator system associated with an administrator of a digital asset database, a first contract proposal, wherein the first contract proposal includes: (i) first user information associated with the first user; and (ii) first contract information comprising at least the following contract parameters: (A) an inception date; (B) an inception value; (C) at least one benchmark; (D) a contract duration; (E) at least one collateral requirement; (F) a notional value of the smart contract; and (G) first side information comprising identification of a first leg of the first contract proposal, wherein the digital asset database is tied to a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network; and wherein the administrator system is associated with an administrator public address associated with the peer-to-peer network; (b) receiving, by the administrator system from a second user device associated with a second user, at least one indication of interest, wherein the at least one indication of interest includes at least: (i) a first user response comprising: (1) second user information associated with the second user; and (2) second side information comprising a second leg of the contract proposal; (c) matching, by the administrator system, the first contract information and the second side information; (d) generating a first module on the peer-to-peer network associated with a fiat-backed digital asset, wherein the module comprises first contract instructions associated with a first module address associated with the peer-to-peer network, wherein the smart contract instructions are saved in the peer-to-peer network and include: (i) first authorization instructions regarding transferring fiat-backed digital assets; (ii) second authorization instructions regarding functions associated with the fiat-backed digital asset; (iii) first trade instructions including execution instructions to execute a first trade between the first user and the second user, wherein the first trade is based on at least the following: 1. the first contract proposal; and 2. the first user response (iv) third authorization instructions regarding transferring security tokens; (v) fourth authorization instructions regarding destroying security tokens; (vi) fifth authorization instructions regarding transferring fiat-backed digital assets from the first smart contract address; (vii) calculating instructions regarding calculating excess collateral; and (viii) dispute instructions regarding disputed benchmark information received by the first smart contract address from an oracle; (e) sending, by the administrator system from the administrator public address to the module address via the peer-to-peer network, the first module and associated first contract instructions; (f) receiving, by the first module address, a first amount of collateral, wherein the first amount of collateral is a first amount of fiat-backed digital assets associated with the first user as collateral, and wherein the first amount of fiat-backed digital assets associated with the first user is based on the at least one collateral requirement; (g) receiving, by the first module address, a second amount of collateral, wherein the second amount of collateral is a second amount of fiat-backed digital assets associated with the second user as collateral, wherein the second amount of fiat-backed digital assets associated with the second user is based on the at least one collateral requirement; (h) receiving, by the first module address from an oracle public address associated with the oracle, a third amount of collateral, wherein the third amount of collateral is a third amount of fiat-backed digital assets associated with the oracle as collateral, wherein the third amount of fiat-backed digital assets associated with the oracle is based on the at least one collateral requirement, wherein the oracle public address is associated with the peer-to-peer network; (i) implementing, by the first module, the first trade instructions via the peer-to-peer network by the plurality of geographically distributed computer systems in the peer-to-peer network, wherein implementing comprises the following steps: (i) receiving, by the first module address from the oracle, a first benchmark message including: (1) first current benchmark information associated with the first contract information; (2) a digital signature associated with the oracle; and (3) a first timestamp; (ii) monitoring, by the administrator system, the first module address for a predetermined amount of time; and (iii) after the predetermined amount of time has elapsed, collecting, by the administrator system from the module address, excess collateral from the first trade, wherein the collecting includes steps of: (1) sending, by the administrator system via the peer-to-peer network, a first message comprising requests for the first smart contract to: (A) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (B) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (C) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (D) distribute the first excess collateral to a first user public address associated with the first user and associated with the peer-to-peer network; (E) distribute the second excess collateral to a second user public address associated with the second user associated with the peer-to-peer network; and (F) distribute the third excess collateral to the oracle public address.
In embodiments, monitoring the first module address for the predetermined amount of time further comprises: (1) receiving, by the first module address, a first dispute message disputing the first current benchmark information, wherein the first dispute message comprises: (A) the first digitally signed benchmark message; and (B) a second digitally signed benchmark message, wherein the second digitally signed benchmark message is digitally signed by the oracle and comprises: i. second current benchmark information; and ii. a second timestamp; (2) comparing, by the first module, the first digitally signed benchmark message to the second digitally signed benchmark message to determine: i. a first difference between the first current benchmark information and the second current benchmark information; and ii. a second difference between the first timestamp and the second time stamp; (3) in the case where the first difference is above a first predetermined threshold and the second difference is below a second predetermined threshold, performing the steps of: (A) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate, based on the dispute instructions, the first amount of collateral; (ii) recalculate, based on the dispute instructions, the second amount of collateral; (iii) recalculate, based on the dispute instructions, the third amount of collateral; (iv) determine first excess collateral for the first trade in accordance with the first module and the first trade instructions; (v) determine second excess collateral for the first trade in accordance with the first module and the first trade instructions; (vi) determine third excess collateral for the first trade in accordance with the first module and first trade instructions; (vii) distribute the first excess collateral for the first trade in accordance with the first module and the first trade instructions to the first user public address; (viii) distribute the second excess collateral for the first trade in accordance with the first module and the first trade instructions to the second user public address; and (ix) distribute the third excess collateral for the first trade in accordance with the first module and the first trades instructions to the oracle public address; (1) in the case where the first difference is above the first predetermined threshold and the second difference is above the second predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network; and (2) in the case where the first difference is below the first predetermined threshold, implementing, by the first module, the first trade instructions via the peer-to-peer network. In embodiments, the first dispute message is received by the first module address from the first user public address. In embodiments, the first excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from the second user public address. In embodiments, the second excess collateral comprises the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is received by the first module address from at least one of the following: (1) the first user public address; (2) the second user public address; and (3) the administrator public address. In embodiments, the first excess collateral comprises a first half of the third amount of collateral, wherein the second excess collateral comprises a second half of the third amount of collateral, and wherein the third excess collateral is zero. In embodiments, the first dispute message is verified by the administrator system. In embodiments, the first dispute message is verified by the first module.
In embodiments, receiving the first digitally signed benchmark message further comprises: (a) sending, from the first module address to the oracle public address, a digitally signed first transaction request; (b) receiving, from the oracle public address by the first module address, the first digitally signed benchmark message; and (c) storing, by the first module, the first digitally signed benchmark message.
In embodiments, the at least one collateral requirement comprises: (1) a user collateral requirement; and (2) an oracle collateral requirement.
In embodiments, the first contract information further comprises the following contract parameter: (H) a trusted oracle selection.
In embodiments, the first time stamp indicates the time at which the first current benchmark data was retrieved by the oracle.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated first collateral amount and the first collateral amount; and (m) receiving, at the first module address, the first additional collateral amount.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the first collateral amount based on the at least one collateral requirement and the first current benchmark information; and (ii) recalculate the second collateral amount based on the at least one collateral requirement and the first current benchmark information; (l) determining, by the first module, a first additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; (m) monitoring, by the administrator system, the first module address on the peer-to-peer network associated with the underlying digital asset; (n) determining, by the administrator system, the first additional collateral amount has not been received by the first contract address; (o) generating, by the administrator system, a default notification indicating that the first additional collateral amount was not received by the second contract address; (p) sending, by the administrator system, the default notification to the first user device, the second user device, and the first module address; (q) generating, by the administrator system, a third message including a request to transfer the first collateral amount and the second collateral amount in accordance with the first contract instructions; and (r) sending, by the administrator system from the administrator public address to the first module address, the third message, wherein, upon receipt of the third message, the first module implements the first trade instructions via the peer-to-peer network by computer systems among the plurality of distributed computer systems in the peer-to-peer network.
In embodiments, the first trade instructions are implemented as a result of a second message sent by the administrator system from the administrator public address to the first module address via the peer-to-peer network.
In embodiments, the first user information further comprises the first user public address, wherein the first user public address corresponds to a first user private key that is mathematically related to the first user public address, wherein the second user information further comprises the second user public address, and wherein the second user public address corresponds to a second user private key that is mathematically related to the second user public address. In embodiments, the step of receiving the first amount of collateral further comprises sending, by the first user device via the underlying peer-to-peer network from the first user public address, a digitally signed first transaction request including a request to transfer the first amount of collateral from the first user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the first user private key. In embodiments, the step of receiving the second amount of collateral further comprises sending, by the second user device via the underlying peer-to-peer network from the second user public address, a digitally signed first transaction request including a request to transfer the second amount of collateral from the second user public address to the first module address, wherein the digitally signed first transaction request is digitally signed by the second user private key.
In embodiments, the step of receiving the third amount of collateral further comprises sending, by an electronic device associated with the oracle via the underlying peer-to-peer network from the oracle public address, a digitally signed first transaction request including a request to transfer the third amount of collateral from the oracle public address to the first module address, wherein the oracle public address corresponds to an oracle private key that is mathematically related to the oracle public address, and wherein the digitally signed first transaction request is digitally signed by the oracle private key.
In embodiments, the excess collateral is calculated by at least one of the following: (i) the administrator system; (ii) the first module; (iii) the second smart contract; (iv) the first user device; and (v) the second user device.
In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) sending, by the administrator system via the peer-to-peer network, a second message comprising requests for the first module to: (i) recalculate the second collateral amount based on the at least one collateral requirement and current benchmark information; (1) determining, by the first module, a second additional collateral amount based on a difference between the recalculated second collateral amount and the second collateral amount; and (m) receiving, at the first module address, the second additional collateral amount. In embodiments, the second collateral amount is recalculated by the first user device. In embodiments, the administrator system sends the second message in response to receiving a request from the first user device. In embodiments, prior to implementing the first trade instructions, the method further comprises: (k) monitoring, by the administrator system, the second contract address on the peer-to-peer network associated with the underlying digital asset; (l) determining, by the administrator system, the second additional collateral amount is not received by the first module address; (m) generating, by the administrator system, a notification indicating that the second additional collateral amount is not received by the first module address; (n) sending, by the administrator system, the notification to the first user device, the second user device and the first module address; (o) generating, by the administrator system, a third message including a request to transfer the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions; and (p) sending, by the administrator system, the third message to the first module address from the administrator public address via the peer-to-peer network, wherein, upon receipt of the third message, the first module address transfers the first collateral amount, the second collateral amount, and the third collateral amount in accordance with the first trade instructions.
In embodiments, the first contract information further comprises at least one of the following: (H) derivative type information; (I) early termination rules; (J) a second benchmark; (K) asset identification information; (L) pricing model information; and (M) volatility information.
In embodiments, prior to step (a), the method further comprising: (k) generating, by the administrator system, machine readable instructions comprising graphical user interface information including a graphical user interface with at least one prompt for the first user to provide the contract proposal; (l) sending, by the administrator system to the first user device, the machine readable instructions such that, upon receipt of the machine readable instructions, the first user device displays the graphical user interface; and (m) receiving, from the first user device in response to the at least one prompt, the contract proposal.
In embodiments, the fiat-backed digital assets are pegged to a predetermined ratio associated with one or more types of fiat.
In embodiments, the fiat-backed digital assets are backed by a reserve of fiat maintained on behalf of an issuer of the fiat-backed digital assets.
The particular systems, methods, and program products of embodiments of the present invention that generate graphical user interface (GUI) provide a solution to electronic order book data visualization problems. The potential for large numbers of orders in an electronic order book creates a technical data visualization problem, whereby it can be difficult for a user (e.g., a trader) to determine how a particular order or prospective order will impact the market or the market within a particular digital asset exchange system or how a particular order will be fulfilled based upon pending orders in a current order book. Embodiments of the present invention provide electronic order book visualization interfaces that include a representation of a prospective order defined by order parameters, which may be edited by the user. Upon editing prospective order parameters, the prospective order graphical representation may be updated to reflect the new parameters. These interfaces can provide a user with an intuitive depiction of both the current market and the effect of the prospective order on the market. The interfaces can also show how a prospective order may be fulfilled, not fulfilled, and/or the degree to which a prospective order will likely be fulfilled based on the current electronic order book. The interfaces also provide an unconventional visualization that can facilitate faster comprehension of the bounds of order book data (e.g., order prices and corresponding order volumes).
Turning to
The dashboard GUI may present various information associated with a digital asset exchange, for example, balance information (including fiat currency balances 1202 and/or digital asset balances 1204), account value information (including present, past, and/or predicted values), historical trends, open orders, past orders, and/or user history, to name a few. Accordingly, such a dashboard interface may include account summary information, such as one or more digital asset balances 1204 and/or fiat currency (e.g., U.S. Dollar) balances 1202 associated with a particular user account or master account, which may be an umbrella account with a plurality of user sub-accounts. The dashboard interface may also include an account value 1206, which may be a sum of all digital asset balances and fiat currency balances. In embodiments, the account value may be expressed in digital asset quantities and/or in fiat currency amounts. Accordingly, the exchange computer system may estimate a conversion amount either from a digital asset balance to a fiat currency value or from a fiat currency balance to a digital asset value, which conversions may be based upon order book information for the exchange and/or a digital asset index, such as a current market price. The dashboard interface may also indicate values for available digital assets 1208 and available fiat currencies 1210 associated with a user account. Amounts available may be based upon account balances and pending orders, such as by subtracting pending digital asset purchase order amounts from a fiat currency balance of a user's fiat currency account associated with (e.g., held in custody by) the exchange or subtracting pending digital asset sale order amounts from a digital asset balance of a user's digital asset account associated with (e.g., held in custody by) the exchange. One or more graphs 1212 illustrating account balances and/or total account value, in digital asset amounts or fiat currency amounts, may be provided in the interface. In embodiments, graphs showing each account balance and a total account value may be overlaid on each other.
A dashboard GUI may include options to access different data. Such options may comprise graphical buttons, hyperlinks, text, and/or icons, to name a few. The GUI can include a user account data selection option, settings selection option, and/or a notification selection option 1216, selection of any of which may cause the digital asset exchange computer system to provide respective data, menus, and/or updated GUIs. For example, a notification selection option 1216 may be used to access a notifications menu or notifications listing.
A dashboard GUI may further include exchange historical data 1220, such as a last price (e.g., price for the most recent executed transaction), a 24-hour change (e.g., a delta between the market price 24 hours prior and the current market price), price deltas over different time ranges (e.g., 30 minutes, 1 hour, 12 hours, 1 week, 1 month, 3 months, 1 year, 5 years, to name a few), a 24-hour range (e.g., showing the lowest and highest prices during the interval), and/or price ranges within other time ranges, to name a few. The dashboard GUI may also include a historical price and/or historical volume graph 1222. The graph may show exchange transaction prices over time and/or corresponding exchange transaction volumes over time. The graph may show transaction data from one or more other digital asset exchanges and/or digital asset indices. Any of this data may be overlaid on the graph. For example, digital asset index data may be overlaid on exchange transaction data.
A dashboard GUI may include an open orders listing 1224 showing open orders associated with an exchange user account. An open orders listing 1224 may indicate the date, time, and/or approximate time (e.g., about 3 hours ago) at which each order was placed. The listing 1224 may include a description of the order, e.g., order type, such as market or limit, purchase or sell, and/or order parameters, such as digital asset quantity, order price, limit order price, and/or total fiat currency amount. The listing 1224 may include an order status indicator, which may comprise a graphical indication, such as a status bar, of the degree to which each order is filled and/or text indicating the same (e.g., a percentage). The order listing 1224 may also include action options, selection of which may cause the exchange computer system to perform an action, such as canceling an order or canceling the remaining unfulfilled portion of an order. A truncated open order listing 1224 may be presented, which may include an option to view more or view all open orders.
A dashboard GUI may include a transaction history listing 1226. A transaction history may list some or all transactions associated with an exchange user account. A transaction history listing 1226 may indicate the date, time, and/or approximate time (e.g., about 3 hours ago) of each transaction and/or a description of the transaction (e.g., order type and/or order parameters, final order status, such as completed or canceled). In embodiments, the transaction history listing 1226 may include one or more options to display additional information (e.g., order details) for each transaction. A truncated transaction history listing may be provided, which may include an option to display more or all transactions (e.g., a view all history button).
A dashboard GUI may include an activity feed 1218 that displays summary information describing transactions, other actions (e.g., account funding), notifications, market activity, and/or exchange activity, to name a few. An activity feed 1218 may be accessed via a notification selection option 1216. Activity feeds are discussed herein with respect to
Referring to
The GUI may include a graphical representation of the order book and the prospective sell order. In embodiments, a first axis, such as the horizontal axis, may show price, and a second axis, such as a vertical axis, may show digital asset quantity. Digital asset quantity may increase in both directions moving away from the price axis. Sell orders may be shown on a first side of the price axis (e.g., above the price axis), while buy orders may be shown on a second side of the price axis (e.g., below the price axis). Accordingly, all pending digital asset sell and purchase orders from the electronic order book may be shown. In embodiments, less than all order may be shown based on the display bounds for one or both axes. A prospective sell order graphical representation may show the digital asset quantity for sale at each price at which it is for sale (e.g., the sell price and higher prices). Such a representation is evident in the dark portion in the upper right quadrant of the graph with respect to the price axis and the digital asset quantity axis taken at the spread point (this dark portion is the bottom right quadrant with respect to the prospective order crosshairs). The prospective sell order graphical representation may also show which pending buy orders from the order book will satisfy the sell order and/or how the sell order, once executed, will modify the existing order book. This can be seen as the dark portion in the lower left quadrant of the graph. A graphical indicator of one or more order parameters (e.g., digital asset quantity and price) may be overlaid on the graph, e.g., near the crosshairs. The exemplary GUI shows a prospective sell limit order with a limit order price above the market price. Accordingly, the order will not be satisfied by the pending purchase orders.
Turning to
Turning to
Referring to
Turning to
Turning to
A spread value may be displayed between the listing of pending purchase orders and the listing of pending sell orders. A graphical and/or textual indicator may indicate a current spread value, which may be determined based on the difference between the highest order price for a pending purchase order and the lowest order price for a pending sell order.
The order listings may be arranged according to price. Thus, the sell order listing may be arranged from highest price to lowest price, with the lowest price listed just before the spread value. After the spread value the purchase order listing may start with the highest purchase price and continue to list orders at each subsequent lower order price. In embodiments, the purchase orders may be listed above the spread value, and the sell orders may be listed below. In other embodiments, the sell orders may be listed first, above the spread value, and the purchase orders may be listed below the spread value. In embodiments, a subset of orders may be displayed in the graphical order listing at a given time. For example, a scroll bar may be used to navigate to additional orders towards the top and/or bottom of the list.
The purchase order GUIs may include market summary information and/or exchange summary information 7318 (e.g., last price, 24-hour change, 24-hour range, and/or such values over other time periods). A time indicator may indicate a time at which the summary information was last updated.
Each purchase order GUI may also include purchase order parameter input fields, such as a digital asset quantity input field 7322, which may include a digital asset identifier (e.g., BTC). Such a digital asset identifier may be changeable by a user to select a particular digital asset type for the transaction. Purchase order parameter input fields can also include an order type selector 7324 (e.g., for choosing between market and limit orders), an order price input field 7326, and/or a total cost field 7328. In embodiments, the order price input field 7326 and/or the total cost field 7328 may comprise fiat currency identifiers, which may be changeable to specify or view a price in different fiat currencies. In embodiments, exchange transactions from one digital asset to a second digital asset may be performed, in which case the fiat currency identifiers would be replaced with digital asset identifiers.
In embodiments, the user may input one or more purchase order parameters and the exchange computer system may calculate one or more other purchase order parameters. In embodiments, only a user may change the order price. Accordingly, a user input in the total cost field 7328 may cause the exchange computer system to calculate a digital asset quantity order based at least in part upon the price parameter and/or to populate the calculated digital asset quantity in the digital asset quantity input field 7322. Similarly, a user input in the digital asset quantity input field 7322 may cause the exchange computer system to calculate, based at least in part upon the price parameter, a total cost and/or populate that total cost in the total cost field 7328. In other embodiments, the exchange computer system may be able to calculate and/or re-calculate the order price, in addition to the other order parameters. If two parameters are entered by a user the exchange computer system may calculate the last parameter and/or populate its respective field. If the user then changes one of the three parameters after those fields are each populated the exchange computer system may recalculate one of the parameters (e.g., the second to last parameter input, the third to last parameter input).
Selection of a purchase option 7336 (e.g., a purchase graphical button) may cause the exchange computer system to place a purchase and/or execute an order corresponding to the input order parameters.
Order information based at least in part upon the order parameters may be calculated and displayed in the GUIs. For example, an order sub-total 7330 may be the value from the total cost field 7328. A fees value 7332 may indicate any fees associated with the transaction (e.g., fees charged by the exchange, government fees, to name a few). An order total 7334 may indicate the sum of the order sub-total 7330 and the fees 7332.
Tables, charts, and/or graphs may provide graphical representations of exchange data, such as electronic order book data, prospective order data, and/or pending order data. An order book display type indicator 7320 may be used to toggle between different graphical representation types, such as toggling between an order book graph and an order book listing.
An order book listing entry may also include a cost sum, which may be a sum of the costs (e.g. product of price and digital asset quantity) of all preceding orders in the listing moving away from the spread value. Accordingly, the cost sum will be calculated separately on the buy side and the sell side of the order book listing. Similarly, an entry can include a volume sum, which may comprise a sum of the volumes of the previous order entries in the listing moving away from the spread value. In embodiments, the order book listing 7338 may include an entry for the prospective purchase order, which may be positioned within the purchase order book listing 7340 according to its order price parameter. Such an entry for a prospective order may be rendered with a different color (e.g., font color, background color, border color, to name a few).
In embodiments, the order book graphical representations may only show a subset of pending digital asset purchase and/or sell orders. For example, a user may manipulate the scaling of the graph, such as by using zoom controls. A user may navigate the graph by scrolling or panning. In embodiments, the positions of the sell and buy order book graphical representations with respect to the order price axis 7356 may be flipped. The sell and buy order book graphical representations may be rendered using different colors and/or different shading or hatching techniques. For example, the sell order book graphical representation 7352b may be rendered as orange while the purchase order book graphical representation 7354b may be rendered as blue.
As can be seen, a digital asset quantity input field 7322b indicates a quantity of 0 digital assets. Accordingly, the graph may not show any representation corresponding to the prospective order defined by order parameters input by a user and/or calculated by the exchange computer system.
The order book and prospective order graphical representation 7346c comprises a sell order book graphical representation 7352c showing the pending digital asset sell orders and a purchase order book graphical representation 7354c showing the pending digital asset purchase orders. In embodiments, the purchase order book graphical representation 7354c may also depict the prospective purchase order data, which may be added to the pending purchase orders or overlaid as a separate graphical representation on the purchase order book graphical representation 7354c. In embodiments, the purchase order book graphical representation 7354c may show be a post-order purchase order book graphical representation showing the purchase orders that would exist after the prospective order is placed and/or executed. A post-order sell order book graphical representation 7358c may be overlaid on the graph to indicate how the prospective order would move the market. Such overlays may be rendered with a different color or a different shade of a color than the existing current order book graphical representations. For the exemplary market purchase order, the exchange computer system may place a series of orders starting with the lowest available price (e.g., whatever volume is available to purchase at the lowest sell order price) and increasing in price until the total cost is reached and/or until the digital asset order quantity is reached.
The graph 7346d shows the current sell order book graphical representation 7352d and a post-order purchase order book graphical representation 7354d. This may show the purchase orders that would exist after the prospective limit purchase order is placed and/or executed. Accordingly, where only a portion of the prospective limit purchase order would be satisfied by the existing pending sell orders, the projected remainder of the prospective order may be added to the purchase order book graphical representation 7354d. That remainder of the limit purchase order (e.g., the portion that would not be satisfied by the current sell orders) may be represented on the graph by the limit purchase order graphical representation 7360d, which is overlaid on the purchase order book graphical representation 7354d. It shows the remaining (e.g., unfulfilled) prospective digital asset order quantity at the limit price and lower prices. In embodiments, the limit purchase order graphical representation 7360d may be rendered as a darker shade or different shade of the color used to render the current purchase order book graphical representation 7354d. Because the exemplary order is a limit order in the money, the remaining limit purchase order graphical representation 7360d makes clear that the prospective order exceeds the existing spread point (buying above the spread) and overlaps with some sell order prices, shown in the sell order book graphical representation 7352d. The overlapping portion would be fulfilled (e.g., fulfilled upon placement of the prospective order). The graph may include a post-order sell order book graphical representation 7358d, which may indicate the data that would compromise the sell order book after the prospective purchase order was placed and/or fulfilled. The remaining limit purchase order graphical representation 7360d does not overlap with the post-order sell order book graphical representation 7358d, illustrating that the remaining portion would not be fulfilled by the sell orders. Limit orders may be fulfilled by the exchange computer system matching engine in the order in which the orders were placed.
The graph 7346e shows the current sell order book graphical representation 7352e and the purchase order book graphical representation 7354e. The limit purchase order is represented on the graph by the limit purchase order graphical representation 7360e, which is overlaid on the purchase order book graphical representation 7354e. In embodiments, the purchase order book graphical representation 7354e may be a post-order representation showing the purchase order book including the prospective purchase order. The limit purchase order graphical representation 7360e indicates the digital asset order quantity at the limit price and lower prices. As can be seen, there is no overlap in prices between the prospective purchase order and the sell order book. Accordingly, no portion of the prospective purchase order will be satisfied by the current sell order book. As illustrated, the sell order book will remain unchanged as a result of this purchase order. The purchase order would remain on the books until the user cancels it, until it automatically expires (e.g., in accordance with a predefined order expiry period), and/or until the market moves such that one or more sell orders are placed that satisfy the limit purchase order.
It will be understood that information displayed across various exemplary embodiments of GUIs described herein may be displayed in the form of text and/or graphical representations. Such displayed information may be manipulated to a desired configuration by a user, for example, through scaling (such as minimization and maximization), highlighting, coloring, and/or rearrangement, to name a few.
In a step S7504, the exchange computer system may access, from non-transitory computer-readable memory, electronic order book information comprising digital asset order information for a plurality of digital asset orders. The digital asset order information may comprise respective order prices denominated in a fiat currency and respective order quantities for each of the plurality of pending digital asset orders. The plurality of pending digital asset orders can include pending digital asset purchase orders and pending digital asset sell orders.
In a step S7506, the exchange computer system may calculate information for a first graphical user interface by determining at each respective order a price first cumulative quantity of digital assets subject to the pending digital asset purchase orders; and by determining at each respective order price a second cumulative quantity of digital assets subject to the pending digital asset sell orders.
In a step S7508, the exchange computer system may generate first machine-readable instructions to render the first graphical user interface including a first electronic order book graphical representation. The first electronic order book graphical representation may comprise a first axis depicting price denominated in the fiat currency; a second axis depicting digital asset quantity; a first set of graphical indicators on a first side of the first axis showing at each price visible along the first axis the first cumulative quantity of digital assets subject to the pending digital asset purchase orders; and a second set of graphical indicators on a second side of the first axis showing at each price visible along the first axis the second cumulative quantity of digital assets subject to the pending digital asset sell orders. In embodiments, the first axis may be a horizontal axis and the second axis may be a vertical axis. In embodiments, the axes may be flipped. In embodiments, the second axis may have a logarithmic scale.
In embodiments, the machine-readable instructions may comprise computer code such as Javascript, HTML, CSS to name a few. In embodiments, the machine-readable instructions may comprise data and/or layout instructions in a language associated with one or more user electronic device operating system types (e.g., iOS, Android, Windows, to name a few) and/or associated with applications (e.g., mobile applications) running on user electronic devices. In embodiments, the machine-readable instruction may comprise data such as JSON data.
In a step S7510, the exchange computer system may transmit to the first user electronic device the first machine-readable instructions so as to cause the first user electronic device (e.g., an application running on the first user electronic device, such as a dedicated downloadable application or a web browser application, which may be mobile applications) to render the first graphical user interface on a display associated with the first user electronic device. In embodiments, a web browser running one the first user electronic device may render the first graphical user interface, e.g., in a webpage. In embodiments, the exchange computer system may transmit the first machine-readable instructions to one or more other user electronic devices and/or other computer systems.
In a step S7512, the exchange computer system may receive from the first user electronic device, first digital asset order information corresponding to a first prospective digital asset purchase order. The first digital asset order information comprise a first order quantity of the digital asset and a first order price parameter related to a first order price of the digital asset. In embodiments, the first order price parameter may comprise a market order indicator. Accordingly, the first order price may be a market price. In embodiments, the exchange computer system may automatically determine the market price for the first order price, e.g., upon receipt of a market order indicator. In embodiments, the first order price parameter may comprise a limit order indicator. Accordingly, the first order price may be a limit price, which may be specified by the user.
In a step S7514, the exchange computer system may store in non-transitory computer-readable memory, the first digital asset order information as a prospective digital asset purchase order.
In a step S7516, the exchange computer system may calculate information for a second graphical user interface by determining at each respective order price a second order quantity of digital assets subject to the first prospective digital asset purchase order and by determining at each respective order price a third cumulative quantity of digital assets subject to the digital asset sell orders that would remain after fulfilling the first prospective digital asset purchase order. The exchange computer system may be specifically programmed to perform these non-routine calculations. They generate data values that enable the exchange computer system to generate machine-readable instructions for an unconventional GUI that provides enhanced order book visualization showing the potential impact of a prospective order. The potential impact of the order can include a visualization of how the order fits within the pending orders of the order book and/or how the order, once placed, will increase or decrease the pending cumulative sell order volumes and/or purchase order volumes available in the order book at each price. In embodiments, the second graphical user interface may be an updated version of the first graphical user interface.
In a step S7518, the exchange computer system may generate second machine-readable instructions to render the second graphical user interface including a second electronic order book graphical representation comprising a graphical representation of the first prospective digital asset purchase order superimposed on a modified first electronic order book graphical representation (e.g., modified to comprise a post-order electronic order book representation). The second electronic order book graphical representation may comprise the first axis depicting price denominated in the fiat currency; the second axis depicting digital asset quantity; the first set of graphical indicators on the first side of the first axis; the second set of graphical indicators on the second side of the first axis; a third set of graphical indicators on the first side of the first axis showing at each price visible along the first axis the respective second order quantity of digital assets subject to the first prospective digital asset purchase order; and a fourth set of graphical indicators on the second side of the first axis showing at each price visible along the first axis the respective third cumulative quantity of digital assets subject to the digital asset sell orders that would remain after fulfilling the first prospective digital asset purchase order.
In embodiments, the third set of graphical indicators may not be displayed, such as for a market order. In embodiments, the first prospective digital asset purchase order may be characterized as out of the money, and the third respective cumulative quantity of digital assets at each price may be zero.
In embodiments, at least one of the first axis or the second axis of the first electronic order book graphical representation have a different scale than the corresponding first axis and the corresponding second axis of the second electronic order book graphical representation. In embodiments, the scaling may be changed upon receipt of an electronic request from the user (e.g., via selection of an element, such as a rendered button, of the graphical user interface). In embodiments, the user may navigate and/or scroll along the axes of the graph and/or zoom in and/or out.
In embodiments, the exchange computer may further determine at each respective order price a fourth cumulative quantity of digital assets subject to both the digital asset purchase orders and the first prospective digital asset purchase order that would remain after fulfillment of at least a portion of the first prospective digital asset purchase order by the pending digital asset sell orders. The first set of graphical indicators of the second electronic order book graphical representation may show at each price visible along the first axis the fourth cumulative quantity of digital assets.
In a step S7520, the exchange computer system may transmit to the first user electronic device, the second machine-readable instructions so as to cause the first user electronic device (e.g., an application running on the first user electronic device, e.g., on one or more processors) to render the second graphical user interface on the display. The first user electronic device (e.g., the application running thereon) may render the second electronic order book graphical representation according to the second machine-readable instructions.
In a step S7522, the exchange computer system may receive from the first user electronic device, first digital asset order information corresponding to a first prospective digital asset sell order. The first digital asset order information may comprise a first order quantity of the digital asset and a first order price parameter related to a first order price of the digital asset, the first order price denominated in the fiat currency.
In a step S7524, the exchange computer system may store in non-transitory computer-readable memory, the first digital asset order information as a prospective digital asset sell order.
In a step S7526, the exchange computer system may calculate information for a second graphical user interface by determining at each respective order price a second order quantity of digital assets subject to the first prospective digital asset sell order and by determining at each respective order price a third cumulative quantity of digital assets subject to the digital asset purchase orders that would remain after fulfilling the first prospective digital asset sell order. These non-routine calculations enable generation of an unconventional GUI that can show electronic order book data with a visualization that enhances rapid understanding of the bounds of the pending buy and sell orders as well as how the prospective order may interact with the existing orders (e.g., to be fulfilled, partially fulfilled, unfulfilled, and/or to move the market by changing the pending orders that remain on the electronic order book).
In a step S7528, the exchange computer system may generate second machine-readable instructions to render the second graphical user interface including a second electronic order book graphical representation comprising a graphical representation of the first prospective digital asset purchase order superimposed on a modified first electronic order book graphical representation (e.g., modified to comprise a post-order electronic order book graphical representation). The second electronic order book graphical representation may comprise the first axis depicting price denominated in the fiat currency; the second axis depicting digital asset quantity; the first set of graphical indicators on the first side of the first axis; the second set of graphical indicators on the second side of the first axis; a third set of graphical indicators on the first side of the first axis showing at each price visible along the first axis the respective third cumulative quantity of digital assets subject to the digital asset purchase orders that would remain after fulfilling the first prospective digital asset sell order; and a fourth set of graphical indicators on the second side of the first axis showing at each price visible along the first axis the respective second order quantity of digital assets subject to the first prospective digital asset sell order. These machine-readable instructions may provide an unconventional GUI that facilitates order book visualization, including visualization of the degree to which a prospective order may be satisfied and how it may move the market.
In embodiments, the exchange computer system may determine at each respective order price a fourth cumulative quantity of digital assets subject to both the digital asset purchase orders and the first prospective digital asset purchase order that would remain after fulfillment of at least a portion of the first prospective digital asset purchase order by the pending digital asset sell orders. The first set of graphical indicators of the second electronic order book graphical representation may show at each price visible along the first axis the fourth cumulative quantity of digital assets.
In a step S7530, the exchange computer system may transmit to the first user electronic device, the second machine-readable instructions so as to cause an application at the first user electronic device to render the second graphical user interface on the display. The first user electronic device may render the second electronic graphical user interface according to the second machine-readable instructions.
In embodiments, transmitting data and/or machine-readable instructions to a user electronic device and/or to an application on the user electronic device may activate the application and/or cause it to render display content on a display screen.
In embodiments, graphical user interfaces similar to those described herein may be generated to show order book and order information related to other types of exchange transactions, such as a first digital asset to a second digital asset, a first fiat currency to a second fiat currency, or a first commodity to a second commodity, to name a few.
Digital asset accounts may be securely generated, accessed, and/or used (e.g., for transactions) from a secure administrative portal. In embodiments, the administrative portal, which may be used for key generation, parsing, and/or reassembly, may be a secure system for transacting in digital math based assets comprising a first computer system comprising one or more processors that generate one or more digital wallets and one or more respective private keys and one or more respective public keys, each of the one or more private keys being segmented into one or more private key segments; one or more writing devices operatively connected to the one or more first computer systems, each of the one or more writing devices adapted to write at least one private key segment of a corresponding one of the one or more private keys, along with information correlating the at least one private key segment to one of the one or more public keys; and at least one networked computer comprising one or more processors that access at least one of the digital wallets using a corresponding one of the one or more private keys as reassembled using the corresponding private key segments.
In embodiments, the administrative portal may further comprise a second computer system comprising one or more processors for reassembling the corresponding one of the one or more private keys based on input into the second computer system of the corresponding private key segments. In embodiments, the input device may be a scanner, a keyboard, a touchscreen, a mouse, a microphone, a camera, and/or a digital card reader, to name a few.
In embodiments, the first computer system of the administrative portal and/or the second computer system may not be associated with a network. In embodiments, the first computer system of the administrative portal and the networked computer system may be a common computer system. In embodiments, the second computer system of the administrative portal and the networked computer system may comprise a common computer system. In further embodiments, the first computer system, the second computer system, and the networked computer system may be a common computer system.
In embodiments, referring to
Referring to the exemplary embodiment illustrated in
In the exemplary embodiment depicted in
In the exemplary embodiment depicted in
In embodiments, the digital assets may be stored in one or more digital wallets residing on one or more computing devices, such as remote servers, personal computers, tablet devices, mobile devices, such as smart phones, or PDAs, to name a few. In the exemplary embodiment of
In embodiments, digital asset accounts and/or digital wallets may be generated by an entity upon receipt of a request to transfer digital assets to the entity and/or may be pre-generated at the time that security measures (e.g., a vault storage system) is set up, to name a few. The digital asset accounts each may be associated with unique private-public key pairs (which may include a plurality of private keys). In embodiments, the key pairs may be created as part of the digital wallet creation process. In other embodiments, the key pairs may be created before or after the creation of the one or more digital wallets and associated with the wallets as a separate step. In embodiments, the assets stored in a digital wallet may be accessed with a key pair, even if the original wallet is destroyed or otherwise unavailable. In such embodiments, only the key pair need be maintained and/or stored to retrieve the assets associated with a given digital wallet. Accordingly, in an embodiment of the present invention, digital wallets may be deleted or otherwise destroyed following the storage of their associated keys. Assets may be added to the wallet even after its destruction using the public key. Assets may thus be stored in a wallet after the wallet is destroyed. The wallet may be re-generated using its keys.
In embodiments, the private key may not be used directly with or on the networked computer 20. In embodiments, a public key (without the corresponding private key) may only be able to receive digital assets for deposit purposes. In embodiments, assets may be transferred to a wallet using its public key and without the transferor knowing the private key. Implementation of the foregoing may require customized software, e.g., software that modifies the standard digital asset protocols.
In embodiments, isolated computer 30 may also be used in conjunction with, e g., one or more printers or other writing devices, to print the key pairs or may be used otherwise to arrange for the storage of one or more aspects and/or portions (or segments or coded and/or encrypted segments) of the key pairs. A printer 32 or other writing device to write, print, or otherwise store the keys may be provided with the isolated computer 30. Such printer(s) and/or other writing device(s) may be connected, directly and/or indirectly, to the isolated computers, such as through hardwire, wireless, or other connection. That device may also be located within a Faraday cage, which may be the same Faraday cage housing isolated computer 30. Storage of the keys is described further below.
In embodiments, one or more isolated computers 30 can be used in conjunction with one or more printers or other writing devices to write, print or otherwise store keys. It will be appreciated by one of skill in the art, that in embodiments it may be desirable to limit the number or printers or other writing devices to as few as possible to reduce risk of exposure of private keys, while in embodiments it may be desirable to have a larger number of printers or other writing devices to handle the volume of wallets and/or keys that need to be generated and/or written by the system for its operation.
Private keys may be stored in the selected format along with their corresponding public keys. In embodiments, the private key may be stored with a reference number which may correlate the private key to its corresponding public key. The reference number may be (or may be stored as) a number, alphanumeric code, bar code, QR code, to name a few. A reference number master list may identify a private key, the reference number, and the corresponding public key. The reference number master list may be printed or etched on paper or some other substrate, may be stored digitally on a tape CD, DVD, computer hard drive, or other medium, or otherwise stored in a manner known in the art. The substrates or media just described may have any suitable size, including microscopic or nano scales. In embodiments, the reference number master list may be stored in a secure storage chamber 60 at secure location 10. Storage chamber 60 may be a lockbox, fireproof box, or other secure chamber. If storage is electronic or digital, chamber 60 may protect against electromagnetic waves.
The private and/or public keys and/or any reference number may be stored in a variety of formats, as described herein. The keys may be divided into separate segments for storage. For example, a 51-character key may be divided into three 17-character segments. The same reference number that correlates the private key to the public key or an additional reference number or other identifier may indicate which key segments are part of the same key. The reference identifier or another identifier may be provided and stored with the one or more segments to indicate their order in the assembled key. A numbering schema or other convention may also be used to identify the order of key segments. For example, a first segment may begin with an “A”, a second segment may begin with a “B”, and a third segment may begin with a “C”. The key segments may be stored in one or more locations. In embodiments, the key segments may be divided among a plurality of vaults 70, as described herein.
In embodiments, keys and/or key segments may be stored digitally and/or electronically, e.g., on one or more computer hard drive, disk, tape, memory card, flash memory, CD-ROM, and/or DVD, to name a few. In embodiments, the keys and/or key segments may be printed on any substrate, including paper, papyrus, plastic, and/or any substrate known in the art. In embodiments, the substrate may be fireproof or fire resistant, such as a fireproof plastic. The substrate may be resistant to fluids, e.g., water resistant, or otherwise nonabsorbent. Other printing options may be holographic printing, three-dimensional printing, raised printing, such as Braille lettering, and/or invisible ink printing, such as using inks that require a special light and/or treatment, e.g., heat and/or chemicals, for viewing. In embodiments, keys may be etched, e.g., in wood, metal, glass, plastic, or other compositions known in the art, e.g., to produce a card. In embodiments, a magnetic encoding may be used to write to the card. In embodiments, etched or printed keys or key segments may take any shape, such as coin-shaped tokens or rectangular blocks, to name a few. In embodiments, keys or key segments may be printed, etched, or otherwise stored as alphanumeric strings. In embodiments, keys or key segments may be printed, etched, or otherwise stored in a form readable by programmed devices, such as scanners. Such a form may be a QR code, a bar code, another available scannable code format and/or a proprietary code format. In embodiments, quality control operations may ensure that the keys or key segments are printed accurately and/or are able to be read. In embodiments, printed or etched keys or key segments may be coated to prevent reading the key without removing or otherwise altering the coating. Such a coating may be a UV coating and/or may block X-rays or other forms of scanning or reading. The coating may be scratched off to reveal the data contained below it. The back of the substrate may also be coated to prevent reading through the substrate. Such a coating may provide an indication of whether a printed key or key segment was accessed or attempted to be accessed (e.g., it can be detected whether someone scratched the coating away).
In embodiments, security measures may be established and implemented to reduce the risk of digital wallets being compromised. Further, redundancies can be put in place to provide and/or help ensure that any information necessary to access digital math-based assets in digital wallets can be maintained and/or accessed by the account holders as appropriate, necessary, and/or desired.
Multiple private keys may be required to access a digital wallet. Multiple keys may be stored in the same manner as key segments. In embodiments, where a second private key is required, the one or more individuals or systems providing the second key may be located in different administrative portals, different rooms, and/or different geographies from the one or more individuals or systems providing the first private key. Accordingly, a plurality of administrative portals may be employed by secure digital asset storage systems in accordance with the present invention. In embodiments, a plurality of portals may be used for retrieval of stored digital assets (e.g., by requiring a signature or private key from at least two individuals located in at least two different portals). In embodiments, one portal may be used for re-assembling key segments and thus providing one private key, and an individual in a second location may be required to provide a second key or signature before a digital wallet may be accessed. The second key or signature may be encrypted and/or segmented as described herein with respect to a single private key.
In embodiments, a digital wallet may have more than one private key (e.g., multi-signature wallets). The plurality of private keys may be stored securely in the same manner as a single private key. Each private key segment pertaining to a single wallet may be stored in separate vaults, which may be electronic and/or physical vaults. By allowing for multi-signature wallets, the wallet can provide for approval/signature authority from more than one individual or entity as a further means to control access to digital assets held in such wallet. In embodiments, a signature authority may be an automated electronic signature authority, such as a computer or computer system programmed with transaction approval rules. The automated electronic signature authority may only provide a signature when a transaction satisfies the transaction approval rules. In other embodiments, required signature authorities may be individuals who may be located in different administrative portals, different rooms, and/or different geographies. Accordingly, a plurality of administrative portals may be employed by secure digital asset storage systems in accordance with the present invention. In embodiments, one portal may be used for re-assembling key segments and thus providing one private key, and an individual or system in a second location may be required to provide a second key or signature before a digital wallet may be accessed. The second location may be a second portal, a location in a different building, and/or a different geography, to name a few. The second key or signature may be encrypted and/or segmented as described herein with respect to a single private key.
Keys or key segments may be encrypted and/or ciphered, using one or more ciphers, as an additional security measure. The encryption and/or ciphers may be applied by computers running encryption software, separate encryption devices, or by the actions of one or more persons, e.g., prior to input of the encrypted and/or ciphered data into one or more computers. In embodiments, a key may be stored in reverse order and/or translated (e.g., by adding 1 to each digit and/or advancing each alphabetic character by one position in the Western alphabet, by substitution such as by mapping each character to a different character (e.g., A=3, 5=P, to name a few), to name a few). In embodiments, other encryption algorithms can comprise scrambling of a sequence of characters, addition of characters, and/or hashing. Other encryption techniques are possible. See, e.g., David Kahn, The Codebreakers: The Story of Secret Writing, 1967, ISBN 0-684-83130-9. See also, Bruce Schneier, Applied Cryptography, John Wiley & Sons, 1994, ISBN: 0-471-59756-2. The encryption and/or ciphers may protect against use of the keys by an unauthorized entity who obtains the keys or key segments or copies thereof. The encoding and/or cipher may be maintained in secret and applied to decrypt or decode the keys only when keys must be accessed and used. In embodiments, ciphering may refer to an alphanumeric translation or reordering, while encryption may refer to higher level algorithms, including hashing algorithms. In embodiments, encryption and ciphering may refer to the same processes, in which case descriptions herein of processes involving both encryption and ciphering steps may only entail performance of one such step so as not to be repetitive.
Following storage of the key pairs, the key pairs may be erased from isolated computer 30. Erasure may occur using the computer operating system's delete features, customized software or computer code designed to remove the data from computer memory, magnets used to physically erase the data from the computer's storage drives, and/or other techniques known in the art.
A key reader 40 may be provided to assemble, read, and/or de-crypt the keys or key segments. The key reader 40 may be contained within a Faraday cage, which may be the same Faraday cage housing isolated computer 30. The key reader 40 may read keys that are printed, etched, digitally stored, or otherwise stored. Key reader 40 may be a scanner (e.g., photo scanner or bar code scanner), QR reader, laser, computer hardware, CD reader, and/or digital card reader, to name a few. Key reader 40 may include or be operationally connected to a microscope or magnifying device, such as for keys that are printed in microscopic sizes or other small sizes. In embodiments, key reader 40 may be paired with optical character recognition (“OCR”) technology to create digitally recognized copies of keys that may have been printed, etched, or otherwise stored in a form not immediately readable by a computer.
In embodiments, key reader 40 may comprise an input device, such as a keyboard, touchscreen, mouse, and/or microphone, to name a few. An input device may be used for manual entry of keys and/or key segments into one or more computers so that the computer may further process the key segments. Key reader 40 may be operationally connected to isolated computer 30, which may be a direct connection (e.g., a USB cable, Ethernet cable, Bluetooth, or Wi-Fi, to name a few). In embodiments, key reader 40 may be operationally connected to networked computer 20. Key reader 40 may be operationally connected to a separate computing device.
In embodiments, reassembled keys may be input directly into a networked computer 20, which may then be used to access one or more digital wallets and/or perform one or more transactions. Key reader 40 and/or corresponding software (e.g., running on a computer operationally connected to the key reader) may be programmed or otherwise designed to assemble key segments into completed keys. Key reader 40 and/or corresponding software (e.g., running on a computer operationally connected to the key reader) may also correlate the private keys with their corresponding public keys, optionally using the reference number master list. In embodiments, one or more pieces of software may be used to retrieve, decrypt, assemble, and/or decipher keys and/or key segments. In embodiments, such software may be run on any of one or more secure storage system computers and/or user devices. In embodiments, multiple authority may be required to initiated a retrieval of stored private keys.
In embodiments, a back-up isolated computer 35 and/or a back-up key reader 45 may be provided at secure location 10, as illustrated in
In embodiments, a digital math-based asset miner, such as a bitcoin miner, may be located at or within the administrative portal. The miner may be one or more computers. In embodiments, the miner may be operationally connected to any of the computers and/or devices at the administrative portal described above.
In embodiments, referring to
One or more vaults 70, 70-1, 70-2, 70-3,70-N, may be used to hold assets. Vaults may be any secure storage facilities, structures, and/or systems. For example, a vault may be a bank vault or a safety deposit box. Vaults may have appropriately controlled environments (e.g., regulated temperature and/or humidity, to name a few) to enable long-term storage of keys and/or key segments substrates. Vaults may be operated by one or more entities, which may be separate entities. In embodiments, only bonded employees may be permitted access to the vaults. Also, vaults may be located in one or more physical (e.g., geographic) and/or digital (e.g., residing on one or more separate computer servers or hard drives) locations. In embodiments, vaults may be used in conjunction with digital wallets and/or other devices and/or systems known in the art for storing digital assets and/or data.
In the exemplary embodiments of
In embodiments, one or more duplicate copies of each key or key segment may be produced. Such duplicate copies may be stored in separate vaults, e.g., three sets of keys split into three segments may be stored in nine vaults, four sets of keys split into two segments may be stored in eight vaults, and/or the copies of key segments may be distributed among some other number of vaults, to name a few. See, e.g.,
In embodiments, vaults may hold the keys in an organized or categorized fashion so as to facilitate location of one or more keys or key segments. In embodiments, a sorting reference number may be used to organize the keys or key segments. The sorting reference number may be the same as the reference number that correlates private and public keys. In embodiments, etched coins or other materials or printed keys or key segments may be stacked or otherwise arranged according to the reference number. In embodiments, an index or card catalog may describe the location of the keys. In embodiments, an automated machine may store and retrieve key segments from storage slots, which machine may receive an input to indicate which keys or key segments to retrieve.
In embodiments, digital math-based assets can be stored and/or transferred using either a website or software, such as downloaded software. The website and/or downloadable software may comprise and/or provide access to a digital wallet. Each digital wallet can have one or more individual digital asset accounts (e.g., digital asset addresses) associated with it. Each user can have one or more digital wallets to store digital math-based assets, digital crypto-currency, assets and the like and/or perform transactions involving those currencies or assets. In embodiments, service providers can provide services that are tied to a user's individual account.
Digital wallets and/or the digital asset accounts associated with and/or stored by a digital wallet may be accessed using the private key (which may be used in conjunction with a public key or variant thereof). Accordingly, the generation, access, use, and storage of digital asset accounts is described herein with respect to generation, access, use, and storage of digital wallets. Such descriptions are intended to be representative of digital asset accounts and not exclusive thereof.
A digital wallet can be generated using a digital asset client 110 (e.g., a Bitcoin client). In embodiments, a digital wallet can be created using a key pair system, such as an asymmetric key pair like a public key and a private key. The public key can be shared with others to designate the address of a user's individual account and/or can be used by registries and/or others to track digital math-based asset transactions involving a digital asset account associated with the digital wallet. Such transactions may be listed or otherwise identified by the digital wallet. The public key may be used to designate a recipient of a digital asset transaction. A corresponding private key can be held by the account holder in secret to access the digital wallet and perform transactions. In embodiments, a private key may be a 256-bit number, which can be represented by a 64-character hexadecimal private key and/or a 51-character base-58 private key. As discussed herein, private keys of other lengths and/or based on other numbering systems can be used, depending upon the user's desire to maintain a certain level of security and convenience. Other forms of key pairs, or security measures can be used consistent with embodiments of the present invention.
A digital wallet, in embodiments, may be associated with one or more of: a bank account, a credit card, a digital asset credit card, a credit application, a loan value application, a business, and/or a country. For example, the digital wallet may include digital assets that may be spent using Flexa. Flexa is associated with a digital payment network that utilizes cryptocurrencies. The digital payment network utilizes Flexa's Spedn application to process consumer transactions with third party merchants via connections with merchant point of sale terminals.
In embodiments, a digital wallet may store one or more private keys or one or more key pairs which may correspond to one or more digital asset accounts.
In embodiments, a digital wallet may be a computer software wallet, which may be installed on a computer. The user of a computer software wallet may be responsible for performing backups of the wallet, e.g., to protect against loss or destruction, particularly of the private and/or public key. In embodiments, a digital wallet may be a mobile wallet, which may operate on a mobile device (e.g., mobile phone, smart phone, cell phone, iPod Touch, PDA, tablet, portable computer, to name a few). In embodiments, a digital wallet may be a website wallet or a web wallet. A user of a web wallet may not be required to perform backups, as the web wallet may be responsible for storage of digital assets. Different wallet clients may be provided, which may offer different performance and/or features in terms of, e.g., security, backup options, connectivity to banks or digital asset exchanges, user interface, and/or speed, to name a few.
The digital asset exchange computer system 3230 may be used to convert digital assets into fiat or other digital assets as well as to exchange fiat for digital assets. In embodiments, a digital asset exchange computer system 3230 may include one or more databases that are used to store user account authentication data, fiat account data, digital wallet data, digital asset customer account data and transaction data, including transaction parameters and transaction instructions. A digital wallet system is operatively connected to a decentralized digital asset network that uses a decentralized electronic ledger in the form of a blockchain maintained by a plurality of physically remote computer systems to track at least one of asset ownership or transactions in a digital asset exchange system. The digital wallet system includes one or more digital wallet modules.
In embodiments, the digital asset exchange computer system 3230 may be operatively connected with a credit application and/or loan value application (e.g. Flexa).
In embodiments, the digital wallet system generates transaction rules for automatic digital asset transactions based at least the one or more received transaction parameters and the received transaction instructions as indicated at step S3804. In embodiments, the transaction rule includes computer code running on the one or more computers to perform a transaction when one or more specified conditions are met or not met, based on the rules.
In embodiments, the digital wallet system accesses transaction data including price data associated with the specified amount of digital assets and stores the transaction data in the one or more databases as indicated in step S3806. In an embodiment the digital wallet system may access the transaction data using an application programming interface of an exchange agent. At step S3808, the digital wallet system evaluates the price data according to the transaction rules and, at step S3810, performs automated transactions when pre-defined conditions are met or not met in accordance with the transaction rules and the price data. This evaluation may include testing the transaction data against one or more logical conditions embodied in the transaction rules. In embodiments, these logical conditions include determining at least one of whether the digital asset price has reached or crossed a threshold value; or whether a rate of change in price has reached or crossed a threshold value. The digital wallet system may format the transaction data to be compatible with the digital wallet system.
In embodiments, at step S3812, the digital wallet system may generate one or more notifications to one or more user devices, with the notices includes at least one of a status update on transactions; notification of at least one of incomplete, pending or failed transactions; a log of all transactions as performed by at least one of the digital wallet system or by a user and a log of all transaction opportunities, including transactions declined or not otherwise authorized and transmits the one or more notifications to the user devices.
The digital asset exchange computer system also includes a fund transfer system including a fiat account funding and redemption system, a digital asset account funding and redemption system operatively connected to the digital wallet system and operatively connected to the decentralized digital asset network and a settlement engine operatively connected to the decentralized digital asset network and configured to carry out transactions. The settlement engine may be configured to process specified customer transactions to purchase or sell digital assets according to a user's instructions, if certain user specified factors are met. The user specified factors include that at least one of digital assets are: (a) within a given price, (b) quantity, or (c) period of time. In embodiments, the settlement engine may perform steps of holding, by the digital asset exchange computer system, funds in escrow until a buyer's payment of fiat is received into a bank account; receiving, by the digital asset exchange computer system from a digital asset buyer device, a notification of received digital assets from a digital asset seller; and providing, by the digital asset exchange computer system to a bank computer system associated with a digital asset exchange bank, n instruction to release the digital asset buyer's funds to the digital asset seller. The settlement engine may include pre-program instructions to transfer an amount of digital assets from a seller wallet to at least one buyer wallet upon the occurrence of user specified conditions.
In embodiments, the transaction may be at least one of formation, buying and selling of derivative products, including call options and put options. In embodiments, the transaction may be at least one or more of digital asset lending, delayed settlements, derivative swaps, futures and forwards.
In embodiments, the digital asset account funding and redemption system is configured to process funding of a digital asset account held by the exchange from an exchange customer by receiving, by the digital asset exchange computer system, an initial transfer of digital assets; receiving, by the digital asset exchange computer system, a confirmation of clearance of the digital asset transfer; and updating, by the digital asset exchange computer system, an existing customer account in the one more or more databases with the received digital assets including making an electronic entry in an exchange digital asset electronic ledger and providing a notification that digital assets are received.
In embodiments, the digital asset account funding and redemption system is configured to process withdrawing a digital asset account held by the exchange from an exchange customer. For example, the digital asset account funding and redemption system may provide a withdrawal interface to a first customer user device associated with a first customer, receive user first withdrawal data including at least a first destination wallet address and a first request digital wallet asset withdrawal amount value from the first customer user device, verify that the first digital asset account associated with the first customer contains sufficient digital assets to cover the requested withdrawal amount by reading a digital asset electronic ledger to determine a first digital asset account balance; update the exchange digital asset electronic ledger to reflect the first withdrawal data as pending, execute a first withdrawal based on the first withdrawal data by broadcasting the first withdrawal to a digital asset network electronic ledger, monitor the network digital asset ledger to determine that a transaction based on the first withdrawal is confirmed and update the digital asset ledger to reflect confirmation of the first withdrawal. In embodiments, the digital wallet system may request authority from a user to proceed with the automated transactions before executing the automated transactions. In embodiments, the digital wallet system may require receipt of a user's authorization before performing a transaction by at least one of telephone dialing a number and entering specified digits, text message, email, or via a computer application or a user's mobile wallet. In embodiments the digital wallet system will automatically perform the transaction if no response is received within a predetermined amount of time set by a user in advance or by default.
The digital asset exchange computer system may also include a fraud analysis system configured to detect fraudulent and/or unauthorized transactions.
In embodiments, the digital math-based asset is bitcoin. In embodiments, the digital math-based asset is based on a mathematical protocol for proof of work. The mathematical protocol may be open source. In embodiments, the mathematical protocol includes a one-way cryptographic algorithm. In embodiments, the mathematical protocol includes a sequential hard memory function. The digital math-based asset may be based on a mathematical protocol for proof of stake and is open source. In embodiments, the digital math-based asset is based on a cryptographic mathematical protocol. The digital math-based asset may be based on a mathematical protocol for a hybrid of proof of work and proof of stake. The digital math-based asset may be based on a mathematical protocol for proof of stake velocity. The mathematical protocol may rely upon ownership of respective digital math-based asset as a function of duration of ownership. The digital math-based asset may be based on a mathematical protocol for proof of burn.
In embodiments, a number of digital math-based assets in the decentralized digital assert network is limited. In embodiments, a number of digital math-based assets in the decentralized digital assert network is not limited. A specified number of digital math-based assets in the decentralized digital asset network may be added into circulation during a defined time period.
In embodiments, the digital wallet is activated by a private key, which is mathematically related to a public address in a one-way function. In embodiments, the digital wallet includes a multi-signature account which requires a plurality of private keys to access the digital assets held by the multi-signature account. In embodiments, more keys are generated for the multi-signature account than are required to access and/or use an account.
In embodiments, an accounting computer 25 may be a hardware security module, which may comprise hardware (e.g., one or more processors, computer-readable memory, communications portals, and/or input devices, to name a few) and/or software (e.g., software code designed to verify transactions, flag potentially erroneous transactions, and/or stop potentially erroneous or unauthorized transactions). Such a device may verify spending transactions before the transactions are executed. A hardware security module may flag transactions for review (e.g., by portal administrators), before the transactions may be confirmed. A hardware security module may be an offline device, which may be given a daily account activity log (e.g., a log of exchange withdrawals, deposits, exchange transactions (e.g., purchases and sales), purchase order receipts, and/or sell order receipts, to name a few) to determine whether proposed transactions, particularly spending transactions, are valid. A protocol for identifying owners of a digital wallet may be used to verify that spending transactions will deliver the correct amount of assets to the correct address. In embodiments, a quorum of a specified size may be required to override a hardware security module. In embodiments, a transaction may be processed using both an isolated and a networked computer, as discussed herein. Such a transaction may be performed using an air-gapped digital wallet, such as described in the context of
In a step S6002, a computer system comprising one or more computers may be used to generate one or more digital asset accounts capable of holding one or more digital math-based assets. In embodiments, such accounts may be associated with digital asset ownership and/or possession without physically holding a digital asset in any location. A digital asset software client, which may comprise part of a digital wallet or may be accessed using a digital wallet, may be used to generate the digital asset accounts.
In a step S6004, the computer system may be used to obtain one or more private keys corresponding to the one or more digital asset accounts. In embodiments, the private keys may be generated as part of the digital asset account creation process.
In a step S6006, the computer system may be used to divide each of the one or more private keys into a plurality of private key segments. In embodiments, such as with a multi-signature wallet, at least one private key for each digital asset account may be divided into private key segments.
In a step S6008, the one or more computers may be used to encrypt each of the plurality of private key segments. Encryption can comprise any of the techniques described herein, such as character substitution, scrambling, mapping, and/or hashing, to name a few. The computer system can apply one or more algorithms to perform the encryption. Symmetric and or asymmetric encryption algorithms may be applied.
In a step S6010, the one or more computers may be used to generate and/or associate each of the plurality of private key segments with a respective reference identifier. A reference identifier may be a number, alphanumeric sequence, or other unique sequence that can be used to identify key segments, which may be used for storage and/or retrieval of key segments. The reference identifier for each key segment may be stored on a reference identifier master list, which may be stored electronically and/or on a physical substrate. The reference identifier master list may associate with each other the reference identifiers for key segments corresponding to the same key, and/or may also associate a digital asset account identifier (e.g., a public key or public address) with the key segments.
In a step S6012, the one or more computers may be used to create one or more cards for each of the encrypted plurality of private key segments. Each card may have fixed thereon one of the encrypted plurality of private key segments along with the respective associated reference identifier. The cards may be paper, such as index cards, 8½ in.×11 in. sheets of paper, or other paper products. In other embodiments, the cards may include plastic or metal. The cards may be laminated. A writing device may fix the key segments and reference identifiers to the cards by techniques such as printing, etching, and/or magnetically encoding, to name a few. A scannable code, such as a bar code or QR code, may be used to write the keys to the cards.
In embodiments, collated sets of cards may be produced for a plurality of digital asset accounts. Each set may contain only one card per private key such that the private key segments for a single private key are divided among different sets of cards.
In embodiments, following creation of the one or more cards, quality control steps can be performed. A reading device may be used to read each of the cards to ensure readability.
In a step S6014, the one or more computers may be used to track storage of each of the one or more cards in one or more vaults. Vaults may be geographically remote. Vaults can include bank vaults and/or precious metal vaults. In embodiments, a main set of vaults and one or more sets of backup vaults may be used. A main set of vaults can be located in a geographically proximate area, such as a metropolitan area of a city, while backup sets of vaults may be located in geographically remote areas. The backup vaults may contain duplicate copies of the cards. Vault locations for each card or set of cards may be included on the reference identifier master list.
In embodiments, the process can further include receiving at the computer system a quantity of digital math-based asset and storing those digital assets in the one or more securely stored digital asset accounts. In embodiments, storing the digital asset can comprise transferring the digital assets into accounts with securely stored private keys. Accordingly, storing can comprise generating electronic transfer instructions for an electronic transfer of the quantity of digital math-based assets to the one or more digital asset accounts and broadcasting the electronic transfer instructions to a decentralized electronic ledger maintained by a plurality of physically remote computer systems.
In a step S6022, a computer system comprising one or more computers may be used to generate one or more digital asset accounts capable of holding one or more digital math-based assets, as described with respect to step S6002 of
In a step S6024, the computer system may be used to obtain one or more private keys corresponding to the one or more digital asset accounts, as described with respect to step S6004 of
In a step S6026, the computer system may be used to encrypt each of the one or more private keys.
After encryption, in a step S6028, the computer system may be used to divide each of the encrypted private keys into a plurality of key segments.
In a step S6030, the one or more computers may be used to generate and/or associate each of the plurality of private key segments with a respective reference identifier.
In a step S6032, the one or more computers may be used to create one or more cards for each of the plurality of private key segments.
In a step S6034, the one or more computers may be used to track storage of each of the one or more cards in one or more vaults.
In a step S6042, a computer system comprising one or more computers may be used to generate one or more digital asset accounts capable of holding one or more digital math-based assets.
In a step S6044, the computer system may be used to obtain a first plurality of private keys corresponding to each of the one or more digital asset accounts. Each first plurality of private keys can comprise the private keys of a multi-signature account.
In a step 6046, the computer system may be used to divide a first private key of the first plurality of private keys into a second plurality of first private key segments. For a multi-signature digital asset account at least one of the private keys may be divided into private key segments.
In a step S6048, the computer system may be used to encrypt each of the second plurality of first private key segments. In embodiments, the second key may be encrypted.
In a step S6050, the computer system may be used to generate and/or associate each of the second plurality of first private key segments with a respective reference identifier.
In a step S6052, the computer system may be used to create one or more one or more cards for each of the encrypted second plurality of first private key segments wherein each of the one or more cards has fixed thereon one of the encrypted second plurality of first private key segments along with the respective associated reference identifier. In embodiments, the second key may be written, e.g. using the writing device, to one or more physical substrates, such as paper, plastic, and/or metal. In other embodiments, the second key may be stored electronically.
In a step S6054, the computer system may be used to track storage of each of the cards in one or more vaults, as well as to track storage of the second private key. A reference identifier master list may identify the storage locations of each key and key segment.
In a step S6062, an electronic isolation chamber may be provided containing one or more writing devices (e.g., printers, engravers, magnetic card encoders, to name a few), one or more reading devices (e.g., scanners, bar code scanners, QR readers, magnetic card readers, to name a few), and an isolated computer operatively connected to the one or more writing devices but not directly connected to an external data network and comprising one or more processors and computer-readable memory.
In a step S6064, the isolated computer may be used to generate a first plurality of digital asset accounts capable of holding one or more digital math-based assets. In embodiments, the first plurality of digital asset accounts may comprise multi-signature digital asset accounts.
In a step S6066, the isolated computer may be used to obtain one or more private keys and a digital asset account identifier corresponding to each of the first plurality of digital asset accounts.
In a step S6068, the isolated computer may be used to associate each of the one or more digital asset accounts with a respective reference identifier. The reference identifier may comprise an alphanumeric sequence. In embodiments, respective reference identifiers may be associated with one or more keys or key segments corresponding to the respective digital asset accounts.
In a step S6070, the isolated computer may be used to divide at least one of the one or more private keys corresponding to each of the first plurality of digital asset accounts into a second plurality of private key segments. In embodiments, each private key segment may be required to regenerate the respective private key. In embodiments, a subset of the second plurality of private key segments (e.g., 3 of 5 keys) could be sufficient to regenerate the respective private key.
In a step S6072, the isolated computer may transmit to the one or more writing devices, electronic writing instructions for writing each of the second plurality of private key segments and the respective reference identifier on a respective card to generate a third plurality of collated sets of cards wherein each of the collated sets of cards comprises cards corresponding to different private keys. In embodiments, the third plurality of collated sets can include one or more duplicate sets for each of the collated sets of cards. In embodiments, the isolated computer may be used to generate the electronic writing instructions prior to transmitting them to the one or more writing devices.
In a step S6074, the one or more writing devices may be used to write each respective private key segment of the second plurality of private key segments and the respective reference identifier on a respective card according to the electronic writing instructions. In embodiments, step S6074 can comprise printing and/or etching each respective private key segment of the plurality of private key segments and the respective reference identifier on respective separate cards. In embodiments, each respective private key segment of the plurality of private key segments may be magnetically encoded on respective separate cards. The respective reference identifiers may be printed on the respective cards, e.g., to be readable without a magnetic card reader. Each respective private key segment of the second plurality of private key segments may be written, e.g., printed, as a scannable code, such as a bar code and/or a QR code.
In a step S6076, the isolated computer may be used to write each of the digital asset account identifiers along with the corresponding reference identifier. In embodiments, step S6076 can further comprise the steps of transmitting, from the isolated computer to the one or more writing devices, second electronic writing instructions for writing each of the digital asset account identifiers along with the corresponding reference identifier, and writing, using the one or more writing devices, each of the digital asset account identifiers along with the corresponding reference identifier according to the second writing instructions. In embodiments, writing according to the second writing instructions can comprise writing to an electronic storage medium, such as a flash drive, hard drive, and/or disc. In embodiments, the electronic storage medium could include a hardware storage module (“HSM”). In embodiments, writing according to the second writing instructions can comprise writing to a physical storage medium, such as paper.
In a step S6078, the one or more reading devices may be used to read each of the cards to ensure readability. In embodiments, step S6078 may be performed after step S6076. In embodiments, step S6078 may be performed before step S6076.
In embodiments, the process illustrated by
In embodiments, the process can further comprise the step of destroying the isolated computer, the one or more writing devices, and the one or more reading devices, or destroying any one of those devices.
In embodiments, the method can further comprise the step of encrypting, using the isolated computer, each of the second plurality of private key segments. In embodiments, encryption techniques can include symmetric-key encryption, asymmetric-key encryption, scrambling, substitution, hashing, or adding characters.
In embodiments, the method can further comprise the step of tracking, using the isolated computer, storage of each of the third plurality of collated sets of cards. In embodiments, each of the third plurality of collated sets of cards may be stored in a vault. In embodiments, each collated set of cards may be stored in a separate vault.
In embodiments, an accounting computer 25 may be a hardware security module, which may comprise hardware (e.g., one or more processors, computer-readable memory, communications portals, and/or input devices, to name a few) and/or software (e.g., software code designed to verify transactions, flag potentially erroneous transactions, and/or stop potentially erroneous or unauthorized transactions). Such a device may verify spending transactions before the transactions are executed. A hardware security module may flag transactions for review (e.g., by portal administrators), before the transactions may be confirmed. A hardware security module may be an offline device, which may be given a daily account activity log (e.g., a log of ETP redemptions and/or creations) to determine whether proposed transactions, particularly spending transactions, are valid. A protocol for identifying owners of a digital wallet may be used to verify that spending transactions will deliver the correct amount of assets to the correct address. In embodiments, a quorum of a specified size may be required to override a hardware security module. In embodiments, a transaction may be processed using both an isolated and a networked computer, as discussed herein. Such a transaction may be performed using an air-gapped digital wallet, such as described in the context of
In exemplary embodiments, in step S702, a computer system comprising one or more computers may be used to determine one or more digital asset account identifiers corresponding to one or more digital asset accounts capable of holding one or more digital math-based assets.
In a step S704, the computer system may be used to access key storage information associated with each of the one or more digital asset account identifiers. In embodiments, the key storage information may comprise a reference identifier associated with one or more stored private key segments.
In a step 706, the computer system may be used to determine, based upon the key storage information, storage locations corresponding to each of a plurality of private key segments corresponding to each of the one or more digital asset accounts.
In a step 708, retrieval instructions for retrieving each of the plurality of private key segments may be issued or caused to be issued.
In a step 710, each of the plurality of private key segments may be received at the computer system.
In a step 712, the computer system may be used to decrypt each of the plurality of private key segments.
In a step 714, the computer system may be used to assemble each of the plurality of private key segments into one or more private keys.
In embodiments, the process depicted in
In embodiments, processes for generating digital asset accounts and/or storing associated keys may be performed by a secure system, e.g., an administrative portal. The system can comprise an electronic isolation chamber, such as a Faraday cage. The system can further comprise one or more isolated computers within the electronic isolation chamber and comprising one or more processors and computer-readable memory operatively connected to the one or more processors and having stored thereon instructions for carrying out the steps of (i) generating, using the one or more isolated computers, one or more digital asset accounts capable of holding one or more digital math-based assets; (ii) obtaining, using the one or more isolated computers, one or more private keys corresponding to the one or more digital asset accounts; (iii) dividing, using the one or more isolated computers, at least one of the one or more private keys for each digital asset account into a plurality of private key segments, wherein each private key segment will be stored; (iv) associating, using the one or more isolated computers, each of the plurality of private key segments with a respective reference identifier; and (v) transmitting, from the one or more isolated computers to one or more writing devices operatively connected to the one or more isolated computers, electronic writing instructions for writing a plurality of cards, collated into a plurality of sets having only one private key segment per digital asset account, and each card containing one of the plurality of private key segments along with the respective associated reference identifier. The system can further comprise one or more writing devices located within the electronic isolation chamber and configured to perform the electronic writing instructions, including collating the plurality of cards into the plurality of sets. The system can also comprise one or more reading devices located within the electronic isolation chamber and configured to read the plurality of private key segments along with the respective associated reference identifier from the one or more cards. The reading devices may be used for quality control, to ensure that the cards are readable.
In embodiments, a digital asset account holder may operate one or more computers to manage, process, and/or store the transactions and/or digital assets. In embodiments, a portion, consisting of some or all, of the digital assets may be stored in cold storage, which involves no outside connections. Cold storage may be a bank vault, a precious metal vault, a lockbox, or some other secure room or area. There may be no communication channels connecting to the cold storage area. In embodiments, electronic vaults may be used. Electronic vaults may comprise cloud storage, one or more hard drives, flash drives, memory cards or like storage technology, to name a few. Electronic vaults may hold one or more keys and/or key segments, which may be encrypted and/or encoded as described herein.
In embodiments, the cold storage may comprise a divided storage system. In a divided storage system, components or portions of components may be stored at multiple locations. Components may be at least digital wallets, public and/or private keys, or assets.
Duplicate sets of the segmented private keys may then be made and stored in separate vaults (e.g., one duplicate copy divided between Vaults 70-B1, 70-B2, and 70-B3, and another duplicate copy divide between Vaults 70-C1, 70-C2, and 70-C3). Each set of segmented keys 80 may be located in the same general vicinity (e.g., Location B for Vaults 70-B1, 70-B2, and 70-B3 and Location C for Vaults 70-C1, 70-C2, and 70-C3), with each general vicinity being different from other general vicinities (e.g., Location B may be Philadelphia and Location C may be Indianapolis, Ind.). Locations may include domestic and/or international locations. Locations can be selected based on at least one or more of the following parameters: ease of access, level of security, diversity of geographic risk, diversity of security/terror risk, diversity of available security measures, location of suitable vaults in existence (e.g., custodian vaults for a trust associated with an ETP), space available at vaults, jurisdictional concerns, to name a few. In embodiments, three geographic locations can be used wherein Location A is within a short intraday time of transit (e.g., 1 hour), Location B is within a longer intraday time of transit (e.g., 3-4 hours), and Location C is within one or more day times of transit (e.g., 1-2 days). In embodiments, the location of the vaults may be within a distance that allows segments of key pairs to be retrieved within a redemption waiting period (e.g., 3 days). A complete key set (e.g., stored private keys parts 1-3) may be stored in each vault general location (e.g., Location A, Location B, Location C).
In
In embodiments, there may be two sets of segmented keys, as illustrated in
In embodiments, duplicate sets may not be embodied in same form as the original set and/or other duplicate sets. For example, two sets may be stored on paper, and a third set is stored on papyrus. In embodiments, at least one set of segmented keys can be stored on paper, while at least one set is stored on one or more disks, memory sticks, memory cards, tapes, hard drives, or other computer readable media. In embodiments, the same number of segments can be used for each set. In embodiments, a different number of segments can be used for at least two of the sets (e.g., 3 segments for 1 set, and 4 segments for 1 set). In embodiments, different types of coding and/or encryption can be used for at least two sets.
A cold storage back-up may be provided by a one-way electronic data recordation system. The system can function as a write-only ledger. Upon deposit of digital assets into cold storage, the corresponding private keys may be transmitted to the recordation system, which will store a record of the transaction. When digital assets are removed from a wallet, a record of the removal and/or wallet destruction can be sent to the system. In the event that wallet keys must be retrieved, the recordation system can be accessed to determine the wallet keys. Accessing the recordation system to retrieve keys can be designed to be a difficult operation, only to be performed in the event of an emergency need to recover wallet keys.
Digital asset storage services and/or digital asset protection may be provided in accordance with the present invention. Digital asset storage may use any of the secure storage systems and methods described herein, including those described with respect to a digital asset ETP. In embodiments, a digital asset storage service may be provided to other entities (e.g., a trust associated with an ETP, authorized participants in the trust, retailers, banks, or other digital asset users), to provide secure storage of digital assets. Such a storage service may use any of the security measures described herein. In embodiments, a digital asset storage service may comprise, form a part of, and/or be associated with a digital asset insurance system, as described herein.
Digital asset protection can be digital asset insurance and/or digital asset warranties. Digital asset insurance may be insured key storage, which may entail secure storage of one or more keys, such as private keys, where the secure storage service may guarantee the return of the stored private key and will pay out some amount if the key cannot be returned. In embodiments, a digital asset warranty can be a warranty against key loss, which may be a warranty against key loss by a digital asset storage service.
A digital asset storage service and/or a digital asset protection system may be associated with and/or accessed through one or more digital wallets. In embodiments, digital asset protection and/or storage services may only be available when using a particular digital asset wallet and/or when employing particular storage mechanisms or procedures. In embodiments, a digital wallet may provide an option to request and/or accept protection and/or an option to request and/or accept storage of one or more keys associated with the wallet. In embodiments, a wallet may prompt and/or require a user to store the private key of the wallet, e.g., using the secure digital asset storage service.
The exemplary system illustrated in
One or more users 3315 may be, e.g., customers and/or claimants of a digital asset storage and/or protection system. Users 3315 may obtain key storage for one or more digital wallets containing digital assets in one or more denominations. Users 3315 may access or otherwise participate in a digital asset storage and/or protection system using one or more user device. In embodiments, the same digital wallet may be accessed from a plurality of user devices using the same key combinations (e.g., private and public keys).
As discussed herein, a digital asset storage service may be provided to users of a digital asset network to provide secure storage of digital assets. In embodiments, the secure storage service may be used in conjunction with a digital asset protection plan, such as an insurance or warranty plan, although the storage service may also be used without insurance or warranties.
In embodiments, a user of a digital asset network may provide one or more keys or key segments to the key storage service for storage. Keys or key segments may be provided to the storage service via email or other electronic data transfer, any of which may be secure or otherwise encrypted. A user may use software to generate a wallet with one or more private keys and/or to divide the keys into segments. The software may include the ability to transmit, e.g., via a secure connection, the keys or key segments to the secure storage company. In embodiments, keys may be delivered to a key storage company in person, via mail, or via fax. Such keys may be stored in accordance with the secure and cold storage vault security mechanisms discussed herein, which may include dividing the keys into segments if not already divided.
Keys may also be generated at the secure storage company, e.g., at the secure storage site. Accordingly, a user may log into a website or otherwise connect to a portal for accessing wallet generation software. Such software may be running on one or more processors located at the secure storage company. The user may use the wallet generation software to create a wallet with one or more private keys. The user may also use such software to split one or more keys into key segments. Each key or key segment may then be printed, transcribed, or otherwise prepared for storage. In embodiments, the software may be programmed to transmit each key or key segment to a different printer, printing device, or electronic storage device, any of which may be located in different rooms, on different premises, in different geographies, and/or in separate vaults, to name a few. Thus, the key storage service may then store each key or key segment in separate locations, in accordance with the secure storage mechanisms discussed herein, such as the cold storage vault systems. Accordingly, the key storage company may never have access to an assembled key or to the required plurality of keys to a multi-key wallet.
Upon a user's request for retrieval of a stored key or keys, the secure key storage company may send to the user originals or copies, physically or electronically, of the keys or key segments. In embodiments, the key storage company may never reassemble keys or access a digital wallet itself. The secure key storage company may charge fees at setup and/or at retrieval, as well as recurring storage fees.
In a step S3424, a user may provide identification information, which may be received at the storage system Identification information may comprise any of a name, contact information (e.g., address, telephone number, e-mail address, to name a few), government ID information (e.g., an image of a driver's license, a driver's license ID number, a passport number, to name a few), biometric information (e.g., a voice sample, current photograph, eye scan, fingerprint, to name a few), username, password, and/or one or more security questions, to name a few. The identification information may be provided by and/or correspond to the requestor of private key storage and/or the private key owner. In embodiments, the digital asset insurance system may receive and/or store a user's identification information.
In a step S3426, the storage system may obtain a private key to be stored. The storage system may receive the key or fetch it, e.g., from a user electronic device, such as a mobile phone. In embodiments, the storage system may also obtain a public key to be stored.
In a step S3428, the storage system may cipher the private key, as described herein. In embodiments, the private key may not be ciphered before dividing it into segments. In other embodiments, the private key may be encrypted.
In a step S3430, the digital asset storage system may divide the ciphered private key into any number of segments. In the case of a multi-key wallet, the keys may not be divided into segments. However, keys to a multi-key wallet may be encrypted and/or ciphered.
In a step S3432, the storage system may encrypt each private key segment. In embodiments, encryption and/or ciphering may occur only before or only after dividing a key into segments. In embodiments, the key segments may not be encrypted after the segments are created. The key segments may be ciphered or not processed further.
In a step S3434, the storage system may transfer each encrypted private key segment to a different electronic vault for storage. In embodiments, the vaults may not be electronic, and the key segments may be printed or otherwise transcribed on a physical substrate and stored in the vaults. Any number of vaults may be used (e.g., one vault for each key segment, multiple vaults for redundant copies of each key segment, one or more vaults with two or more key segments stored together, to name a few). A code, such as a bar code or QR code, may be provided along with the key segments (e.g., printed with a physically transcribed copy of a key segment electronically saved with an electronic key segment, or appended to an electronic key segment, to name a few). The code may identify the key segments (e.g., which key segments are part of the same key) and/or the order of the key segments.
In a step S3436, the storage system may store, in one or more databases, key storage plan information (e.g., a subscription for key storage costing $1.99/month), user identification information, private key segment vault location information, and decryption and deciphering instructions. The databases may be computer-readable databases or physical (e.g., paper) databases that may be scanned and then read by one or more computers. In embodiments, the stored information may be sent to a user and/or an storage system administrative coordinator, which may be a computer that can handle retrieval of stored keys.
In a step S3438, the digital asset storage system may send confirmation of private key storage (e.g., over a data transfer network) to the user (e.g., requestor of private key storage or other person associated with the received identification information) and/or a third party. Confirmation of storage may be recorded by the storage system and/or another entity associated with the storage system.
In a step S3444, the storage system may receive user or digital wallet owner account identification information.
In a step S3446, the storage system may obtain (e.g., receive or fetch) a private key.
In a step S3448, the storage system may cipher the private key. In embodiments, no ciphering may occur before dividing the key into segments.
In a step S3450, the storage system may divide the private key (or ciphered private key) into segments.
In a step S3452, the storage system may cipher each private key segment.
In a step S3454, the storage system may print each ciphered private key segment. One or more copies of the key segments may be printed and/or otherwise transcribed onto any substrate and/or multiple substrates (e.g., paper, plastic, metal, to name a few). A code, such as a QR code or bar code, may be used to identify corresponding key segments and/or the order of the key segments. Such a code may be printed or otherwise provided with the key segments.
In a step S3456, the digital asset storage system may store each ciphered private key segment, as discussed herein. The key segments may be stored in electronic vaults (e.g., hard drives, tape drives, solid state memory, to name a few). Separate vaults may be used for each key segment, although multiple key segments corresponding to multiple different private keys may be stored in the same vault.
In a step S3458, the storage system may store each printed key segment in a physical vault, which may be separate vaults for each key segment.
In a step S3460, the storage system may store, in one or more databases, key storage plan information, user identification information, private key segment vault location information, deciphering instructions, and decryption instructions, where applicable.
In a step S3462, the storage system may send confirmation of private key storage to the user.
Recovering Stored Keys from a Digital Asset Key Storage Service
A user of a secure storage service or system may request access to a stored key, which may be a means of recovering a lost key.
In a step S3502, a user may submit a claim for a lost private key, which may be received by a computer system of a secure storage service storing a copy of the user's private key. A claim may be a request for retrieval of one or more stored keys.
In a step S3504, the storage system, using the computer system, may correlate the received claim to one or more locations where private key segments are stored. For example, the computer system may access a database of policy information to determine where (e.g., in which vaults) a claimants keys or key segments are stored.
In a step S3506, a message, which may constitute instructions, may be transmitted to one or more storage facilities to retrieve the private key segments. A computer system may automatically generate such a message based upon the information pertaining to stored keys or key segments. Such a key retrieval message can include a security code or other authorization to access a secure storage location. In embodiments, the computer system may employ security measures, such as a secure code or digital signature, to provide verification and/or authentication of a retrieval message.
In a step S3508, the private key segments may be verified. Keys or key segments may be retrieved from their respective storage locations. Quality control measures may verify that the correct key segments were retrieved and/or that the keys or key segments are readable, e.g., by a specially programmed scanning device, such as a QR scanner.
In a step S3510, the private key segments may be transmitted to a device and/or account corresponding to the user. One or more secure transmissions may be used. Two-factor authentication may be required of the recipient before a transmission is sent and/or opened by the recipient. In embodiments, the system may decrypt, reassemble, and/or decipher private keys and/or key segments before returning the keys and/or key segments to a user. In embodiments, a user may be provided with the option of having the system perform the decrypting, reassembling, and/or deciphering steps. In embodiments, software may be provided to a user to enable such steps to be performed by a user or under a user's control. In embodiments, the computer system may never decrypt keys or key segments that were encrypted by a user. Accordingly, in step S3510, the user may be provided with key segments and/or reassembled keys, which may be in various states of security (e.g., ciphered, segmented, and/or encrypted).
In a step S3512, the system may receive confirmation that the user received the private keys or key segments. A user device may automatically generate and/or transmit a confirmation upon receipt of the keys or key segments, upon reassembling thereof, upon opening a corresponding digital asset wallet, or upon instruction for a user, to name a few. Such confirmation may provide an indication that the secure storage service and/or protection service met its obligation, e.g., to the customer.
Thus, in a step S3522, a user may submit a claim for a lost private key, which may be received by a secure storage service storing a copy of the user's private key.
In a step S3524, the secure storage system may authenticate the identity of the claimant. Authentication may involve any of receipt of any of a user's identification information, such as name, username, password, biometric information, or the like. In embodiments, three forms of identification information may be required. In embodiments, a claimant may receive a phone call, which may be auto-generated and auto-executed by the system, which may provide the claimant with a code to input at a user device. In embodiments, the user may be required to repeat a phrase, which may be a unique phrase. Voice analysis and/or recognition techniques may be employed. The user may be required to submit a current picture or video. The system may compare the received identification information to a database of authorized user identification information in order to authenticate the identity of the claimant.
In a step S3526, the system may correlate the received claim to one or more locations where private key segments may be stored.
In a step S3528, a message, which may constitute instructions, may be transmitted to one or more storage facilities to retrieve the private key segments.
In a step S3530, the private key segments may be verified.
In a step S3532, the private key segments may be transmitted to a device and/or account corresponding to the user. In embodiments, decryption, reassembly, and or deciphering of private keys and/or key segments may occur before or after returning the keys and/or key segments to a user and may be performed by the system or by a user, who may use software provided by the system.
In a step S3534, the system may receive confirmation that the user received the private key segments.
Another exemplary process for recovering a key is provided in
Thus, in a step S3542, a user may submit a claim for a lost private key, which may be received by a secure storage service storing a copy of the user's private key.
In a step S3544, the secure storage system may authenticate the identity of the claimant, in manners described for step S3524 of
In a step S3546, the system may check the account balance of the account.
In a step S3548, the system may determine whether to proceed with the requested key retrieval. In embodiments, retrieval may be halted if an account balance is above a threshold or below a threshold.
In a step S3550, the system may correlate the received claim to one or more locations where private key segments may be stored.
In a step S3552, a message, which may constitute instructions, may be transmitted to one or more storage facilities to retrieve the private key segments.
In a step S3554, the private key segments may be verified.
In a step S3556, the private key segments may be transmitted to a device and/or account corresponding to the user of the account. In embodiments, decryption, reassembly, and or deciphering of private keys and/or key segments may occur before or after returning the keys and/or key segments to a user and may be performed by the system or by a user, who may use software provided by the system.
In a step S3558, the system may receive confirmation that the user received the private key segments.
In exemplary embodiments, a user of a secure storage service or system may be required to provide proof of control of an account before a lost key for that account may be recovered and provided to the user. Exemplary systems and methods for implementing such proof of control are described in further detail below.
In embodiments, an ETP can be provided using a digital math-based asset, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether and PhenixCoin, to name a few. An ETP may be a special purpose entity, statutory trust, business trust, or other corporate form established under the laws (e.g., of a state of the United States) that continuously issues and/or redeems its shares in exchange for a portfolio of specified assets, such as digital assets, currencies, physical commodities, securities and/or other assets. The ETP may issue equity securities which it may register with the US Securities and Exchange Commission. The ETP may list the equity securities for trading in the secondary market at intraday prices on a stock exchange. Each issued share of an ETP may represent a ratable undivided interest in its underlying portfolio of assets. In embodiments, shares of an ETP may be created only in large blocks or lot sizes, such as creation units. In embodiments, only large market participants may be authorized participants (“APs”) who may obtain creation units in exchange for a deposit of a specified amount of assets into the ETP's portfolio. APs may hold or sell into the secondary market the individual shares comprising the creation units issued.
In embodiments, an AP can be a person or entity who is a registered broker-dealer or other securities market participant such as a bank or other financial institution which is not required to register as a broker-dealer to engage in securities transactions, is a participant in a third-party clearing agency, such as the DTC, has entered into an Authorized Participant Agreement with the trustee and the sponsor, and/or has established an AP custody account. In embodiments, only APs may place orders to create or redeem one or more baskets of trust shares. For example, a basket of shares can be a block of 10,000 shares, 20,000 shares, 30,000 shares, 40,000 shares, 50,000 shares, 75,000 shares, 100,000 shares, and/or some other denomination of shares.
In embodiments, an Authorized Participant Agreement can be an agreement entered into by an AP, the sponsor and/or the trustee which provides the procedures for the creation and redemption of baskets of trust shares and for the delivery of the digital math-based assets, e.g., Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether and PhenixCoin, required for such creations and redemptions.
In embodiments, an AP custody account can be a segregated account for digital math-based assets, e.g., a segregated bitcoin account, owned by an AP and established with the trustee and/or custodian by an Authorized Participant Custody Account Agreement. An AP custody account can be used to facilitate the deposit and withdrawal of digital math-based assets, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether and PhenixCoin, to name a few, by an AP in creation and redemption processes, as discussed herein by way of example with respect to
In embodiments, an Authorized Participant Custody Account Agreement can be the agreement between an AP and the trustee which can establish an AP custody account.
In embodiments, in order to initiate the issuance of shares, an AP may place a creation order with the trustee and/or administrator of the ETP. Upon the trustee's acceptance of the order, the trustee and/or administrator, using the trust computer system, may notify the AP of the exact amount or quantity of portfolio assets that is required to be deposited into the ETP's account in exchange for one or more creation baskets, which are valued at their current net asset value. In embodiments, the trustee and/or administrator may hold the ETP's portfolio assets on behalf of all shareholders. In embodiments, the trustee and/or administrator may be authorized to make transfers from the trust account to third parties only under certain specific circumstances, such as to pay for the ETP's permitted operational expenses or to redeem creation units tendered for redemption by an AP. A redemption of creation units may be the reverse of a creation; the AP may place a redemption order with the trustee. Upon the trustee's and/or administrator's acceptance of the order, the AP may tender to the trustee the stated number of creation units for redemption and in exchange may receive the pro rata amount or quantity of portfolio assets represented by such shares. The trustee and/or administrator may then cancel and/or instruct a third party clearing agency (e.g., DTC) to cancel all shares comprising the creation units so delivered. This continuous issuance and redemption feature of an ETP provides an arbitrage mechanism for APs, who may either create or redeem creation units when the current trading price of the individual shares on the secondary market deviates from the underlying net asset value of such creation units, thereby reducing such deviation between the trading price and the underlying net asset value.
In embodiments, the trust may have an investment objective for shares to reflect the performance of a blended price of digital math-based assets, e.g., a blended bitcoin price of bitcoin, less expenses of the trust's operations. The shares can be designed for investors who want a cost-effective and convenient way to invest in digital math-based assets with minimal credit risk.
In embodiments, the trust can directly hold digital math-based assets, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether and PhenixCoin, using the trust's hardware and/or software security system, which in embodiments may include storage of the trust's digital assets and/or the private keys relating to the digital wallets holding the trust's digital assets in one or more locations in, for example, high security vaults.
In embodiments, the trust may hold any combination assets, including digital math-based assets, physical commodities, securities and/or other assets. A trust agreement may specify and/or limit which assets a particular trust may hold.
As illustrated in
In embodiments, an ETP may involve an underlying trust and one or more of the entities discussed herein.
An initial purchaser 210 may provide seed capital to the trust in exchange for a set number of creation units of the same value. A market maker 205 may undertake to buy or sell creation units in the trust at specified prices at all times.
A custodian 220 can safe keep the trust's assets and can engage one or more sub-custodians to do so in different locations. In embodiments, the one or more sub-custodians may comprise different entities. In embodiments, the one or more sub-custodians may comprise different aspects of the same entity or may be affiliated entities. A custodian 220 may hold copies of segmented private keys in one or more vaults.
An administrator 225 can keep books and records for the trust, conduct other ministerial duties and/or may calculate the trust's daily net asset value, daily share price, and/or other pertinent information about the trust, the trust's assets, and/or the trust shares.
The trustee 215, the custodian 220 and/or the administrator 225 may be the same person or entity, may be different operations of the same person or entity, may be different persons or entities, or may be multiple persons or entities performing the same and/or overlapping functions.
A listing exchange 235 is a venue where shares registered with the SEC may be listed and traded during business days. The listing exchange 225 can track using one or more computers and publish electronically using one or more computers an estimated intraday indicative value (“IIV”) of a trust regularly, e.g., every 15 seconds. A calculation agent 240 using one or more computers may also perform daily calculations of trust assets using methods known in the art and may provide the IIV. The trustee 215 and/or the administrator 225 may also serve as the calculation agent 240 and may be the same person and/or entity, different operations of the same person and/or entity, and/or may be different persons.
A marketing agent 245 may also be engaged to provide services to the trust relating to the public marketing of its shares for sale. The marketing agent 245 may review marketing documents for regulatory compliance, e.g., rules of the Financial Industry Regulatory Authority (“FINRA”) and/or relevant regulatory authority. The marketing agent may file the trust's marketing materials with FINRA and/or relevant regulatory authority.
The processes of clearance and settlement of trust shares may be performed by a clearing agency or a registered third-party entity 250, such as the Depository Trust Company (“DTC”) and/or the National Securities Clearing Corporation (“NSCC”). Shares may be available only in book-entry form, meaning that individual certificates may not be issued for the trust's shares. Instead, shares may be evidenced by one or more global certificates that the trustee may issue to a clearing agency or a registered third-party entity 250, e.g., DTC. The global certificates may evidence all of the trust's shares outstanding at any time. As a result, in embodiments, shares may be only transferable through the book-entry system the third-party clearing agency 250. Shareholders may hold and/or transfer their shares directly through the third-party clearing agency 250, if they are participants in the clearing agency 250, or indirectly through entities that are participants in the clearing agency 250 (e.g., participants in DTC). Transfers may be made in accordance with standard securities industry practice.
An index provider 270 may license its intellectual property to the trust for pricing, portfolio selection, and/or other services, and may, using one or more computers, calculate and/or upkeep the index during the term of the license. In embodiments, for example, an index of digital asset values (such as bitcoin values) or blended digital asset prices (such as blended bitcoin prices) may be used to price the digital assets transferred to and/or from the trust and/or held by the trust. Other forms of valuation of the digital assets (such as bitcoin) can also be used as discussed herein.
Lawyers 255 and accountants 260 may provide services to the sponsor 230 and/or the trust and/or other participants in the trust.
In embodiments, transactions with the trust may be restricted to one or more APs 265. The trust may establish requirements for becoming an AP, e.g., must be an entity of a certain size, financially or otherwise, must be a large market investor, like a broker-dealer and/or a bank, must seek and obtain formal approval from the trustee, must enter into an agreement with the trustee and/or other such requirements known in the art, to name a few. In embodiments, APs may be broker-dealers and/or banks. APs may enter into an AP agreement with the trust and/or the sponsor 230, which may include rules for the issuance and/or redemption of creation units. Depending on the nature of the trust's intended assets, an AP may be required to hold and deliver specific commodities, e.g., a digital math-based asset, directly to the trust.
In embodiments, a trustee 215 may be generally responsible for the day-to-day administration of the trust. A trustee 215 (or its designee, such as the custodian 220 and/or administrator 225) may perform one or more of the following tasks associated with the trust:
As described in greater detail herein with respect to
As described earlier, in the primary market APs 265 may obtain and/or redeem shares in the trust through the creation and redemption redeem processes. APs 265 may then sell shares in a secondary market. APs 265 may also buy shares in the secondary market. In an exemplary secondary market for shares in the trust for a digital math-based asset ETP, e.g., a Bitcoin ETP, a listing stock exchange 235 may be the primary listing venue for individual ETP shares. In embodiments, the listing stock exchange 235 may be required to file listing rules with the SEC if no applicable listing rules already exist. The listing exchange 235 may enter into a listing agreement with the sponsor 230. In embodiments, the listing exchange 235 may appoint the lead market maker and/or other market makers 205. The market makers 205 may facilitate the secondary market trading of shares in the trust underlying the ETP. Market makers 205 may facilitate creations and/or redemptions of creation units through one or more APs. In embodiments, such creations and/or redemptions may be related to market demand, e.g., to satisfy market demand.
Still referring to
Other market liquidity providers 405 may also participate in the secondary market. In embodiments, other market liquidity providers 405 may buy and/or sell one or more shares on a list stock exchange 235. In embodiments, other market liquidity providers 405 may buy and/or sell one or more creation units through one or more APs 265. Other market liquidity providers 405 may include, by way of example, arbitragers, prop traders, “upstairs”, private investors, dark pools, to name a few.
In an exemplary embodiment, the ETP may be based on an ownership stake in a digital asset investors trust, such as a Bitcoin investors trust. A trust may be created as a common law trust or a statutory trust that may elect, grantor trust status. It will be appreciated by those in the art that other forms of trust are possible, including but not limited to master trusts, owner trusts, and revolving asset trusts. Such a trust may register its shares with the SEC under the Securities Act of 1933, as amended, to sell shares to the public. A trust may hold portfolio assets that may require the sponsor or administrator of the trust to register as a commodity pool operator under the Commodity Exchange Act with the U.S. Commodity Futures Trading Commission (“CFTC”).
In embodiments, the trust's assets may be digital math-based assets, such as bitcoin, held in one or more digital wallets maintained by and/or for the trustee 215. Other forms of asset storage and security are discussed herein. In embodiments, the trust assets can include other forms of digital math-based assets, such as other forms of digital assets, digital math-based assets, peer-to-peer electronic cash system, digital currency, synthetic currency, or digital crypto-currency. Exemplary digital assets can include Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin, to name a few. In embodiments, the trust's assets can include additional assets besides digital math-based assets, such as, other commodities, currencies, futures, derivatives, and/or securities, to name a few. In embodiments, the trust's assets may include derivatives of digital assets, such as futures, options, calls and/or puts, based on one or more digital assets, to name a few. In embodiments, the trust's assets may include only one or more types of derivatives of one or more digital assets, without holding directly any digital asset itself.
The trust's assets may be held in various forms of storage using any of the security systems and methods described herein. In embodiments, the trust may employ a hardware and/or software security system to protect the digital math-based assets, such as bitcoin assets. In embodiments, the trustee 215, the administrator 225, the custodian 220, and/or some other entity may perform operations related to creations and redemptions from a secure administrative portal. In embodiments, digital asset accounts and/or digital wallets may be created after a request for a deposit is made, at the time the trust's security measures are set up (e.g., 10,000 wallets created at the outset), at some intermediate point during the life of the trust, or at any other time where digital wallets are deemed necessary or desirous, e.g., to ensure that the amount of assets in any given wallet remains below some threshold.
At set up of a trust, seed baskets and/or initial baskets may be issued to one or more initial purchasers 210 in connection with the formation of the trust.
In embodiments, creations may involve the transfer of assets to the trust, and redemptions may involve the withdrawal of assets from the trust, as discussed herein. In embodiments, the trust may be passive, such as not actively managed, in which case it may be subject to the additions or reductions in the asset inventory caused by creations and/or redemptions. In embodiments, the trust may restrict issuance and/or redemption of shares to creation units. In embodiments, creation units may describe the specific number of shares that may be exchanged for digital assets of the same value. Creation units may be lot sizes of a pre-defined number of shares. In embodiments, creation units may be large lot sizes of shares. For example, in embodiments, a creation unit may be 10,000 shares, 20,000 shares, 30,000 shares, 40,000 shares, 50,000 shares, 75,000 shares, 100,000 shares, and/or some other denomination of shares. In embodiments, the creation unit may be based on some fractional amount of shares. In embodiments, a creation unit may correlate to a creation deposit (for creations) or withdrawal proceeds (for redemptions) that comprise a lot size of assets, securities, to name a few. For example, in embodiments a creation of 50,000 shares may correlate to a creation deposit of 10,000 digital assets (e.g., bitcoin). In embodiments, a creation unit may correlate to a creation, deposit or withdrawal proceeds that comprise a lot size of fractional denominations of assets, e.g., 100 Satoshis, 200 Satoshis, 10,000 Satoshis, or some other denomination of Satoshi.
In embodiments, one or more creation units may be created in a process in which one or more creation deposits is transferred to the trust in exchange for issuance a specified set number of shares in the fund, e.g., 50,000 shares. For a redemption, as described herein, an AP may redeem one or more creation units in exchange for the related withdrawal proceeds and resulting in the cancellation of a corresponding set number of shares. In embodiments, an AP may only transact in whole creation units. Thus, the AP may only deposit assets equal to one or more whole creation units. Similarly, the AP may relinquish shares amounting to one or more whole creation units in order to redeem those creation units. In embodiments, transactions involving fractional amounts of a creation unit may be allowed.
Transactions may occur on a daily basis. In embodiments, transactions may occur multiple times each day. In embodiments, the frequency of transactions may be limited by rule so as to limit the number of transactions, e.g., one transaction per week, three transactions in a given month, to name a few. In embodiments, transactions may be limited by rule to occurring during certain time periods, such as only on a given day of the week (e.g., Mondays) or only on a given day of the month (e.g., the first day of the month), after 3 P.M., to name a few. In embodiments, transactions may be limited to occurring on business days.
The trust may accept only a single commodity, currency or other asset. In embodiments, multiple types of commodities, currencies or assets may be accepted, for example, like a basket currency model. Those in the art will appreciate that the asset may be a commodity, currency and/or other asset which may be physical, digital, or otherwise existing.
In embodiments, only an AP may obtain shares in the trust. Thus, in the primary market for shares only APs can participate. However, in a secondary market, APs may sell or otherwise transfer shares in whatever manner and for whatever consideration they choose. In embodiments, APs may sell shares for cash and/or other remuneration. A shareholder can own beneficial interest in shares in the trust. In embodiments, an AP's ability to transfer shares may be limited by securities laws, FINRA, and/or corporate compliance procedures, to name a few. Shares in a trust may include units of fractional undivided beneficial interest in and ownership of a trust.
Administration of the trust may involve the use of one or more accounts, including one or more custody accounts. In embodiments, referring to
A custody account can be a segregated account operated by the trustee on behalf of another involved with the trust, e.g., sponsor or AP, to name a few. In embodiments, a custody account may be a digital wallet, a digital asset account, and/or a Bitcoin account. In embodiments, a custody account may be created, e.g., by the trustee, for each new transaction, e.g., creation, redemption, payment of sponsor's fee, to name a few. Referring to the exemplary embodiment illustrated in
In embodiments, trust expense account 305 may be used by the trustee 215 to pay extraordinary expenses that have not been assumed by the sponsor 230. Indirect payment of such expenses may occur when assets are distributed to the trustee's trust expense account 305. The trustee 215 may then sell or otherwise transfer assets from the trust expense account in order to satisfy expenses. A sponsor custody account 310 may be used to accept payments by the trust of a sponsor's fee. In embodiments, payments may be made in digital math-based assets, such as bitcoin. Payment of the sponsor's fee may be a periodic, e.g., monthly, event. One or more AP custody accounts 315-1 . . . 315-N may be owned by one or more APs, 265-1 . . . 265-N. AP custody account 315 may be used to receive deposits of assets from an AP for use in a creation, as detailed in
It should be appreciated by those of skill in the art that each of these accounts may be made up of one or more accounts, and/or one or more digital wallets.
The trustee and/or administrator and/or custodian may use one or more trust computers in performance of the processes and/or tasks described herein. A trust computer system may be located at an administrative portal. As illustrated in
Still referring to
In embodiments, the trust for the ETP can create and/or redeem shares from time to time. In some embodiments, the creation and/or redemption must be in whole baskets, e.g., a block of a fixed number of shares, e.g., 50,000 shares. The creation and/or redemption of baskets can require, respectively, the delivery to the Trust or the distribution from the Trust of the number of bitcoin represented by the baskets being created and/or redeemed, the amount of which can be based on the combined NAV of the underlying assets relating to the number of shares included in the baskets being created and/or redeemed. In embodiments, an initial number of bitcoin required for deposit with the Trust to create Shares can be a fixed amount per basket. In embodiments, the number of bitcoin required to create a basket or to be delivered upon the redemption of a basket may change over time, due to, e.g., the accrual of trust's expenses, the transfer of the trust's bitcoin to pay sponsor's fee and/or the transfer of the trust's bitcoin to pay any trust expenses not assumed by the Sponsor, to name a few.
In embodiments, the number of whole and fractional bitcoin in the deposit required for a basket (“Creation Basket Deposit”) may be determined by dividing the number of bitcoin held by the trust by the number of baskets outstanding, as adjusted for the number of whole and fractional bitcoin constituting estimated accrued but unpaid fees and expenses of the trust. Fractions of a bitcoin smaller than a Satoshi (i.e., 0.00000001 of a bitcoin) which are included in the Creation Basket Deposit amount are disregarded in the foregoing calculation. All questions as to the composition of a Creation Basket Deposit will be conclusively determined by the Trustee. The Trustee's determination of the Creation Basket Deposit shall be final and binding on all persons interested in the Trust.
In embodiments, baskets may be created and/or redeemed only by APs, such as APs who pay a transaction fee for each order to create and/or redeem Baskets and/or have the right to sell the shares included in the Baskets they create to other investors. In embodiments, the Trust may or may not issue fractional baskets.
In embodiments, a method for purchasing shares of a trust associated with an exchange traded product holding digital math-based assets may comprise receiving, at a trust computer system from an AP computer system, a request from an AP to purchase shares in the trust; providing or creating, at the trust computers system, one or more digital wallets associated with a trust custody account to hold digital math-based assets, each digital wallet have a respective public key and a respective private key; providing, from the trust computer system to the AP computer system, each respective public key; receiving, at the trust computers systems, into the one or more digital wallets a first amount of digital math-based assets, from one or more digital wallets associated with an AP; sending, from the trust computer system to a digital asset network, an asset notification to provide for the asset transfer recorded on a public transaction ledger of a digital asset network to reflect the transfer of the first amount of digital math-based assets; receiving, at the trust computer system, confirmation from the digital asset network, that the transfer is valid; and sending instructions to a third-party clearing entity to transfer a first amount of shares in the trust to the AP.
In an exemplary embodiment, the fund asset can be a digital asset. In exemplary embodiments, the digital asset can be a bitcoin. To obtain shares in the trust, an AP may convert cash or anything of value to one or more digital assets. This conversion may be performed independently of the ETP or may be performed through an entity or system related to the ETP or may be performed through the ETP. In an exemplary embodiment, the AP obtains digital assets through an exchange. The AP may also have stored digital assets, e.g., an inventory of assets, which it may choose to deposit with the ETP. The AP may then deposit the digital assets with the ETP in exchange for one or more creation units of shares. Deposit of digital assets may occur via a public registry. The transfer of digital assets may occur as a peer-to-peer (“P2P”) transaction, also known in the art as an end-user to end user transaction.
In embodiments, the AP may first place a creation order with the trustee, e.g., by transmitting the creation order to an administrative operations division of the trustee. In embodiments, as described above, shares may only be issued in creation units and/or in exchange for digital assets of pre-defined amounts. For example, one creation unit may consist of 50,000 shares and may be issued by the trustee in correlation with a deposit of the requisite amount of digital assets into the trust's account.
The trustee may accept the AP's creation order, which may begin a settlement period, e.g., a 3-day settlement period, during which the AP may engage in a settlement process. The settlement process may allow an AP time to hedge, with one possible goal being to avoid or limit risk. In embodiments, no-limit risk may be applicable. In embodiments, a goal of the hedging process may be to protect, e.g., from price movements, the AP's position in the digital assets being delivered to the trust.
In embodiments, the trustee, using one or more computers, may establish one or more digital wallets for each creation. In embodiments, the one or more digital wallets may comprise an AP custody account, which may receive assets deposited by an AP. In embodiments, an AP custody account may remain open throughout the process, and new digital wallets within the account may be created as needed and/or desired to fulfill orders and allow transfers. In embodiments, the trust may provide its own digital wallet system, which may include an interface and a programmed back end, or the trust may use an existing system. In embodiments, an AP may identify the public address of the digital wallet from which it will transfer assets to the trust.
At or before the close of the settlement window, the AP may instruct the trustee to transfer the required digital assets from the AP custody account for deposit into the trust. Upon such transfer from the AP to the trust, the AP may have satisfied its obligation. The trust, through a third-party clearing agency 250 (e.g., the DTC), may then issue shares in the required number of creation units to the AP.
In an exemplary embodiment, digital assets may be transferred from the AP to the trust by transferring the assets first from the AP's one or more outside digital wallets to the AP custody account's one or more digital wallets and, second, from the AP custody account's one or more digital wallets to the trust custody account's one or more digital wallets. In embodiments, both the transferor and the transferee's digital wallets may be required to report the transaction(s) to a registry or other system or entity in order for the transaction(s) to complete. In embodiments, there may be a time window within which both wallets must report the transaction(s). In embodiments, a transaction ledger will be updated to reflect the transfer(s).
In a step S124, the trust computer system may receive, from one or more authorized participant user devices of an authorized participant, an electronic request to purchase a third quantity of shares.
In a step S126, the trust computer system may determine a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares.
In a step S128, the trust computer system may be used to obtain one or more destination digital asset account identifiers corresponding to one or more destination digital asset accounts for receipt of digital math-based assets from the authorized participant. In embodiments, the one or more destination digital asset account identifiers may comprise one or more digital asset account addresses and/or public keys.
In a step S130, the one or more destination digital asset account identifiers and an electronic amount indication of the fourth quantity of digital math-based assets may be transmitted from the trust computer system to the one or more authorized participant user devices.
In a step S132, an electronic transfer indication of a transfer of digital math-based assets to the destination digital asset account may be received at the trust computer system. In embodiments, the electronic transfer indication may further comprise an identification of one or more origin digital asset accounts.
In a step S134, the trust computer system may verify, using a decentralized electronic ledger maintained by a plurality of physically remote computer systems, a receipt of the fourth quantity of digital math-based assets in the one or more destination digital asset accounts. In embodiments, step S134 may further comprise the steps of accessing, using the trust computer system, a plurality of updates to the decentralized electronic ledger; analyzing, using the trust computer system, each of the plurality of updates for a first confirmation of the receipt by a node in a network associated with the digital math-based asset; and determining, using the trust computer system, a final confirmation of the receipt after detecting first confirmations of the receipt in a predetermined number of the plurality of updates to the decentralized electronic ledger. In embodiments, the plurality of updates to the decentralized electronic ledger may comprise new blocks added to a bitcoin blockchain.
In a step S136, the trust computer system may be used to issue or cause to be issued the third quantity of shares to the authorized participant.
In embodiments, the process depicted in
In embodiments a system for determining and/or providing a blended digital math-based asset price can comprise one or more processors and one or more computer-readable media operatively connected to the one or more processors and having stored thereon instructions for carrying out the steps of: (i) determining, by a trust computer system including one or more computers, share price information based at least in part upon a first quantity of digital math-based assets held by a trust at a first point in time and a second quantity of shares in the trust at the first point in time; (ii) receiving, at the trust computer system from one or more authorized participant user devices of an authorized participant, an electronic request to purchase a third quantity of shares; (iii) determining, by the trust computer system, a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares; (iv) obtaining, using the trust computer system, one or more destination digital asset account identifiers (e.g., one or more digital asset account addresses, and/or one or more digital asset account public keys, to name a few) corresponding to one or more destination digital asset accounts for receipt of digital math-based assets from the authorized participant; (v) transmitting, from the trust computer system to the one or more authorized participant user devices, the one or more destination digital asset account identifiers and an electronic amount indication of the fourth quantity of digital math-based assets; (vi) receiving, at the trust computer system, an electronic transfer indication of a transfer of digital math-based assets to the destination asset account; (vii) verifying, by the trust computer system using a decentralized electronic ledger maintained by a plurality of physically remote computer systems, a receipt of the fourth quantity of digital math-based assets in the one or more destination digital asset accounts; and (viii) issuing or causing to be issued, using the trust computer system, the third quantity of shares to the authorized participant.
The creation process involves the deposit of digital assets into the trust's accounts. During a creation, assets or other funds may be deposited into one or more trust accounts. In embodiments, a trust may limit the number of assets or amount of funds stored in each of its wallets, e.g., for security reasons to reduce exposure if any one wallet is compromised. In multi-wallet structures, various asset distributions among the wallets are possible, and various distribution methods or waterfalls may be employed.
In embodiments, wallets may be filled in a pre-determined order. In embodiments, wallets may be filled according to one or more desired capacities or account balances, e.g., deposit 10,000 bitcoin in each wallet before proceeding to deposit in the next wallet.
For example, with reference to
In step S220, a fixed number of digital wallets to be stored in one or more vaults can be created in advance of anticipated use. In creating the digital wallets, as described herein e.g., in relation to
In step S222, an AP using an AP computer system can send to the trustee, custodian and/or administrator using a trust computer system, which in turn receives, assets (e.g., digital math assets such as bitcoin) to be deposited into the trust. For example, the trust computer system can send electronically to the AP computer system a public key associated with a trust custody account to receive the digital assets. The AP can then enter the public key into an AP digital wallet on the AP computer system to send the required digital assets (e.g., bitcoin) from the AP account to the trust custody account using the AP's private key and the public key associated with the trust custody account. The trust computer system can then acknowledge (e.g., electronically) receipt of the transferred digital assets in the trust custody account. In embodiments, one or more AP accounts and/or one or more trust custody accounts can be used. The trust custody account can be an AP custody account and/or a vault account, as appropriate, to name a few.
In embodiments, in step S224, after receipt of digital assets deposited into the trust, digital assets deposited by an AP into the trust, can be transferred using the trust computer system to one or more digital wallets associated with an AP trust custody account. In embodiments, the initial transfer of assets may be made directly one or more AP accounts into one or more AP custody accounts.
In step S226, the digital assets in the digital wallets associated with the AP trust custody account may be transferred using the trust computer system in whole or part into one or more of the previously created digital wallets whose private key segments are stored in vaults. In embodiments, the digital assets may be distributed by the trust computer system to trust wallets, such as discussed in the context of
With reference to
In step S240, an AP custodial digital wallet can be created using the trust computer system to receive assets from an AP digital wallet on an AP computer system.
In step S242, an AP using an AP computer system can send to the trustee, custodian and/or administrator using a trust computer system (which in turn receives) assets (e.g., digital math assets such as bitcoin) to be deposited into the trust. For example, the trust computer system can send electronically to the AP computer system a public key associated with a trust custody account to receive the digital assets. The AP can then enter the public key into an AP digital wallet on the AP computer system to send the required digital assets (e.g., bitcoin) from the AP account to the trust custody account using the AP's private key and the public key associated with the trust custody account. The trust computer system can then acknowledge (e.g., electronically) receipt of the transferred digital assets in the trust custody account. In embodiments, one or more AP accounts and/or one or more trust custody accounts can be used. The trust custody account can be an AP custody account and/or a vault account, as appropriate, to name a few.
In step S244, after receipt of digital assets deposited into the trust, digital assets deposited by an AP into the trust, can be transferred using the trust computer system to one or more digital wallets associated with an AP trust custody account. In embodiments, the initial transfer of assets may be made directly one or more AP accounts into one or more AP custody accounts.
In embodiments, the creation distribution methodology/algorithm can depend at least in part upon one or more of the following criteria or parameters:
With reference to
In step S220′, a fixed number of digital wallets to be stored in one or more vaults can be created in advance of anticipated use. In generating the digital wallets, as described herein e.g., in relation to
In step S222′, an exchange user using computer system or user device can send to a deposit address associated with a deposit digital wallet maintained by the exchange, which in turn receives, assets (e.g., digital math assets such as bitcoin) to be deposited with the exchange. For example, the exchange computer system can send electronically to the user device a public key or deposit address associated with an exchange deposit wallet to receive the digital assets. The user can then enter the public key or address into a user digital wallet on the user device to send the digital assets (e.g., bitcoin) to the exchange deposit wallet using a private key associated with the user digital wallet and the address associated with the exchange deposit wallet. The exchange computer system can then acknowledge (e.g., electronically) receipt of the transferred digital assets in the deposit wallet. In embodiments, one or more private keys associated with deposit digital wallets may be stored in cold storage.
In embodiments, in step S224′, the exchange computer system may generate digital asset instructions (e.g., machine-readable instructions comprising at least a destination digital wallet address) for a transfer from the deposit digital wallet to one or more cold storage wallets.
In step S226′, the digital assets in the deposit digital wallets may be transferred using the exchange computer system in whole or part into one or more of the previously created cold storage digital wallets whose private key segments are stored in cold storage. In embodiments, the digital assets may be distributed by the exchange computer system to exchange digital wallets, such as discussed in the context of
With reference to
In step S240′, an exchange deposit digital wallet can be created using the exchange computer system to receive assets from one or more user digital wallets.
In step S242′, digital assets may be received in the deposit digital wallet from one or more origin digital addresses (e.g., corresponding to exchange user digital wallets).
In step S246′, one or more cold storage digital wallets may be created to store digital assets. In embodiments, such cold storage digital wallets may already exist and be stored according to the secure storage systems and methods described herein.
In a step S247′, the exchange computer system may generate digital asset transfer instructions for transfers from the deposit digital wallet. The transfer instructions may be generated based at least in part upon a distribution algorithm. In embodiments, the deposit distribution methodology/algorithm can depend at least in part upon one or more of the following criteria or parameters:
In a step S248′, the digital asset transfer instructions may be executed using the exchange computer system to transfer digital assets from the deposit digital wallet to the one or more cold storage digital wallets.
In embodiments a method for redeeming shares in a trust associated with an exchange traded product holding digital math-based assets may comprise receiving, at a trust computer system from an AP computer system, a redemption order from an AP to redeem a first number of shares in the trust; determining, using the trust computer system, one or more trust wallets to access to satisfy the redemption order; generating, using the trust computer system, instructions to a custodian to retrieve at least one copy of each private key segment corresponding to the one or more trust wallets; sending the instructions to the custodian; reassembling, using the trust computer system, the one or more trust wallets using the at least one copy of each private key segment; transferring, using the trust computer system, from the one or more trust wallets a first number of digital math-based assets to an AP wallet associated with the AP; generating, using the trust computer system, instructions to the third-party clearing agency to cancel the first number of shares in the trust of the AP; and sending the instructions to the third-party clearing agency. In embodiments, the trustee using the trust computer system may approve the redemption order and/or send confirmation (e.g., electronically) of the order.
In embodiments, the redemption distribution from the trust may consist of a transfer to the redeeming AP's Authorized Participant Custody Account of the number of the bitcoin held by the trust in the Trust Custody Account evidenced by the shares being redeemed. In embodiments, fractions of a bitcoin included in the redemption distribution smaller than a Satoshi (i.e., 0.00000001 of a bitcoin) may be disregarded. In embodiments, redemption distributions may be subject to the deduction of any applicable tax or other governmental charges that may be due.
In step S202, the trust computer system may receive a request, e.g., a redemption order, from an AP computer system for an AP to redeem shares in the trust. In embodiments, the trustee using the trust computer system may approve the redemption order and/or send confirmation (e.g., electronically) of the order. In embodiments, a settlement process entailing, for example, a 3-day settlement window, may be triggered. Other durations of settlement periods may be used as convenient. In embodiments, the trust computer system may receive from the AP computer system one or more public keys associated with AP wallets and/or AP accounts to which redemption proceeds are designated by the AP to be distributed. For example, public key information may be sent electronically from the AP computer system to the trust computer system using, e.g., a digital wallet, e-mail, text message, a digital asset exchange, electronic communications, to name a few. In embodiments, the trustee may designate one or more existing trust custody wallets and/or create one or more new wallets using the trust computer system to be used as AP custody accounts. In embodiments, the trustee may determine the number of digital assets (e.g., bitcoin) required for the redemption, e.g., by using the trust computer system to multiply the number of shares to be redeemed by the NAV value per share less any transaction fees associated with the redemption. In embodiments, depending upon the timing of the redemption, an ANAV value per share may be used in lieu of the NAV value per share. The trust may request and/or receive, e.g., through the third-party clearing agency 250 (e.g., the DTC), shares to be redeemed.
In step S204, the trust computer system may determine one or more wallets to access to satisfy the redemption. The determination as to how many and which wallets should be used to redeem assets may be based at least in part on one or more of the parameters discussed herein (see, e.g., Redemption Distribution Waterfalls Among Wallets).
In step S206, the trustee may instruct the custodian to retrieve from one or more vaults a copy of each private key segment comprising one or more private keys corresponding to the digital wallets that will be accessed to satisfy the redemption. In embodiments, special security measures may be implemented to limit the risk of one or more key segments being lost, damaged and/or stolen in transport. For example, bonded armored cars can be used to transport key segments. The timing of key segment retrieval and transport may be spaced so that only one segment is transported at a time. The timing and/or route of retrieval may also be randomized and/or varied to avoid predictability of transport of key segments from the vault to the administrative portal.
In step S208, the trustee, administrator and/or custodian using the trust computer system may use the retrieved private key segments to reassemble the private keys. In embodiments, this may be performed by decrypting the private key segments and reassembling the segments into a complete private key. In embodiments, the retrieved private key segments may be scanned using key reader 40, and decrypted (as necessary) using decryption software on the isolated computer 30 as part of the trust computer system, and combined and associated with the corresponding public key to regenerate a trust wallet.
In embodiments, as described in a step S208′ in
In step S210, the trust computer system may identify and/or correlate the one or more private keys with the associated public keys to create one or more digital wallets to access the digital assets. In embodiments, preassembled wallets may be generated on one or more isolated transaction computers 32 to hold public key and private key information and transfer instructions awaiting closing. In embodiments, the use of preassembled wallets may expedite the wallet generation process associated with digital math based assets. In embodiments, the trust computer system may include one or more digital asset miners (e.g., bitcoin miners) to allow for prompt transfer of ledger information to reassembled digital wallets. In embodiments, digital math-based assets earned by the digital asset miners may be added to the trust and/or paid to the administrator and/or sponsor as a fee.
In step S212, the trust computer system may reassemble, regenerate, or otherwise access the one or more trust custody account digital wallets (which may, in embodiments, be vault wallets) using the private and/or public keys. The trust computer system may transfer, from the one or more vault wallets to one or more digital wallets in the AP custody account, the assets being redeemed, and then transfer such assets being redeemed to the AP's one or more outside digital wallets. In embodiments, the AP wallet may be an AP custodial wallet. In embodiments, the trust computer system may delete or destroy one or more wallets involved in the transaction, e.g., the AP custody wallet and/or any vault wallets that were emptied, to name a few.
In step S214, the trustee may cancel and/or instruct to cancel, e.g., using the third-party clearing agency 250 (e.g., DTC), the AP's shares corresponding to the number of assets withdrawn and delivered to the AP.
In embodiments, in step S216, the AP may convert the assets to some other asset or currency or use them to conduct one or more transactions.
In embodiments, security measures, such as described with respect to
In a step S2022, a trust computer system comprising one or more computers may determine share price information based at least in part upon a first quantity of digital math-based assets held by a trust at a first point in time and a second quantity of shares in the trust at the first point in time. In embodiments, the share price information may be transmitted to one or more authorized participant user devices. The share price information can comprise a net asset value per share, an adjusted net asset value per share, and/or a net asset value per a basket of shares (e.g., where the number of shares comprising the basket of shares may be associated with one creation unit of shares), to name a few. In embodiments, the basket of shares can comprise any of 5,000 shares, 10,000 shares, 15,000 shares, 25,000 shares, 50,000 shares, or 100,000 shares, to name a few.
In a step S2024, the trust computer system may receive from one or more authorized participant user devices of an authorized participant, an electronic request (e.g., a redemption order) to redeem a third quantity of shares.
In a step S2026, the trust computer system may determine a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares. Determining the fourth quantity of digital assets can comprise obtaining a net asset value per share; determining a digital math-based asset value of the third quantity of shares based upon the net asset value per share; determining transaction fees (e.g., denominated in a unit of the digital math-based asset) and/or expenses associated with the electronic request to redeem shares; and determining the fourth quantity of digital math-based assets by subtracting the transaction fees from the digital math-based asset value of the third quantity of shares.
In a step S2028, the trust computer system may obtain one or more destination digital asset account identifiers corresponding to one or more destination digital asset accounts for receipt by the authorized participant of a transfer of the fourth quantity of digital math-based assets from the trust. The destination digital asset accounts may correspond to an authorized participant custody account.
In a step S2030, the trust computer system may obtain one or more origin digital asset account identifiers corresponding to one or more origin digital asset accounts for the transfer. In embodiments, the origin digital asset accounts may be securely stored accounts, as described herein. The origin digital asset accounts may correspond to a trust custody account.
In a step S2032, the trust computer system may initiate the transfer of the fourth quantity of digital math-based assets from the one or more origin digital asset accounts to the one or more destination digital asset accounts. Initiating a transfer of assets from the trust can comprise retrieving or causing to be retrieved (e.g., issuing retrieval instructions) one or more private keys associated with the one or more origin digital asset accounts, and accessing the one or more origin digital asset accounts using at least the one or more private keys.
Retrieving keys can comprise issuing retrieval instructions for retrieving a plurality of encrypted private keys corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private keys; and obtaining, using the trust computer system, one or more private keys by decrypting the plurality of private keys.
In other embodiments, retrieving keys can comprise issuing, using the trust computer system, retrieval instructions for retrieving a plurality of private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of private key segments; and obtaining, using the trust computer system, one or more private keys by assembling the plurality of private keys.
In still other embodiments, retrieving keys can comprise issuing, using the trust computer system, retrieval instructions for retrieving a plurality of encrypted private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private key segments; and obtaining, using the trust computer system, one or more private keys by decrypting the plurality of private key segments and assembling the segments into one or more private keys.
For a multi-signature digital asset account, retrieving keys can comprise issuing, using the trust computer system, retrieval instructions for retrieving a plurality of encrypted private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private key segments; obtaining, using the trust computer system, one or more first private keys by decrypting the plurality of private key segments and assembling the segments into one or more first private keys; and obtaining, using the trust computer system, at least one second private key corresponding to the one or more origin digital asset accounts.
In a step S2034, the trust computer system may broadcast the transfer to a decentralized electronic ledger maintained by a plurality of physically remote computer systems.
In a step S2036, the trust computer system may verify, using the decentralized electronic ledger, a receipt of the fourth quantity of digital math-based assets at the one or more destination digital asset accounts. Transaction verification can comprise accessing, using the trust computer system, a plurality of updates to the decentralized electronic ledger (e.g., new blocks added to a bitcoin blockchain); analyzing, using the trust computer system, each of the plurality of updates for a first confirmation of the receipt by a node in a network associated with the digital math-based asset; and determining, using the trust computer system, a final confirmation of the receipt after detecting first confirmations of the receipt in a predetermined number of the plurality of updates to the decentralized electronic ledger.
In a step S2038, the trust computer system may cancel or cause to be canceled (e.g., by issuing instructions to a third-party clearing agency) the third quantity of shares from the authorized participant.
In embodiments, the process can include determination of and/or institution of a settlement period associated with the electronic request to redeem shares.
In embodiments, the trust computer system may be operated by a trustee and/or an administrator of the trust.
In embodiments a system for determining and/or providing a blended digital math-based asset price can comprise one or more processors and one or more computer-readable media operatively connected to the one or more processors and having stored thereon instructions for carrying out the steps of (i) determining, by a trust computer system comprising one or more computers, share price information based at least in part upon a first quantity of digital math-based assets held by a trust at a first point in time and a second quantity of shares in the trust at the first point in time; (ii) receiving, at the trust computer system from the one or more authorized participant user devices of the authorized participant, an electronic request to redeem a third quantity of shares; (iii) determining, by the trust computer system, a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares; (iv) obtaining, by the trust computer system, one or more destination digital asset account identifiers corresponding to one or more destination digital asset accounts for receipt by the authorized participant of a transfer of the fourth quantity of digital math-based assets from the trust; (v) obtaining, using the trust computer system, one or more origin digital asset account identifiers corresponding to one or more origin digital asset accounts for the transfer; (vi) initiating, using the trust computer system, the transfer of the fourth quantity of digital math-based assets from the one or more origin digital asset accounts to the one or more destination digital asset accounts; (vii) broadcasting, using the trust computer system, the transfer to a decentralized electronic ledger maintained by a plurality of physically remote computer systems; (viii) verifying, by the trust computer system using the decentralized electronic ledger, a receipt of the fourth quantity of digital math-based assets at the one or more destination digital asset accounts; and (ix) canceling or causing to be canceled, using the trust computer system, the third quantity of shares from the authorized participant.
In embodiments, a redemption distribution waterfall may be implemented using one or more computers based at least in part on one or more parameters. Retrieval distributions may be dictate the order in which digital wallets (and/or their associated private and/or public keys) are retrieved from storage (e.g., from varying levels of cold storage, such as an on-premises safe, nearby safety deposit box, and/or geographically remote bank or secure storage facility). Retrieval distributions may also dictate quantities of digital assets to transfer from each wallet. In embodiments, redemption distribution algorithms may control such retrievals, e.g., by generating retrieval instructions, indicating one or more wallets to retrieve, and/or indicating one or more amounts to transfer from each identified wallet. In embodiments, such parameters may include at least one or more of the following:
It has been a widespread problem with custodial accounts for digital assets that the digital assets purportedly being held are in fact not present. Such digital custodial accounts present a series of technical issues associated with not only securely holding digital assets in a custodial nature, but also proving control over such digital assets, while minimizing security risks and depleting digital assets. Previous attempts to prove control have required that a transaction involving the custodial account be exercised, which when a transaction fee is charged reduces the overall assets within the custodial account. The transaction fee poses a problem in this case because the fees are conventionally paid from the digital wallets held in the administrative account, so that providing many proofs of control over time may ultimately lead to depletion of the digital assets held in the digital wallets.
Exemplary embodiments of the present invention address the technical challenge by providing proof of control from a custodial digital asset account, with payment of the transaction fee associated with the proof of control event from a separate operating account. Embodiments of proof of control systems can be applied to a wide variety of implementations associated with digital asset wallets, such as custodial wallets for exchange traded products, hedges funds, trusts, and other fiduciaries, or non-custodial wallets. The proof of control itself may be in the form of a message sent along with a zero net transfer of digital assets from the administrative account. The message may relate to a recent event, such as an event that occurred within a very recent time period (e.g., the previous 10 minutes, previous hour, previous 12 hours, previous 24 hours, previous day, previous week, previous month, to name a few). As noted above the message may be or include the additional information that is included in the logs displayed in
Referring to
In Step S5302, an administrative portal of a trust computer system is requested to initiate an proof of control event. The trust computer system may be operatively connected to a decentralized digital asset network that uses a decentralized electronic ledger in the form of a blockchain maintained by a plurality of physically remote computer systems to track at least one of asset ownership or transactions in a digital math based asset system. Examples of a blockchain include Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin. The request to initiate may come from, for example, an auditor and may include a statement of a recent event to use in the proof of control exercise.
In Step S5304, the trust computer system generates script instructions to carry out a transaction involving one or more digital wallets held in a digital asset trust custody account so as to verify control of digital assets held in the one or more digital wallets. Step S5304, may be performed though the following substeps. In Substep S5304-02, a statement is selected which is associated with an event that occurred within a predetermined time frame. For example, the message may relate to a recent event, such as an event that occurred within a very recent time period (e.g., the previous 10 minutes, previous hour, previous 12 hours, previous 24 hours, previous day, previous week, previous month, to name a few). For example, the message may be a recent newspaper headline, blog post title, price at a given date and time from an exchange, like the Gemini Auction price on a given date, to name a few. When a statement is provided as part of Step S5302, then the provided statement would be used.
Depending upon the length of the statement, various alternative processes may be employed. By way of example, for a short enough statement (e.g., less than 80 characters), the statement may be maintained in its original form. For example, “GeminiAuction02/08/18=8190.73”. For a larger statement, like a “Express News Report on Feb. 8, 2018: Bitcoin price SURGE: Why is BTC bouncing back today? Cryptocurrency market rising, available at https://www.express.co.uk/finance/city/916246/bitcoin-price-news-why-BTC-bouncing-back-rising-today-cryptocurrency”, a secure shortened version of the statement can be generated. For example, a cryptographic has of the statement can be applied.
In embodiments, where the length of the statement is not predetermined, the trust computer system can perform the following additional substeps as part of the Step S5304 process, including: Sub Step S5304-04, the trust computer system may determine whether the statement fits within memo field length constraints of the script associated with the digital asset type. For example, Bitcoin uses “OP RETURN outputs” as its mechanism for a memo field, which is limited to 80 bytes, and Ethereum uses Log Events on a pay-per-use basis. In SubStep S5304-06, if the determining SubStep S5304-04 indicates that the statement fits within the memo field length constraints, the trust computer system may maintain the statement in its original form. In SubStep S5304-08, if the determining SubStep S5304-04 indicates that the statement does not fit within the memo field length constraints, the trust system may generates a cryptographic hash of the statement to be used as a statement.
Next, in Step S5306, the trust computers system may generate, based on the script instructions, a transaction with the following parameters: (i) a first input of a first amount of digital assets to a digital asset account associated with the trust custody account as accessed through the decentralized digital asset network using a trust custody account digital asset account identifier; (ii) a first output of a second amount of digital assets from the digital asset account associated with the trust custody account as accessed through the decentralized digital asset network using the trust custody account digital asset account identifier, the first amount of digital assets being equal to the second amount of digital assets; (iii) a second input of a third amount of digital assets to a digital asset account associated with an operating account as accessed through the decentralized digital asset network using an operating account digital asset account identifier; (iv) a second output of a fourth amount of digital assets from the digital asset account associated with the operating account as accessed through the decentralized digital asset network using the operating account digital asset account identifier, the fourth amount of digital assets being reduced relative to the third amount by a transaction fee amount; (v) a third output that comprises the statement in a memo field; and (vi) applying a digital signature to the transaction using a private key associated with the trust custody account. At step S5308, the trust system will perform the transaction.
In embodiments, insurance may be provided for digital assets. Such insurance may be provided to individual users of digital assets (including vendors), groups of users, exchanges, exchange agents, trusts providing exchange traded products associated with digital assets, to name a few. Insurance may be provided for a digital asset wallet and/or the contents of a digital asset wallet (e.g., insurance for 100 Bitcoin stored in a digital wallet). Such insurance may involve secure storage of the private key to a wallet and/or the public key. In embodiments, the blended digital math-based asset price as discussed herein may be used as a benchmark for such insurance.
In embodiments, a digital asset kiosk, such as a digital math-based asset kiosk, may be used to perform one or more transactions associated with digital assets. The transactions may require an appropriate money transmit business in order to meet regulatory requirements. In embodiments, a person or entity must use a money transmit business registered in the person or entity's domicile.
In embodiments, an ETP may use a blended digital math-based asset price as a benchmark. Accordingly, a net asset value (“NAV”) of shares in a trust for an exchange traded product holding digital math-based assets may be calculated based in part upon a blended digital math-based asset price or a digital asset index, which may in turn comprise a plurality of blended digital math-based asset prices. A NAV may be determined by obtaining, using one or more computers from one or more exchange computers, a value of digital math-based assets held by the trust at a defined time; calculating or obtaining, using the one or more computers, a blended digital asset value of the digital math-based assets during the predefined period of time; calculating, using the one or more computers, the value of the digital math-based assets held by the trust at a defined time by multiplying the units of each digital math-based asset held by the trust by the price per unit of each such digital math-based asset; determining or obtaining, using the one or more computers, estimated accrued but unpaid expenses, including sponsor fees, incurred by the trust since the last payment of a sponsor fee up to, but not included, the date on which the valuation is made; calculating, using the one or more computers, the adjusted net asset value of the trust by subtracting the estimated accrued but unpaid fees and expenses since the last payment of a sponsor fee up to, and included, the last valuation date of the digital math-based assets held by the trust on such date; determining or obtaining, using the one or more computers, estimated unpaid fees and expenses incurred by the trust since the last valuation date; calculating, using the one or more computers, net asset value of the trust by subtracting estimated accrued but unpaid fees and expenses incurred since the last valuation date form the adjusted net asset value of the trust; calculating, using the one or more computers, net asset value per share of the trust by dividing the net asset value of the trust by a number of outstanding shares of the trust; storing in one or more databases on computer readable media operatively connected to the one or more computers the accrued but unpaid fees and expenses, adjusted net asset value, net asset value and the net asset value per share of the trust; and publishing, from the one or more computers to one or more publication systems, the net asset value and the net asset value per share of the trust. In embodiments a time period of 12 hours, 24 hours, or 36 hours may be used.
In embodiments, NAV of a trust or its equivalent can be calculated by a computer system comprising one or more computer. For example, in embodiments, a NAV can be calculated using one or more computers on a daily basis (for each evaluation day, e.g., a day on which the trust shares are available to be created, redeemed and/or exchanged). In embodiments, a NAV can use one or more formulas to estimate a fair market value of a unit of a digital asset and/or a share in a trust at a given point in time. In embodiments, an industry standard formula can be used to calculate a NAV. In embodiments, a proprietary formula can be used to calculate a NAV. For example, one or more computers may calculate a digital asset price using data from the largest exchanges in the digital asset exchange market. In embodiments, a blended digital asset price can be calculated by one or more computers using an averaged price.
In embodiments, a blended digital asset price can be the price for digital assets determined each valuation day at a set time, such as, e.g., 3:00 p.m. Eastern Time. In embodiments, a blended digital math-based asset price may be obtained from a blended digital math-based asset index, which may be accessed via an API. In general, an API is a set of routines or subroutines, protocols and tools for building software applications, which facilitate communications between various software components. An API may be for a web-based system, operating system, database system, computer hardware or software library. An API specification can take many forms, but often includes specifications for routines, data structures, object classes, variables or remote calls. POSIX, Windows API and ASPI are examples of different forms of APIs. Documentation for the API is usually provided to facilitate usage. An example of such an order placing API is available with the Gemini Exchange, as discussed at https://docs.gemini.com/rest-api/#new-order. In embodiments, the system may calculate a blended digital asset price, by obtaining transaction data from one or more exchanges selected from a list of exchanges approved by, e.g., the sponsor, to determine either the average of the high and low prices on each exchange or the weighted (based on volume of shares traded) average of the transaction prices for the prior fixed time period (e.g., 12 or 24 hours) of trading activity on such one or more exchanges. In embodiments, the system may then average the price for each exchange, using weighting based on each exchange's volume during the period. Other methodologies can be used by the system to calculated the blended digital asset prices. For example, three exchanges, four exchanges, five exchanges, ten exchanges, or any number of exchanges as may be appropriate in view of the market for the math-based assets may be selected to determine the blended digital asset price. In embodiments, a time period of other than 12 or 24 hours may also be used depending upon the volume and volatility of the math-based asset price. For example, in a low volume period the time period may be increased to, e.g., 36 hours, while in a high volatility period the time period may be decreased to, e.g., 4 hours. In embodiments, a blended digital math-based asset price may be calculated by computing a volume weighted exponential moving average of actual transactions (e.g., considering price and volume of each executed transaction) from one or more digital asset exchange. In embodiments, the moving average may be taken over a period such as 2 hours. In embodiments, other periods may be used, such as 24 hours, 1 hour, 30 minutes, and/or 15 minutes, to name a few.
The NAV and NAV per Share can be published daily after its calculation using one or more computers. A third party agent can be employed to perform the calculation and to electronically publish it. In embodiments, the following process can be used:
Step 1: Valuation of Digital Assets
In embodiments, a NAV and NAV per Share, can be struck using one or more computers each evaluation day (e.g., each day other than a Saturday or Sunday or any day on which the listing exchange 235 is not open for regular trading).
The NAV and NAV per Share striking can occur at or as soon as reasonably practicable after a predetermined time of day (e.g., 4:00 p.m. Eastern time) each evaluation day and can be conducted by the trustee.
The first step for striking the NAV may be the valuation of the digital assets held by the Trust. In embodiments, the calculation methodology for valuing the Trust's digital assets can be as follows:
Value of digital assets=(#of digital assets held by trust)×(blended digital asset price)
If the blended digital asset price is unavailable on any given day, the sponsor can instruct the use of the prior day's blended digital asset price or, if the prior day's blended digital asset Price is deemed unfair/unsuitable, such other price as it deems fair.
Step 2: Calculation of ANAV
Once the value of the digital assets in the trust has been determined on an evaluation day, the trustee, using one or more computers, can subtract all estimated accrued but unpaid fees (other than the fees accruing for such day on which the valuation takes place computed by reference to the value of the Trust or its assets), expenses and other liabilities of the trust from such NAV of the trust. The resulting figure is the adjusted net asset value (“ANAV”) of the trust. The ANAV can be used to calculate fees of trustee and/or sponsor.
In embodiments, the ANAV can calculated using the following methodology:
ANAV=(value of digital assets)−(estimated accrued but unpaid fees/expenses/liabilities)
Step 3: Calculation of Daily Expense
Once the NAV has been determined, any fees or expenses that accrued since the last striking of the NAV can be calculated using one or more computers based on the evaluation day ANAV.
All fees accruing for the day (and each day since the last evaluation day) on which the valuation takes place computed by reference to the value of the trust or its assets can be calculated by one or more computers using the ANAV calculated for such evaluation day.
In embodiments, in arrears using the average of the daily ANAV for the prior month, the daily expense fee (for each day since prior evaluation day) can be estimated on a daily basis using the following methodology:
Daily Expense*=(Sponsor's Fee)+(other fees)+(other expenses or liabilities accruing since the prior Evaluation Day)
Step 4: Calculation of NAV and NAV Per Share
In embodiments, the trustee can calculate using one or more computers the NAV, by subtracting from the ANAV the Daily Expense.
In embodiments, the trustee can also calculate using one or more computers the NAV per share by dividing the NAV of the trust by the number of the shares outstanding as of the close of trading. In embodiments, the number of shares outstanding as of the close of trading may be obtained from the NYSE Arca (which includes the net number of any Shares created or redeemed on such evaluation day).
Calculation methodology:
NAV=ANAV−(Daily Expense)
NAV per Share=NAV÷(#of Shares outstanding)
The Blended Digital Asset Price
A blended digital asset price, such as a blended digital math-based asset price, can be calculated, using one or more computers, each evaluation day. Systems and methods for calculating a blended digital asset price are described in U.S. application Ser. No. 14/313,873, filed Jun. 24, 2014, the contents of which are incorporated herein by reference.
The calculation can occur as of and at or as soon as reasonably practicable after 3:00 p.m. Eastern time each evaluation day (time could also be noon, 1 p.m., 2 p.m.—simply needs to be sufficient time before NAV striking to complete the calculations).
The blended digital asset price can be the functional equivalent of a rules-based index and therefore has rules to populate the universe of data inputs and rules on calculation using such inputs. As discussed herein, the blended digital asset price can be used to create an index, to be electronically published. The index can, in turn, also serve as a price benchmark or can be used to create derivative products. Accordingly, in embodiments, a blended digital math-based asset index may be a benchmark for a derivative product, an exchange traded derivative product, a fund, a company, an exchange traded fund, a note, an exchange traded note, a security, a debt instrument, a convertible security, an instrument comprising a basket of assets including one or more digital math-based assets, and/or an over-the-counter product, to name a few.
In embodiments, a blended digital asset price may be obtained from a digital asset index. For example, one or more computers may access (e.g., via an API) one or more blended digital math-based asset values from a computer or database of underlying digital asset index values. In embodiments, digital asset index values may be interpolated to determine a value at a requested point in time, e.g., 4 p.m. E.T.
Eligible Data Inputs for a Blended Digital Asset Price
In embodiments, data for the blended digital asset price can be drawn from the largest exchanges that publicly publish transaction data and principally utilize acceptable currencies, e.g., currencies other than the Chinese Yuan. In this example, the Yuan denominated exchanges may not be included because of manipulation of that currency and unreliability thereof. In embodiments, additional currency denominations may be added or excluded at one or more future dates, which may be dates following the initial formation of the trust.
The sponsor can approve each eligible exchange (which, in embodiments, can be no fewer than three to five exchanges at any given time).
Selection of Data Inputs for a Blended Digital Asset Price
The rules for the blended digital asset price can provide for the use in calculation of the data from the three largest exchanges (by volume) on the sponsor approved list.
In embodiments, this determination of the three exchanges for use can be done on a weekly basis, (e.g., on each Monday) based at least in part on the volume on each such exchange during the prior week. In embodiments, this determination could be done on a different periodic basis (e.g., on a daily basis or a monthly basis) or on a when needed basis (e.g., whenever some circumstances occurs requiring a change of determination).
In embodiments, so long as exchange selection is not on a daily basis, to the extent an exchange that has been selected for inclusion experiences a halt in trading for more than 24 consecutive hours (e.g., a lack of any recorded transactions during the prior 24 hours, regardless of the reason), that exchange can be replaced by the next largest exchange (by volume) on the sponsor approved list. In embodiments, this determination can be made automatically by one or more computers as part of an algorithm.
In embodiments, in the instance of a replacement, the restoration of daily volume on the halted exchange to a level more than the daily volume on the exchange that substituted for it could trigger a reversal of the substitution, if such restoration occurred prior to the next scheduled reconstitution of the included exchanges.
In embodiments, an exchange may be removed where there is a significant drop in trading on that exchange (e.g., 90% drop in trading volume) during a relevant time period (e.g., prior 24 hours, prior week, prior month, to name a few).
In a step S2402, one or more computers may obtain exchange transaction data for an exchange, where the data covers at least one tracking period. The exchange data may be received via electronic transmission (e.g., over the Internet) and/or electronically accessed (e.g., using one or more APIs). The tracking period may be any period of time over which the exchange will be assessed for approval for use in the calculation of a blended digital asset price, such as 15 minutes, 1 hour, 12 hours, 24 hours, and/or 1 week, to name a few.
In a step S2404, the one or more computers may determine whether a volume traded on the exchange during the tracking period satisfies a threshold volume. In embodiments, a threshold volume may be 500 units of digital assets. In embodiments, a threshold volume may be expressed as a percent (e.g., a percent of the digital assets in circulation). The threshold may be modified periodically to help increase or decrease the number of qualified exchanges.
In a step S2406, the one or more computers may determine whether the exchange transacts in an approved currency. The computers may either test for an approved currency (e.g., by comparing to a database of approved currencies) or for an unapproved currency (e.g., by comparing to a database of unapproved currencies). In embodiments, only one currency may be approved, and the test for that currency may be hard-coded in exchange approval software. Currencies may be approved or unapproved based on considerations of reliability and/or stability, to name a few.
In a step S2408, the one or more computers may determine whether qualified transaction data is available for the exchange for a threshold aggregate period of time. Qualified transaction data may be data from a reference period during which a threshold number of transactions occurred (e.g., at least 3 transactions) and/or a maximum volatility threshold was not exceeded (e.g., the high and low price during the reference period did not fluctuate by more than 50% compared to the respective average high and low prices during that reference period of the other top (e.g., top 4) potential qualified exchanges by volume). In embodiments, transaction data may be evaluated from a plurality of reference periods to determine whether the data satisfies qualification criteria. In embodiments, transaction data to be qualified must satisfy qualification criteria for at least a specified period of time, which may be sub-divided into reference periods. For example, qualified transaction data may be determined for reference periods of 15 minutes, and to be a qualified exchange, the exchange must have qualified transaction data for an aggregate of at least 10 hours (40 reference periods) over a 24-hour tracking period. In embodiments, if an exchange satisfies each of the criteria examined in this exemplary process, it may be considered a qualified exchange for the tracking period over which it was examined. The determination of qualified exchanges may be performed at the end of each tracking period or on a rolling basis (e.g., re-evaluated at the end of each reference period).
Description of Electronic Data Pulled from Inputs
For each exchange on the approved list, the prior 24 hours of data setting forth each trade on the exchange by execution price and quantity transacted can be obtained, e.g., received and/or retrieved. Such transaction data may be obtained In embodiments, one or more digital asset prices, such as, e.g., auction price, closing price, traded value, bid price, ask price, and/or spot price, to name a few, may be obtained. In embodiments, only the highest and lowest exchange prices and their respective transaction volumes may be obtained. In embodiments, all exchange price and transaction data may be obtained. In embodiments, a shorter period of time than 24 hours may be used, e.g., 12 hours, 3 hours, to name a few, or a longer period of time such as 48 hours may be used, to insure a sufficient volume of transaction data is considered.
Application of Electronic Data
For each of the exchanges included in the calculation for any given evaluation day, an average price for such date can be used. In embodiments, using each average exchange price for such date, a blended and weighted average price for all exchanges can be extracted and used as the blended digital asset price.
In embodiments, the auction price and/or the blended price may be used as a benchmark for various financial products. As used herein, the term financial products includes, but is not limited to exchange traded notes, futures products (such as options), derivative products (such a puts and calls), other indices (such as volatility indices), swaps, currencies, fixed income products, bonds, securities and equities to name a few.
In embodiments, a blended digital asset price may be calculated by first calculating each selected exchange's daily average and then blending (e.g., averaging) the averages into a blended digital asset price. The daily average may be a time-weighted (e.g., exponential) moving mean and/or volume weighted mean. In other embodiments, a blended digital asset price may be calculated using the data from the selected exchanges (e.g., the top 3 qualified exchanges) without first determining single exchange averages.
Single Exchange Average
In embodiments, a single exchange averages may be used instead of a blended digital asset price. In other embodiments, single exchange averages may be combined into a blended digital asset price.
In embodiments, the single exchange average may be calculated by one or more computers using the unweighted mean average of the high and low trading prices for such day (the average price of each trade during the day—which could be subject to manipulation through outlier price trades).
In embodiments, the single exchange average may be calculated by one or more computers using the weighted mean average of the high and low trading prices for such day (e.g., the trading price for each share traded that day, rather than for each executed trade regardless of share size).
In embodiments, the single exchange average may be calculated by one or more computers using the median average of the high and low trading prices for such day.
In embodiments, the single exchange average may be calculated by one or more computers using the weighted median average of the high and low trading prices for such day.
In embodiments the single exchange average may be calculated by one or more computers using any of a median, weighted median, average, and/or weighted average (by volume, time, or otherwise), any of which may be taken of high and low trading prices for a time period (e.g., 1 day, 1 hour, 15 minutes, to name a few), of the second highest and second lowest trading prices for a time period, and/or of all trades during a time period. For example, all transaction price data for a time period may be weighted by the volume transacted at the prices and/or by time (e.g., linearly or exponentially) in order to give greater weight to the more recent price data. Coefficients or other factors may be used to adjust the weighting so as to dampen or exacerbate any price fluctuations. For example, in embodiments, a coefficient for exponential weighting may be 0.69. In other embodiments, such a coefficient may be approximately 0.5, approximately 0.6, approximately 0.7, approximately 0.8, approximately 0.9, to name a few. Accordingly, in embodiments, a coefficient of exponential weighting can fall with a range 0.5-0.9, within a range 0.6-0.8, or within a range 0.7-0.8, to name a few.
In embodiments, as discussed above, digital asset price may be determined via auction conducted either periodically or aperiodically.
Blended Digital Asset Price
In embodiments, the blended digital asset price can be calculated by the average of the single exchange averages. In embodiments, the average may be weighted by volume. An average may weight different exchanges differently in order to account for differences in ease of access of funds from an exchange and/or ease of transacting on the exchange. As described herein, a blended digital asset price may be calculated as part of providing a generated digital asset index.
In embodiments, a collar may be placed on a single exchange auction price as a benchmark. The collar may be based on a benchmark such as the spot price at a particular time, plus or minus a defined range, such as a percentage of the benchmark price. In embodiments, the collar could be set using percentages such as 1%, 2%, 3%, 5%, 10% of the benchmark price, to name a few. By way of illustration, the collar may be based on a 5% variation from a benchmark of 1 BTC=USD$10,000, such that the collar is between USD$9,500 and USD$10,500. The spot price may be based on the last transaction immediately prior to the auction. A spot price may be based on an average of the most recent bid/ask price for the digital asset. In embodiments, a collar may be set based on a blended digital asset price. For example, a single exchange digital asset price could be determined based on a volume weighted average and/or time weighted average of recent digital asset pricing. In embodiments, a blended digital asset price may be based on a pricing from digital assets taken from a plurality of exchanges. In embodiments, the collar price may be based on a blended digital asset price comprising a plurality of digital asset exchanges (e.g., 4) executing trade data for a fixed period of time (e.g., a 10 minute period) using a volume weighting with a fixed percentage (e.g., 5%) of the highest priced trades and a second fixed percentage (e.g., 5%) of the lowest priced trades removed.
For example, a collar may be placed on the auction price, by using fixed percentage (e.g., 1 percent, 5 percent, 10 percent) of an benchmark against the continuous book price at given time period or set of time period. In embodiments, the benchmark could be a midpoint of the spot price of the continuous book price at the given time period, (e.g., auction price), In embodiments, the benchmark could be a weighted average (such as a time weighted average, volume weighted average, or time and volume weighted average) of the continuous book during a pre-set window (e.g., 10 minutes for before auction, 1 hour before the auction, 12 hours before the auction, 24 hours before the auction, to name a few).
In embodiments, the collar may be a blended digital asset price as discussed elsewhere herein.
In embodiments, if the final auction price falls outside the collar, the auction may fail.
In embodiments, the blended digital asset price may be calculated as illustrated in
Still referring to
Still referring to
In a step S822, one or more computers may access from one or more electronic databases stored on computer-readable memory, electronic digital math-based asset pricing data associated with a first period of time for a digital math-based asset from a plurality of reference digital math-based asset exchanges (e.g., four exchanges). In embodiments, the electronic pricing data can include transaction prices and/or bid and ask prices, to name a few. In embodiments, the one or more computers may access transaction data, including transaction volume data.
In a step S824, the one or more computers may determine a plurality of qualified digital math-based asset exchanges (e.g., three exchanges) from the plurality of reference digital math-based asset exchanges. In embodiments, the plurality of qualified exchanges may be determined by evaluating, by the one or more computers, electronic exchange selection criteria, which may comprise one or more electronic exchange selection rules.
In a step S826, a blended digital math-based asset price for the first period of time may be calculated, using the one or more computers, using a volume weighted average of the electronic digital math-based asset pricing data from the plurality of qualified exchanges for the first period of time.
In a step S828, the one or more computers may store in one or more databases the blended digital math-based asset price for the first period of time. In embodiments, the databases may be remotely located, e.g., in a cloud computing architecture. In embodiments, the databases may store one or more other blended digital math-based asset prices corresponding to one or more other periods of time.
In a step S830, the one or more computers may publish to one or more other computers the blended digital math-based asset price for the first period of time. As described herein, publishing can comprise transmitting the price to one or more computer, transmitting the price to one or more user electronic device (e.g., a mobile phone), providing the price to an electronic display (e.g., a scrolling display), and/or providing the price to a website, to name a few. In embodiments, the price may be published from the database of blended digital math-based asset prices. In other embodiments, the price may be published by the calculating computer directly, e.g., from working memory.
In a step S842, a first plurality of constituent digital math-based asset exchanges may be determined, using the one or more computers, for a first period of time (e.g., a 24-hour period). In embodiments, electronic digital math-based asset pricing data and associated volume data may be obtained, at the one or more computers, for a first tracking period for each of a plurality of reference digital math-based asset exchanges. In embodiments, the total volume of transactions made on the respective exchange during the tracking period may be calculated, by the one or more computers, for each of the plurality of reference digital math-based asset exchanges. In embodiments, a first plurality of constituent digital math-based asset exchanges may be determined, by the one or more computers, by ranking the plurality of reference digital math-based asset exchanges by total volume for the tracking period and selecting a second plurality of the reference digital math-based asset exchanges (e.g., three) according to the largest total volumes, wherein the second plurality is less than the first plurality.
In embodiments, the process for determining the first plurality of constituent digital math-based asset exchanges can further comprise determining, by the one or more computers, for each of the plurality of reference digital math-based asset exchanges whether the total volume of transactions made on the respective exchange during the tracking period satisfies a threshold volume; determining, by the one or more computers, whether the digital math-based asset exchange transacts in an approved currency; and determining, by the one or more computers, for each of the plurality of reference digital math-based asset exchanges whether qualified transaction data is available from the respective digital math-based asset exchange for a threshold aggregate period of time, wherein qualified transaction data is data from a calculation period during which (1) a threshold number of transactions occurred and (2) a maximum volatility threshold was not exceeded, and wherein a calculation period is a subperiod of the tracking period.
In a step S844, electronic digital math-based asset pricing data may be obtained, using the one or more computers, for each of the first plurality of constituent digital math-based asset exchange for a first subperiod of the first period of time (e.g., a 2-hour period within the first period of time). In embodiments, electronic digital math-based asset pricing data (e.g., transaction prices, bid and ask prices, transaction volume data, to name a few) may be obtained, using the one or more computers, for each of the first plurality of constituent digital math-based asset exchange for a second subperiod of the first period of time.
In a step S846, a blended digital math-based asset price may be determined, using the one or more computers, for the first subperiod, by calculating an exponential volume-weighted moving average of the digital math-based asset pricing data for each of the first plurality of constituent digital math-based asset exchange for the first subperiod. In embodiments, a blended digital math-based asset price may be determined, using the one or more computers, for the second subperiod, by calculating an exponential volume-weighted moving average of the digital math-based asset pricing data for each of the first plurality of constituent digital math-based asset exchange for the second subperiod. In embodiments, the exponential moving average utilizes a coefficient between 0.6 and 0.8.
In a step S848, the blended digital math-based asset price may be stored, using the one or more computers, for the first subperiod in a blended price database stored on computer-readable memory operatively connected to the one or more computers. In embodiments, the blended digital math-based asset price may be stored, using the one or more computers, for the second subperiod in the blended price database. In embodiments, the blended price database may comprise at least blended digital math-based asset prices at a specified interval, e.g., prices every 15 seconds, every minute, and/or once per day, such as at a specified time each day, to name a few. Accordingly, prices at the intervals may be interpolated from the blended digital asset prices closest in time.
In a step S850, blended digital math-based asset price for the first subperiod may be published, by the one or more computers. In embodiments, blended digital math-based asset prices may be published, by the one or more computers, for a plurality of consecutive subperiods during the first period of time. In embodiments, the blended digital math-based asset price for the first subperiod or for the plurality of consecutive subperiods may be published from the blended price database. In embodiments, the blended digital math-based asset price may be published to one or more user devices. In embodiments, the blended digital math-based asset price may be electronically published through a dedicated website and/or through one or more electronic access points. The blended digital asset price can be published, using one or more computers, on the trust's website and distributed to APs. The blended digital asset price may form the basis of a digital asset index, as discussed herein. In embodiments, no intraday blended digital asset price may be required to be published throughout the day.
Still referring to step S850, a graphical representation of blended digital math-based asset prices may be generated, by the one or more computers. The graphical representation may include the blended digital math-based asset prices for the plurality of consecutive subperiods during the second period of time. The graphical representation may be provided from the one or more computers to the one or more second computers. In embodiments, the graphical representation includes a graphical representation of the digital math-based asset pricing data for each of the first plurality of constituent digital math-based asset exchanges for the plurality of consecutive subperiods during the second period of time. In embodiments, the graphical representation further includes a second graphical representation of volume data for each of the first plurality of constituent digital math-based asset exchanges for the plurality of consecutive subperiods during the second period of time.
In still other embodiments, an API for accessing the blended digital math-based asset price may be provided, by the one or more computers to one or more third computers. An electronic API request to access a blended digital math-based asset price for a subperiod may be received, by the one or more computers from the one or more third computers, and the blended digital math-based asset price for the first subperiod may be provided by the one or more computers to the one or more third computers.
In embodiments, generating a blended digital asset price and/or a blended digital asset price index can comprise accessing transaction data from a plurality of exchanges, as described herein. Such processes can include data normalization, which can convert data to a consistent and/or uniform format. For example, digital asset price data from one exchange may be provided in units of bitcoin, while price data from another exchange may be provided in units of milli-bitcoin, and data from another exchange may be provided in satoshis. Upon accessing the data from the different exchanges, the data may be converted to a common format, such as milli-bitcoin. In embodiments, time data may also be converted to a common format, e.g., 24-hour time, and/or a common time zone, e.g., GMT.
In an exemplary embodiment, a blended digital asset price may be calculated by blending the trading prices in U.S. dollars for the top three (by volume) qualified exchanges during the previous two-hour period using a volume-weighted exponential moving average. Constituent exchanges of the index can be selected according to rules, such as requiring that the exchanges have electronic trading platforms on which users may buy or sell digital assets with other users in exchange for U.S. dollars. The value of the index (including a daily spot price) can be determined using exchange transaction data on a moving average basis over a trailing two-hour period. The computer code used to generate the index may weight exchange transactions by volume on a proportional basis. In order to reflect the latest in pricing information, the most recent transactions may be weighted exponentially greater than earlier transactions in the two-hour period.
Without meaning to limit the scope of the present invention, the following examples illustrate exemplary embodiments in accordance with the present invention and set forth the basic operation of the trust on a day-to-day basis by reflecting exemplary creations, redemptions, payments of the sponsor's fee, netting of transfers, trustee instructions and actions, and the creation and activation of cold storage digital wallets from the cold storage vault security system.
Each of these examples assume the following facts:
In the exemplary embodiments described in the following examples, the trust operates by rounding only to the nearest Satoshi, which is one hundred-millionth of a bitcoin. As a result, transactions in bitcoin will be reflected to eight decimal places. To assist in the orderly netting and administration of the administrative portal and the cold storage security system, a three business day settlement period is used. The sponsor's fee represents the trust's only expected regular charge. These examples do not include extraordinary expenses, meaning that the sponsor's fee will be the only expense accruing on a daily basis. This will be reflected in the reduction of the bitcoin represented by a creation unit on each of the three days of the example.
In Example 1, the following particular facts are assumed:
AP1 places a creation order for three creation unit. AP2 places a redemption order for one creation unit. No Sponsor's Fee or extraordinary expenses payable on settlement date. The trust composition is: 5,000,000 outstanding Shares, representing 999,370.51327457 bitcoin. bitcoin per creation unit: 9,986.44922498. Amount of bitcoin in only partially-filled cold storage digital wallets (Index Number 02814): 370.51327457.
On day T, AP1 and AP2 place their orders for three creation units and one redemption, respectively. Trustee accepts the creation and redemption orders and confirms such receipt to AP1 and AP2.
On day T+1, trustee calculates expected netting to be 1 creation unit (i.e., 3 creation units created less 1 creation unit redeemed; no expected Sponsor's Fee or extraordinary expense payments). Trustee determines that no paper tokens need to be retrieved for withdrawals or distributions of bitcoin on the settlement date. The trustee determines and identifies 20 cold storage digital wallets from the Index Number-Public Key list for deposit activation for settlement date creations.
On day T+2, AP1 submits a creation wallet address supplement identifying the public key from which AP1 can deposit its creation deposit of 29,959.34767494 bitcoin. Using the administrative portal, trustee generates a wallet for the AP1 custody account and provides such wallet's public key to AP1 to receive the creation deposit. AP2 submits a redemption wallet address supplement identifying the public key to which AP2 can receive its redemption proceeds of 9,986.44922498 bitcoin. Using the administrative portal, trustee generates a wallet for the AP2 custody account and provides such wallet's public key to AP2 as the account distributing bitcoin. AP1 delivers 29,959.34767494 bitcoin to the public key identified for its AP1 custody account. Trustee acknowledges receipt of such creation deposit. AP2 delivers 50,000 shares to the trust through the third-party clearing agency (e.g., DTC) clearance process. Trustee acknowledges receipt of such share tender.
On day T+3 (Settlement Date), for netting purposes and using the administrative portal, trustee generates a wallet for the trust custody account and transfers 9,986.44922498 bitcoin from the AP1 custody account to such wallet in the trust custody account. Using the administrative portal, the trustee transfers 9,986.44922498 bitcoin from a trust custody account to the newly created wallet in the AP2 custody account; transfers such bitcoin from the AP2 custody account to wallet associated with the Public Key identified by AP2 as its outside account; and instructs the third-party clearing agency (e.g., the DTC) to cancel the 50,000 shares tendered by AP2, in settlement of the redemption. Using the administrative portal, trustee transfers 629.48672543 bitcoin from the AP1 custody account to partially-filled cold storage digital wallets (Index Number 02814) in cold storage; transfers 1,000 bitcoin each from AP1 custody account to 19 additional newly-activated cold storage digital wallets in cold storage; transfers 343.41172453 bitcoin from AP1 custody account to the newly activated cold storage digital wallets (Index Number 08649) in cold storage; and instructs the third-party clearing agency (e.g., the DTC) to transfer 150,000 newly issued shares to AP1 and to cancel the 50,000 shares tendered by AP2, in settlement of the creation.
At the end of this process, there is a net gain of 100,000 shares (2 creation units) issued and 19,972.89844996 bitcoin deposited into the trust; 20 cold storage digital wallets activated, no cold storage digital wallets expired. All temporary wallets are discarded after use. Amount of bitcoin in only partially-filled cold storage digital wallets (Index Number 08649): 343.41172453.
Example 2 is treated as the next business day after settlement of Example 1. In Example 2, the following additional particular facts are assumed: AP1 places a creation order for two creation units. AP2 places a redemption order for two creation units. Sponsor's Fee of 837.22012681 bitcoin is due. The trustee can have calculated the sponsor's fee and the sponsor can have confirmed this calculation and provided a Public Key for its outside account prior to Day T. No extraordinary expenses are due payable on settlement date. The trust composition is: 5,100,000 outstanding shares, representing 1,019,343.41172453 bitcoin. The bitcoin per creation unit is: 9,985.35481959 (reduced because of four days of accrued but unpaid Sponsor's Fee). Amount of bitcoin in only partially-filled cold storage digital wallet (Index Number 08649): 343.41172453.
On day T, AP1 and AP2 place their orders for two creation units and two redemption units, respectively. Trustee accepts the creation and redemption orders and confirms such receipt to AP1 and AP2.
On day T+1, trustee calculates expected netting of 19,970.70963918 (i.e., 2 creation units created less 2 creation units redeemed less expected sponsor's fee, with no expected extraordinary expense payments). Trustee determines that one public key must be retrieved through paper tokens for sponsor's fee distributions on the settlement date and requests that the custodian deliver the paper token for the selected Index Number (cold storage digital wallet 00185) from sets A1, A2 and A3. The Trustee determines that only partially-filled cold storage digital wallet Index Number 08649 can be required for deposit activation for remainder bitcoin from the sponsor's fee distribution.
On day T+2, AP1 submits a creation wallet address supplement identifying the public key from which it can deposit its creation deposit of 19,970.70963917 bitcoin. Using the administrative portal, trustee generates a wallet for the AP1 custody account and provides such wallet's public key to AP1 to receive the creation deposit. AP2 submits a redemption wallet address supplement identifying the public key to which it can received its redemption proceeds of 19,970.70963917 bitcoin. Using the administrative portal, trustee generates a wallet for the AP2 custody account and provides such wallet's public key to AP2 as the account distributing bitcoin. Custodian delivers to trustee (or trustee collects from custodian's premises) the paper tokens for the selected Index Number (cold storage digital wallet 00185) from sets A1, A2 and A3. Trustee scans the QR codes, decrypts and reassembles the Private key and decrypts the public key for cold storage digital wallet 00185. AP1 delivers 19,970.70963917 bitcoin to the public key identified for its AP1 custody account. Trustee acknowledges receipt of such creation deposit. AP2 delivers 50,000 shares to the trust through the third-party clearing agency 250 (e.g., the DTC) clearance process. Trustee acknowledges receipt of such share tender.
On day T+3, settlement occurs. For netting purposes and using the administrative portal, Trustee generates a Wallet for the trust custody account and transfers 19,970.70963917 bitcoin from the AP1 Custody Account to such Wallet in the trust custody account. Using the administrative portal, the trustee transfers 19,970.70963917 bitcoin from the trust custody account to the newly created wallet in the AP2 custody account; transfers such bitcoin from the AP2 custody account to wallet associated with the public key identified by AP2 as its outside account; and instructs the third-party clearing agency (e.g., the DTC) to transfer 100,000 newly issued shares to AP1, in settlement of the creation, and to cancel the 100,000 shares tendered by AP2, in settlement of the redemption. Using the administrative portal, trustee generates a wallet in the sponsor custody account and transfers 837.22012681 bitcoin from Index Number cold storage digital wallets 00185 to the newly created sponsor custody account wallet. Trustee also transfers such bitcoin from the sponsor custody account to the public key identified by sponsor as its outside account; and transfers 162.77987319 bitcoin from Index Number cold storage digital wallet 00185 to the partially filled index number cold storage digital wallet 08649 in cold storage.
At the end of this process, there is no net change of shares issued. bitcoin deposited with the Trust is reduced by 837.22012681. No new cold storage digital wallets activated by deposit; one cold storage digital wallets expired after recall from cold storage and use. All temporary wallets discarded after use. Amount of bitcoin in only partially-filled cold storage digital wallet (Index Number 08649): 506.19159772.
Example 3 is treated as the next business day after settlement of Example 2. In Example 3, the following additional particular facts are assumed: AP2 places a redemption order for four creation units. AP1 does not place any order. No Sponsor's Fee or extraordinary expenses payable on settlement date. The trust composition is: 5,100,000 outstanding shares, representing 1,018,506.19159772 bitcoin. bitcoin per creation unit is: 9,985.08121824 (reduced because of four days of accrued but unpaid Sponsor's Fee). Amount of bitcoin in only partially-filled cold storage digital wallet (index Number 08649): 506.19159772.
On day T, AP2 place its redemption order for four creation units. Trustee accepts the redemption order and confirms such receipt to AP2.
On day T+1, trustee calculates expected netting (none). Trustee determines that 40 public keys need to be retrieved through paper tokens for redemption distributions on the settlement date and requests that the custodian deliver the paper tokens for the selected Index Numbers from sets A1, A2 and A3. The trustee determines that only partially-filled cold storage digital wallets Index Number 08649 can be required for deposit activation for remainder bitcoin from the redemption proceeds withdrawal.
On day T+2, AP submits “redemption wallet address supplement” identifying the public key to which it can received its redemption proceeds of 39,940.32487295 bitcoin. Using the administrative portal, trustee generates a wallet for the AP2 custody account and provides such wallet's public key to AP2 as the account distributing bitcoin. Custodian delivers to trustee (or trustee collects from custodian's premises) the paper tokens for the selected 40 cold storage digital wallets by Index Number from Sets A1, A2 and A3. Trustee scans the QR codes, decrypts and reassembles the Private Keys and decrypts the Public Keys for the 40 cold storage digital wallets by Index Number. AP2 delivers 200,000 shares to the Trust through the third-party clearing agency (e.g., the DTC) clearance process. Trustee acknowledges receipt of such share tender.
On day T+3 (Settlement Date), using the administrative portal, the trustee transfers 1,000 bitcoin from each of 39 of the cold storage digital wallets pulled from cold storage to the newly created wallet in the AP2 custody account, totaling 39,000 bitcoin; transfers 940.32487295 bitcoin from the remaining cold storage digital wallet pulled from cold storage to the newly created wallet in the AP2 custody account; transfers 59.67512705 bitcoin from the remaining cold storage digital wallet to partially-filled cold storage digital wallet (Index Number 08649); transfers the total of 39,940.32487295 such bitcoin from the wallet in AP2 custody account to the public key identified by AP2 as its outside account; and instructs the third-party clearing agency (e.g., the DTC) to cancel the 200,000 shares tendered by AP2, in settlement of the redemption.
At the end of this process, there is a reduction of 20,000 shares issued by the trust and a reduction of 39,940.32487295 bitcoin deposited with the trust. No new cold storage digital wallets activated by deposit; forty cold storage digital wallets expired after recall from cold storage and use. All temporary wallets discarded after use. Amount of bitcoin in only partially-filled cold storage digital wallet (Index Number 08649): 565.86672477.
In embodiments, a digital asset kiosk, such as a digital math-based asset kiosk, may be used to perform one or more transactions associated with digital assets. The transactions may require an appropriate money transmit business in order to meet regulatory requirements. In embodiments, a person or entity must use a money transmit business registered in the person or entity's domicile.
Still referring to
One or more insurers 2042 may provide insurance for fiat accounts, such as fiat exchange accounts. In embodiments, fiat exchange accounts may be held at an exchange partner bank. Such accounts may be insured by the Federal Deposit Insurance Corporation (FDIC). In embodiments, insurers 2042 may be private insurance companies. Insurers 2042 may also provide digital asset insurance, which may cover private key loss and/or theft and/or digital asset losses or thefts.
Still referring to
Still referring to
Still referring to
Still referring to
A digital asset wallet module 2152 may handle the creation of one or more digital asset wallets and/or the accessing of one or more existing digital asset wallets of one or more denomination. For example, a digital asset wallet module 2152 may handle wallets associated with a single digital asset, such as Bitcoin wallets, or handle wallets associated with a plurality of digital assets, such as Litecoin wallets, and/or Namecoin wallets, in addition to Bitcoin wallets, to name a few. In embodiments, a digital asset kiosk may provide a unified wallet or an umbrella wallet, which may hold assets of different denominations. Such a wallet may use one or more exchange rates to show (e.g., in a single denomination) an aggregate value of assets contained in the wallet. Such exchange rates may be associated with a specific exchange, or a blended exchange rate as discussed herein. The wallet may comprise sub-wallets to hold separately each differently denominated asset. In embodiments, the digital asset wallet module 2152 may also be linked to a fiat currency digital wallet module, which transacts in a fiat currency, such as dollars, euro, yen, to name a few.
The wallet may show a breakdown of the value or number of assets of each denomination that is stored in the wallet. A digital asset wallet module 2152 may otherwise show account balances for one or more digital asset wallets. A digital asset transfer module 2154 may process one or more types of transactions involving the sending of digital assets. Digital assets may be sent to one or more other accounts and/or digital wallets, which may be associated with the user, other people, and/or other institutions. A digital asset request module 2156 may handle the requesting of digital asset transfers. For example, a digital asset request module 2156 may provide an interface by which a user can designate an amount of digital assets to request as well as another user, account, or digital wallet address from which to request the digital assets.
An exchange module 2158 may process exchange and/or conversion transactions involving digital assets. Exchange transactions may involve the conversion of digital assets of one denomination to digital assets of a different denomination, digital assets to fiat currencies, and/or fiat currencies to digital assets. In embodiments, exchange and/or conversion transactions may entail the use of a money transmit business, which may be selected by an exchange module 2158 based on the domicile of a user (e.g., a user performing an exchange transaction, a user sending funds that require an exchange transaction, a user paying a bill that requires an exchange transaction, to name a few). Accordingly, an exchange module 2158 may be used in conjunction with one or more other modules to process any transactions requiring an exchange transaction. In embodiments, an exchange module 2158 may allow a user to select an exchange (e.g., from a list of exchanges) to be used for the transaction. Such an option may enable a user to choose select exchanges located in different geographic regions, such as other countries. An exchange module 2158 may display and/or otherwise communicate one or more exchange rates corresponding to one or more exchanges and/or money service businesses.
Still referring to
A deposit module 2160 may handle the physical deposit of money of one or more fiat currency and/or one or more checks or other financial instruments into a digital asset kiosk 2005. In embodiments, tokens and/or other physical embodiments of digital assets may be deposited, subject to applicable government regulations. A deposit module 2160 may control, interface with, and/or receive data from any of a cash deposit device 2126, check deposit device 2132, and/or counter 2136, to name a few. In embodiments, a deposit module 2162 may handle the deposit of funds of any denomination (e.g., funds from money and/or financial instruments inserted into a digital asset kiosk 2005) into one or more accounts of any denomination.
A withdrawal module 2164 may process withdrawals of money in any denomination using a digital asset kiosk 2005. Withdrawals may be made from any fiat currency account, investment account, and/or digital asset account. In embodiments, physical embodiments of one or more digital assets may be withdrawn, in conformance with applicable laws.
A fund transfer module 2166 can handle transactions involving the transfer of funds between accounts and/or between people and/or entities. Transfers of funds between accounts can entail moving digital assets from one account to another, which may be denominated differently, moving fiat currency from one account to another, which may be denominated differently, moving digital assets to an account denominated in a fiat currency, and/or moving funds from a fiat currency account to a digital asset account, to name a few. Transfers between differently denominated accounts, including transfers between digital asset and fiat currency accounts, may entail one or more exchange transactions. A fund transfer module 2166 may access (e.g., through one or more AP1) price and/or exchange data from one or more exchanges and/or may show one or more exchange rates associated with one or more exchanges. A fund transfer module 2166 may provide an interface for selecting options related to a fund transfer transaction and/or may implement commands to carry out a fund transfer transaction. Fund transfers can be between accounts with a common owner. Fund transfers can also be from one person or entity to another person or entity.
A payment module 2168 may handle payments using a digital asset kiosk 2005. A payment module 2168 may enable the paying of one or more bills (e.g., electric bill, gas bill, Internet bill, credit card bill, to name a few). A payment module 2168 may process automatic bill pay using digital assets, which may be converted to a fiat currency prior to payment. The payment module 2168, in embodiments, may be enabled to communicate with a credit or loan value application (e.g. Flexa).
An insurance module 2170 may handle the insuring of one or more digital asset accounts and/or transactions. An insurance module 2170 may communicate with one or more insurers to provide insurance options with users, such as basic insurance plans, premium plans, and/or custom coverage plans. Insurance options may comprise different coverage amounts, different premiums, and/or different asset storage policies, to name a few.
A preferences module 2172 may provide an interface for receiving user preferences and/or may implement those preferences. Preferences can include the language that is used, a default account to use for fund transfers, and/or a default exchange, to name a few. One or more preferences may be stored as part of a user profile such that the preferences may be loaded when a user logs into a digital asset kiosk 2005.
A user profile module 2174 can store user data (e.g., name, contact information, address, telephone number, email address, social security number, government ID information, biometric information, photograph, username, password, security questions, and/or membership data associated with a digital asset kiosk network, to name a few). A user profile module 2174 may store information associated with one or more fiat currency accounts and/or digital asset accounts (e.g., digital asset wallets), so that a user may access and/or use those accounts via a digital asset kiosk 2005.
A transaction history module 2176 may track and/or display account activity for one or more accounts. A transaction history module 2176 may show destinations, recipients, amounts, and/or dates of fund transfers and/or payments and/or may show withdrawals, deposits, exchange transactions, and/or insurance transactions.
In embodiments, an external application (e.g., mobile application, desktop downloadable software, or a website, to name a few) may integrate with a digital asset kiosk. A user may initiate a kiosk transaction using the external application. For example, a user may send, using the external application, transaction instructions to sell digital assets. When the sending of digital assets to from the user to the buyer is confirmed (e.g., by a digital asset network or by an exchange), an electronic notification may be provided to the user to notify the user that the transfer was confirmed and/or that fiat currency is available for withdrawal. In embodiments, the fiat currency received from a buyer, which may be the exchange itself, may be stored in an exchange fiat currency account associated with the user. As described herein, the exchange fiat currency account may be a pooled account for a plurality of exchange users. In embodiments, the pooled account may provide insurance, such as FDIC insurance or insurance from another governmental body. The user may then log in at a digital asset kiosk and select an option to withdraw fiat currency. The kiosk may then provide the currency to the user. This integration of an external application to an exchange and kiosk system can eliminate the need for a user to log into a kiosk, initiate a transaction, and wait for the transaction to occur and clear before funds are available for withdrawal.
In a step S5202, a digital asset kiosk may receive via a user input device first user identification data comprising at least a state of domicile.
In a step S5204, the digital asset kiosk may transmit to an exchange computer system, the first user identification data.
In a step S5206, the digital asset kiosk may receive from the exchange computer system, first display data related to an anti-money laundering user data collection interface based upon the state of domicile.
In a step S5208, the digital asset kiosk may render on a display device operatively connected to the apparatus, the first display data.
In a step S5210, the digital asset kiosk may receive via the user input device, second user identification data corresponding to the anti-money laundering user data collection interface.
In a step S5212, the digital asset kiosk may transmit to the exchange computer system, the second user identification data.
In a step S5214, the digital asset kiosk may receive from the exchange computer system, second display data related to a registration confirmation.
In a step S5216, the digital asset kiosk may render on the display device, the second display data.
Accordingly, in embodiments, an apparatus, which may be an electronic kiosk, may be programmed to perform the following steps: receiving, at the apparatus via a user input device, first user identification data comprising at least a state of domicile; transmitting, from the apparatus to an exchange computer system, the first user identification data; receiving, at the apparatus from the exchange computer system, first display data related to an anti-money laundering user data collection interface based upon the state of domicile; rendering, by the apparatus on a display device operatively connected to the apparatus, the first display data; receiving, at the apparatus via the user input device, second user identification data corresponding to the anti-money laundering user data collection interface; transmitting, from the apparatus to the exchange computer system, the second user identification data; receiving, at the apparatus from the exchange computer system, second display data related to a registration confirmation; and rendering, by the apparatus on the display device, the second display data.
In embodiments, such an apparatus may be an electronic kiosk. In embodiments, such an apparatus may be a user device, such as a smart phone, tablet computer, and/or computer.
In embodiments, the apparatus may be further programmed to perform the steps of receiving, at the apparatus from the exchange computer system, third display data related to exchange transaction options; rendering, by the apparatus on the display device, the third display data; receiving, at the apparatus via a user input device, a selection of an exchange transaction option related to a fiat withdrawal and a corresponding transaction request comprising at least a fiat withdrawal amount; and transmitting, from the apparatus to the exchange computer system, the transaction request.
In embodiments, an apparatus programmed to perform the following steps: receiving, at the apparatus via an input device, user account credentials; transmitting, from the apparatus to the exchange computer system, the user account credentials; receiving, at the apparatus from the exchange computer system, first display data corresponding to a plurality of exchange transaction options for an authenticated user; rendering, by the apparatus, the first display data on a display device operatively connected to the apparatus; receiving, at the apparatus via the input device, user selections corresponding to a first exchange transaction option that is an exchange transaction order; receiving, at the apparatus via the input device, exchange transaction order parameters; transmitting, from the apparatus to the exchange computer system, the exchange transaction order parameters; receiving, at the apparatus from the exchange computer system, second display data corresponding to order placement confirmation; and rendering, by the apparatus, the second display data on the display device.
As shown in
Referring again to
In a step S2504, the notification system 2515 may generate one or more rules for automatic digital asset price notification based at least upon the one or more received parameters and the received notification instructions. For example, a notification rule may be a logical rule comprising a condition and an action. When the condition is satisfied, the action may be performed. Conditions may relate to the type of notification (e.g., price of a particular digital asset drops below a threshold, price exceeds a threshold, exchange is unavailable), and actions may relate to the type of notification (e.g., send an SMS to a particular mobile telephone number). The generated notification rules may be stored by the notification system 2515 and/or incorporated into price monitoring and comparison operations performed by a notification module 2520.
In a step S2506, the notification system 2515 may access, from one or more digital asset exchanges 2505, price data associated with one or more digital assets. A notification module 2520 may perform the step of accessing digital price data, e.g., by interfacing through one or more exchanges 2505 through one or more exchange APIs or by otherwise receiving or fetching the price data, as from a price feed. Price data may be normalized or otherwise formatted to be compatible with the notification system 2515.
In a step S2508, the notification system 2515 may evaluate the digital asset price data according to the notification rules. A notification module 2520 may perform step S2508. In embodiments, evaluation of digital asset price data may comprise comparing the price data to a price threshold to determine whether the threshold was reached and/or crossed.
In a step S2510, the notification system 2515 may generate one or more digital asset notifications. Notification generation may be performed by the notification module 2520. Digital asset notifications may be emails, SMS messages, push notifications, or other notifications, messages, or alerts, and they may indicate that notification criteria have been satisfied (e.g., price thresholds exceeded). Digital asset notifications may be price notifications, indicating the price of one or more digital assets.
In a step S2512, the notification system 2515 may transmit to one or more user devices 2510 the digital asset notification according to the notification instructions embodied in the notification rules. For example, notifications may be transmitted both to a cell phone, to an email account, and to a digital wallet client running on a computer. In embodiments, the user device 2510 that requests notifications (e.g., by setting notification settings) in a step S2502 may be a different user device from the user device that receives notifications in a step S2512. In embodiments, the users associated with the user devices that request notifications and receive notifications may be different users.
An automatic digital asset transaction system 2815 can receive data, such as digital asset transaction data and/or digital asset price data, from one or more exchange 2805 (e.g., 2805-1, 2805-2, . . . , 2805-N), which may be digital asset exchanges. In embodiments, data may be received from one or more exchange agents.
Still referring to
A transaction module 2820 may be software that can receive transaction instructions and transaction parameters, generate transaction rules, access data from one or more exchanges 2805, evaluate digital asset price data according to transaction rules, perform automated transactions (e.g., when pre-defined conditions are met), request authority (e.g., from a user) to proceed with an automatically generated transaction, and/or provide notifications of completed transactions, to name a few. In embodiments, one or more steps in a digital asset notification process may be decentralized, e.g., performed by a user device.
In a step S2804, the automatic transaction system 2815 may generate one or more rules for automatic digital asset transactions based at least upon the one or more received transaction parameters and the received transaction instructions. The generated rules may be logical rules comprising one or more conditions and one or more actions to perform when the conditions are met or not met. Such logical rules may be implemented by computer code running on one or more computers associated with the automatic transaction system 2815. The generation of transaction rules may be performed by a transaction module 2820.
In a step S2806, the automatic transaction system 2815 may access, from one or more digital asset exchanges 2805, transaction data, which may include price data, associated with one or more digital assets. The automatic transaction system 2815 may store transaction data 2825 in one or more databases. The transaction data may be fetched or otherwise received, e.g., using APIs or data feeds from one or more exchanges 2805 or exchange agents. Transaction data may be normalized or otherwise formatted to be compatible with an automatic transaction system 2815, which formatting may be performed by a transaction module 2820.
In a step S2808, the automatic transaction system 2815 may evaluate the digital asset transaction data according to the generated transaction rules. In embodiments, evaluation of the digital asset transaction data may involve testing the transaction data against one or more logical conditions embodied in the transaction rules. For example, the transaction data may be evaluated to determine whether the digital asset price has reached or crossed a threshold value or whether a rate of change in the price has met or crossed a threshold value. A transaction module 2820 may perform the evaluation of the transaction data.
In a step S2810, the automatic transaction system 2815 may perform one or more digital asset transactions according to the transaction rules. Transactions may be performed, initiated, and/or verified by a transaction module 2820. The digital asset transactions may only be performed when one or more conditions are satisfied. In embodiments, an alert of a potential transaction and/or a request for authorization may be sent to a user before automatically performing a transaction. Receipt of a user's authorization by the automatic transaction system 2815 may be required before the system will perform a transaction. Authorization may be provided through telephone (e.g., dialing a number and entering certain digits), SMS (e.g., replying to a text message, sending a code, and/or sending another message authorizing a transaction), email (e.g., replying to an email and/or sending a certain message in the body and/or subject line), web site (e.g., clicking an “Authorize” button), and/or within a software application, such as a digital wallet, to name a few. In embodiments, a request for authorization may be sent, and the transaction may be performed automatically if no response is received within a predetermined amount of time, settings for which may be set in advance by a user and/or set by default.
In a step S2812, the automatic transaction system 2815 may transmit one or more notifications of the performed transaction to one or more user devices 2810. Notifications may be generated by a transaction module 2820. In embodiments, notifications of incomplete, pending, and/or failed transactions may be transmitted. In embodiments, the automatic transaction system 2815 may provide a portal or other mechanism for a user to monitor and/or receive updates regarding transaction statuses. The automatic transaction system 2815 may provide a log of all transactions and/or automatic transactions performed by the system and/or by a user. In embodiments, the automatic transaction system 2815 may provide a log of all transaction opportunities, including declined transactions (e.g., not authorized by a user).
An arbitrage notification system 2920 can receive data, such as digital asset transaction data, from one or more digital asset exchange 2905 (e.g., 2905-1, 2905-2, . . . , 2905-N). In embodiments, data may be received from one or more digital asset exchange agents. An arbitrage notification system 2920 can also receive data, such as fiat currency price data, from one or more fiat currency exchanges 2910 (e.g., 2910-1, 2910-2, . . . 2910-n). In embodiments, fiat currency price data may be received from one or more fiat currency brokers 2940. In embodiments, receiving data may entail fetching data, such as by using an AP1 to access data from one or more exchange.
Still referring to
An arbitrage module 2925 may be software that receives and/or processes requests for arbitrage alerts, generates arbitrage notification rules, stores arbitrage notification rules, executes operations to access data from digital asset and fiat currency exchanges, maps exchange transactions, computes effective exchange rates for mapped transactions, evaluates effective exchange rates and direct exchange rates in accordance with arbitrage notification rules, and/or provides notifications of arbitrage opportunities, to name a few. In embodiments, one or more steps in an arbitrage notification process may be decentralized, e.g., performed by a user device.
In a step S2904, the arbitrage notification system 2920 may access, from one or more digital asset exchanges 2905, digital asset exchange rate data, which may comprise currency pairs relating prices for one or more digital assets to a plurality of other digital assets and/or fiat currencies. In embodiments, other digital asset data may be accessed. For example, a USD/BTC currency pair would provide a ratio of U.S. dollars to bitcoin, which would comprise an exchange rate. Such a currency pair may be used to compute transactions from USD to bitcoin and from bitcoin to USD (using the reciprocal of the exchange rate). Accessing digital asset exchange rate data may entail using one or more APIs for one or more digital asset exchanges 2905 to fetch the price data and/or receiving a data stream of price data. In embodiments, digital asset exchange rate data may be obtained from one or more broker or exchange agent.
In a step S2906, the arbitrage notification system 2920 may access, from one or more fiat currency exchanges 2910, fiat currency exchange rate data, which may comprise one or more currency pairs relating prices for one or more fiat currencies to one or more other fiat currencies. An example of a fiat currency pair is EUR/USD, which relates Euros to U.S. dollars. Fiat currency exchange rate data may be accessed using one or more APIs for one or more fiat currency exchanges and/or by reading a data feed from one or more exchanges, to name a few. In embodiments, a fiat currency exchange 2910 may be an exchange in the foreign exchange market. In embodiments, exchange rate data may be obtained from one or more exchange agent or broker, such as a fiat currency broker 2940.
In a step S2908, the arbitrage notification system 2920 may map currency paths from a starting denomination to an ending denomination using at least two currency pairs or at least three denominations, since two currency pairs may share a common base. In embodiments, the arbitrage notification system 2920 may calculate arbitrage opportunities from the starting denomination to the ending denomination and/or from the ending denomination to the starting denomination. For the path from the starting to the ending denomination, the first currency pair in the currency path should include the starting denomination, while the last pair in the currency path should include the ending denomination. A currency path can include any number of intermediate currency pairs, which may or may not be cross currency pairs. For example, a currency path from USD to BTC may involve 1/(EUR/USD)*(EUR/JPY)*(JPY/BTC), where EUR/JPY is an intermediate cross currency pair. In embodiments, no starting or ending denominations may be received in a step S2902, and the arbitrage notification system 2920 may determine one or more currency paths relating a variety of denominations to detect the presence of any arbitrage opportunity among denominations supported by the arbitrage notification system 2920. In embodiments, only a starting or an ending denomination may be received, in which case the arbitrage notification system 2920 may determine a plurality of currency paths that start and/or end with the received denomination.
In a step S2910, the arbitrage notification system 2920 may compute effective exchange rates for the mapped currency paths. An effective exchange rate may relate the prices of two endpoints of a currency path. The effective exchange rate may be computed by multiplying the exchange rate for each currency pair in the currency path.
In a step S2912, the arbitrage notification system 2920 may evaluate (e.g., by processing on a computer system) arbitrage notification rules to determine the presence of an arbitrage opportunity meeting notification criteria and to determine actions to perform (e.g., notifications to transmit) based thereupon. In embodiments, evaluating arbitrage notification rules may entail, in part, comparing the computed effective exchange rates for one or more currency paths to a direct exchange rate associated with a currency pair relating the starting and ending denominations. Where the effective exchange rate differs from the direct exchange rate, as related by the direct starting/ending currency pair, an arbitrage opportunity may exist. An arbitrage opportunity can exist where the effective exchange rate is either greater than or less than the direct exchange rate.
The arbitrage notification system 2920 can formulate one or more transactions to take advantage of the arbitrage opportunity. The transactions required and the order in which they should be performed will depend, at least in part, on whether the effective exchange rate is greater than or less than the direct exchange rate. In embodiments, transactions may be structured to convert from one denomination to a different denomination. In other embodiments, circular transactions may be structured to perform a plurality of currency conversions and end with the original currency, ideally of a greater amount than transacted at the start (e.g., performing transactions according to a currency path from a starting to an ending denomination, followed by a direct transaction from the ending denomination to the starting denomination). Notifications may be provided to alert one or more users of the existence and/or details of such formulated transactions.
Accordingly, in a step S2914, the arbitrage notification system 2920 may provide to one or more user devices 2915 one or more notifications of one or more arbitrage opportunities. Notifications may indicate the existence of an arbitrage opportunity. Notifications may indicate a projected return on a series of transactions (e.g., 5% increase in bitcoin holdings, 23 BTC increase, 800 USD increase, to name a few). Notifications may also indicate a currency path and/or a plurality of formulated transactions. Notifications can be provided to a plurality of devices associated with a user and via a plurality of media (e.g., SMS, email, automated telephone call, push notification, to name a few).
An arbitrage transaction system 3020 can receive data, such as digital asset price data, from one or more digital asset exchange 3005 (e.g., 3005-1, 3005-2, . . . , 3005-N). In embodiments, data may be received from one or more digital asset exchange agents or brokers. An arbitrage transaction system 3020 can also receive data, such as fiat currency price data, from one or more fiat currency exchanges 3010 (e.g., 3010-1, 3010-2, . . . 3010-n). In embodiments, fiat currency price data may be received from one or more fiat currency brokers 3040. In embodiments, receiving data may entail fetching data, such as by using an AP1 to access data from one or more exchange.
Still referring to
An arbitrage module 3025 may be software that receives and/or processes requests for automated arbitrage transactions, generates arbitrage transaction rules, stores arbitrage transaction rules, executes operations to access data from digital asset and fiat currency exchanges, maps exchange transactions, computes effective exchange rates for mapped transactions, evaluates effective exchange rates and direct exchange rates according to arbitrage transaction rules, requests and/or processes transaction confirmation, performs transactions, and/or provides notifications of arbitrage transaction statuses, to name a few. In embodiments, one or more steps in an arbitrage notification process may be decentralized, e.g., performed by a user device.
In a step S3004, the arbitrage transaction system 3020 may generate one or more rules for automatic arbitrage transactions based at least in part on the received request for automatic arbitrage transactions and the starting and ending denominations, as may be determined by the system if not specified by a user.
In a step S3006, the arbitrage transaction system 3020 may store one or more rules for automatic arbitrage transactions. The rules may be stored in a database (e.g., for retrieval and use by arbitrage opportunity evaluation software or devices programmed to perform such operations) or integrated directly into a program for testing and evaluating exchange rate data, to name a few.
In a step S3008, the arbitrage transaction system 3020 may access, from one or more digital asset exchanges 3005, digital asset exchange rate data, which may comprise currency pairs relating prices for one or more digital assets to a plurality of other digital assets and/or fiat currencies. Accessing digital asset exchange rate data may entail using one or more APIs for one or more digital asset exchanges 3005 to fetch the price data and/or receiving a data stream of price data. In embodiments, digital asset exchange rate data may be obtained from one or more broker or exchange agent.
In a step S3010, the arbitrage transaction system 3020 may access, from one or more fiat currency exchanges 3010, fiat currency exchange rate data, which may comprise one or more currency pairs relating prices for one or more fiat currencies to one or more other fiat currencies. Fiat currency exchange rate data may be accessed using one or more APIs for one or more fiat currency exchanges and/or by reading a data feed from one or more exchanges, to name a few. In embodiments, a fiat currency exchange 3010 may be an exchange in the foreign exchange market. In embodiments, exchange rate data may be obtained from one or more exchange agent or broker, such as a fiat currency broker 3040.
In a step S3012, the arbitrage transaction system 3020 may map currency paths from a starting denomination to an ending denomination using at least two currency pairs or at least three denominations, since two currency pairs may share a common base. The mapping of currency paths is described herein with respect to step S2908.
In a step S3014, the arbitrage transaction system 3020 may compute effective exchange rates for the mapped currency paths. An effective exchange rate may relate the prices of two endpoints of a currency path. The effective exchange rate may be computed by multiplying the exchange rate for each currency pair in the currency path.
In a step S3016, the arbitrage transaction system 3020 may evaluate (e.g., by processing on a computer system) arbitrage transaction rules to determine the presence of an arbitrage opportunity meeting transaction criteria and to determine actions to perform (e.g., seeking authorization to perform a transaction and/or performing a transaction, to name a few) based thereupon. In embodiments, evaluating arbitrage transaction rules may entail, in part, comparing the computed effective exchange rates for one or more currency paths to a direct exchange rate associated with a currency pair relating the starting and ending denominations. Where the effective exchange rate differs from the direct exchange rate, as related by the direct starting/ending currency pair, an arbitrage opportunity may exist, and transactions may be formulated accordingly. Transactions may be structured to convert from one denomination to a different denomination (e.g., following one or more mapped currency paths). In other embodiments, circular transactions may be structured to perform a plurality of currency conversions and end with the original currency, ideally of a greater amount than transacted at the start (e.g., performing transactions according to a currency path from a starting to an ending denomination, followed by a direct transaction from the ending denomination to the starting denomination).
In embodiments, requests for authorization to proceed with a transaction may be sent to a user. In embodiments, if a response is not received from a user within a set period of time, the transaction may proceed.
In a step S3018, the arbitrage transaction system 3020 may perform one or more transactions according to the one or more rules for automatic arbitrage transactions. In embodiments, the performed transactions may follow the mapped currency paths.
In a step S3020, the arbitrage transaction system 3020 may provide one or more transaction status notifications. Transaction status notifications may indicate that one or more transactions were executed automatically, and/or the details of the transactions. Transaction status notifications may also indicate failed and/or pending transactions.
As previously described with respect to
Referring to
In a step S7204, the computer system may transfer or have transferred the transaction amount to a first exchange fiat account associated with the first user and denominated in the starting currency (e.g., draw from user's bank account linked to the exchange but unaffiliated with the exchange and deposit in the first exchange fiat account, which may be affiliated with the exchange). As an alternative, in a step S7206, the computer system may confirm that the transaction amount exists in the first exchange fiat account associated with the first user and denominated in the starting currency.
In a step S7208, the computer system may place a market buy order on a first order book denominated in the starting currency. The market buy order may be an order to buy a quantity of digital assets corresponding to the transaction amount at a current starting currency market price.
In a step S7210, the computer system may execute one or more transactions to fulfill the market buy order. In embodiments, the first digital asset exchange may execute these transactions, e.g., upon receiving a transaction request from the computer system.
In a step S7212, the computer system may debit (e.g., using a fiat currency electronic ledger) the first exchange fiat account by the transaction amount.
In a step S7214, the computer system may credit (e.g., using a digital asset electronic ledger) a digital asset account associated with the first user by the quantity of digital assets. Optionally, where the first exchange handles transactions in the starting currency and a second exchange handles transaction in the destination currency, in a step S7218, the computer system may transfer the quantity of digital assets to a second digital asset exchange denominated in the destination currency.
In a step S7216, the computer system may place a market sell order on a second order book denominated in the destination currency. The market sell order may be an order to sell the quantity of digital assets at a current destination currency market price.
In a step S7220, the computer system may execute one or more second transactions to fulfill the market sell order. In embodiments, the second digital asset exchange may execute these transactions, e.g., upon receiving a transaction request from the computer system.
In a step S7222, the computer system may debit the digital asset account by the quantity of digital assets.
In a step S7224, the computer system may credit a second exchange fiat account associated with the first user and denominated in the destination currency.
In a step S7232, a first digital asset exchange computer system may receive an electronic request from a user device associated with a first user for a limit order exchange transaction. The electronic request may comprise a transaction amount expressed in a starting currency, a digital asset purchase limit price, and a destination currency.
In a step S7234, the first digital asset exchange computer system may transfer the transaction amount to a first exchange fiat account associated with the first user and denominated in the starting currency. Alternatively, in a step S7236, the first digital asset exchange computer system may confirm that the transaction amount exists in a first exchange fiat account associated with the first user and denominated in the starting currency.
In a step S7238, the first digital asset exchange computer system may generate a machine-readable account hold instruction to hold the transaction amount in the first exchange fiat account.
In a step S7240, the first digital asset exchange computer system may generate a digital asset limit purchase order at the digital asset purchase limit price by determining a first transaction digital asset quantity corresponding to the transaction amount at the digital asset purchase limit price, wherein the first transaction digital asset quantity and the digital asset purchase limit price are digital asset purchase transaction parameters; and adding the digital asset purchase transaction parameters to a first digital asset order book denominated in the starting currency.
In a step S7242, the first digital asset exchange computer system may execute one or more transactions with one or more digital asset sellers to fulfill the digital asset limit purchase order.
In a step S7244, the first digital asset exchange computer system may generate a digital asset sell order comprising a sale of the purchased digital asset quantity for a second fiat currency.
In a step S7246, the first digital asset exchange computer system may execute the digital asset sell order.
In embodiments, a foreign exchange system may perform this process by interacting with one or more digital asset exchanges.
In embodiments, insurance may be provided for digital assets, e.g., held by a digital asset exchange. Such insurance may be provided to individual users of digital assets (including vendors), groups of users, exchanges, exchange agents, trusts providing exchange traded products associated with digital assets, to name a few. Insurance may be provided for a digital asset wallet and/or the contents of a digital asset wallet (e.g., insurance for 100 Bitcoin stored in a digital wallet). Such insurance may involve secure storage of the private key to a wallet and/or the public key. In embodiments, the blended digital math-based asset price as discussed herein may be used as a benchmark for such insurance.
In embodiments, a digital asset kiosk, such as a digital math-based asset kiosk, may be used to perform one or more transactions associated with digital assets. The transactions may require an appropriate money transmit business in order to meet regulatory requirements. In embodiments, a person or entity must use a money transmit business registered in the person or entity's domicile.
In embodiments, a digital asset exchange may provide and/or support transactions (e.g., formation, buying, and/or selling) of derivate products. Such exchange traded derivatives can include options such as calls and/or puts. A digital asset exchange may also support digital asset lending, delayed settlements, derivative swaps, futures, and/or forwards, to name a few.
In embodiments, a computer-implemented method may comprise the steps of (i) determining, by a trust computer system including one or more computers, share price information based at least in part upon a first quantity of digital math-based assets held by a trust at a first point in time and a second quantity of shares in the trust at the first point in time; (ii) receiving, at the trust computer system from one or more authorized participant user devices of an authorized participant, an electronic request to purchase a third quantity of shares; (iii) determining, by the trust computer system, a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares; (iv) obtaining, using the trust computer system, one or more destination digital asset account identifiers (e.g., one or more digital asset account addresses, and/or one or more digital asset account public keys, to name a few) corresponding to one or more destination digital asset accounts for receipt of digital math-based assets from the authorized participant; (v) transmitting, from the trust computer system to the one or more authorized participant user devices, the one or more destination digital asset account identifiers and an electronic amount indication of the fourth quantity of digital math-based assets; (vi) receiving, at the trust computer system, an electronic transfer indication of a transfer of digital math-based assets to the destination asset account; (vii) verifying, by the trust computer system using a decentralized electronic ledger maintained by a plurality of physically remote computer systems, a receipt of the fourth quantity of digital math-based assets in the one or more destination digital asset accounts; and (viii) issuing or causing to be issued, using the trust computer system, the third quantity of shares to the authorized participant.
In embodiments, the computer-implemented method may further comprise the step of, after the determining step (i) above, transmitting, from the trust computer system to the one or more authorized participant user devices, the share price information. In embodiments, the determining step (i) above may further comprise the steps of determining, by the trust computer system, a fifth quantity of digital math-based assets held by the trust that are attributable to shareholders; determining, by the trust computer system, a sixth quantity of digital math-based assets by subtracting from the fifth quantity a seventh quantity of digital math-based assets associated with trust expenses; and dividing the sixth quantity by an eighth quantity of outstanding shares.
In embodiments, the verifying step (vii) above may further comprise the steps of accessing, using the trust computer system, a plurality of updates to the decentralized electronic ledger (e.g., new blocks added to a bitcoin blockchain); analyzing, using the trust computer system, each of the plurality of updates for a first confirmation of the receipt by a node in a network associated with the digital math-based asset; and determining, using the trust computer system, a final confirmation of the receipt after detecting first confirmations of the receipt in a predetermined number of the plurality of updates to the decentralized electronic ledger.
In embodiments, the computer-implemented method may further comprise the step of transferring, using the trust computer system, the fourth quantity of digital math-based assets into one or more digital asset accounts associated with a trust custody account.
In embodiments, the computer-implemented method may further comprise the step of transmitting, from the trust computer system to the one or more authorized participant user devices, an electronic receipt acknowledgement indicating the receipt of the fourth quantity of digital math-based assets.
In embodiments, the computer-implemented method may further comprise the step of transmitting or causing to be transmitted, to the one or more authorized participant user devices, an electronic share issuance indication of the issuing of the third quantity of shares.
In embodiments, the share price information may be a quantity of digital math-based assets per share and/or per a basket of shares corresponding to a number of shares associated with one creation unit of shares. In embodiments, the basket of shares may comprise one or more quantities of shares selected from the group consisting of: 5,000 shares, 10,000 shares, 15,000 shares, 25,000 shares, 50,000 shares, and 100,000 shares.
In embodiments, the electronic transfer indication may further comprise an identification of one or more origin digital asset accounts.
In embodiments, the trust computer system may be operated by a trustee of the trust and/or an administrator of the trust on behalf of the trust.
In embodiments, a computer-implemented method may comprise the steps of (i) determining, by a trust computer system comprising one or more computers, share price information based at least in part upon a first quantity of digital math-based assets held by a trust at a first point in time and a second quantity of shares in the trust at the first point in time; (ii) receiving, at the trust computer system from the one or more authorized participant user devices of the authorized participant, an electronic request to redeem a third quantity of shares; (iii) determining, by the trust computer system, a fourth quantity of digital math-based assets based at least in part upon the share price information and the third quantity of shares; (iv) obtaining, by the trust computer system, one or more destination digital asset account identifiers corresponding to one or more destination digital asset accounts for receipt by the authorized participant of a transfer of the fourth quantity of digital math-based assets from the trust; (v) obtaining, using the trust computer system, one or more origin digital asset account identifiers corresponding to one or more origin digital asset accounts for the transfer; (vi) initiating, using the trust computer system, the transfer of the fourth quantity of digital math-based assets from the one or more origin digital asset accounts to the one or more destination digital asset accounts; (vii) broadcasting, using the trust computer system, the transfer to a decentralized electronic ledger maintained by a plurality of physically remote computer systems; (viii) verifying, by the trust computer system using the decentralized electronic ledger, a receipt of the fourth quantity of digital math-based assets at the one or more destination digital asset accounts; and (ix) canceling or causing to be canceled, using the trust computer system, the third quantity of shares from the authorized participant.
In embodiments, the computer-implemented method may further comprise the step of transmitting, from the trust computer system to the one or more authorized participant user devices, the share price information.
In embodiments, the computer-implemented method may further comprise the steps of obtaining, using the trust computer system, a net asset value per share; determining, using the trust computer system, a digital math-based asset value of the third quantity of shares based upon the net asset value per share; determining, using the trust computer system, transaction fees associated with the electronic request; and determining, using the trust computer system, the fourth quantity of digital math-based assets by subtracting the transaction fees from the digital math-based asset value of the third quantity of shares.
In embodiments, the computer-implemented method may further comprise the step of determining, by the trust computer system, a settlement period associated with the electronic request.
In embodiments, the computer-implemented method may further comprise the step of retrieving or causing to be retrieved, using the trust computer system, one or more private keys associated with the one or more origin digital asset accounts; and accessing the one or more origin digital asset accounts using at least the one or more private keys.
In embodiments, the computer-implemented method may further comprise the steps of issuing, using the trust computer system, retrieval instructions for retrieving a plurality of encrypted private keys corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private keys; and obtaining, using the trust computer system, one or more private keys by decrypting the plurality of private keys.
In embodiments, the computer-implemented method may further comprise the steps of issuing, using the trust computer system, retrieval instructions for retrieving a plurality of private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of private key segments; and obtaining, using the trust computer system, one or more private keys by assembling the plurality of private keys.
In embodiments, the computer-implemented method may further comprise the steps of issuing, using the trust computer system, retrieval instructions for retrieving a plurality of encrypted private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private key segments; and obtaining, using the trust computer system, one or more private keys by decrypting the plurality of private key segments and assembling the segments into one or more private keys.
In embodiments, the computer-implemented method may further comprise the steps of issuing, using the trust computer system, retrieval instructions for retrieving a plurality of encrypted private key segments corresponding to the one or more origin digital asset accounts; receiving, at the trust computer system, the plurality of encrypted private key segments; obtaining, using the trust computer system, one or more first private keys by decrypting the plurality of private key segments and assembling the segments into one or more first private keys; and obtaining, using the trust computer system, at least one second private key corresponding to the one or more origin digital asset accounts. In embodiments, the one or more first private keys and the at least one second private key may be keys for one or more multi-signature digital asset accounts.
In embodiments, the computer-implemented method may further comprise the steps of accessing, using the trust computer system, a plurality of updates to the decentralized electronic ledger (e.g., new blocks added to a bitcoin blockchain); analyzing, using the trust computer system, each of the plurality of updates for a first confirmation of the receipt by a node in a network associated with the digital math-based asset; and determining, using the trust computer system, a final confirmation of the receipt after detecting first confirmations of the receipt in a predetermined number of the plurality of updates to the decentralized electronic ledger.
In embodiments, the transaction fees may be denominated in a unit of the digital math-based asset. In embodiments, the share price information may comprise a net asset value per share, an adjusted net asset value per share, and/or a net asset value per a basket of shares corresponding to a number of shares associated with one creation unit of shares.
In embodiments, the basket of shares may comprise one or more quantities of shares selected from the group consisting of: 5,000 shares, 10,000 shares, 15,000 shares, 25,000 shares, 50,000 shares, and 100,000 shares.
In embodiments, the electronic request may comprise a redemption order.
In embodiments, the trust computer system may be operated by a trustee of the trust and/or an administrator of the trust on behalf of the trust.
In embodiments, the one or more origin digital asset accounts may correspond to a trust custody account.
In embodiments, the one or more destination digital asset accounts may correspond to an authorized participant custody account.
In embodiments, a computer-implemented method may comprise the steps of (i) generating, using a computer system comprising one or more computers, one or more digital asset accounts capable of holding one or more digital math-based assets; (ii) obtaining, using the computer system, one or more private keys corresponding to the one or more digital asset accounts; (iii) dividing, using the computer system, each of the one or more private keys into a plurality of private key segments; (iv) encrypting, using the computer system, each of the plurality of private key segments; (v) associating, using the computer system, each of the plurality of private key segments with a respective reference identifier; (vi) creating, using the computer system, one or more cards for each of the encrypted plurality of private key segments wherein each of the one or more cards has fixed thereon one of the encrypted plurality of private key segments along with the respective associated reference identifier; and (vii) tracking, using the computer system, storage of each of the one or more cards in one or more vaults.
In embodiments, the computer-implemented method may further comprise the steps of generating, using the computer system, electronic transfer instructions for an electronic transfer of the quantity of digital math-based assets to the one or more digital asset accounts; and broadcasting, using the computer system, the electronic transfer instructions to a decentralized electronic ledger maintained by a plurality of physically remote computer systems.
In embodiments, the computer system includes at least one isolated computer that is not directly connected to an external data network.
In embodiments, the encryption step (iv) above, may further comprise implementing, using the computer system, a symmetric-key and/or asymmetric-key encryption algorithm.
In embodiments, the one or more cards may be plastic, a paper product, index cards, sheets of paper, metal, and/or laminated.
In embodiments, each of the encrypted plurality of private key segments along with the respective associated reference identifier may be fixed on the one or more cards via printing, etching. In embodiments, each of the encrypted plurality of private key segments may be fixed on the one or more cards via a magnetic encoding and/or scannable code. In embodiments, the scannable code may be a bar code and/or a QR code.
In embodiments, the one or more vaults may be geographically remote from each other. In embodiments, the one or more vaults may include a bank vault and/or a precious metal vault. In embodiments, the one or more vaults may comprise a main set of vaults and one or more sets of backup vaults. In embodiments, the main set of vaults may be located in a geographically proximate area and at least one of the one or more sets of backup vaults are located in a geographically remote area. In embodiments, the geographically proximate area may be a metropolitan area of a first city.
In embodiments, each of the plurality of private key segments corresponding to a first private key may be stored in separate vaults.
In embodiments, the computer-implemented method may further comprise the steps of receiving, at the computer system, a quantity of digital math-based assets; and storing, using the computer system, the quantity of digital math-based assets in the one or more digital asset accounts.
In embodiments, a computer-implemented method may comprise the steps of (i) generating, using a computer system comprising one or more computers, one or more digital asset accounts capable of holding one or more digital math-based assets; (ii) obtaining, using the computer system, a first plurality of private keys corresponding to each of the one or more digital asset accounts; (iii) dividing, using the computer system, a first private key of the first plurality of private keys into a second plurality of first private key segments; (iv) encrypting, using the computer system, each of the second plurality of first private key segments; (v) associating, using the computer system, each of the second plurality of first private key segments and a second private key with a respective reference identifier; (vi) creating, using the computer system, one or more cards for each of the encrypted second plurality of first private key segments wherein each of the one or more cards has fixed thereon one of the encrypted second plurality of first private key segments along with the respective associated reference identifier; and (vii) tracking, using the computer system, storage of each of the one or more cards in one or more vaults and storage of the second private key.
In embodiments, the computer-implemented method may further comprise the step of encrypting, using the computer system, the second private key.
In embodiments, the computer-implemented method may further comprise the step of electronically storing the second private key on a computer-readable substrate.
In embodiments, the computer-implemented method may further comprise the steps of generating, using a computer system comprising one or more computers, one or more digital asset accounts capable of holding one or more digital math-based assets; obtaining, using the computer system, one or more private keys corresponding to the one or more digital asset accounts; encrypting, using the computer system, each of the one or more private keys; dividing, using the computer system, each of the one or more encrypted private keys into a plurality of private key segments; associating, using the computer system, each of the plurality of private key segments with a respective reference identifier; creating, using the computer system, one or more cards for each of the plurality of private key segments wherein each of the one or more cards has fixed thereon one of the plurality of private key segments along with the respective associated reference identifier; and tracking, using the computer system, storage of each of the one or more cards in one or more vaults.
In embodiments, the one or more digital asset accounts may comprise multi-signature digital asset accounts.
In embodiments, a computer-implemented method may comprise the steps of (i) determining, using a computer system comprising one or more computers, one or more digital asset account identifiers corresponding to one or more digital asset accounts capable of holding one or more digital math-based assets; (ii) accessing, using the computer system, key storage information associated with each of the one or more digital asset account identifiers; (iii) determining, using the computer system, based upon the key storage information, storage locations corresponding to each of a plurality of private key segments corresponding to each of the one or more digital asset accounts; (iv) issuing or causing to be issued, retrieval instructions for retrieving each of the plurality of private key segments; (v) receiving, at the computer system, each of the plurality of private key segments; (vi) decrypting, using the computer system, each of the plurality of private key segments; (vii) assembling, using the computer system, each of the plurality of private key segments into one or more private keys.
In embodiments, the computer-implemented method may further comprise the step of accessing, using the computer system, the one or more digital asset accounts associated with the one or more private keys.
In embodiments, the computer-implemented method may further comprise the steps of accessing, using an isolated computer of the computer system, wherein the isolated computer is not directly connected to an external data network, the one or more digital asset accounts associated with the one or more private keys; generating, using the isolated computer, transaction instructions comprising one or more transfers from the one or more digital asset accounts; transferring the transaction instructions to a networked computer of the computer system; and broadcasting, using the networked computer, the transaction instructions to a decentralized electronic ledger maintained by a plurality of physically remote computer systems.
In embodiments, the key storage information may comprise a reference identifier associated with one or more stored private key segments.
In embodiments, a system may comprise (i) one or more networked computers comprising one or more processors and computer-readable memory; (ii) one or more isolated computers comprising one or more processors and computer-readable memory and configured to generate digital asset accounts and generate transaction instructions for digital math-based asset transactions; (iii) a writing device configured to write digital asset account keys; and (iv) a reading device configured to read digital asset account keys.
In embodiments, the system may further comprise an accounting computer comprising one or more processors and computer-readable memory and configured to track digital math-based asset transactions involving one or more specified digital asset accounts.
In embodiments, the one or more isolated computers, the writing device, and the reading device may be located within a Faraday cage.
In embodiments, the isolated computer may not be physically connected to an external data network.
In embodiments, the writing device may be a printer and/or an engraver.
In embodiments, the reading device may be a disk drive, an electronic card reader. a QR reader, and/or a scanner. In embodiments, the scanner may be a bar code scanner.
In embodiments, the writing and/or device may be operationally connected to the one or more isolated computers.
In embodiments, a secure system for storing digital math-based assets may comprise (a) an electronic isolation chamber; (b) one or more isolated computers within the electronic isolation chamber and comprising one or more processors and computer-readable memory operatively connected to the one or more processors and having stored thereon instructions for carrying out the steps of (i) generating, using the one or more isolated computers, one or more digital asset accounts capable of holding one or more digital math-based assets; (ii) obtaining, using the one or more isolated computers, one or more private keys corresponding to the one or more digital asset accounts; (iii) dividing, using the one or more isolated computers, at least one of the one or more private keys for each digital asset account into a plurality of private key segments, wherein each private key segment will be stored; (iv) associating, using the one or more isolated computers, each of the plurality of private key segments with a respective reference identifier; and (v) transmitting, from the one or more isolated computers to one or more writing devices operatively connected to the one or more isolated computers, electronic writing instructions for writing a plurality of cards, collated into a plurality of sets having only one private key segment per digital asset account, and each card containing one of the plurality of private key segments along with the respective associated reference identifier; (c) the one or more writing devices located within the electronic isolation chamber and configured to perform the electronic writing instructions, including collating the plurality of cards into the plurality of sets; and (d) one or more reading devices located within the electronic isolation chamber and configured to read the plurality of private key segments along with the respective associated reference identifier from the one or more cards.
In embodiments, a computer-implemented method may comprise the steps of (i) receiving, at a computer system comprising one or more computers, an electronic request to transfer first respective quantities of digital math-based assets from each of a first plurality of digital asset accounts; (ii) accessing, using the computer system, each of the first plurality of digital asset accounts; (iii) generating, using the computer system, transaction instructions comprising one or more transfers of the first respective quantities from each of the first plurality of digital asset accounts; and (iv) broadcasting, using the computer system, the transaction instructions to a decentralized electronic ledger maintained by a plurality of physically remote computer systems.
In embodiments, the first respective quantities of digital math-based assets comprise different quantities for different digital asset accounts.
In embodiments, a computer-implemented method for dynamically providing a graphical user interface for an electronic order book may comprise receiving, by an exchange computer system comprising one or more computers from non-transitory computer-readable memory operatively connected to the one or more computers, from a user device, a request to access the electronic order book associated with a digital asset traded on an electronic exchange, and accessing, by the exchange computer system, electronic order book information comprising digital asset order information for a plurality of digital asset orders, the digital asset order information comprising respective order prices denominated in a fiat currency and respective order quantities for each of the plurality of pending digital asset orders, wherein the plurality of pending digital asset orders includes pending digital asset purchase orders and pending digital asset sell orders. The method may further comprise calculating, by the exchange computer system, information for a first graphical user interface by determining, by the exchange computer system, at each respective order a price first cumulative quantity of digital assets subject to the pending digital asset purchase orders; and determining, by the exchange computer system, at each respective order price a second cumulative quantity of digital assets subject to the pending digital asset sell orders. The method may also comprise generating, by the exchange computer system, first machine-readable instructions to render the first graphical user interface including a first electronic order book graphical representation, the first electronic order book graphical representation comprising: (i) a first axis depicting price denominated in the fiat currency; (ii) a second axis depicting digital asset quantity; (iii) a first set of graphical indicators on a first side of the first axis showing at each price visible along the first axis the first cumulative quantity of digital assets subject to the pending digital asset purchase orders; and (iv) a second set of graphical indicators on a second side of the first axis showing at each price visible along the first axis the second cumulative quantity of digital assets subject to the pending digital asset sell orders. The method may comprise transmitting, by the exchange computer system to the first user electronic device, the first machine-readable instructions so as to cause an application (e.g., downloadable dedicated application, such as a mobile application, or a web browser application) at the first user electronic device to render the first graphical user interface on a display associated with the first user electronic device.
In embodiments, the method may further comprise receiving, at the exchange computer system from the first user electronic device, first digital asset order information corresponding to a first prospective digital asset purchase order, the first digital asset order information comprising a first order quantity of the digital asset and a first order price parameter related to a first order price of the digital asset, the first order price denominated in the fiat currency. The method may comprise storing, by the exchange computer system in the non-transitory computer-readable memory, the first digital asset order information as a prospective digital asset purchase order. The method may comprise calculating, by the exchange computer system, information for a second graphical user interface (e.g., a new interface or an updated version of the prior graphical user interface) by determining, by the exchange computer system, at each respective order price a second order quantity of digital assets subject to the first prospective digital asset purchase order and determining, by the exchange computer system, at each respective order price a third cumulative quantity of digital assets subject to the digital asset sell orders that would remain after fulfilling the first prospective digital asset purchase order. The method may comprise generating, by the exchange computer system, second machine-readable instructions to render the second electronic graphical user interface including a second electronic order book graphical representation comprising a graphical representation of the first prospective digital asset purchase order superimposed on a modified first electronic order book graphical representation, the second electronic order book graphical representation comprising (i) the first axis depicting price denominated in the fiat currency; (ii) the second axis depicting digital asset quantity; (iii) the first set of graphical indicators on the first side of the first axis; (iv) the second set of graphical indicators on the second side of the first axis; (v) a third set of graphical indicators on the first side of the first axis showing at each price visible along the first axis the respective second order quantity of digital assets subject to the first prospective digital asset purchase order; and (vi) a fourth set of graphical indicators on the second side of the first axis showing at each price visible along the first axis the respective third cumulative quantity of digital assets subject to the digital asset sell orders that would remain after fulfilling the first prospective digital asset purchase order. The method may comprise transmitting, by the exchange computer system to the first user electronic device, the second machine-readable instructions so as to cause the application at the first user electronic device to render the second graphical user interface on the display.
In embodiments, the machine-readable instructions may be rendered in a webpage by a web browser. In embodiments, the machine-readable instructions may be rendered by a downloadable application, such as a mobile application running on the user electronic device.
In embodiments, the first axis may be a horizontal axis.
In embodiments, the second axis may have a logarithmic scale. In embodiments, at least one of the first axis or the second axis of the first electronic order book graphical representation have a different scale than the corresponding first axis and the corresponding second axis of the second electronic order book graphical representation.
In embodiments, the first order price parameter may comprise a market order indicator and the first order price is a market price. In embodiments, the third set of graphical indicators may not be displayed.
In embodiments, the first order price parameter may comprise a limit order indicator and the first order price may be a limit price specified by the user. In embodiments, the first prospective digital asset purchase order may be characterized as out of the money and the third respective cumulative quantity of digital assets at each price may be zero.
In embodiments, the step of calculating information for a second electronic order book graphical representation may further comprise determining, by the exchange computer system, at each respective order price a fourth cumulative quantity of digital assets subject to both the digital asset purchase orders and the first prospective digital asset purchase order that would remain after fulfillment of at least a portion of the first prospective digital asset purchase order by the pending digital asset sell orders. In the second electronic order book graphical representation, the first set of graphical indicators may show at each price visible along the first axis the fourth cumulative quantity of digital assets.
In embodiments, the method may comprise receiving, at the exchange computer system from the first user electronic device, first digital asset order information corresponding to a first prospective digital asset sell order, the first digital asset order information comprising a first order quantity of the digital asset and a first order price parameter related to a first order price of the digital asset, the first order price denominated in the fiat currency. The method may comprise storing, by the exchange computer system in the non-transitory computer-readable memory, the first digital asset order information as a prospective digital asset sell order. The method may comprise calculating, by the exchange computer system, information for a second graphical user interface (e.g., a new graphical user interface or an updated version of the prior graphical user interface) by determining, by the exchange computer system, at each respective order price a second order quantity of digital assets subject to the first prospective digital asset sell order; and determining, by the exchange computer system, at each respective order price a third cumulative quantity of digital assets subject to the digital asset purchase orders that would remain after fulfilling the first prospective digital asset sell order. The method may comprise generating, by the exchange computer system, second machine-readable instructions to render the second graphical user interface including a second electronic order book graphical representation comprising a graphical representation of the first prospective digital asset purchase order superimposed on a modified first electronic order book graphical representation, the second electronic order book graphical representation comprising (i) the first axis depicting price denominated in the fiat currency; (ii) the second axis depicting digital asset quantity; (iii) the first set of graphical indicators on the first side of the first axis; (iv) the second set of graphical indicators on the second side of the first axis; (v) a third set of graphical indicators on the first side of the first axis showing at each price visible along the first axis the respective third cumulative quantity of digital assets subject to the digital asset purchase orders that would remain after fulfilling the first prospective digital asset sell order; and (vi) a fourth set of graphical indicators on the second side of the first axis showing at each price visible along the first axis the respective second order quantity of digital assets subject to the first prospective digital asset sell order. The method may comprise transmitting, by the exchange computer system to the first user electronic device, the second machine-readable instructions so as to cause the application at the first user electronic device to render the second graphical user interface on the display.
In embodiments, the step of calculating information for a second electronic order book graphical representation may further comprise determining, by the exchange computer system, at each respective order price a fourth cumulative quantity of digital assets subject to both the digital asset purchase orders and the first prospective digital asset purchase order that would remain after fulfillment of at least a portion of the first prospective digital asset purchase order by the pending digital asset sell orders. In the step of generating machine-readable instructions for the second electronic order book graphical representation, the first set of graphical indicators may show at each price visible along the first axis the fourth cumulative quantity of digital assets.
In embodiments, the present invention generally relates to systems, methods, and program products for use with custodial electronics wallets for an ETPs or other financial products holding digital assets, including digital math-based assets, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin, to name a few. For purposes of discussion, without limiting the scope of the invention, embodiments involving bitcoin may be discussed to illustrate the present invention. The disclosure can encompass other forms of digital assets, digital math-based assets, peer-to-peer electronic cash system, digital currency, synthetic currency, or digital crypto-currency.
In embodiments, the present invention generally relates to systems, methods, and program products providing particular applications of an electronic digital asset exchange facilitating the purchase and sale of digital math-based assets, including digital math-based assets, such as Bitcoin, Ethereum, Ripple, Cardano, Litecoin, NEO, Stellar, IOTA, NEM, Dash, Monero, Lisk, Qtum, Zcash, Nano, Steem, Bytecoin, Verge, Siacoin, Stratis, BitShares, Dogecoin, Waves, Decred, Ardor, Hshare, Komodo, Electroneum, Ark, DigiByte, E-coin, ZClassic, Byteball Bytes, PIVX, Cryptonex, GXShares, Syscoin, Bitcore, Factom, MonaCoin, ZCoin, SmartCash, Particl, Nxt, ReddCoin, Emercoin, Experience Points, Neblio, Nexus, Blocknet, GameCredits, DigitalNote, Vertcoin, BitcoinDark, Bitcoin Cash, Skycoin, ZenCash, NAV Coin, Achain, HTMLCOIN, Ubiq, BridgeCoin, Peercoin, PACcoin, XTRABYTES, Einsteinium, Asch, Counterparty, BitBay, Viacoin, Rise, Guiden, ION, Metaverse ETP, LBRY Credits, Crown, Electra, Burst, MinexCoin, Aeon, SaluS, DECENT, CloakCoin, Pura, ECC, DeepOnion, Groesticoin, Lykke, Steem Dollars, I/O Coin, Shift, HempCoin, Mooncoin, Dimecoin, Namecoin, Feathercoin, Diamond, Spectrecoin, Filecoin, Tezos, PPCoin, Tonal bitcoin, IxCoin, Devcoin, Freicoin, I0coin, Terracoin, Liquidcoin, BBQcoin, BitBars, Gas, Tether, Ether Classic and PhenixCoin, to name a few. For purposes of discussion, without limiting the scope of the invention, embodiments involving bitcoin may be discussed to illustrate embodiments of the present invention. The disclosure can encompass other forms of digital assets, digital math-based assets, peer-to-peer electronic cash system, digital currency, synthetic currency, or digital crypto-currency. The disclosure may also encompass assets or utilities, in the forms of “tokens,” that may reside on top of a blockchain. For example, a token may in the form of a digital asset that exists on another digital asset's platform. A more specific example is Ethereum's ERC20 token, implemented by the ERC20 protocol that defines a set of rules which need to be met in order for the token to be accepted on the Ethereum platform.
In embodiments, systems and methods of the present invention may take into account blockchain forks, such as a “hardfork.” A fork or hardfork may be a radical change to the blockchain protocol that makes previously invalid blocks/transactions valid (or vice-versa), and as such requires all nodes or users to upgrade to the latest version of the protocol software. Put differently, a hard fork is a permanent divergence from the previous version of the blockchain, and nodes running previous versions will no longer be accepted by the newest version. This essentially creates a fork in the blockchain, one path which follows the new, upgraded blockchain, and one path which continues along the old path. Generally, after a short period of time, those on the old chain will realize that their version of the blockchain is outdated or irrelevant and quickly upgrade to the latest version. In regards to bitcoin, examples of forks include Bitcoin Cash and Bitcoin Gold.
In embodiments, the present invention may be used in connection with products or services other than ETPs, which can include digital asset price calculators, digital asset indices, digital asset account monitoring systems, correlation of news events to digital asset prices, exchanges for converting from, to, or between digital assets, such as digital math-based assets, automated notification, transaction, and/or arbitrage systems involving digital assets, including digital math-based assets, kiosk systems for transacting or interacting with digital math-based assets, digital asset insurance systems, digital asset secure storage systems, and/or other financial products based on the same.
A digital asset exchange computer system may provide a technological platform to convert between digital assets and fiat currencies and/or between digital assets and other digital assets. Exchanges known in the art have suffered from security breaches, money-laundering risk, and an inability to authenticate customer's using their real-world identities, and inefficiencies. The systems, methods, and program products of the present invention provide technological solutions to these problems.
In embodiments, the present invention may be used in connection with other products or services related to digital assets and digital asset exchanges, which can include automated notification, transaction, and/or arbitrage systems involving digital assets, including digital math-based assets, and/or kiosk systems for transacting or interacting with digital math-based assets.
In embodiments, the present invention generally relates to systems, methods, and program products providing an electronic digital asset exchange facilitating the purchase and sale of digital math-based assets, including digital math-based assets. The electronic digital asset exchange provides a technological solution to user identity verification, anti-money laundering verification, and secure storage of digital math-based assets and fiat currency associated with customer accounts.
In embodiments, referring to
In embodiments, an insured omnibus fiat account may comprise a plurality of the associated insured fiat accounts. In embodiments, at least one insured fiat account may be insured by the Federal Deposit Insurance Corporation. In embodiments, a digital wallet may hold digital math-based assets corresponding to a plurality of the digital math-based asset accounts.
In embodiments, the method may further comprise the step of transmitting, from the digital math-based asset computer system, an electronic transaction confirmation. In embodiments, an electronic transaction confirmation may be transmitted to the first user electronic device. In further embodiments, an electronic transaction confirmation may be transmitted to the second user electronic device. In still further embodiments, an electronic transaction confirmation may be transmitted to the second user electronic device to a computer system associated with an institution associated with the exchange institutional account.
In embodiments, the security systems and methods described herein may be used, e.g., as security protocols, associated with various financial products, such as a derivative product, an exchange traded derivative product, a fund, a company, an exchange traded fund, a note, an exchange traded note, a security, a debt instrument, a convertible security, an instrument comprising a basket of assets including one or more digital math-based assets, and/or an over-the-counter product.
In embodiments, an apparatus may be programmed to perform the following steps: receiving, at the apparatus via a user input device, first user identification data comprising at least a state of domicile; transmitting, from the apparatus to an exchange computer system, the first user identification data; receiving, at the apparatus from the exchange computer system, first display data related to an anti-money laundering user data collection interface based upon the state of domicile; rendering, by the apparatus on a display device operatively connected to the apparatus, the first display data; receiving, at the apparatus via the user input device, second user identification data corresponding to the anti-money laundering user data collection interface; transmitting, from the apparatus to the exchange computer system, the second user identification data; receiving, at the apparatus from the exchange computer system, second display data related to a registration confirmation; and rendering, by the apparatus on the display device, the second display data.
In embodiments, such an apparatus may be an electronic kiosk. In embodiments, such an apparatus may be a user device, such as a smart phone, tablet computer, and/or computer.
In embodiments, the apparatus may be further programmed to perform the steps of receiving, at the apparatus from the exchange computer system, third display data related to exchange transaction options; rendering, by the apparatus on the display device, the third display data; receiving, at the apparatus via a user input device, a selection of an exchange transaction option related to a fiat withdrawal and a corresponding transaction request comprising at least a fiat withdrawal amount; and transmitting, from the apparatus to the exchange computer system, the transaction request.
In embodiments, an apparatus programmed to perform the following steps: receiving, at the apparatus via an input device, user account credentials; transmitting, from the apparatus to the exchange computer system, the user account credentials; receiving, at the apparatus from the exchange computer system, first display data corresponding to a plurality of exchange transaction options for an authenticated user; rendering, by the apparatus, the first display data on a display device operatively connected to the apparatus; receiving, at the apparatus via the input device, user selections corresponding to a first exchange transaction option that is an exchange transaction order; receiving, at the apparatus via the input device, exchange transaction order parameters; transmitting, from the apparatus to the exchange computer system, the exchange transaction order parameters; receiving, at the apparatus from the exchange computer system, second display data corresponding to order placement confirmation; and rendering, by the apparatus, the second display data on the display device.
A technical challenge of many digital asset exchanges is how to allow authorized users to exchange large blocks of digital assets without causing unwelcome price movements due to the pending transaction. For example, if a large order (e.g., bid or ask) for a large number of digital asset units (e.g., 10 BTC, which at a USD$10,000 per BTC price could be USD$100,000, or 100 BTC, to name a few) is identified on a public order book, the public posting of such an offer may cause the price of the digital asset to spike or drop disproportionate to the spot price that might otherwise be available in the market if it was not on the public order book.
In embodiments, the digital asset exchange computer system may include block trading options, which can overcome these technical problems. By way of illustration, a separate block trading order book can be set up for a specific digital asset class or pair (e.g., BTC-USD) in which only certain designated users may participate. For example, the separate block trading order book may only be available for customers who have a sufficient quantity of digital assets to meet minimum block requirement such as those discussed below, such as institutional customers, such that they can buy or sell in large volume transactions, as a block taker, and a plurality of qualified market makers who are qualified to act as a counter party, maker(s), responding to a proposed request or indication of interest with a response. In embodiments, a separate block trading order book for each taker request may be maintained separately from other order books, such as a continuous trading order book, an auction trading order book, or other block trading order books, to name a few.
By way of illustration, a block trading order book for a pairing including a digital asset may be set up in which blocks of a designated digital asset size and/or fiat value may be traded. In embodiments, a minimum block size may be established for participation in a block order book. By way of example, for bitcoin, a minimum block size may include amounts such as 5 BTC, 10 BTC, 15 BTC, 20 BTC, 50 BTC, 100 BTC, to name a few. In embodiments, the minimum block size may be specified based on notional value associated with a respective fiat. For example, in a digital asset to fiat block order trading book, such as bitcoin to USD (BTC-USD), when the notional value of BTC to USD is set at 1 BTC=USD$10,000, a block size of USD$100,000 may be set or 10 BTC. By further example, if the notional value of BTC to USD is set at 1 BTC=USD$20,000, a block size of USD$100,000 may be set at 5 BTC. In embodiments, the block size may be pegged exactly to a notional fiat value, e.g., $100,000. In embodiments, the block size may be pegged to the nearest significant digit of a digital asset value. For example, in the above example, if the notional value of BTC to USD is set at 1 BTC=USD$11,535, the block size may be set at 10 BTC, instead of 8.66926 BTC. In embodiments, under the same example, the block size could be set at 8.7 BTC, choosing the first decimal place as the relevant significant digit. In embodiments, the block sizes could be modified to reflect changing market conditions. In embodiments, block sizes may also be designated in different amounts and/or different digital assets (e.g., ether, litecoin, bitcoin cash, to name a few) consistent with exemplary embodiments. In embodiments, block trading order books may be set up using digital asset to fiat pairings (e.g., BTC-USD) and/or digital asset to digital asset pairings (e.g., BTC-ETH).
In embodiments, block sizes may be set up in multiples of minimum block sizes. For example, if the minimum block size is set at 10 BTC, then blocks sizes could be set up as 10 BTC, 20 BTC, 30 BTC, etc. to name a few. In embodiments, block sizes may be set up in values that are at fixed intervals, but not necessarily at multiples of minimum block sizes. For example, if the minimum block size is set at 10 BTC, then block sizes could be set up at 5 BTC intervals, starting with the minimum block size, e.g., 10 BTC, 15 BTC, 20 BTC, 25 BTC, 30 BTC, etc., to name a few. In embodiments, block sizes may be set up in values that are not in fixed intervals, such as, by way of example, any block sizes that are above a minimum block size, e.g., any order of over 10 BTC, such as 10.2 BTC or 11 BTC, or 28 BTC to name a few. Other examples of block sizes may be implemented consistent with exemplary embodiments.
With reference to
In embodiments, the digital asset exchange computer system 3230 also includes or at least is operationally connected to a digital asset ledger 5806 for each digital asset, a fiat asset ledger 5808 for each fiat. In embodiments, a digital asset ledger 5806 will maintain a list of the beneficial ownership of all the digital assets held by the digital asset exchange. In embodiments, each separate digital asset (e.g., BTC, ETH, etc.) may be maintained in a separate digital asset ledger 5806, or in an aggregated digital asset ledger. In embodiments, a fiat asset ledger 5808 will maintain a list of the beneficial ownership of all the fiat held by the digital asset exchange. In embodiments, each separate fiat (e.g., USD, euro, yet, etc.) may be maintained in a separate fiat ledger 5806, or in an aggregated fiat ledger. In embodiments, where the digital asset exchange allows market makers to obtain operational advances, a market maker advance ledger 5810 may be maintained. In embodiments, the market maker advance ledger 5810 will maintain a list of market makers, advance limits, amounts advanced and/or available advance amounts.
In embodiments, the digital asset exchange computer system 3230 may communicate with a plurality of n market maker computer systems including at least Market Maker 1 Computer System 3250 a, Market Maker 2 Computer System 3250b and Market Maker n Computer System 3250n. In embodiments, the digital asset exchange computer system 3230 may communicate with one or more market maker computer systems 3250 using an advanced programming interface (AP1), such as the kind used in an automated trading system. In general, an AP1 is a set of routines or subroutines, protocols and tools for building software applications, which facilitate communications between various software components. An AP1 may be for a web-based system, operating system, database system, computer hardware or software library. An AP1 specification can take many forms, but often includes specifications for routines, data structures, object classes, variables or remote calls. POSIX, Windows AP1 and ASPI are examples of different forms of APIs. Documentation for the AP1 is usually provided to facilitate usage. An example of such an order placing AP1 is available with the Gemini Exchange, as discussed at https://docs.gemini.com/rest-api/#new-order.
Referring to
In step S5602, digital asset exchange computer system 3230 receives from a taker user device 3232 associated with a taker (customer), a first block trade order associated with a first pair of a first digital asset and either a first fiat or a second digital asset. The first block trade order specifies block characteristics (e.g. digital asset type, quantity of the digital asset, side of the transaction, minimum fill quantity/price limit). An exemplary block order 5902 is illustrated in
In step S5604, digital asset exchange computer system 3230 may set a collar for the block trade, including a collar minimum and a collar maximum. First, the digital asset exchange computer system 3230 may access, from at least a first database stored on a computer readable medium operatively connected to the digital asset computer system, pricing data associated with the first digital asset pair at a predefined time associated with a time of the first block trade order. In embodiments, pricing data can include a spot price. In embodiments, pricing data may be based on the last transaction immediately prior to the block trade. In embodiments, pricing data may be based on an average of the most recent bid/ask price for the digital asset. In embodiments, the pricing data may be set based on a blended digital asset price as discussed elsewhere herein. For example, a single exchange digital asset price could be determined based on a volume weighted average and/or time weighted average of recent digital asset pricing. In embodiments, a blended digital asset price may be based on pricing from digital assets taken from a plurality of exchanges (such as qualified exchanges). In embodiments, pricing data may be a blended digital asset price comprising a plurality of digital asset exchanges (e.g., 4) executing trade data for a fixed period of time (e.g., a 10 minute period) using a volume weighting with a fixed percentage (e.g., 5%) of the highest priced trades and a second fixed percentage (e.g., 5%) of the lowest priced trades removed. The digital asset exchange computer system 3230 may calculate a collar minimum for the first block trade order based on the pricing data less an amount equal to a first percentage of the pricing data, and a collar maximum for the first block trade order based on the pricing data plus an amount equal to the first percentage of the pricing data. Thus, a collar may be based on a spot price at the time for the first block trade order, plus or minus a defined range, such as a percentage of the spot price or other pricing data. In embodiments, the collar could be set using percentages such as 1%, 2%, 3%, 5%, 10% of the spot price or other pricing data, to name a few. By way of illustration, if a 5% collar is used with a spot price of 1 BTC=USD$10,000, the collar would be set at between USD$9,500 and USD$10,500.
Accordingly, in embodiments, in substep S5604a, the digital asset exchange computer system 3230 may retrieve a current pricing information (e.g., bid/ask price) from continuous trading order book 5702a associated with a first digital asset pairing and establish a spot price for the first digital asset pairing. As noted above, in embodiments, the spot price may be the average of the current bid/ask price or may be the price used in the last transaction in the continuous trading book, to name a few. In embodiments, the spot price may be a blended digital asset price, in which one or more different order books from one or more digital asset exchanges or index databases may be required to be access to obtain such price. In embodiments, the blended digital asset price may be obtained by being calculated and/or by accessing a blended digital asset price database (not shown). In substep S5604b, the digital asset exchange computer system may establish the collar, for example, based on adding and/subtracting a fixed percentage of the spot price to the spot price as discussed above, for example.
At step S5606, the digital asset exchange computer system 3230 may verify that the first block trade order qualifies as a legitimate transaction. In embodiments, at substep S5606a, the digital asset exchange computer system 3230 may determine whether the price in the block trade order is within the limits of the collar determined in step S5604b (e.g., at or above the collar minimum and at or below the collar maximum). At step S606b, the digital asset exchange computer system 3230 may determine whether the taker has sufficient digital assets and/or fiat to complete the transaction based on information provided in the digital asset ledger 5806 and/or fiat ledger 5808. In embodiments, takers are always required to maintain full-reserve for block trading.
In embodiments, in step S5606, the digital asset exchange computer system 3230 may verify the block characteristics of the first block trade order to confirm that the block characteristics are valid block characteristics. In the case where the side of the transaction is buy, the digital asset exchange computer system 3230 may verify the taker has sufficient amounts of the first fiat or second digital asset as appropriate, to cover the first block trade order if filled in full. In the case where the side of the transaction is sell, the digital asset exchange computer system 3230 may verify the taker has sufficient amounts of the first digital asset to cover the first block trade order if filled in full.
Assuming that the first block trade order qualifies, in step S5608, the digital asset exchange computer system 3230 updates exchange databases, including e.g., a block trading order book 5706a, 5706b, 5706c associated with the digital asset of the order, a digital asset ledger 5806, and/or a fiat ledger 5808 of the taker, as appropriate. In embodiments, the updating process may include substep S5608a in which the digital asset exchange computer system 3230 updates taker's user account in the digital asset ledger 5806 and/or the fiat ledger 5808 as appropriate with block trade order information, and places holds on reserve the full of amount of digital assets and/or fiat being offered in the block trade. As noted above, in embodiments, block trading may require a full reserve on the taker side. In embodiments, the updating process may include substep S5608b in which the digital asset exchange computer system 3230 updates the block trading order book 5706a, 5706b, 5706c with the first block trade.
Thus, in embodiments, upon successful verification of the first block trade order in step S5608, the digital asset exchange computer system 3230 may update a user account associated with the taker to set aside sufficient reserves in the first digital asset, the first fiat and/or the second digital asset sufficient to cover the first block trade order if filled in full. Thereafter, the digital asset exchange computer system 3230 may store on one or more computer readable mediums, a first block order trading book including the first block trade.
In step S5610, the digital asset exchange computer system 3230 publishes to a plurality of n market maker computer systems 3250a, 3250b, . . . 3250n, a quantity and digital asset of the first block trade. An example of a publication of such an indication of interest (IOI) 5904 is shown in
In embodiments, in step S5610, the digital asset exchange computer system 3230 may generate a first indication of interest associated with the first block trade including: (i) the first digital asset as digital asset type; (ii) the digital asset quantity of the first digital asset; (iii) the collar minimum; and (iv) the collar maximum. Thereafter, the digital asset exchange computer system 3230 may publish the first indication of interest to a first plurality of market maker computer systems 3250a, 3250b . . . 3250n, wherein each market maker computer system is associated with a respective market maker.
In step S5612, the digital asset exchange computer system 3230 receives from one or more of the plurality of market maker computer systems 3250a, 3250b . . . 3250n associated with respective market makers, one or more responses relating to at least a portion of the quantity of the first block trade. If no responses are received within a pre-set time period, the block trade order will fail. In
In embodiments, a limited time window (e.g., 1 minute, 5 minute, 10 minute to name a few) may be set in which the digital asset exchange computer system 3230 may accept responses to the indication of interest. In such embodiments, the timer 5804 may be set at the time step S5610 is executed to determine a time-out period. At the end of the limited time window (e.g., when the time-out period expires), the digital asset exchange computer system 3230 will stop accepting responses from market maker computer systems and close the block trading window.
In embodiments, market makers may not be required to maintain full-reserve, and may be granted operational advances. Operational advance limits are preferably fixed, and generally made on a customer-by-customer basis, and can be adjusted from time to time. In embodiments, other operational advance limits may be set. As discussed above, in embodiments, an operational advance ledger 5810 may be maintained by the digital asset exchange computer system 3230 to track, for each market maker, available operational advances.
In embodiments, the digital asset exchange computer system 3230 may verify the validity of each response by each market maker received during the available time period, and only validated responses may be considered. In embodiments, a response which offers a bid that is outside the collar may be rejected. In embodiments, a response which offers an amount outside of the authorized amount for the respective market maker may also be rejected. In embodiments, a response which is not for a least an acceptable minimum amount may also be rejected. In embodiments, a response for an amount of digital assets greater than the indication of interest may also be rejected, and/or applied as if it were for the amount of digital assets included in the indication of interest. In embodiments, other validation criteria may also be applied.
Thus, during a first time period after step S5610, the digital asset exchange computer system 3230 may receive from one or more market maker computer systems of the first plurality of market maker computer systems 3250a, 3250b . . . 3250n, one or more first responses to the first indication of interest. In embodiments, for each response received, the digital asset exchange computer system 3230 further verifies that the respective response is a valid response, coming within the parameters of the first indication of interest. In embodiments, upon verification of the respective response, the digital asset exchange computer system 3230 may update the first block trading order book to including the respective response.
In embodiments, each market maker may be limited to a single response to each indication of interest. In embodiments, each market maker may be authorized to submit more than one response for each indication of interest.
In step S5614, after the block trading window is closed, the digital asset exchange computer system 3230 crosses the first block trade order with the one or more validated responses to complete at least a portion of the first block trade, if possible. In embodiments, only complete block trades may be filled. In embodiments, partial block trades may be filled. In embodiments, matching is accomplished via a set of predetermined matching rules. In embodiments, price is given preference over all other parameters in the market maker responses such that where the block trade order is a “sell” side transaction by the taker, matching will give preference to those responses including a maximum “buy” price. Conversely, in embodiments, where the block trade order is a “buy” side transaction by the taker, matching will give preference to those responses including a minimum “sell” price. Generally, in embodiments, where two or more market makers propose the same matching price, preference may be given to the response received by the digital asset exchange computer system 3230 first. In embodiments, each matching trade will be applied in the designated priority order (e.g., price-time priority) until the order is filled, or the matching responses are exhausted.
In embodiments, upon closing of the block trading window, the digital asset exchange computer system 3230 may identify one or more matching market maker responses associated with respective market makers, by crossing the first block trade order with each of the respective responses in the first order book, to identify based on price-time priority, each of the matching responses to the first block trade order until the earliest of: (i) the first block trade order being filled by matching responses; (ii) no more matching responses are present while less than all of the first block trade order is filled; or (iii) there are no matching responses before the block trading window closes in which case the block trade fails.
In step S5616, the digital asset exchange computer system 3230 notifies at least the taker computer system 3232 and market maker computer systems 3250a, 3250b . . . 3250n associated with market maker(s) who are included in the completed block transfer of the block transfer. In embodiments, neither the taker nor the market makers are informed of the identity of any other party (or parties) to the completed block trade. In embodiments, once the digital asset exchange computer system completes the matching in step S5614, no further action is required by either party to the transaction.
In embodiments, if a block trade order does not result in the order being completely filled as may be determined at step S5620 of
In step S5618, the digital asset exchange computer system updates user accounts (including takers and successful market makers in the block trade order book) based on block changes, and lifts, as appropriate, any unused reserves. This update may include any transactions made with respect to the steps of
The following example illustrates embodiments of the present invention. It is not intended to be limiting. It will be appreciated by those of skill in the art that embodiments may be applied to other use cases not specifically called out herein without departing from the present invention.
At time T1 (the initiation of the process), a taker (Fund X) places an order message 5902 to the digital asset exchange computer system 3230 for a block trade order on the buy side of 1,000 BTC at a maximum price of $10,100. At the time T1, the bid/ask spread from the continuous book is $9,999/$10,001.
In response to receipt of the order message 5902, the digital asset exchange computer system 3230 determines the collar to be $9,500 to $10,500 per BTC based on the bid/ask spread at T1, and verifies the request including that taker (FundX) has sufficient funds to perform the transaction. A fund hold is placed on taker's (FundX's) fiat account until the block trade order process is completed based on the amount of the maximum price of $10,100 (e.g., $10,100×1000 units=$1,010,000, in Example 1).
Thereafter, once the block trade order has been verified, and sufficient fiat to cover taker FundX's maximum price has been reserved, the digital asset exchange computer system 3230 publishes message 5904 (the indication of interest message) to each of the n qualified Market Makers Market Maker 1, Market Maker 2 . . . Market Maker n as also shown in
Market makers may be required to meet a minimum bid requirement (e.g., $50,000 notional in Example 1). In embodiments, market makers can submit multiple price levels on each side.
Once the block order is initiated and published, market makers have a fixed time period (e.g., 1 minute in Example 1) to respond. A timer 5804 (described in connection with
Once these responses are received and the time limit to respond has expired at time T6, the responses 5906a, 5906b and 5906c are crossed with the request 5902 and the block trade order is completed automatically based on the winning matches with no further input from either taker or makers. In Example 1, trades are filled based on price-time priority only and partial fills are permitted. In other words, the best price wins, and if there is a tie, the earliest of the tied prices wins. In embodiments, trades may be filled on other priorities too. The minimum fill size is always at least one block size minimum (e.g., 10 BTC in Example 1) and market makers must quote at least the minimum block size. In Example 1, the trade is completed between Market Maker 1 and taker since Market Maker 1 submitted the best price at the earliest time T3 and that request fills the order.
At time T6, the digital asset exchange computer system 3230 notifies taker that the block trade order is completed in full, via exemplary message 5908a. Separately, the digital asset exchange computer system 3230 notifies Market Maker 1, as the winner, via exemplary message 5908b, that the order has been filled and the amount and price of the transaction and the amount of digital assets that have been advanced. In embodiments, the market makers that made bids which were not accepted, may optionally be notified that their respective bids failed (not shown). In embodiments, only successful market makers will be notified. In Example 1, the continuous book is not crossed for block trades. Trade information for the block trade order in response to request 5902 may be published on a delayed basis, such as a fixed period (e.g., 10 minutes in Example 1) after the block trade order is completed (time T6 in Example 1).
As in
In response to receiving the order message 5902, the digital asset exchange computer system 3230 determines the collar to be $9,500 to $10,500 per BTC based on the bid/ask spread at T1, and verifies the request as noted above. A fund hold is placed on taker FundX's fiat account until the block trade order process is completed based on the amount of the maximum price of $10,100 (e.g., $10,000×1000 units=$1,010,000, in Example 2).
Thereafter, once the block order has been verified, and sufficient fiat to cover taker's (FundX's) maximum price has been reserved, the digital asset exchange computer system 3230 publishes message 5904 including the indication of interest message to each of the n qualified market makers, Market Maker 1, Market Maker 2 . . . Market Maker n, as also shown in
As with Example 1, market makers may be required to meet a minimum bid requirement (e.g., $50,000 notional in Example 2). In embodiments, market makers are submitting multiple price levels on each side.
Once the block order is initiated and published to the market makers, they have a fixed time period (e.g., 1 minute in Example 2) in which to respond. Timer 5804 may be set to track this time-out period. In Example 2, as illustrated in
Once these responses are received and the time limit has expired at time T9′, the responses 5906a′, 55906b′, 5906c′, 5906d′, 5906e′, 5906f are crossed with the request 5902 and the block trade order is completed automatically as noted above. The trade in Example 2 is partially filled by Market Maker 1 and Market Maker 3, as the matches that meet the price-time priority within the parameters of the block trade order book for request 5902. In particular, Market Maker 1 sells 300 BTC to taker at a price of $10,020, 300 BTC to taker at a price of $10,050 while Market Maker 3 sells 100 BTC to taker at a price of $10,050.
At time T9, the digital asset exchange computer system 3230 notifies taker that the block trade order is partially filled and the prices at which partial fulfilment took place in the exemplary message 5908a′. The digital asset exchange computer system 3230 also notifies Market Maker 3 of that that one of their offers has been accepted and the terms of the accepted offer via exemplary message 5908c′. Separately, the digital asset exchange computer system 3230 notifies Market Maker 1, as another partial winner, via exemplary message 5908b′, that the their offers have been accepted and filled and the amount and prices of these transactions.
Since taker's order is only partially fulfilled, the digital asset exchange computer system 3230 may offer one or more successful market makers the opportunity to fulfill the remainder of taker's order. In embodiments, the successful market makers may be offered the opportunity to fulfill the remainder of taker's order. In embodiments, the market maker offering the best price, Market Maker 1 in Example 2, is offered the opportunity to fulfill the remainder of the order at the best price in message 5908b′. In embodiments, market makers must respond to the opportunity to fulfill the remainder of the order within a second time limit (e.g. 5 seconds, 10 second or 15 seconds to name a few). In embodiments, Market Maker 3, may be offered an opportunity to fulfill the remainder of the taker's order in message 5908c′, if Market Maker 1 does not accept this opportunity within the time limit. In other embodiments, Market Maker 1 and Market Maker 3 may each be offered the opportunity to fulfill a portion of the remainder of the order in the messages 5908b′ and 5908c′. In embodiments, all of the market makers may be offered the opportunity to fulfill the remainder of the order with the market maker first to respond with the best price being awarded the remainder of the order. In embodiments, the remainder may run as a new order book, with either the same time limits, or shorter time limits. In any event, as in
In Step S11402, a first designated key pair, including a first designated public key of an underlying digital asset and a corresponding first designated private key, which is mathematically related, is provided. The underlying digital asset may be maintained on a distributed public transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network in the form of the blockchain (such as the Ethereum blockchain or NEO blockchain). The first designated private key may be stored on a first computer system which is connected to the distributed public transaction ledger through the Internet (e.g., in a hot wallet).
In Step S11404, a second designated key pair, including a second designated public key of the underlying digital asset and a corresponding second designated private key, which is mathematically related, is provided. The second designated private key is stored on a second computer system which is physically separated from the first computer system and is not operatively or physically connected to the distributed public transaction ledger or the Internet (e.g., a cold wallet).
In embodiments, additional off-line designated key pairs may also be provided.
In Step S11406, first smart contract instructions for a stable value digital asset token associated with a first contract address associated with the underlying digital asset are also provided. The smart contract instructions are saved in the blockchain for the underlying digital assets and include instructions for: (1) token creation; (2) token transfer; (3) token destruction; (4) authorization instructions for the first designated key pair; and (5) authorization instructions for the second designated key pair. In embodiments, these smart contract instructions may be contained in one or a plurality of contract addresses, as discussed above.
Referring to
In Step S11410, the digital asset token issuer system confirms receipt of the second sum of fiat.
In Step S11412, digital asset token issuer system determines whether the first designated key pair has authority to obtain the first sum of stable value digital asset tokens.
Referring to
Referring to
Referring to
In embodiments, in Step S11416, the digital asset token issuer system may receive a second request to obtain a third sum of stable value digital asset tokens in exchange for a fourth sum of fiat. The third sum corresponds to the fourth sum based on the fixed ratio of stable value digital asset token to fiat (e.g., 1 SV Coin Token=1 USD). The second request may come from a second requesting user with an associated second requester key pair, including a second request public key of the underlying asset and a corresponding second request private key, which are mathematically related.
In Step S11418, the digital asset token issuer system confirms receipt of the fourth sum of fiat.
In Step S11420, the digital asset token issuer system, determines whether the first designated key pair has authority to obtain the third sum.
In the case where the digital asset token issuer system determines in Step S11420 that the first designated key pair does not have authority to obtain the third sum, in Step S11422, the digital asset token issuer system determines whether the second designated key pair has authority to obtain the third sum.
Referring to
Referring to
In Step S11424, the digital asset token issuer system confirms that the third sum of stable value digital asset tokens have been obtained and transferred to the second request public key based on reference to the blockchain.
In embodiments, the step of sending, from the second portable memory device to the plurality of geographically distributed computer systems, the second digitally signed instructions comprises the further steps of transferring, form the second portable memory device to the digital asset computer system, the second digitally signed instructions; and transferring, from the digital asset computer system to the plurality of geographically distributed computer systems, the second digitally signed instructions.
Referring to
Referring to
In Step S11202, the Security Token issuer (who will generally by a registered user with the digital asset exchange) will log into the digital asset exchange. In embodiments, the SVCoin issuer is any trusted entity, including a digital asset exchange, bank, trust or other trusted entity. In embodiments, the Security Token issuer will be an authorized user, or otherwise qualified with respect to the trusted entity. In embodiments, the trusted entity may act as agent of the Security Token issuer to generate, distribute and maintain a ledger of SVCoins on behalf of the Security Token issuer.
In Step S11204, the Security Token issuer system, or any trusted entity system acting as agent, will navigate to the dashboard Security Token interface to initiate a request for transfer of SVCoins to Security Token holders. While for purposes of illustration, the request is made via the dashboard Security Token interface, those of skill in the art will appreciate that the request may be made via AP1 calls, submitted by electronic mail, and/or other electronic interactions, consistent with embodiments of the invention. In embodiments, the request shall identify: (i) the Security Token; (ii) the total amount of SVCoins to be distributed; (iii) the Security Token holder's digital asset addresses; (iii) the amount of SVCoins to be distributed to each digital asset address; and/or (iv) other information sufficient to calculate or otherwise determine this information. In embodiments, this information may be provided by providing the digital asset exchange, or other trusted entity system acting on behalf of the SVCoin issuer, with the access to the Security Token database, which would include the list of all current Security Token holders and their respective digital asset address and Security Token balances. In embodiments, the Security Token database may include a list of all current Security Token holders and digital asset addresses associated with each. In such embodiments, the Security Token issuer, may still need to provide the digital asset exchange system, or other trusted entity system, with the amount of SVCoins to be distributed, either individually and/or in total and how to prorate the distribution among Security Token holders.
In Step S11206, the digital asset exchange system, or other trusted entity system, may analyze and verify that the request can be properly processed. In step S11206-a, the digital asset exchange system, as the SVCoin issuer or on behalf of the SVCoin issuer, may verify that the user has sufficient fiat currency maintained at the digital asset exchange to cover the transaction, including a sufficient amount of fiat to cover the amount of SVCoin being acquired, as well as any transaction fees that may be charged. If the user does not have sufficient fiat in the system, the transaction may be terminated for insufficient funds. In embodiments, the user may be provided an opportunity to obtain sufficient funds, by, e.g., selling digital assets maintained by the user on the digital asset exchange or by making a deposit of additional fiat. In step S11206-b, the digital asset exchange system, may also verify that the digital asset addresses, provided are each a valid digital asset addresses. To the extent any digital asset addresses are not verified, the transaction may be rejected, and/or the digital asset exchange system may enter into a reconciliation process with the Security Token issuer system or trusted entity system.
At step S11206-c, the digital asset exchange system, or other trusted entity system, may determine an amount of SVCoins to be distributed to each of the digital addresses of the Security Token holders. In embodiments, this determination may be made based on the total number of Security Token holders and the total amount of SVCoins requested by the Security Token issuer. In embodiments, the Security Token issuer may designate a specific sum of SVCoins per Security token. In embodiments, a total amount of SVCoins to be purchased may be designated in the request of the Security Token issue with directions to equally or proportionally divide the total sum between the Security Token holders.
In S11208, after the digital asset exchange system, or other trusted entity system, has confirmed that the user has sufficient fiat to cover the transaction, the digital asset exchange system may initiate the process of generating the requested SVCoin.
In S11208-a, the digital asset exchange system, or other trusted entity system, may debit the designated fiat funds from a fiat ledger associated with the Security Token issuer user account, and credit a corresponding amount of fiat to the SVCoin fiat ledger to be held in trust by the exchange. In embodiments, this fiat is held in a custodial account of the exchange or an agent of the exchange.
In S11208-b, the digital asset exchange system, or other trusted entity system, shall generate instructions to generate the requested SVCoin tokens, including instructions to update the SVCoin token ledger database to reflect the addition of the new tokens and the corresponding digital asset addresses associated with such new SVCoin tokens.
In S11208-c, the digital asset exchange system, or other trusted entity system, shall publish to the blockchain network (e.g., the Ethereum Network) the transaction with instructions to be recorded by the blockchain network. In embodiments, a transaction fee may be required by, e.g., a miner, to process and add the requested transaction on the blockchain.
In embodiments, where SVCoin tokens have already been created and are maintained by the digital asset exchange system on reserve, S11208 may be replaced with S11208′ as follows. In step S11208-a′, the digital asset exchange system, or other trusted entity system, may debit the designated fiat funds from a fiat ledger associated with the Security Token issuer user account, and credit a corresponding amount of fiat to the SVCoin fiat ledger to be held in trust by the exchange, or otherwise reserved by the trusted entity.
At step S11208-b′, the digital asset exchange computer system, or other trusted entity system may then determine a portion of the reserve for transfer based on the requested amount of SVCoin identified by the Security Token issuer for transfer to the Security Token holder(s).
At step S11208-c′, the digital asset exchange computer system, or other trusted entity system may update the SVCoin token ledger to change the address associated with the determined portion of the reserve SVCoin tokens to the address, or addresses, associated with the Security Token holder.
In S11210, the digital asset exchange computer system may send a message to the Security Token issuer registered user, and/or each of the designated digital asset addresses to reflect that the transaction was successfully processed. In embodiments, such messages may include information including: (i) digital asset address; (ii) the amount of tokens generated/or determined for transfer; and/or (iii) the new balances for the digital asset address or digital wallet associated therewith, to name a few. In embodiments, the message may include additional information related to the Security Token, including: (iv) the amount of the Security Token held; (v) the dividend issued; and/or (vi) instructions on how to redeem the SVCoin.
The following examples illustrate embodiments of the present invention. They are not intended to be limiting. It will be appreciated by those of skill in the art that embodiments may be applied to other use cases not specifically called out herein, without departing from the present invention.
In embodiments, shares in a real estate investment trust (“REIT Trust”) may be issued using a digital asset, such as a token on the Ether Network (“REIT Token”). The REIT Trust may hold income generating property such as real estate which is leased. As the income generating property generates fiat profits which are intended to be distributed to shareholders, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the REIT Trust) to REIT Token holders at the respective REIT Token holder's digital asset addresses associated with the Ether Wallet holding the REIT Token.
In embodiments, the income generating property may generate profits in the form of digital assets. For example, one or more individuals may pay rent in one or more of: an SVCoin, a fiat-backed digital asset, a digital math-based asset, a digital asset, and/or a combination thereof, to name a few. The profits generated, which may be intended to be distributed to shareholders, may be deposited with a digital asset exchange and/or a digital asset exchange computer system, such as a regulated digital asset exchange like Gemini. In the case where profits are collected in SVCoin, the SVCoin may be distributed on a pro-rata basis (or as otherwise instructed by the REIT Trust) to REIT Token holders at the respective REIT Token holder's digital asset addresses associated with the Ether Wallet holding the REIT Token. In the case where profits are not collected in SVCoin, the digital assets may be converted into a SVCoin by the digital asset exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the REIT Trust) to REIT Token holders at the respective REIT Token holder's digital asset addresses associated with the Ether Wallet holding the REIT Token.
REIT Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, shares in an Energy Master Limited Partnership (“Energy MLP”) may be issued using a digital asset, such as a token on the Ether Network (“Energy MLP Token”). The Energy MLP may offer shares (otherwise known as “units”) in the form of a digital asset, such as Energy MLP Tokens that are publicly traded and which generate dividends to the shareholders. As the dividends are distributed on a periodic basis in the form of fiat currency, a corresponding amount of fiat is deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the Energy MLP) to Energy MLP Token holders at the respective Energy MLP Token holder's digital asset addresses associated with the Ether Wallet holding the Energy MLP Token.
Energy MLP Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, equity shares corresponding to a stock certificate in an entity may be issued using a digital asset, such as a token on the Ether Network (“Equity Token”). As dividends based on the Equity Token are generated for distribution to shareholders, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the entity distributing the shares) to Equity Token holders at the respective Equity Token holder's digital asset addresses associated with the Ether Wallet holding the Equity Token.
Equity Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, shares in a Venture Capital fund (“VC Fund”) may be issued using a digital asset, such as a token on the Ether Network (“VC Token”). As the VC Fund generates returns to be distributed to investors in the VC Fund, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the VC Fund) to VC Token holders at the respective VC Token holder's digital asset addresses associated with the Ether Wallet holding the VC Token.
VC Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, shares in a Private Equity fund (“PE Fund”) may be issued using a digital asset, such as a token on the Ether Network (“PE Token”). As the PE Fund generates returns to be distributed to investors in the PE Fund, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the PE Fund) to PE Token holders at the respective PE Token holder's digital asset addresses associated with the Ether Wallet holding the PE Token.
PE Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, digital certificate of deposits (“Digital CD”) may be issued using a digital asset, such as a token on the Ether Network (“CD Token”). As interest amounts are generated based on the terms of the certificate of deposits, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. Upon maturity of the Digital CD (or before maturity), the SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the Digital CD issuer and/or less any premature withdrawal penalty) to CD Token holders at the respective CD Token holder's digital asset addresses associated with the Ether Wallet holding the CD Token.
CD Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, digital bonds may be issued using a digital asset, such as a token on the Ether Network (“Bond Token”). As interest amounts are generated based on the coupon rates of the digital bonds, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the digital bond issuer) to Bond Token holders at the respective Bond Token holder's digital asset addresses associated with the Ether Wallet holding the Bond Token.
Bond Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, a peer-to-peer lending service (“P2P Service”) may issue a digital asset, such as a token on the Ether Network (“P2P Loan Token”). As lending amounts and interest payments are distributed, corresponding amounts of fiat is deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the lender/borrower) to P2P Loan Token holders at the respective P2P Loan Token holder's digital asset addresses associated with the Ether Wallet holding the P2P Loan Token.
P2P Loan Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, a Crowdfunding service may issue a digital asset, such as a token on the Ether Network (“CF Token”). As funds are collected, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the Crowdfunding service) to CF Token holders at the respective CF Token holder's digital asset addresses associated with the Ether Wallet holding the CF Token.
CF Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, a Real Estate Crowdsourcing services may issue a digital asset, such as a token on the Ether Network (“RE Token”). As funds are collected, a corresponding amount of fiat is to be deposited with a digital asset exchange, such as a regulated digital asset exchange like Gemini. The fiat is then converted into a SVCoin by the Exchange. The SVCoin may then be distributed on a pro-rata basis (or as otherwise instructed by the Real Estate Crowdsourcing service) to RE Token holders at the respective RE Token holder's digital asset addresses associated with the Ether Wallet holding the RE Token. RE Token holders may then use the SVCoin as a digital asset to conduct other transactions. Eventually, the SVCoin can be exchanged for fiat at the exchange based on the notional value (e.g., 1 SVCoin=1 dollar).
In embodiments, tokens may be issued against an artistic work, such as a song or movie (DR Token), for example, as a token on the Ethereum network. As royalties are collected for use of the song or movie, a corresponding amount of fiat may be deposited with a digital asset exchange. The fiat may be converted into SVCoin and distributed on a pro-rata basis to the rights holders who are DR Token holders. More specifically, the SVCoin may be transferred the digital asset address associated with a wallet of a DR Token holder as a payment of royalties.
In embodiments, of the examples discussed above, the token holders may instigate payment of SVCoin by sending a request for payment. In this case, any transaction fees will be the responsibility of the token holder. In embodiments, the token issuer, or an agent thereof, may implement or instruct distribution of payments in which case transaction fees are the responsibility of the token issuer.
The process described in
In step S11702 of
At step S11702B, the digital asset exchange computer system determines that the first user device is authorized to access the digital asset exchange computer system based at least on the first user credential information. In embodiments, the digital asset exchange computer system may further determine that the first user is a registered user of the digital asset exchange. In embodiments, the digital asset exchange may be licensed by a government regulatory authority.
At step S11702C, the digital asset exchange computer system generates first graphical user interface (GUI) information for displaying a first graphical user interface on the first user device. In step S11702D, the digital asset exchange computer system transmits the first graphical user interface information to the first user device.
Referring back to
In step S11704B, in response to receiving the first electronic deposit request, the digital asset exchange computer system obtains first account balance information of the first user indicating a first amount of available fiat for the first user held by the digital asset exchange on behalf of the first user. In embodiments, the digital asset exchange computer system obtains the first amount of available fiat from a fiat account ledger database stored on a computer readable member accessible by the digital asset exchange computer system.
In step S11704C, the digital asset exchange computer system obtains a user specific destination address. The user specific destination address may be uniquely associated with the first user. In step S11704D, the digital asset exchange computer system generates second graphical user interface information including at least the first account balance information and the user specific destination address. In embodiments, the graphical user interface described in step S11704C may be the graphical user interface shown in connection with
At step 1704E, the digital asset exchange computer system may transmit the second graphical user interface information to the first user device. In embodiments, this may cause the first user device to display the graphical user interface shown in connection with
In step 1704F, the digital asset exchange computer system may receive a second electronic deposit request form the first user device. In embodiments, the second electronic deposit request may comprise at least: (1) a first amount of stable value digital asset tokens to be deposited; (2) a designated public address of the first user on the underlying blockchain from which the first amount of stable value digital asset tokens will be transferred; and (3) a digital signature based on a designated private key of the first user. In embodiments, the designated private key of the first user is mathematically related to the designated public address of the first user.
In embodiments, the designated private key of the first user may be stored in a custodial system, the custodial system may be part of digital asset exchange computer system, the administrator system, the stable value token issuer system or a third party system and may be accessed to provide the digital signature based on authorization of the first user. In embodiments, the first user may authorize transactions based on authentication information. In embodiments, the authentication information may include a user name and password associated with the first user. In embodiments, multi-fact verification may be necessary in order for the first user to authorize the custodial system to access the designated private key and provide a digital signature to authorize a transaction. In embodiments, the multi-fact verification may include the use of an authorization code that is sent to a predetermined user device, e-mail address, or mobile phone number, to name a few, associated with the first user, for example, as used in AUTHY® (AUTHY® is a registered trademark of Twilio, Inc.). In embodiments, other multi-factor verifications may be used, such as identification of a user device associated with the first user based on phone number or mobile network, location information and shared secret verification, to name a few.
Referring back to
In step S11706B, the digital asset exchange computer system determines that the first amount of stable value digital asset tokens is present at the designated public address of the first user. In the case where the first amount of stable value digital asset tokens is present at the designated public address of the first user, as indicated in step S11706C, the digital asset exchange computer system determines a third amount of fiat associated with an updated amount of available fiat of the first user. In embodiments, the third amount of fiat equals the first amount of available fiat of the first user plus the second amount of fiat.
At step 1706D, the digital asset computer system updates the fiat account ledger to reflect that the updated amount of available fiat of the first user is the third amount of fiat. At step S11706E, the digital asset exchange computer system generates a first transaction request for the blockchain from a first digital asset exchange public key address on the blockchain to a first contract address associated with a stable value token issuer. In embodiments, the first digital asset exchange public key address is mathematically related to a first digital asset exchange private key which is stored in the computer readable member accessible by the digital asset exchange computer system.
In embodiments, the first transaction request includes: (1) a request to obtain the first amount of stable value digital asset tokens from the designated public address of the first user; and (2) a request to destroy the first amount of stable value digital asset tokens. In alternative embodiments, the first transaction request may include: (1) a request to obtain the first amount of stable value digital asset tokens from the designated public address of the first user; and (2) a request to provide the first amount of stable value digital asset tokens to a specific destination address. In embodiments, the first transaction request is signed with a generated digital signature based on the digital asset exchange private key of the digital asset exchange.
In step S11706F, the digital asset exchange computer system may update a stable value digital asset token issuer fiat ledger. The update may decrease the balance of fiat by the second amount of fiat. In embodiments, the digital asset exchange computer system may transfer the second amount of fiat from a stable value digital asset token issuer to a digital asset exchange fiat account. In embodiments, the digital asset exchange computer system may periodically transfer fiat between a stable value digital asset token issuer fiat account and a digital asset exchange fiat account based on net transactions over a predetermined period of time.
At step S11706G, the digital asset exchange computer system may transmit the first transaction request to the blockchain network via the Internet. In step, S11706H, the digital asset exchange system confirms, via reference to the blockchain, that the first amount of stable value digital asset tokens is not present at the designated public address of the first user.
In step S11602 of
At step S11602B, the digital asset exchange computer system determines that the first user device is authorized to access the digital asset exchange computer system based at least on the first user credential information. In embodiments, the digital asset exchange computer system may further determine that the first user is a registered user of the digital asset exchange. In embodiments, the digital asset exchange may be licensed by a government regulatory authority.
At step S11602C, the digital asset exchange computer system generates first graphical user interface (GUI) information for displaying a first graphical user interface on the first user device. In step S11602D, the digital asset exchange computer system transmits the first graphical user interface information to the first user device.
Referring back to
In step S11604B, the digital asset exchange computer system obtains first account balance information of the first user indicating a first amount of available fiat for the first user held by the digital asset exchange on behalf of the user. The digital asset exchange computer system may obtain the first account balance from a fiat account ledger database stored on computer readable member accessible by the digital asset exchange computer system.
In step S11604C, the digital asset exchange computer system generates second graphical user interface information including at least the first account balance information. In step S11604D, the digital asset exchange computer system transmits the second graphical user interface information to the first user device. In embodiments, the first user device may display the second graphical user interface in response to this transmission. For example, the first user device may display the graphical user interface shown in connection with
In step S11604E, the digital asset exchange computer system receives a second electronic withdrawal request from the first user device. The second electronic withdrawal request may comprise at least: (1) a first amount of stable value digital asset tokens to be withdrawn; and (2) a destination public address on the underlying blockchain to transfer the first amount of stable value digital asset tokens.
Referring back to
At step S11606B, the digital asset exchange computer system determines that the second amount of fiat is less than the first amount of available fiat of the first user. In step 1606C, where the second amount of fiat is less than the first amount of available fiat of the first user, the digital asset exchange computer system determines a third amount of fiat associated with an updated amount of available fiat of the first user. In embodiments, the third amount of fiat equals the first amount of available fiat of the first user less the second amount of fiat.
In step S11606D, the digital asset exchange computer system updates the fiat ledger database to reflect the updated amount of available fiat. In step S11606E, the digital asset exchange computer system updates a stable value digital asset token issuer fiat ledger, increasing the balance of fiat by the second amount of fiat. In embodiments, the digital asset exchange computer system may transfer the second amount of fiat from a digital asset exchange fiat account to a stable value digital asset token issuer fiat account. In embodiments, the digital asset exchange computer system may periodically transfer fiat between the digital asset exchange fiat account and the stable value digital asset token issuer fiat account.
In step S11606F, the digital asset exchange computer system generates a first transaction request for the blockchain network from a first digital asset exchange public key address on the blockchain to a first contract address associated with a stable value digital asset token issuer. In embodiments, the first digital asset exchange public key is mathematically related to a first digital asset exchange private key which is stored in the computer readable member accessible by the digital asset exchange computer system. The first transaction request may comprise a first message including a request to obtain in the first designated public address the first amount of stable value digital asset tokens. In embodiments, the first transaction request is signed with a digital signature generated using at least the digital asset exchange private key. In embodiments, the request to obtain may further include a request to generate the first amount of stable value digital asset tokens at the first designated public address of the first user. In embodiments, the request to obtain may include a request to transfer the first amount of stable value digital asset tokens from a stable value digital asset token issuer public address to the first designated public address of the first user.
In step S11606G of
In embodiments, as noted above, customers may exchange U.S. dollars for Gemini Dollar tokens at a 1:1 exchange rate, for example, by initiating a withdrawal of Gemini Dollar tokens from their digital asset exchange account to any Ethereum address they specify. The U.S. dollar amount of Gemini Dollar tokens will be debited from the customer's exchange account balance at the time of withdrawal. In embodiments, as noted above, customers may exchange U.S. dollars for a fiat-backed digital asset at an exchange rate based on the value of the fiat-backed digital asset, for example, by initiating a withdrawal of Libra Tokens from their account to any public address associated with an account on a peer-to-peer network.
In embodiments, one or more users may withdraw stable value digital assets from a trusted third party. The user, in embodiments, may not be a user of the administrator of the stable value digital asset, the digital asset exchange computer system, and/or the network associated with the stable value digital asset, to name a few. For example, a first user of Trusted Entity A may want to withdraw 100 Gemini Dollars. The first user, continuing the example, may transmit a request to Trusted Entity A for 100 Gemini Dollars. Trusted Entity A, in embodiments, may generate and send a transaction request for 100 Gemini Dollars, using fiat and/or other digital assets owned by the first user. Trusted Entity A may receive 100 Gemini Dollars in an account associated with Trusted Entity A. The 100 Gemini Dollars may then be transferred to the first user by Trusted Entity A.
The process of withdrawing fiat-backed digital assets from a digital asset exchange may be similar to the process discussed above in connection with
In embodiments, first user device, as used herein, may, in embodiments, correspond to one or more suitable types of electronic devices including, but not limited to, desktop computers, mobile computers (e.g., laptops, ultrabooks), servers, mobile phones, portable computing devices, such as smart phones, tablets and phablets, televisions, set top boxes, smart televisions, personal display devices, personal digital assistants (“PDAs”), gaming consoles and/or devices, virtual reality devices, smart furniture, smart household devices (e.g., refrigerators, microwaves, etc.), smart vehicles (e.g., cars, trucks, motorcycles, etc.), smart transportation devices (e.g., boats, ships, trains, airplanes, etc.), and/or wearable devices (e.g., watches, pins/broaches, headphones, etc.), to name a few. In some embodiments, first user device may be relatively simple or basic in structure such that no, or a minimal number of, mechanical input option(s) (e.g., keyboard, mouse, track pad) or touch input(s) (e.g., touch screen, buttons) are included. For example, first user device may be able to receive and output audio, and may include power, processing capabilities, storage/memory capabilities, and communication capabilities. However, in other embodiments, first user device may include one or more components for receiving mechanical inputs or touch inputs, such as a touch screen and/or one or more buttons.
The first user device may, in embodiments, be a voice activated electronic device. A voice activated electronic device, as described herein, may correspond to any device capable of being activated in response to detection of a specific word (e.g., a word, a phoneme, a phrase or grouping of words, or any other type of sound, or any series of temporally related sounds). For example, a voice activated electronic device may be one or more of the following: Amazon Echo®; Amazon Echo Show®; Amazon Echo Dot®; Smart Television (e.g., Samsung® Smart TVs); Google Home®; Voice Controlled Thermostats (e.g., Nest®; Honeywell® Wi-Fi Smart Thermostat with Voice Control), smart vehicles, smart transportation devices, wearable devices (e.g., Fitbit®), and/or smart accessories, to name a few.
In embodiments, the first user device may include one or more processor(s), memory, and a communication portal. One or more processor(s), may include any suitable processing circuitry capable of controlling operations and functionality of first user device, as well as facilitating communications between various components within first user device. In some embodiments, processor(s) may include a central processing unit (“CPU”), a graphic processing unit (“GPU”), one or more microprocessors, a digital signal processor, or any other type of processor, or any combination thereof. In some embodiments, the functionality of processor(s) may be performed by one or more hardware logic components including, but not limited to, field-programmable gate arrays (“FPGA”), application specific integrated circuits (“ASICs”), application-specific standard products (“ASSPs”), system-on-chip systems (“SOCs”), and/or complex programmable logic devices (“CPLDs”). Furthermore, each of processor(s) may include its own local memory, which may store program systems, program data, and/or one or more operating systems. However, processor(s) may run an operating system (“OS”) for the first user device, and/or one or more firmware applications, media applications, and/or applications resident thereon. In some embodiments, processor(s) may run a local client script for reading and rendering content received from one or more websites. For example, processor may run a local JavaScript client for rendering HTML or XHTML content received from a particular URL accessed by the first user device.
In embodiments, as mentioned above, the first user device may also include memory. Memory may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store data for the first user device. For example, information may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof. Furthermore, memory may be implemented as computer-readable storage media (“CRSM”), which may be any available physical media accessible by processor(s) to execute one or more instructions stored within memory. In some embodiments, one or more applications (e.g., mobile application software, gaming, music, video, calendars, lists, banking, social media etc.) may be run by processor(s) and may be stored in memory.
In embodiments, as mentioned above, the first user device may also include a communications portal. The communications portal may include any circuitry allowing or enabling one or more components of the first user device to communicate with one another, with the digital asset exchange computer system, and/or with one or more additional devices, servers, and/or systems. As an illustrative example, data retrieved from memory of the first user device may be transmitted via a network, to the digital asset exchange computer system using any number of communications protocols. For example, the network may be accessed using Transfer Control Protocol and Internet Protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), Hypertext Transfer Protocol (“HTTP”), WebRTC, SIP, and wireless application protocol (“WAP”), are some of the various types of protocols that may be used to facilitate communications between the first user device and the digital asset exchange computer system. In some embodiments, the first user device and the digital asset exchange computer system may communicate with one another via a web browser using HTTP. Various additional communication protocols may be used to facilitate communications between the first user device and/or the digital asset exchange computer system, include the following non-exhaustive list, Wi-Fi (e.g., 802.11 protocol), Bluetooth, radio frequency systems (e.g., 900 MHz, 1.4 GHz, and 5.6 GHz communication systems), cellular networks (e.g., GSM, AMPS, GPRS, CDMA, EV-DO, EDGE, 3GSM, DECT, IS 136/TDMA, iDen, LTE or any other suitable cellular network protocol), infrared, BitTorrent, FTP, RTP, RTSP, SSH, and/or VOIP.
The communications portal may use any communications protocol, such as any of the previously mentioned exemplary communications protocols. In some embodiments, the first user device may include one or more antennas to facilitate wireless communications with a network using various wireless technologies (e.g., Wi-Fi, Bluetooth, radiofrequency, etc.). In yet another embodiment, the first user device may include one or more universal serial bus (“USB”) ports, one or more Ethernet or broadband ports, and/or any other type of hardwire access port so that the communications portal allows the first user device to communicate with one or more communications networks.
The digital asset exchange computer system and/or the digital asset exchange, in embodiments, may also each include one or more processor(s), network connection interface, and memory. The one or more processor of the digital asset exchange computer system and/or the digital asset exchange, as used herein, may be similar to the one or more processor(s) described above, the description of which applying herein. The network connection interface of the digital asset exchange computer system and/or the digital asset exchange may be similar to the communication portal described above, the description of which applying herein. Memory of the digital asset exchange computer system and/or the digital asset exchange may be similar to the memory described above, the description of which applying herein. In embodiments, the digital asset exchange computer system may be similar to exchange computer system 3230 and/or exchange computer system 3210, the descriptions of which applying herein. In embodiments, the digital asset exchange computer system and/or the digital asset exchange may be a trusted entity, an administrator, and/or a portal, to name a few.
The process of authenticating an access request in embodiments, may be performed via the steps illustrated in
The process of authenticating an access request may continue with step S14810. At step S14810, the digital asset exchange computer system determines that the first user device is authorized to access the digital asset exchange computer system. In embodiments, the digital asset exchange computer system may authorize the first user device based on the first user credentials. For example, the digital asset exchange computer system may obtain verified first user credentials (e.g. credentials associated with the first user that are already verified) by accessing (via e.g. authenticator module 5124) one or more user identification data bases (e.g. user identification data 5110, user authentication data 5112) that store the verified first user credentials. Once obtained, the verified first user credentials may be compared to the received first user credentials by the digital asset exchange computer system. If the received first user credentials do not match the verified first user credentials, the digital asset exchange computer system may determine that the first user is not authorized to access the digital asset exchange computer system. If the received first user credentials are not authorized, the process of
In embodiments, the digital asset exchange computer system may further verify the first user credentials. The digital asset exchange computer system may determine whether the first user is a registered user of the digital asset exchange associated with the digital asset exchange computer system. The verification process may be similar, with verified registered user credentials being compared to the first user credentials. In embodiments, the first user may be authorized to access the digital asset exchange computer system, but not a registered user. In embodiments, the digital asset exchange may be a government regulated authority.
The process of authenticating an access request may continue with step S14812. At step S14812 the digital asset exchange computer system may generate first graphical user interface information. In embodiments, the first graphical user interface information may be for displaying a graphical user interface on the first user device. For example, the first graphical user interface information may include first machine-readable instructions representing one or more of the following: (1) a home page of a website or mobile application associated with the digital asset exchange computer system; and/or (2) a log-in success message and/or home page, to name a few.
The process of authenticating an access request may continue with step S14814. At step S14814, the digital asset exchange computer system may transmit the first graphical user interface information to the first user device via a network. In embodiments, upon receipt of the first graphical user interface information, the first user device displays the graphical user interface associated with the graphical user interface information on a display of the first user device. For example, the digital asset exchange computer system may send the first machine-readable instructions to the first user device, and, upon receiving the first machine-readable instructions, the first user device executes the first machine-readable instructions which may cause the first GUI to be displayed on a display screen of the first user device.
Referring back to
In embodiments, the fiat-backed digital asset may be tied to a distributed transaction ledger which may be maintained on a peer-to-peer network that includes a plurality of geographically distributed computer systems. In embodiments, the distributed transaction ledger may be public, private, semi-private, and/or semi-public, to name a few. For example, the distributed transaction ledger may be published publicly available to anyone who wants to see it. As another example, the distributed transaction ledger may not be published and, to be able to access the distributed transaction ledger, a user may send a query the peer-to-peer network.
The peer-to-peer network, in embodiments, may be: the Ethereum Network, the Libra Network, the Neo Network, the Bitcoin Network, and/or the Stellar Network, to name a few. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of work. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of stake. The peer-to-peer network, in embodiments, may be based on a cryptographic mathematical protocol. In embodiments, the peer-to-peer network may be based on a mathematical protocol that is open sourced. In embodiments, the digital asset security token database, in embodiments, may be stored on computer readable media associated with a digital asset security token issuer system (e.g. memory of the digital asset security token issuer system). In embodiments, the digital asset security token database may be maintained and stored on the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the distributed transaction ledger may include a fiat-backed digital asset database. In embodiments, the fiat-backed digital asset data base may be maintained on a sidechain. A sidechain, in embodiments, may refer to a portion of the distributed transaction ledger. For example, an administrator, user, and/or trusted entity may maintain a portion of the distributed transaction ledger and/or an electronic copy of a portion of the distributed transaction ledger. A trusted entity in embodiments, and as used herein, may refer to one or more of: a trusted entity, a digital asset exchange, a portal (e.g. MasterCard, Visa, to name a few), a digital asset exchange, an administrator, and/or a custodian, to name a few. In embodiments, a portion of the distributed transaction ledger, in the context of a Merkel Tree, may refer to one or more “leafs” of the Merkel Tree, one or more statuses of the Merkel Tree, and/or a complete Merkel Tree with one or more past transactions being “pruned.” In the context of a blockchain, the portion of the distributed transaction ledger may be one or more blocks of the blockchain. The information on the sidechain may be updated periodically or aperiodically. For example, the information on the sidechain may be updated, published, and stored on the peer-to-peer network at predetermined times (e.g. twice a day, once a day, once a week, once a month, and/or once a quarter, to name a few). As another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the execution of a transaction and/or the execution of a batch of transactions. As yet another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the commitment of a transaction and/or the commitment of a batch of transactions. A transaction, for example, may be committed by a consensus of trusted entities of the peer-to-peer network.
In embodiments, the peer-to-peer network may utilize one or more protocols and/or programs for security purposes. For example, the peer-to-peer network may utilize a byzantine fault tolerance protocol as a consensus mechanism. As another example, the peer-to-peer network may utilize a whitelist for the execution of a transaction and/or the transfer of funds. As yet another example, the peer-to-peer network may also utilize one or more of the following: encryption, point-to-point encryption, two-factor authentication, and/or tokenization, to name a few.
The process for obtaining a withdrawal request may continue with step S14818. At step S14818, in response to receiving the first request to withdraw fiat-backed digital assets, the digital asset computer system may obtain first account balance information of the first user. The first account balance may, in embodiments, indicate a first amount of available fiat. The first amount of available fiat may be fiat owned by the first user that is located in an account associated with the first user and the digital asset exchange computer system. In embodiments, the first amount of available fiat may be owned by the first user and in the custody of the digital asset exchange computer system and/or the digital asset exchange. In embodiments, the first account balance information may be stored on a fiat ledger associated with the digital asset exchange computer system (e.g. fiat account balance data 5118, electronic ledger data 5116, fiat account module 5134). Obtaining an account balance may be similar to the descriptions of obtaining an account balance described throughout, the description of which applying herein.
The process for obtaining a withdrawal request may continue with step S14820. At step S14820, the digital asset exchange computer system may generate second graphical user interface information. In embodiments, the second graphical user interface information may be for displaying a graphical user interface on the first user device. For example, the second graphical user interface information may include second machine-readable instructions representing one or more of the following: (1) a display that includes the first account balance information; (2) a display that includes user identification information; and/or (3) a display that includes the first user's past transactions (all of the past transactions and/or a portion of the past transactions), to name a few.
The process of obtaining a withdrawal request may continue with step S14822. At step S14822, the digital asset exchange computer system may transmit the second graphical user interface information to the first user device via a network. In embodiments, upon receipt of the second graphical user interface information, the first user device displays the graphical user interface associated with the graphical user interface information on a display of the first user device. For example, the digital asset exchange computer system may send the second machine-readable instructions to the first user device, and, upon receiving the second machine-readable instructions, the first user device executes the second machine-readable instructions which may cause the second GUI to be displayed on a display screen of the first user device.
The process for obtaining a withdrawal request may continue with step S14824. At step S14824, the digital asset exchange computer system receives a second electronic withdrawal request of a first amount of fiat-backed digital assets. The second electronic withdrawal request may include one or more of the following: an amount of fiat-backed digital assets to withdraw (e.g. the first amount of fiat-backed digital assets); a designated public address on the disturbed transaction ledger of which the withdrawal of fiat-backed digital assets is directed towards; and/or a timestamp, to name a few. The timestamp, in embodiments, may be one or more timestamps indicating one or more of the following: the time and/or date at which the second withdrawal request was sent, the time and/or date at which the second withdrawal request was received, and/or the time and/or date the first user wishes to withdraw the first amount of fiat-backed digital assets, to name a few. In embodiments, the second withdrawal request may be digitally signed by a private key associated with the first user. The private key associated with the first user may, in embodiments, have a corresponding public key. The public key and private key, in embodiments, may be mathematically related. The public key may be associated with one or more private keys. The one or more private keys may be mathematically related to one another. In embodiments, the public key associated with the first user may be used to generate a first user public address associated with the first user. The first user public address, in embodiments, may be generated by applying a hash algorithm to the public key associated with the first user. The result of the application of the hash algorithm may, in embodiments, be the first user public address.
In embodiments, the designated public address may be associated with a public key which may have been used to generate the designated public address. For example, the digital asset address associated with the designated public address may be generated by applying a hash algorithm to the public key associated with the user associated with the designated public address. The result of the application of the hash on the public key may be the designated public address.
In embodiments, the second withdraw request may further include a request to transfer the first amount of fiat-backed digital assets from a fiat-backed digital asset issuer (e.g. an administrator) public address to the first designated public address. In embodiments, the second withdraw request may further include a request to generate the first amount of fiat-backed digital assets and, after printing the first amount of fiat backed digital assets, assigning the new fiat-backed digital assets to the first designated public address. In embodiments, the second withdraw request may further include a request to generate the first amount of fiat-backed digital assets and, after printing the first amount of fiat backed digital assets, assigning the new fiat-backed digital assets to the first designated public address. The process of issuing fiat-backed digital assets may be similar to the processes discussed in connection with issuing digital assets described herein, the descriptions of which applying herein. In embodiments, the fiat-backed digital asset issuer may issue fiat-backed digital assets in response to fluctuations in demand of the fiat-backed digital asset. For example, if the demand of the fiat-backed digital asset increases, the fiat-backed digital asset issuer may print fiat-backed digital assets. Continuing the example, the fiat-backed digital asset issuer may print fiat-backed digital assets in proportion to the increase in demand. Alternatively, the fiat-backed digital asset issuer may print fiat-backed digital assets based on a predetermined number, instructions, rules associated with printing fiat-backed digital assets, and/or not in proportion to the increase of demand, to name a few. As another example, if the demand of the fiat-backed digital asset decreases, the fiat-backed digital asset issuer may burn fiat-backed digital assets. Continuing the example, the fiat-backed digital asset issuer may burn fiat-backed digital assets in proportion to the decrease in demand. Alternatively, the fiat-backed digital asset issuer may burn fiat-backed digital assets based on a predetermined number, instructions, rules associated with burning fiat-backed digital assets, and/or not in proportion to the decrease of demand, to name a few. In embodiments, the fiat-backed digital asset issuer may require that a commensurate fiat and/or asset(s) deposit be made to account for the printed fiat-backed digital asset.
In embodiments, after receiving the second withdrawal request, the digital asset exchange computer system may verify the second withdrawal request. Verifying the second withdrawal request may include confirming one or more of the following: the validity of the first user public address, the amount of fiat owned by the first user, that the first user owns at least the second amount of fiat, and/or the designated public address is not prohibited from receiving a fiat-backed digital assets on behalf of the first user, to name a few. For example, to confirm the first user public address, the digital asset exchange computer system may compare the first user public address to a verified first user public address stored by the digital asset exchange computer system. Continuing the example, if the first user public address is the same as the verified first user public address, the first user public address may be verified. If the first user public address is not the same as the verified first user public address, the second withdraw request may be denied and/or a notification may be generated and sent by the digital asset exchange computer system to the first user device. The notification may indicate that the first user public address was not verified and the withdrawal request is denied. As another example, if the second withdrawal request includes a designated public address, the digital asset exchange computer system may verify whether the designated address is on a whitelist associated with the first user. Continuing the example, if the first user is associated with a whitelist, the digital asset exchange computer system may compare the designated public address to the whitelist. If the designated public address is on the whitelist, the designated public address may be verified. If the designated public address is not on the whitelist and thus is not verified, the second withdrawal request may be denied and/or a notification may be generated and sent by the digital asset exchange computer system to the first user device and/or a second user device associated with the first user. The notification may indicate that the designated public address is not authorized to receive fiat-backed digital assets on behalf of the first user and the withdraw request has been denied. The process of verifying designated addresses in the context of a whitelist may be similar to the process described in connection with
Referring back to
Referring to
Processing the second withdraw request may continue at step S14828. At step S14828, the digital asset exchange computer system determines that the second amount of fiat is either less than the first amount of available fiat or equal to the first amount of available fiat. In embodiments, the digital asset exchanged computer system may compare the second amount of fiat to the first amount of available fiat to make the determination regarding whether the first user has sufficient funds to withdraw the first amount of fiat-backed digital asset.
If, in embodiments, the first amount of available fiat is less than the second amount of fiat, the digital asset exchange computer system may determine that the first user has insufficient funds to complete the withdrawal. If the first user has insufficient funds, the process of
Processing the second withdraw request may continue at step S14830. At step S14830, the digital asset exchange computer system may determine a third amount of fiat associated with an updated amount of available fiat of the first user. The third amount of fiat, in embodiments, may correspond to an amount of fiat the first user may own after the withdraw request is executed and/or committed. To determine the third amount, the digital asset exchange computer system may subtract the second amount of fiat from the first amount of available fiat. For example, if the first amount of available fiat is 100 Dollars and the second amount of fiat is 75 Dollars, the third amount of fiat, in this example, would be 25 Dollars. In embodiments, the withdrawal request may have one or more fees associated with executing and/or committing the withdrawal request. These fees (e.g. transaction fees), may be represented as an amount of fiat-backed digital asset or an amount of fiat, or both. For example, if the first amount of available fiat is 100 Dollars, the second amount of fiat is 75 Dollars, and the transaction fee is 1 Dollar, the third amount of fiat, in this example, would be 24 Dollars.
Processing the second withdraw request may continue at step S14832. At step S14832, the digital asset exchange computer system may update a fiat account ledger database. In embodiments, the update to the fiat account ledger database may be to account for the second amount of fiat associated with the second withdraw request. The fiat account ledger, in embodiments, may be stored on computer readable member accessible by the digital asset exchange computer system. The fiat account ledger, in embodiments, may include one or more of the following: the amount of fiat each user owns in the custody of the digital asset exchange computer system; the total amount of fiat in the custody of the digital asset exchange computer system; the total amount of fiat that the digital asset exchange and/or digital asset exchange computer system owns; transactions associated with each user and/or fiat; and/or transactions associated with the digital asset exchange and/or digital asset exchange computer system and/or fiat, to name a few.
Processing the second withdrawal request may continue at step S14834. At step S14834, the digital asset exchange computer system may update a fiat-backed digital asset issuer fiat ledger. In embodiments, the update to the fiat-backed digital asset issuer fiat ledger may be to account for the second amount of fiat associated with the second withdraw request. In embodiments, the fiat-backed digital asset issuer fiat ledger may be associated with a fiat-backed digital asset issuer (e.g. the issuer of the fiat-backed digital asset associated with the process described herein). In embodiments, the fiat-backed digital asset issuer fiat ledger may be updated by the digital asset exchange computer system sending a request to the fiat-backed digital asset issuer. The request, in embodiments, may include a request to update the fiat-backed digital asset issuer fiat ledger. In response to receiving the request, the fiat-backed digital asset issuer may update their fiat-backed digital asset issuer fiat ledger.
In embodiments, the digital asset exchange computer system may also transfer the second amount of fiat to the fiat-backed digital asset issuer (e.g. from an account on the peer-to-peer network associated with the digital asset exchange to an account on the peer-to-peer network associated with the fiat-backed digital asset issuer). In embodiments, the digital asset exchange computer system may transfer the second amount of fiat before, with, or after the request to update the fiat-backed digital asset issuer fiat ledger is sent to the fiat-backed digital asset issuer. In embodiments, the digital asset exchange computer system may periodically transfer fiat from an account on the peer-to-peer network associated with the digital asset exchange to an account on the peer-to-peer network associated with the fiat-backed digital asset issuer. The periodic transfers may be made at defined time intervals. The defined time intervals may be defined based on: the amount of fiat that is due to be transferred from the digital asset exchange computer system to the fiat-backed digital asset issuer; the amount of transactions including fiat; the processing capabilities of the fiat-backed digital asset issuer and/or the digital asset exchange computer system; and/or one or more government regulations, to name a few. For example, the digital asset exchange computer system may transfer fiat to the fiat-backed digital asset issuer once the digital asset exchange computer system is in custody of $50,000 owned by the fiat-backed digital asset issuer. In embodiments, the defined time intervals may be predetermined times throughout each day, week, month, and/or year, to name a few. For example, the digital asset exchange computer system may periodically transfer fiat from an account on the peer-to-peer network associated with the digital asset exchange to an account on the peer-to-peer network associated with the fiat-backed digital asset issuer every day at 2:00 PM EST.
Processing the second withdraw request may continue at step S14836. At step S14836, the digital asset exchange computer system may generate a first transaction request. The first transaction request, in embodiments, may include a first message that includes a request to obtain the first amount of fiat-backed digital assets. The first message may also include instructions to transfer the obtained first amount of fiat-backed digital assets to the first designated public address. In embodiments, the transaction request may be for the distributed transaction ledger and addressed to a contract address associated with the fiat-backed digital asset issuer. for the distributed transaction ledger
In embodiments, the transaction request may include instructions to update the fiat-backed digital asset database and to reserve enough fiat-backed digital assets to cover the first amount of fiat-backed digital assets. In embodiments, the transaction request may include a digital signature associated with the digital asset exchange computer system. In embodiments, the transaction request may include a digital signature associated with a trusted entity system. The digital signature associated with the trusted entity system may be a combined digital signature based on of one or more private keys associated with one or more trusted entities of the trusted entity system. The digital signature, in embodiments, may further include one or more private keys associated with the first user.
Processing the second withdraw request may continue at step S14838. At step S14838, the digital asset exchange computer system transmits the transaction request to the peer-to-peer network via a network (e.g. network 15). In embodiments, transmitting the first transaction request to the peer-to-peer network may cause the first transaction request to be published by a trusted entity system. In embodiments, the trusted entity system may publish the transaction request to the peer-to-peer network via a network (e.g. Network 15). In embodiments, publishing the transaction request may cause the peer-to-peer network to go through a process of executing and/or committing the transaction request (e.g. a consensus protocol) which may result in the transfer of the first amount of fiat-backed digital assets from the fiat-backed digital asset issuer to the first designated public address.
Processing the second withdraw request may continue at step S14840. At step S14840, the balance of the first user (e.g. the first designated public address and/or the first user public address) includes the first amount of fiat-backed digital assets. The confirmation, in embodiments, may be based on reference to the distributed transaction ledger. In embodiments, the first user public address in embodiments, may be the first designated public address. In embodiments, the digital asset exchange computer system may confirm that the first user received the fiat-backed digital assets (or the first designated public address received the first amount, in the case where the first designated public address is not associated with the first user) received the correct amount of fiat-backed digital assets. The confirmation process may be a call/return to and from the designated public address and/or the first user public address. In embodiments, the confirmation process may be a query to the peer-to-peer network for a status of the distributed transaction ledger, which may result in a receipt of the status of the distributed transaction ledger which may include the transfer of the first amount of fiat-backed digital assets.
The steps of the processes described in connection with
Referring to
The process for depositing an amount of fiat-backed digital asset into a digital asset exchange computer system may continue with step S14904. At step S14904, the digital asset exchange computer system obtains a deposit request. In embodiments, a process for obtaining a deposit request may be performed by the steps illustrated in
In embodiments, the fiat-backed digital asset may be tied to a distributed transaction ledger which may be maintained on a peer-to-peer network that includes a plurality of geographically distributed computer systems. In embodiments, the distributed transaction ledger may be public, private, semi-private, and/or semi-public, to name a few. For example, the distributed transaction ledger may be published publicly available to anyone who wants to see it. As another example, the distributed transaction ledger may not be published and, to be able to access the distributed transaction ledger, a user may send a query the peer-to-peer network.
The peer-to-peer network, in embodiments, may be: the Ethereum Network, the Libra Network, the Neo Network, the Bitcoin Network, and/or the Stellar Network, to name a few. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of work. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of stake. The peer-to-peer network, in embodiments, may be based on a cryptographic mathematical protocol. In embodiments, the peer-to-peer network may be based on a mathematical protocol that is open sourced. In embodiments, the digital asset security token database, in embodiments, may be stored on computer readable media associated with a digital asset security token issuer system (e.g. memory of the digital asset security token issuer system). In embodiments, the digital asset security token database may be maintained and stored on the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the distributed transaction ledger may include a fiat-backed digital asset database. In embodiments, the fiat-backed digital asset data base may be maintained on a sidechain. A sidechain, in embodiments, may refer to a portion of the distributed transaction ledger. For example, an administrator, user, and/or trusted entity may maintain a portion of the distributed transaction ledger and/or an electronic copy of a portion of the distributed transaction ledger. In embodiments, a portion of the distributed transaction ledger, in the context of a Merkel Tree, may refer to one or more “leafs” of the Merkel Tree, one or more statuses of the Merkel Tree, and/or a complete Merkel Tree with one or more past transactions being “pruned.” In the context of a blockchain, the portion of the distributed transaction ledger may be one or more blocks of the blockchain. The information on the sidechain may be updated periodically or aperiodically. For example, the information on the sidechain may be updated, published, and stored on the peer-to-peer network at predetermined times (e.g. twice a day, once a day, once a week, once a month, and/or once a quarter, to name a few). As another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the execution of a transaction and/or the execution of a batch of transactions. As yet another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the commitment of a transaction and/or the commitment of a batch of transactions. A transaction, for example, may be committed by a consensus of trusted entities of the peer-to-peer network.
In embodiments, the peer-to-peer network may utilize one or more protocols and/or programs for security purposes. For example, the peer-to-peer network may utilize a byzantine fault tolerance protocol as a consensus mechanism. As another example, the peer-to-peer network may utilize a whitelist for the execution of a transaction and/or the transfer of funds. As yet another example, the peer-to-peer network may also utilize one or more of the following: encryption, point-to-point encryption, two-factor authentication, and/or tokenization, to name a few.
The process of obtaining a deposit request may continue with step S14910. At step S14910, in response to the first request, the digital asset exchange computer system obtains account balance information for a first user where the account balance information indicates an amount of available fiat of the first user. In embodiments, the account balance information may be obtained from a fiat account ledger database and/or the distributed transaction ledger. The fiat account ledger database, in embodiments, may indicate how much fiat (e.g. U.S. Dollars) the first user has available for use and/or owns. For example, the fiat-account ledger database may indicate the first user has a first amount of available fiat. In embodiments the account balance information may include first fiat-backed digital asset account balance information of the first user. The first fiat-backed digital asset account balance information may indicate a balance of fiat-backed digital assets that are owned by the first user and/or available for use by the first user. For example, the first fiat-backed digital asset account information may indicate that the first user has a second amount of fiat-backed digital assets available for use. In embodiments, the first amount of available fiat and/or the second amount of fiat-backed digital assets may be in the custody of the digital asset exchange computer system and/or the digital asset exchange. In embodiments, the fiat account ledger database may be stored on computer readable memory accessible by the digital asset exchange computer system. In embodiments, the digital asset exchange computer system may obtain and/or store a copy of the distributed transaction ledger on computer readable memory accessible by the digital asset exchange computer system.
The process of obtaining a deposit request, in embodiments, may continue with step S14912. At step S14912, the digital asset exchange computer system obtains a destination address. A destination address may be the public address associated with the entity the first user intends to deposit the first amount of fiat-backed digital assets. For example, the destination address may be a public address associated with the digital asset exchange computer system.
The process for obtaining a deposit request may continue with step S14914. At step S14820, the digital asset exchange computer system may generate second graphical user interface information. In embodiments, the second graphical user interface information may be for displaying a graphical user interface on the first user device. For example, the second graphical user interface information may include second machine-readable instructions representing one or more of the following: (1) a display that includes the first fiat-backed digital asset account balance information; (2) a display that includes the first account balance information; (3) a display that includes user identification information; and/or (4) a display that includes the first user's past transactions (all of the past transactions and/or a portion of the past transactions), to name a few.
The process of obtaining a deposit request may continue with step S14916. At step S14822, the digital asset exchange computer system may transmit the second graphical user interface information to the first user device via a network. In embodiments, upon receipt of the second graphical user interface information, the first user device displays the graphical user interface associated with the graphical user interface information on a display of the first user device. For example, the digital asset exchange computer system may send the second machine-readable instructions to the first user device, and, upon receiving the second machine-readable instructions, the first user device executes the second machine-readable instructions which may cause the second GUI to be displayed on a display screen of the first user device.
The process for obtaining a deposit request may continue with step S14918. At step S14918, the digital asset exchange computer system receives a second electronic deposit request of a first amount of fiat-backed digital assets. The second electronic deposit request may include one or more of the following: an amount of fiat-backed digital assets to deposit (e.g. the first amount of fiat-backed digital assets); a designated public address on the disturbed transaction ledger of which the deposit of fiat-backed digital assets is being transferred from (e.g. the first user public address); and/or a timestamp, to name a few. The timestamp, in embodiments, may be one or more timestamps indicating one or more of the following: the time and/or date at which the second deposit request was sent, the time and/or date at which the second deposit request was received, and/or the time and/or date the first user wishes to deposit the first amount of fiat-backed digital assets, to name a few. In embodiments, the second deposit request may be digitally signed by a private key associated with the first user. The private key associated with the first user may, in embodiments, have a corresponding public key. The public key and private key, in embodiments, may be mathematically related. The public key may be associated with one or more private keys. The one or more private keys may be mathematically related to one another. In embodiments, the public key associated with the first user may be used to generate a first user public address associated with the first user. The first user public address, in embodiments, may be generated by applying a hash algorithm to the public key associated with the first user. The result of the application of the hash algorithm may, in embodiments, be the first user public address.
In embodiments, the destination public address may be associated with a public key which may have been used to generate the destination public address. For example, the digital asset address associated with the destination public address may be generated by applying a hash algorithm to the public key associated with the user associated with the destination public address. The result of the application of the hash on the public key may be the destination public address.
In embodiments, the second deposit request may further include a request to transfer the first amount of fiat-backed digital assets from the destination public address to a fiat-backed digital asset issuer (e.g. an administrator) public address. In embodiments, the second deposit request may further include a request to burn the first amount of fiat-backed digital assets. The process of burning a fiat-backed digital asset may be similar to the process described in connection with
In embodiments, after receiving the second deposit request, the digital asset exchange computer system may verify the second deposit request. Verifying the second withdrawal request may include confirming one or more of the following: the validity of the first user public address, the amount of fiat-backed digital assets owned by the first user, that the first user owns at least the first amount of fiat-backed digital assets, the validity of the designated public address, and/or the destination public address is not prohibited from receiving a fiat-backed digital assets on behalf of the first user, to name a few. For example, to confirm the first user public address, the digital asset exchange computer system may compare the first user public address to a verified first user public address stored by the digital asset exchange computer system. Continuing the example, if the first user public address is the same as the verified first user public address, the first user public address may be verified. If the first user public address is not the same as the verified first user public address, the second withdraw request may be denied and/or a notification may be generated and sent by the digital asset exchange computer system to the first user device. The notification may indicate that the first user public address was not verified and the withdrawal request is denied. As another example, if the second deposit request includes a destination public address, the digital asset exchange computer system may verify whether the destination public address is on a whitelist associated with the first user. Continuing the example, if the first user is associated with a whitelist, the digital asset exchange computer system may compare the destination public address to the whitelist. If the destination public address is on the whitelist, the destination public address may be verified. If the destination public address is not on the whitelist and thus is not verified, the second deposit request may be denied and/or a notification may be generated and sent by the digital asset exchange computer system to the first user device and/or a second user device associated with the first user. The notification may indicate that the destination public address is not authorized to receive fiat-backed digital assets on from the first user and the deposit request has been denied. The process of verifying destination addresses in the context of a whitelist may be similar to the process described in connection with
Referring back to
In embodiments, processing the deposit request may continue at step S14922. At step S14922, the digital asset exchange computer system determines that the first amount of fiat-backed digital assets is present in the designated public address. In embodiments, the digital asset exchange computer system may determine whether the first amount of fiat-backed digital assets is less than or equal to a second amount of fiat-based digital assets available to the user. In embodiments, the digital asset exchanged computer system may compare the second amount fiat-backed digital assets to the first amount of fiat-backed digital assets to make the determination regarding whether the first user has sufficient asset to deposit the first amount of fiat-backed digital asset.
If, in embodiments, the second amount of available fiat-backed digital assets is less than the first amount of fiat-backed digital assets, the digital asset exchange computer system may determine that the first user has insufficient assets to complete the deposit. If the first user has insufficient funds, the process of
Processing the second deposit request may continue at step S14924. At step S14924, the digital asset exchange computer system may determine a third amount of fiat associated with an updated amount of available fiat of the first user. The third amount of fiat, in embodiments, may correspond to an amount of fiat the first user may own after the deposit request is executed and/or committed. To determine the third amount, the digital asset exchange computer system may add the second amount of fiat (e.g. the calculated value in fiat of the first mount of fiat-backed digital assets) to the first amount of available fiat. For example, if the first amount of available fiat is 100 Dollars and the second amount of fiat is 75 Dollars, the third amount of fiat, in this example, would be 175 Dollars. In embodiments, the deposit request may have one or more fees associated with executing and/or committing the deposit request. These fees (e.g. transaction fees), may be represented as an amount of fiat-backed digital asset or an amount of fiat, or both. For example, if the first amount of available fiat is 100 Dollars, the second amount of fiat is 75 Dollars, and the transaction fee is 1 Dollar, the third amount of fiat, in this example, would be 174 Dollars.
Processing the second deposit request may continue at step S14926. At step S14926, the digital asset exchange computer system may update a fiat account ledger database. In embodiments, the update to the fiat account ledger database may be to account for the second amount of fiat associated with the second deposit request. The fiat account ledger, in embodiments, may be stored on computer readable member accessible by the digital asset exchange computer system. The fiat account ledger, in embodiments, may include one or more of the following: the amount of fiat each user owns in the custody of the digital asset exchange computer system; the total amount of fiat in the custody of the digital asset exchange computer system; the total amount of fiat that the digital asset exchange and/or digital asset exchange computer system owns; transactions associated with each user and/or fiat; and/or transactions associated with the digital asset exchange and/or digital asset exchange computer system and/or fiat, to name a few.
Processing the second deposit request may continue at step S14928. At step S14928, the digital asset exchange computer system may update a fiat-backed digital asset issuer fiat ledger. In embodiments, the update to the fiat-backed digital asset issuer fiat ledger may be to account for the first amount of fiat-backed digital assets associated with the second deposit request, updating the first user's available fiat-backed digital asset balance to a third amount of fiat-backed digital assets (e.g. the second amount of fiat backed digital assets less the first amount of fiat-backed digital assets). In embodiments, the fiat-backed digital asset issuer fiat ledger may be associated with a fiat-backed digital asset issuer (e.g. the issuer of the fiat-backed digital asset associated with the process described herein). In embodiments, the fiat-backed digital asset issuer fiat ledger may be updated by the digital asset exchange computer system sending a request to the fiat-backed digital asset issuer. The request, in embodiments, may include a request to update the fiat-backed digital asset issuer fiat ledger. In response to receiving the request, the fiat-backed digital asset issuer may update their fiat-backed digital asset issuer fiat ledger.
In embodiments, the digital asset exchange computer system may also receive the second amount of fiat from the fiat-backed digital asset issuer (e.g. from an account on the peer-to-peer network associated with the digital asset exchange to an account on the peer-to-peer network associated with the fiat-backed digital asset issuer). In embodiments, the digital asset exchange computer system may receive the second amount of fiat before, with, or after the request to update the fiat-backed digital asset issuer fiat ledger is sent to the fiat-backed digital asset issuer. In embodiments, the digital asset exchange computer system may periodically receive fiat at an account on the peer-to-peer network associated with the digital asset exchange from an account on the peer-to-peer network associated with the fiat-backed digital asset issuer. The periodic transfers may be made at defined time intervals. The defined time intervals may be defined based on: the amount of fiat that is due to be transferred from the digital asset exchange computer system to the fiat-backed digital asset issuer; the amount of transactions including fiat; the processing capabilities of the fiat-backed digital asset issuer and/or the digital asset exchange computer system; and/or one or more government regulations, to name a few. For example, the digital asset exchange computer system may receive fiat from the fiat-backed digital asset issuer once the digital asset exchange computer system has transferred $50,000 as a result of deposits of fiat-backed digital assets. In embodiments, the defined time intervals may be predetermined times throughout each day, week, month, and/or year, to name a few. For example, the digital asset exchange computer system may periodically receive fiat from an account on the peer-to-peer network associated with the fiat-backed digital asset issuer every day at 5:00 PM EST.
Processing the second deposit request may continue at step S14930. At step S14930, the digital asset exchange computer system may generate a first transaction request. The first transaction request, in embodiments, may include a first message that includes a request to obtain from the first designated public address, the first amount of fiat-backed digital assets and to provide the fiat-backed digital assets to the destination address. The first message may also include a request to burn the first amount of fiat-backed digital assets. Alternatively, in embodiments, the first message may also include a request to store the first amount of fiat-backed digital assets at the destination address. In embodiments, the transaction request may be addressed to a public address associated with the fiat-backed digital asset issuer from a public address associated with the digital asset exchange computer system. In embodiments, the transaction request may include instructions to update the fiat account ledger database and to reserve enough fiat to cover the second deposit request. In embodiments, the transaction request may include a digital signature associated with the digital asset exchange computer system. In embodiments, the transaction request may include a digital signature associated with a trusted entity system. The digital signature associated with the trusted entity system may be a combined digital signature based on of one or more private keys associated with one or more trusted entities of the trusted entity system. The digital signature, in embodiments, may further include one or more private keys associated with the first user.
In embodiments, processing the deposit request may continue, optionally, at step S14932. At step S14932, the digital asset exchange computer system may update the fiat-backed digital asset issuer fiat ledger to account for the generated transaction request. In embodiments, the update to the fiat-backed digital asset issuer fiat ledger may be to decrease a balance of fiat by the second amount of fiat (e.g. the amount of fiat the digital asset exchange computer system exchanged for the first amount of fiat-backed digital assets).
Processing the second deposit request may continue at step S14934. At step S14838, the digital asset exchange computer system transmits the transaction request to the peer-to-peer network via a network (e.g. network 15). In embodiments, transmitting the first transaction request to the peer-to-peer network may cause the first transaction request to be published by a trusted entity system. In embodiments, the trusted entity system may publish the transaction request to the peer-to-peer network via a network (e.g. Network 15). In embodiments, publishing the transaction request may cause the peer-to-peer network to go through a process of executing and/or committing the transaction request (e.g. a consensus protocol) which may result in the deposit of the first amount of fiat-backed digital assets from the designated public address to the destination public address.
Processing the second deposit request may continue at step S14936. At step S14936, the first amount of fiat-backed digital assets is confirmed as not present at the designated public address of the first user. The confirmation, in embodiments, may be based on reference to the distributed transaction ledger. In embodiments, the first user public address in embodiments, may be the first designated public address. In embodiments, the digital asset exchange computer system may confirm that the first amount of fiat-backed digital assets is not present at the designated public address (or the first destination public address received the first amount of fiat-backed digital assets). The confirmation process may be a call/return to and from the designated public address and/or the first user public address. In embodiments, the confirmation process may be a query to the peer-to-peer network for a status of the distributed transaction ledger, which may result in a receipt of the status of the distributed transaction ledger which may include the deposit of the first amount of fiat-backed digital assets.
In embodiments, the steps of the processes of
In embodiments, a data incident or data breach may occur, causing a risk to digital assets owned by one or more customers of the digital asset exchange. A security incident, in embodiments, may refer to an event that may indicate that the digital asset exchange's systems or data have been compromised or that measures put in place to protect the systems or data have failed. A data breach, in embodiments, may refer to a security incident in which sensitive, protected, or confidential data is copied, transmitted, viewed, stolen or used by an unauthorized source or individual. Referring to
The digital asset computer exchange system may next determine whether the first transaction request was caused by the security incident. In embodiments, the first transaction request may have been caused by a security incident. Referring to
In response to determining the second transaction request was caused by the security incident, at step S16352-1, the digital asset exchange computer system at step S16352-1, may transmit the first solution to the first mathematical puzzle. The first solution, in embodiments, may be obtained by the digital asset exchange computer system via and transmitted to the first user device via network 125. The transmission of solution to the puzzle may be based on the type of security incident the digital asset exchange is experiencing.
Once the first solution is received by the first user device, the first user device may transmit a transaction request including the first solution to withdrawal the first amount of digital asset to a first scripted address and/or a second scripted address. The transaction request, in embodiments, may be digitally signed by the customer private key. When the transaction request is received, a first scripted address and/or a second scripted address may transfer the first amount of digital assets deposited by the first user to the first user public address. In embodiments, a first scripted address and/or a second scripted address may transfer the first amount of digital assets to the first user public address.
To ensure that the customer did not lose any digital assets as a result of the security incident, the digital asset exchange computer system may, at step S16356-1, may confirm that the first amount of digital assets has been received by the first user public address. To confirm receipt, the digital asset exchange computer system may send a call to the first user public address to confirm receipt of the digital assets. In return, the first user public address may send a return either confirming receipt or not confirming receipt. If receipt of the digital assets is not confirmed, the digital asset exchange computer system may generate and send a data breach notification to the first user device, indicating what happened and how the first user can proceed.
In embodiments, the first transaction request may not have been caused by the security incident. At a step S16352-2, the digital asset exchange computer system determines that the security incident did not cause the first transaction request. In these embodiments, the digital asset exchange computer system may take steps to end the trading of the first user on the digital asset exchange.
At step S16354-2, the digital asset exchange computer system may digitally sign the first transaction request. After the digital asset exchange computer system digitally signs the first transaction request, the first transaction request would then have the transfer requests, the customer private key, and a private key associated with the digital asset exchange (e.g. the first exchange private key, the second exchange private key, and/or the third exchange private key, to name a few). First authorization instructions of first scripting limitations of a first scripted account may authorize transactions that include both the customer private key and a private key associated with the digital asset exchange.
In embodiments, the digital asset exchange computer system may generate a second transaction request reflecting the first order. In embodiments, the second transaction request may be to transfer the second amount of digital assets to a public address associated with the digital asset exchange. Additionally, in embodiments, the second transaction request may have a second transfer to transfer a third amount (e.g. the first amount less the second amount) to the first user public address. Once the second transaction is generated, the digital asset exchange computer system may transmit the second transaction request to the first user device. After receiving the second transaction request, the first user device may digitally sign the second transaction request and send the digitally signed transaction request back to the digital asset exchange computer system. Once received, the digital asset exchange computer system may verify and sign the second transaction request.
Next, the digital asset exchange computer system at step S16356-2 may transmit the first transaction request (and/or the aforementioned second transaction request) to a first scripted address via network 125. The transmission of the first transaction request, in embodiments, may cause the first transaction request to be executed by a first scripted address. In embodiments, when publishing the first transaction request and/or the second transaction request on the blockchain, in embodiments, the digital asset exchange computer system may flag the request as published as a result of a security incident detected that did not affect the transaction/order. In embodiments, publishing of the first and/or second transaction request on the blockchain, in embodiments, may cause the remaining digital assets that are owned by the first user and located on a first scripted address and/or a second scripted address to be transferred to the first user public address.
To ensure that the customer did not lose any digital assets as a result of the security incident, the digital asset exchange computer system at step S16358-2 may confirm that a third amount of digital assets has been received by the first user public address. In embodiments, the third amount may refer to the first amount of digital assets less the second amount of digital assets. To confirm receipt, the digital asset exchange computer system may send a call to the first user public address to confirm receipt of the third amount of digital assets. In return, the first user public address may send a return either confirming receipt or not confirming receipt. If receipt of the digital assets is not confirmed, the digital asset exchange computer system may generate and send a data breach notification to the first user device, indicating what happened and how the first user can proceed.
The steps of the process described in connection with
In embodiments, network 15, may be a wide area network, a local area network, a telephone network, dedicated access lines, a proprietary network, a satellite network, a wireless network, a mesh network, or through some other form of end-user to end-user interconnection, which may transmit data and/or other information. Any participants in a digital asset network may be connected directly or indirectly, as through the data network 15, through wired, wireless, or other connections. In embodiments, network 15 may be accessed using Transfer Control Protocol and Internet Protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), Hypertext Transfer Protocol (“HTTP”), WebRTC, SIP, and wireless application protocol (“WAP”), are some of the various types of protocols that may be used to facilitate communications between administrator system 1801 and user devices 11805 . . . 11805X. In some embodiments, el administrator system 1801 and/or user devices 11805 . . . 11805X may communicate with one another via a web browser using HTTP. Various additional communication protocols may be used to facilitate communications between administrator system 1801 and/or user devices 11805 . . . 11805X, including, but not limited to, Wi-Fi (e.g., 802.11 protocol), Bluetooth, radio frequency systems (e.g., 900 MHz, 1.4 GHz, and 5.6 GHz communication systems), cellular networks (e.g., GSM, AMPS, GPRS, CDMA, EV-DO, EDGE, 3GSM, DECT, IS 136/TDMA, iDen, LTE or any other suitable cellular network protocol), infrared, BitTorrent, FTP, RTP, RTSP, SSH, and/or VOIP.
As illustrated in
The blockchain 1807 may include one more contract addresses, such as contract address for, e.g., a proxy smart contract 11310 (contract address 1), IMPL smart contract 11320 (contract address 2), PRINT LIMITER smart contract 11360 (contract address 3), STORE smart contract 11330 (contract address 4), CUSTODIAN 1 smart contract 11819 (contract address 5), CUSTODIAN 2 smart contract 11350 (contract address 6), CUSTODIAN 3 smart contract 11823 (contract address 7), as illustrated in
In embodiments, the blockchain 1807 may be a plurality of geographically distributed computer systems in a peer-to-peer network. Wireless communication may be provided using any of a variety of communication protocols and/or wireless communication networks, including e.g. GSM, GSM-R, UMTS, TD-LTE, LTE, LTE-Advanced Pro, LTE Advanced, Gigabit LTE, CDMA, iDEN, MVNO, MVNE, Satellite, TETRA, WiMAX, AMPS TDMA, Roaming SIM, DC-HSPA, HSPA, HSPA+, HSDPA, G, 2G, 3.5G, 4G, 4.5G, 5G, 5.5G, 6G, 6.5G, VoLTE, EDGE, GPRS, GNSS, EV-DO, 1×RTT, WCDMA, TDS-CDMA, CDMA2000, CSFB, FDMA, OFDMA, PDMA, AMPS, EV-DO, DECT, IS-95, NMT, UMTS, MPLS, MOCA, Broadband over Power Lines, NB-IoT, enhanced MTC (eMTC), LTE-WLAN, ISDN, Microwave, Long Range Wifi, Point to Point Wifi, EC-GSM-IoT, LTE-M, NB-IoT, Evolved Multicast Broadcast Multimedia Service (eMBMS) and LTE-Broadcast (LTE-B), to name a few.
The system described in connection with
The system described in connection with
In embodiments, proxy smart contract 11310 may have a contract address (e.g., contract address 1) associated therewith on the blockchain 1807 proxy smart contract 11310. Proxy smart contract 11310, as seen in
In embodiments, PROXY delegation instructions module 11829 (i.e. first delegation instructions module) may include one or more instructions to delegate received requests to other smart contracts on the blockchain, such as, for example, IMPL smart contract 11320 (contract address 2), PRINT LIMITER smart contract 11360 (contract address 3), STORE smart contract 11330 (contract address 4), CUSTODIAN 1 smart contract 11819 (contract address 5), CUSTODIAN 2 smart contract 11350 (contract address 6), CUSTODIAN 3 smart contract 11823 (contract address 7), to name a few. Additionally, in embodiments, PROXY delegation instructions module 11829 (i.e. first delegation instructions module) may include one or more instructions to delegate received requests to public addresses such as off-line public address 1 11817, off-line public address N 11817N, on-line public address 1 11825, on-line public address N 1825N, user 1 public address 11827, and/or User X public address 11827X, to name a few.
In embodiments, the first authorization instruction module 11831 may include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts, to name a few.
In embodiments, PRINT LIMITER smart contract 11360 may have a contract address (e.g. contract address 3) associated therewith on the blockchain 1807. PRINT LIMITER smart contract 11360, as seen in
In embodiments, PRINT LIMITER token creation instructions module 11833 may include one or more instructions that indicate conditions under which tokens of a digital asset token are created. In embodiments, the PRINT LIMITER token creation instructions module 11833 may include instructions that limit the conditions under which tokens may be created. For example, the PRINT LIMITER token creation instructions module 11833 may include instructions that limit the production of tokens to 1,000,000 tokens. In embodiments, the instructions may also include a temporal component. For example, the PRINT LIMITER token creation instructions module 11833 may include instructions that only allow 1,000 tokens to be created within a 24 hour period. Or, as another example, the PRINT LIMITER token creation instructions module 11833 may include instructions that only allow tokens to be created during business hours. In embodiments, the PRINT LIMITER may also include authorization instructions related to the first key pair.
In embodiments, custodian instructions module 11835 may include one or more instructions that limit the PRINT LIMITER smart contract 11360A authority. For example, if a request is received by the PRINT LIMITER smart contract 11360 to create digital asset tokens beyond a pre-approved token supply limit, the custodian instructions module 11835 may require authorization from a print limiter custodian (i.e. CUSTODIAN 2 smart contract 11350 (contract address 6)).
In embodiments, the second authorization instruction module 11839 and the PRINT LIMITER second authorization instructions module 11841 (i.e. third authorization instructions module) may each include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts, to name a few. Second authorization instruction module 11839 may include instructions for the first designated key pair (on-line keyset 1 11362 . . . 11362N), with respect to token creation of the digital asset token. In embodiments, the second authorization instructions with respect to token creation may be below a first threshold over a first period of time. PRINT LIMITER second authorization instructions module 11841 (i.e. third authorization instructions module) may include instructions for the second designated key pair (i.e. off-line keyset 11803 . . . 111803N) with respect to token creation of the digital asset token. In embodiments, PRINT LIMITER first authorization instructions module 11839 and PRINT LIMITER second authorization instructions module 11841 may be the same module.
In embodiments, the PRINT LIMITER Third Authorization Instructions Module 11835 may include instructions to modify the token supply. For example, the PRINT LIMITER Third Authorization Instructions Module 11835 may include instructions that, when called to execute, may create and/or burn tokens of the digital asset token. In embodiments, instructions that modify the token supply may cause the STORE Smart Contract 11330 to alter an electronic ledger that tracks the token supply.
In embodiments, the token transfer instructions module 11843, in embodiments, may include instructions to transfer digital asset tokens. In embodiments, the transfer may be from one public address to another public address. For example, a transfer of tokens may be from User 1 public address 11827 to User X public address 11827X. In embodiments, such transfer instructions may include rules by which certain transfer are allowed or blocked and may specify one or more key pair or contract addresses that may be authorized to perform one or more types of transfer operations. A more detailed description of the transfer of digital asset tokens is located in connection with the description of
In embodiments, the token destruction instructions module 11845 may include instructions on when, and with whose authority, security tokens associated with one or more specified addresses shall be destroyed or “burned”, and thus removed from the security token supply. A more detailed description of token destruction is described in connection with
In embodiments, token balance modification instructions module 11847 may include instructions that may alter, edit, and/or update a transaction ledger in accordance with token creation, token transfer, and/or token destruction instructions (or modules), to name a few.
In embodiments, CUSTODIAN 2 smart contract may have a contract address (e.g. contract address 6) associated therewith on the blockchain 1807. CUSTODIAN 2 smart contract 11350, as seen in
In embodiments, the CUSTODIAN 2 first authorization instructions module 11849 (i.e. fourth authorization instructions module) and the CUSTODIAN 2 second authorization instructions module 11851 (i.e. fifth authorization instructions module) may each include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts, to name a few CUSTODIAN 2 first authorization instructions module 11849 (i.e. fourth authorization instructions module) may include instructions for the off-line keyset 11803 . . . 11803N to authorize the issuance of instructions to the PRINT LIMITER smart contract 11360 with respect to token creation, above a first threshold during a first period of time. CUSTODIAN 2 second authorization instructions module 11851 (i.e. fifth authorization instructions module) may include instructions to raise a ceiling of token creation. A more detailed description of raising the ceiling of token creation is located below in the descriptions in connection with
In embodiments, STORE smart contract 11330 may have a contract address (e.g. contract address 4) associated therewith on the blockchain 1807. STORE smart contract 11330, as seen in
In embodiments, storage instructions module 11853, may include instructions to store any alterations, edits, or updates to a transaction ledger in accordance with token creation, token transfer, and/or token destruction. In embodiments, the storage instructions module 11853 may be called through a transaction request received from one or more smart contracts. For example, as shown in
In embodiments, the STORE authorization instructions module 11855 may include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts, to name a few.
In embodiments, IMPL smart contract 11320 may have a contract address (e.g. contract address 2) associated therewith on the blockchain 1807. The IMPL smart contract 11320, as seen in
In embodiments, the generate hash instructions module 11857 may include instructions to generate a unique hash. A unique hash may be generated by the generate hash instructions module 11857 by applying a hash algorithm. Examples of hash algorithms include MD 5, SHA 1, SHA 256, RIPEMD, and Keccak-256, to name a few. Hash algorithms take an input of any length and create an output of fixed length, allowing the trade instructions to be detectable and usable by administrators and users on the underlying blockchain.
In embodiments, the IMPL authorization instructions module 11859 may include instructions to authorize request received, the requests, in embodiments, being transaction requests from administrators, user public addresses, or other smart contracts, to name a few. In embodiments, the requests may include requests to generate digital asset tokens from administrators, user public addresses, and/or other smart contracts, to name a few.
In embodiments, the IMPL token transfer instructions module 11861 may include instructions to transfer digital asset tokens. In embodiments, the transfer may be from one public address to another public address. For example, a transfer of tokens may be from User 1 public address 11827 to User X public address 11827X. In embodiments, such transfer instructions may include rules by which certain transfer are allowed or blocked and may specify one or more key pair or contract addresses that may be authorized to perform one or more types of transfer operations. In embodiments, the IMPL token transfer instructions module 11861 may be similar to the token transfer instructions module 11843, described in connection with
In embodiments, IMPL token balance modification instructions module 11863 may include instructions that may alter, edit, and/or update a transaction ledger in accordance with token creation, token transfer, and/or token destruction instructions (or modules), to name a few. In embodiments, the IMPL token balance modification instructions module 11863 may be similar to the token balance modification module 11847 described in connection with
In embodiments, IMPL delegation instructions module 11837 (i.e. second delegation instructions module) may include one or more instructions to delegate received requests to other smart contracts, such as, for example, contract address 1 (proxy smart contract) 11809, PRINT LIMITER smart contract 11360 (contract address 2), STORE smart contract 11330 (contract address 4), CUSTODIAN 1 smart contract 11819 (contract address 5), CUSTODIAN 2 smart contract 11350 (contract address 6), CUSTODIAN 3 smart contract 11823 (contract address 7), off-line public address 1 1817, off-line public address N 1817N, on-line public address 1 11825, on-line public address N 1825N, user 1 public address 11827, and/or User X public address 11827X. PRINT LIMITER delegation instructions module 11837 (i.e. second delegation instructions module) may include instructions for delegating to one or more designated store contract addresses data storage operations or other functions for the digital asset token as authorized by the first designated custodian contract address.
In embodiments, the IMPL token creation module 11865 may include one or more instructions to create digital asset tokens, and thus add to the token supply. Such instructions may specify one or more authorized key pairs or contract addresses that may be authorized to request creation of security tokens under specified conditions (such as one or more on-line keysets 11362 . . . 11362N). In embodiments, the token creation instructions module 11833 may include instructions related to increasing the token supply. In embodiments, the token creation instructions module 11865 may include instructions on how to create new digital asset tokens within pre-approved token supply limits and how to assign newly created or “minted” tokens to specific designated public addresses or contract addresses on the underlying blockchain. In embodiments, the IMPL token creation module 11865 may cause the IMPL Smart Contract 11320 to communicate with STORE Smart contract 11330, the IMPL Smart Contract 11320 sending a transaction request to the Store Smart Contract 11330, causing the Store Smart Contract 11330 to alter a ledger, or otherwise record an increase or decrease in the token supply of a digital asset token.
Referring to
In step S12004, a second designated key pair including a second designated public key (off-line keyset 11803) of the underlying digital asset and a corresponding second designated private key is provided. In embodiments, the second designated private key is stored on a second computer system which is physically separated from the first computer system and is not operatively or physically connected to the distributed public transaction ledger or the internet (network 15). In embodiments, the second computer system may be the hardware storage module 1900. In embodiments, the second designated key pair may be multiple on-line keys with multiple electronic signatures.
In step S12006, first smart contract instructions for a digital asset token associated with a first contract address associated with the blockchain associated with the underlying digital asset are provided. In embodiments, the first contract address is contract address 1 (proxy smart contract) 11809 and first smart contract instructions of step S12006 are the proxy contract instructions 11310A-1, both described in connection with
In step S12008, second smart contract instructions for the digital asset token associated with a second contract address associated with the blockchain associated with the underlying digital asset may be provided. In embodiments, the second smart contract address is at contract address 3 (print limiter smart contact) 11813 and the second smart contract instructions are the print limiter contract instructions 11360A-1, both described in connection with
In embodiments, as described above in connection with print limiter contract instructions 11360A-1 of
In embodiments, as described above in connection with print limiter contract instructions 11360A-1 of
In step S12010, third smart contract instructions for the digital asset token associated with a third contract address associated with the blockchain associated with the underlying digital asset are provided. In embodiments, the third smart contract address is CUSTODIAN 2 smart contract 11350 (contract address 6) and the second smart contract instructions are the custodian 2 contract instructions 11350A-1, both described in connection with
In embodiments, a token creation request may exceed a ceiling (i.e. a request for 150 tokens when the ceiling is 100 tokens), CUSTODIAN 2 smart contract 11350 may authorize an increase in the ceiling. This authorization may be fifth authorization instructions of the CUSTODIAN 2 second authorization instructions module 11851 (i.e. fifth authorization instructions module) and may include instructions for the second designated key pair (off-line keyset 11803 . . . 111803N) to authorize the issuance of instructions to the first smart contract instructions to change the one or more designated contract address from the second contract address to a different designated contract address. In embodiments, a ceiling is raised by creating a second print limiter smart contract on the blockchain 1807 with a higher ceiling. Once the second print limiter smart contract is created, the request for token creation can be routed to the second print limiter smart contract.
A more detailed description of the process of raising the token creation ceiling is located in connection with
In response to receiving the first transaction request, the print limiter 11813 executes the first transaction request 11903 and returns a unique lock identifier (LockId1) to IMPL smart contract 11320 (contract address 2).
Next, referring to
In response to receiving the second transaction request, custodian 1821 executes the second transaction request 11907 and returns a unique hash (reqMessageHash1). The unique hash may be generated by applying a hash algorithm. Examples of hash algorithms include MD 5, SHA 1, SHA 256, RIPEMD, and Keccak-256 to name a few. Hash algorithms take an input of any length and create an output of fixed length, allowing the trade instructions to be detectable and usable by administrators and users on the underlying blockchain. However, applying a hash algorithm is not always necessary if trade instructions are published ahead of time.
In response to the returned unique hash, a third transaction request is generated 1909. The third transaction request may include a request that the reqMessageHash1 to be signed by HSM 11900 offline.
The third request then may be sent 1911 to HSM 11900 and signed using offline private keyset 11803. The signed request may be returned to administrator system 1801.
After returning the signed transaction request, the third transaction request is may be sent 11913 from the on-line public address 11825 to contract address 6 (custodian (print limiter)) 11821. The third transaction request may include a fourth request to complete the unlock with requestMessageHash1 with the HSM signature. In embodiments, the fourth request is signed by on-line private key 1.
After receiving the fourth request, custodian 11821 may execute the request to validate the unlock and return call to contract address 3 (print limiter) 11813 to raise the ceiling, which returns call to contract address 4 (store) 11815 to raise ceiling which updates ceiling.
The process of
The process may continue with step S12013. At step S12013, fifth smart contract instructions for the digital asset token for the digital asset token associated with the blockchain associated with the underlying digital asset are provided. In embodiments, the fifth contract address is the IMPL smart contract 11320 (contract address 2) and the fifth smart contract instructions of step S12013 are the IMPL Contract instructions 11320A-1, both described in connection with
The process described in
In step S12020 the first transaction request is sent by the digital asset token issuer system, from the on-line public key address 11825 to the fifth contract address (IMPL 11320).
Next, in step S12021, the first transaction request is sent by the digital asset token issuer system via the underlying blockhain from the fifth contract address (IMPL 1320) to the second contract address (PRINT LIMITER 11360). In embodiments, the second contract address (PRINT LIMITER 11360) executes, via the blockchain 1807, the first transaction request to return a first unique lock identifier associated with the first transaction request. In embodiments, the first transaction request may include first transaction fee information for miners in the blockchain network to process the first transaction request.
Next, In step S12022, the first unique lock identifier may be obtained by the digital asset token issuer system, based on reference to the blockchain 1807.
In step S12024, a second transaction request may be generated by the digital asset token issuer system. The generated transaction request may include a second message including a second request to unlock the total supply of the digital asset token in accordance with the first request including the first unique lock identifier. The second transaction request being from the on-line public key address 11825 to the third contract address (custodian (print limiter) 11350). In embodiments, the second transaction request may be signed by the first on-line private key.
In step S12026 the second transaction request is sent by the digital asset token issuer system, from the on-line public key address 11825 to the third contract address (custodian (print limiter) 11350). In embodiments, the third contract address (custodian (print limiter) 11350) executes, via the blockchain 1807, the first transaction request to return a first unique lock identifier associated with the second transaction request to return a first unique request hash associated with the second transaction request. In embodiments, the first transaction request may include second transaction fee information for miners in the blockchain network to process the second transaction request.
Next, in step S12028, the first unique request hash is obtained, by the digital asset token issuer system, based on reference to the blockchain 1807.
The process described in
Next, at step S12032, the third transaction request is transferred from the digital asset token issuer system to a first portable memory device. A portable memory device may, in embodiments, be a flash drive, USB drives, external hard drives, and/or portable CD/DVD-ROM drives, to name a few.
At step S12034, the third transaction request is transferred from the first portable memory device to the second computer system. Next, at a step S12036, the third transaction request is digitally signed using the second designated private key (off-line keyset 11803) to generate a third digitally signed transaction request.
The process of
In embodiments, the first portable memory device is the second portable memory device. In embodiments, the first portable memory device is not the second portable memory device. In embodiments, the third digitally signed transaction request is returned to the STORE smart contract 11330. Once returned to the STORE smart contract 11330, the third digitally signed transaction request is returned to the print limiter 11813.
Referring back to
In embodiments, the steps of
Merely for the purposes of description, the following example is provided.
Tx 1.
TO=address of PrintLimiter
DATA=‘requestCeilingRaise(100,000,000)’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function.)
Execution produces a unique lock identifier, say ‘lockId1’.
Tx 2.
TO=address of (Print)Custodian (instance of the Custodian contract, with cold tier keys, intended to be the offline custodian of printing operations)
DATA=‘requestUnlock(lockId1, address of PrintLimiter, selector for functionconfirmCeilingRaise, . . . and a detail I'm going to omit . . . )’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function. If it's a not the primary key there is an anti-spam mechanism.)
Execution produces a unique request hash, say ‘reqMsgHash1’.
2 of the offline keys set up with (Print)Custodian sign ‘reqMsgHash1’; we'll name the signatures ‘sig1_a2’ and ‘sig1_b’
Tx 3.
TO=address of (Print)Custodian
DATA=‘completeUnlock(requestMsgHash1, sig1_a, sig1_b)’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function.)
Execution validates the signatures (and enforces other details around time locks and revocation).
Next, it executes a call to PrintLimiter and its confirmCeilingRaise (NOTE that those two detailed were fixed in Tx2 as parameters to the call to requestUnlock).
CALL ‘(address of PrintLimiter).confirmCeilingRaise(lockId1)’
Execution continues in PrintLimiter in the function ‘confirmCeilingRaise’.
Storage for the contract is updated:
STORE supply ceiling=current supply ceiling+100,000,000
In step S12104, a second designated key pair including a second designated public key (off-line keyset 11803) of the underlying digital asset and a corresponding second designated private key is provided. In embodiments, the second designated private key is stored on a second computer system which is physically separated from the first computer system and is not operatively or physically connected to the distributed public transaction ledger or the internet (network 15). In embodiments, the second computer system may be the hardware storage module 1900. In embodiments, the second designated key pair may be multiple on-line keys with multiple electronic signatures.
In step S12106, first smart contract instructions for a digital asset token associated with a first contract address associated with the blockchain associated with the underlying digital asset are provided. In embodiments, the first contract address is contract address 1 (proxy smart contract) 11809 and first smart contract instructions of step S12106 are the proxy contract instructions 11310A-1, both described in connection with
In step S12108, second contract instructions for the digital asset token associated with a second contract address associated with the blockchain associated with the underlying digital asset is provided. In embodiments, the second smart contract address is contract address 3 (print limiter smart contact) 11813 and the second smart contract instructions are the print limiter contract instructions 11360A-1, both described in connection with
In embodiments, as described above in connection with print limiter contract instructions 11360A-1 of
In embodiments, as described above in connection with print limiter contract instructions 11360A-1 of
In step S12110, third smart contract instructions for the digital asset token associated with a third contract address associated with the blockchain associated with the underlying digital asset are provided. In embodiments, the third smart contract address is CUSTODIAN 2 smart contract 11350 (contract address 6) and the second smart contract instructions are the custodian 2 contract instructions 11350A-1, both described in connection with
In embodiments, a token creation request may exceed a ceiling (i.e. a request for 150 tokens when the ceiling is 100 tokens), CUSTODIAN 2 smart contract 11350 may authorize an increase in the ceiling. This authorization may be fifth authorization instructions of the CUSTODIAN 2 second authorization instructions module 11851 (i.e. fifth authorization instructions module) and may include instructions for the second designated key pair (off-line keyset 11803 . . . 11803N) to authorize the issuance of instructions to the first smart contract instructions to change the one or more designated contract address from the second contract address to a different designated contract address. In embodiments, a ceiling is raised by creating a second print limiter smart contract on the blockchain 1807 with a higher ceiling. Once the second print limiter smart contract is created, the request for token creation can be routed to the second print limiter smart contract.
A more detailed description of the process of raising the token creation ceiling is located above in connection with
The process of
At a step S12114, fifth smart contract instructions are provided for the digital asset token associated with a fifth contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the fifth smart contract address is IMPL smart contract 11320 (contract address 2) and the fifth smart contract instructions are impl contract instructions 11320A-1.
The process of
At step, S12118, the digital asset token issuer system generates the first amount of digital asset token and assigns the first amount of digital asset tokens to the first designated public address. In embodiments, step S12118 may include the digital asset token issuer system generating a first transaction request. The first transaction request, in embodiments, may be address from the online public key address (On-line public address 1 11825) to the fifth contract address (IMPL Smart Contract (Contract Address 2) 11320). The first transaction request may include a first message including a first request to generate the first amount of digital asset token and assign said first amount of digital asset token to the first designated public address. In embodiments, the first transaction request is digitally signed by the first on-line private key (on-line keyset 1362). After the transaction request is generated, the first transaction request may be sent from the online public key address (On-line public address 1 11825) to the fifth contract address (IMPL smart contract 11320 (contract address 2)). In embodiments, the first transaction request includes first transaction fee information for miners in the blockchain network to process the first transaction request.
After the first transaction request is received by the fifth contract address, in embodiments, the fifth smart contract (IMPL 1320) may execute, via the blockchain 1807, the first transaction request to validate the first request and the authority of the first on-line private key (on-line keyset 1 11362) to call the second smart contract (print limiter 11813) to execute the first transaction request. The second smart contract (print limiter 1360) may also send a first call request to the fifth contract address (IMPL smart contract 11320 (contract address 2)) to generate and assign to the first designated public address (user 1 public address 11827) the first amount of digital asset tokens.
In response to the return call, in embodiments, the fifth smart contract (IMPL smart contract 11320) may execute via the blockchain 1807 the first call request to generate a first unique lock identifier. The fifth smart contract (IMPL smart contract 11320) may return to the second smart contract address (print limiter 11813) the first unique lock identifier.
In embodiments, in response to the return of the first unique lock identifier, the second smart contract (print limiter 1360) may execute, via the blockchain 1807, a second call request to the fifth smart contract address (IMPL smart contract 11320 (contract address 2)) to confirm the first call request with the first lock identifier.
In response to the second call request, in embodiments, the fifth smart contract (IMPL smart contract 11320) executes, via the blockchain 1807, the pending first call request to execute a third call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to obtain the total supply of digital asset tokens in circulation.
In embodiments, the fifth smart contract (IMPL 1320) executes, via the blockchain network 1807, the call to execute the first call to execute a second call to the fourth smart contract (STORE smart contract 11330) to obtain the total supply of digital asset tokens in circulation. After executing the third call request, the fourth smart contract (STORE smart contract 11330) returns, to the fifth contract address (IMPL smart contract 11320 (contract address 2)), a second amount of digital asset tokens corresponding to the total supply of digital asset tokens in circulation.
In response to the return of the second amount, in embodiments, the fifth smart contract (IMPL smart contract 11320 (contract address 2)) executes via the blockchain 1807 a fourth call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to set a new total supply of digital asset tokens in circulation to a third amount. The third amount, in embodiments, may be the total of the first amount and the second amount.
In embodiments, in response to the fourth call request, the fourth smart contract (STORE smart contract 11330) executes via the blockchain 1807 the fourth call request and sets a new total supply of digital asset tokens in circulation at the third amount. Once the total supply is set to the third amount, the fourth smart contract (STORE smart contract 11330) returns to the fifth contract address (IMPL smart contract 11320 (contract address 2)).
The fifth smart contract executes, in embodiments, in response to the return, via the blockchain 1807, a fifth call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to add the first amount of digital asset tokens to the balance associated with the first designated public address.
In embodiments, in response to the fifth call request, the fourth smart contract (STORE smart contract 11330) executes, via the blockchain 1807, the fifth call request to set the balance of digital asset tokens in the first designated public address (user 1 public address 11827) at a fourth amount which includes the addition of the first amount to the previous balance.
In embodiments, the fourth smart contract (STORE smart contract 11330) returns to the fifth contract address (IMPL smart contract 11320 (contract address 2)). Once the fifth contract address receives the return, in embodiments, the fifth contract address returns to the second contract address (PRINT LIMITER smart contract 11360 (contract address 3)).
The process of
In embodiments, the steps of
Tx 1.
TO=address of PrintLimiter
DATA=‘limitedPrint(address of User 1, 10,000,000)’
(Tx signed by Administrator . . . analogous to above)
Execution validates that the new supply including 10 million cents would not exceed the ceiling.
Next,
CALL ‘(address of Impl.).requestPrint(address of User 1, 10,000,000)’
Execution continues in Impl. in function ‘requestPrint’.
This function produces a unique lock identifier, say ‘lockId2’.
Execution returns from Impl. to PrintLimiter, passing ‘lockId2’.
Next, in PrintLimiter
CALL ‘(address of Impl).confirmPrint(lockId2)’.
Execution continues in Impl. in function ‘confirmPrint’.
The pending print associated with ‘lockId2’ (address of User 1, 10,000,000) is retrieved.
Next,
CALL ‘(address of Store).totalSupply( )’ (Execution continues in Store, in function totalSupply, which returns with the value of the total supply)
let new supply=current supply+10,000,000
Next,
CALL ‘(address of Store).setTotalSupply(new supply)’
Execution continues in Store in function ‘setTotalSupply’.
STORE total supply=new supply
Execution returns to Impl.
Next,
CALL ‘(address of Store).addBalance(address of User 1, 10,000,000)’
Execution continues in Store in function ‘addBalance’.
STORE balance of User 1=balance of User 1+10,000,000
Execution returns to Impl. (some logging occurs, but let's skip over this)
Execution returns to PrintLimiter and terminates.
In embodiments, the process of
Once the second transaction request is sent, the first smart contract address (contract address 1 (proxy smart contract) 11809) executes, via the blockchain 1807, the second transaction request to execute 11939, via the blockchain 107 a sixth call request to the fifth contract address (IMPL smart contract 11320 (contract address 2)) to transfer a fifth amount of digital assets form the first designated public address (User 1 public address 11827) to the second designated public address (User X public address 11827X). As shown in
In response to the sixth call request, the fifth smart contract (IMPL smart contract 11320 (contract address 2)) executes, via the blockchain 1807, authorization instructions to verify the sixth call came from an authorized contract address, and, upon verification, executes a seventh call request 11941 to the fourth contract address (STORE smart contract 11330 (contract address 4)) to obtain a sixth amount of digital asset tokens which reflect a current balance of digital asset tokens associated with the first designated public address. As shown in
In response to receiving the seventh call request, the fourth smart contract address (STORE smart contract 11330 (contract address 4)) executes 11943, via the blockchain 1807, the seventh call request to return the sixth amount of digital asset tokens. As shown in
In response to the return of the sixth amount of digital asset, the fifth smart contract (IMPL smart contract 11320 (contract address 2)) executes 11945, via the blockchain 1807, a balance verification instruction to confirm that the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens. In the case where the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens, the fifth smart contract executes, via the blockchain 1807, a seventh call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to set a new balance for the digital asset tokens in the first designated public address to a seventh amount which equals the sixth amount less the fifth amount. As shown in
In response to the seventh call, the fourth smart contract (STORE smart contract 11330) executes 11947, via the blockchain 1807, the seventh call to set and store the new balance for the first designated public address as the seventh amount and returns the new balance for the first designated public address as the seventh amount. As shown in
In response to the return of the new balance, the fifth smart contract (IMPL smart contract 11320) executes 11949, via the blockchain 1807, an eighth call to add the second amount of digital asset tokens to the balance associated with the second designated public address (User X public address 11827X) at a seventh amount which includes the addition of the second amount to a previous balance associated with the second designated public address. As shown in
In response to receiving the either call, the store smart contract executes the eighth call and sets the balance associated with the second user to the balance before the transfer and the transfer amount 11951.
In embodiments, the STORE smart contract 11330 returns to the IMPL smart contract 11320. In response to the return, the IMPL smart contract 11320 may log the new balance associated with the second user 11953. In embodiments, the IMPL smart contract 11320 may then return to the proxy smart contract 11310.
In embodiments, once the transfer has been completed, the first user device (user 1 device 11805) may confirm that the balance of digital asset tokens in the first designated public address is the sixth amount of digital asset tokens based on reference to the blockchain 1807. Similarly, the second user device (user X device 11805X) may also confirm that the balance of digital asset tokens in the second designated public address is the seventh amount of digital asset tokens based on reference to the blockchain 1807.
Tx 1.
TO=address of Proxy
DATA=‘transfer(address of User 2, 1,000)’
Tx signed by User 1 private key, therefore FROM=address of User 1 public key
Execution immediately jumps to Impl.
CALL ‘(address of Impl.).transferWithSender(address of User 1, address of User 2, 1,000)’
Execution continues in Impl. in function ‘transferWithSender’.
This function validates that it was called by the sender it trusts, so it checks that sender is address of Proxy.
Next,
CALL ‘(address of Store).balances(address of User 1)’ (Execution continues in Store, in function ‘balances’, which returns the balance associated with the address of User 1)
Execution returns and continues in Impl where the retrieved balance value is compared to 1,000 to check that User 1 has at least 1,000 tokens.
let new balance of User 1=balance of User 1−1,000
Next,
CALL ‘(address of Store).setBalance(address of User 1, new balance of User 1)’
Execution continues in Store in function ‘setBalance’. (function checks that it was called by the sender it trusts, the active Impl.)
STORE balance of User 1=new balance of User 1
Execution returns to Impl.
Next,
CALL ‘(address of Store).addBalance(address of User 2, 1,000)’
Execution continues in Store in function ‘addBalance’. (function checks that it was called by the sender it trusts . . . )
STORE balance of User 2=balance of User 2+1,000
Execution returns to Impl. (some logging occurs, but let's skip over this)
Execution returns to Proxy and terminates.
In embodiments, the process of
The blockchain 1807 may receive a second transaction request 11955 by the blockchain 1807 from the third computer system (i.e. user device 1). The second transaction request may include a second message including a second request to burn a fifth amount of digital asset tokens from a balance associated with the third designated public key address. The second transaction request may be sent from the third designated public key address to the fifth contract address (IMPL smart contract 11320 (contract address 2)). The second transaction request, in embodiments, is digitally signed by a third designated private key.
In response to receiving the second transaction request, the fifth smart contract (IMPL smart contract 11320) executes 11957, via the blockchain 1807, the second transaction request to execute, via the blockchain 1807, a sixth call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to obtain a sixth amount of digital asset tokens which reflect a current balance of digital asset tokens associated with the third designated public key address. As shown in
In response to the sixth call request, the fourth smart contract (STORE smart contract 11330), executes 11959 via the blockchain 1807, the seventh call request to return the sixth amount of digital asset tokens. As shown in
In response to the return of the sixth amount of digital asset, the fifth smart contract (IMPL smart contract 11320) executes 11961, via the blockchain 1807, a balance verification instruction to confirm that the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens. In the case where the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens, the fifth smart contract (IMPL smart contract 11320) executes, via the blockchain 1807, a seventh call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to set a new balance for the digital asset tokens in the third designated public key address to a seventh amount which equals the sixth amount less the fifth amount. As shown in
In response to the seventh call, the fourth smart contract (STORE smart contract 11330) executes 11963, via the blockchain 1807, the seventh call to set and store the new balance for the third designated public key address as the seventh amount and returns the new balance for the third designated public key address as the seventh amount. As shown in
In response to the return of the new balance, the fifth smart contract (IMPL smart contract 11320) executes 11965, via the blockchain 1807, an eighth call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to obtain a total supply of digital asset tokens in circulation. As shown in
In response to the eighth call request, the fourth smart contract (STORE smart contract 11330) executes 11967, via the blockchain 1807 the eighth call request and returns, to the fifth contract address (IMPL smart contract 11320 (contract address 2)), an eighth amount of digital asset tokens corresponding to the total supply of digital asset tokens in circulation. As shown in
In response to the return of the eighth amount, the fifth smart contract (IMPL smart contract 11320) executes 11969, via the blockchain, a ninth call request to the fourth contract address (STORE smart contract 11330 (contract address 4)) to set a new total supply of digital asset tokens in circulation to a ninth amount, which is the eighth amount less the fifth amount. As shown in
In response to the ninth call request, the fourth smart contract (STORE smart contract 11330) executes 11971, via the blockchain 1807, the ninth call request and sets a new total supply of digital asset tokens in circulation at the ninth amount and returns to the fifth contract address (IMPL smart contract 11320 (contract address 2)). In embodiments, the token balance modification instructions module 11847 balances the deposits and withdrawals at a predetermined time (i.e. end of the day or close of business).
In response to receiving a return from the STORE smart contract 11330, the IMPL smart contract 11320 logs 11973 the new total supply of digital asset tokens in circulation.
Tx 1.
TO=address of Impl.
DATA=‘burn(1,000,000)’
(Tx is signed by the key of the address that is going to sacrifice some of its balance.)
let address of sender=address of key that signed Tx 1.
Execution immediately jumps to Store
CALL ‘(address of Store).balances(address of sender)’ (Execution continues in Store, in function ‘balances’, which returns the balance associated with the sender)
Execution returns and continues in Impl where the retrieved balance value is compared to the burn amount of 1,000,000 to check that the sender has at least 1,000,000 tokens.
let new balance of sender=balance of sender−1,000,000
Next,
CALL ‘(address of Store).setBalance(address of sender, new balance of sender)’
Execution continues in Store in function ‘setBalance’. (function checks that it was called by the sender it trusts, the active Impl.)
STORE balance of sender=new balance of sender
Execution returns to Impl.
Next,
Call ‘(address of Store).totalSupply( )’ (Execution continues in Store, in function ‘totalSupply’, which returns with the value of the total supply)
let new supply=current supply+1,000,000
Next,
CALL ‘(address of Store).setTotalSupply(new supply)’
Execution continues in Store in function ‘setTotalSupply’.
STORE total supply=new supply
Execution returns to Impl. (some logging occurs, but let's skip over this) And execution terminates.
Tx 1.
TO=address of Proxy
DATA=‘requestImplChange(address of Impl_V2)’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function.)
Execution produces a unique lock identifier, say ‘lockId3’.
Tx 2.
TO=address of (Upgrade)Custodian (instance of the Custodian contract, with cryo tier keys, intended to be the offline custodian of upgrade operations)
DATA=‘requestUnlock(lockId3, address of Proxy, selector for function confirmImplChange, . . . and a detail I'm going to omit . . . )’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function. If it's a not the primary key there is an anti-spam mechanism.)
Execution produces a unique request hash, say ‘reqMsgHash2’.
2 of the offline keys set up with (Upgrade)Custodian sign ‘reqMsgHash2’; we'll name the signatures ‘sig2_a’ and ‘sig2_b’.
Tx 3.
TO=address of (Upgrade)Custodian
DATA=‘completeUnlock(requestMsgHash2, sig2_a, sig2_b)’
(Tx would be signed by Adminstrator's ‘primary’ key, although there are no restrictions on who can call this function.)
Execution validates the signatures (and enforces other details around time locks and revocation).
Next, it executes a call to Proxy and its confirmImplChange (NOTE that those two detailed were fixed in Tx2 as parameters to the call to requestUnlock).
CALL ‘(address of Proxy). confirmImplChange(lockId3)’
Execution continues in PrintLimiter in the function ‘confirmImplChange’.
Storage for the active implementation address is updated:
STORE impl=address of Impl_V2
(some logging occurs, but let's skip over this)
Execution returns to (Upgrade)Custodian
(some logging occurs, but let's skip over this)
Execution terminates.
In response to receiving the first transaction request, the PRINT LIMITER smart contract 11360 executes 11919 a first call request, via the blockchain 1807, to the impl smart contract address 11811 to print 10 million digital asset tokens to user 1 public address 11827. In response to receiving the first call request, the impl returns a lockID 11921 to the print limiter smart contract address 11813.
In response to receiving the lockID, the print limiter smart contract executes 11923 a second call request, via the blockchain 1807, to the impl smart contract address 11811 to confirm the print of 10 million digital asset tokens using the lockID.
In response to receiving the second call, the IMPL smart contract 11320 retrieves the pending request to print 10 million digital asset tokens and executes 11925, via the blockchain 1807, a third call request to the store smart contract address 11815 to determine the total supply of digital asset tokens.
In response to receiving the third call, the STORE smart contract 11330 determines 11927 the total supply of digital asset tokens to be 100 million digital asset tokens. The total supply amount determined by the STORE smart contract 11330 is then returned by the STORE smart contract 11330 to the impl smart contract address 11811.
In response to receiving the return from the store smart contract address 11815, the impl smart contract address executes 11929, via the blockchain, a fourth call request to set the total supply of digital asset tokens to 110 million, the original total supply 100 million plus the requested print amount of 10 million. The fourth call request may be sent to the store smart contract address 11815.
In response to receiving the fourth call request, the STORE smart contract 11330 sets 11931 the total supply of digital asset tokens to 110 million digital asset tokens and returns to the impl smart contract address 11811.
In response to receiving the return from the store smart contract address 11815, the impl smart contract may execute 11933 a fifth call to add the newly printed 10 million digital asset tokens to user 1 public address 11827. The call may be sent to the store smart contract address 11815.
In response to receiving the fifth call to add the 10 million digital asset tokens to user 1 public address 11827, the STORE smart contract 11330 may store 1935 a new balance associated with the user 1 public address 11827, the new balance being the original balance plus the 10 million digital asset tokens. The STORE smart contract 11330 may then return to the impl smart contract address 11811. In response to receiving the return from the STORE smart contract 11330, the impl smart contract may return to the print limiter smart contract public address 11813.
In embodiments, the steps of
In embodiments, the first designated key pair may include a plurality of key pairs (e.g. on-line keyset N 11362N). For example, the first designated key pair may further include a first additional designated public key and a corresponding first additional designated private key. In embodiments, each key pair of the aforementioned plurality of key pairs of the first designated key pair may each correspond to a designated public address. For example, a first key pair of the plurality of key pairs may correspond to a first designated public address associated with the underlying digital asset. A second key pair of the plurality of key pairs may correspond to a second designated public address associated with the underlying digital asset. In embodiments, each key pair of the aforementioned plurality of key pairs may correspond to the same designated public address. For example, the first and second key pairs mentioned in the examples above may be associated with the same designated public address.
In embodiments, the first designated public address may be derived by using and/or applying a cryptographic hash function of the first designated public key. In embodiments, the first designated public address is a result of the cryptographic hash function, or, in embodiments, at least a part of the result of the cryptographic hash function. A cryptographic hash function may be a hash function that is a mathematical algorithm which maps data of arbitrary size to a bit string of a fixed size (e.g. a hash). In embodiments, the cryptographic hash function may be designed to be a one-way function (e.g. a function that is infeasible to invert). The cryptographic hash function, may include one or more of the following prosperities: (1) deterministic such that the same message produces results in the same hash; (2) high speed, such that the hash value for a message is computed in a manner that does not slow the process down; (3) infeasible to generate a message from the hash, such that generating a message from the hash value would require attempting all possibilities (e.g. a brute force approach); and (4) unique, such that messages to not have the same hash value and/or small changes to a message alter the hash value such that the values do not correlate, to name a few.
The process of
In embodiments, the second designated key pair may be stored on a second computer system. The second computer system may be physically and/or operationally separated from the first computer system. Additionally, the second computer system may be physically and/or operationally separated (e.g. not connected to) from the distributed public transaction ledger and/or the internet (e.g. network 15). This separation, as described above in connection with
In embodiments, the second computer system may be a hardware storage module. The hardware storage module may be located in a vault (e.g. Vault 70-A1) Location A, Location B, Location C . . . Location N described above in connection with
In embodiments, the hardware storage module, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the second designated key pair. For example, the second designated key pair may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the second designated key pair may include a plurality of key pairs (e.g. off-line keyset N 11803N). For example, the second designated key pair may further include a first additional designated public key and a corresponding first additional designated private key. In embodiments, each key pair of the aforementioned plurality of key pairs of the second designated key pair may each correspond to a designated public address. For example, a first key pair of the plurality of key pairs may correspond to a first designated public address associated with the underlying digital asset. A second key pair of the plurality of key pairs may correspond to a second designated public address associated with the underlying digital asset. In embodiments, each key pair of the aforementioned plurality of key pairs may correspond to the same designated public address. For example, the first and second key pairs mentioned in the examples above may be associated with the same designated public address.
In embodiments, the second designated public address may be derived by using and/or applying a cryptographic hash function of the second designated public key. In embodiments, the second designated public address is a result of the cryptographic hash function, or, in embodiments, at least a part of the result of the cryptographic hash function. The cryptographic hash function applied may be similar and/or the same cryptographic hash function applied to the first designated key pair. In embodiments, the cryptographic hash function applied to the second designated key pair may be different than the cryptographic hash function applied to the first key pair. A different cryptographic hash function may be used, in embodiments, as an additional security measure.
In embodiments, the process of
The first authorization instructions, in embodiments, may be associated with the second designated key pair. In embodiments, first authorization instructions may be similar to the authorization instructions described above in connection with PROXY Authorization Instructions Module 11831.
In embodiments, the first smart contract may be PROXY smart contract 11310 described above in connection with
The process or
The print limiter token creation instructions, in embodiments, may indicate one or more conditions under which digital asset tokens of the underlying digital asset are created. In embodiments, the print limiter token creation instructions may be similar to the PRINT LIMITER token creation instructions described above in connection with the PRINT LIMITER Token Creation Instructions Module 11833.
The second authorization instructions, in embodiments, may include instructions to create tokens of the digital asset token. In embodiments, the first designated key pair is designated to authorize the second authorization instructions. In embodiments, the second designated key pair is designated to authorize the second authorization instructions. The second authorization instructions, in embodiments, may include instructions limiting the creation of digital asset tokens. The limitation placed on token creation may prevent the creation of tokens above a first threshold. For example, the second authorization instructions may limit the creation of tokens to 100,000 tokens. In embodiments, the first threshold may be relative to a first period of time. For example, the second authorization instructions may limit the creation of tokens to 500,000 tokens per day. In embodiments, the second authorization instructions may be similar to the first authorization instructions described above in connection with PRINT LIMITER First Authorization Instructions Module 11839.
The third authorization instructions, in embodiments, may also include instructions with respect to token creation. In embodiments, the third authorization instructions may designate a first designated custodian address (e.g. a custodian address associated with CUSTODIAN 2 Smart Contract 11350) with respect to token creation of the digital asset token. In embodiments, the third authorization instructions may be similar to the second authorization instructions described above in connection with PRINT LIMITER Second Authorization Instructions Module 11841.
In embodiments, the second smart contract instructions may also include token balance modification instructions (e.g. instructions of the Token Balance Modification Instructions Module 11847). The token balance modification instructions may be related to modifying the total balance of tokens of the digital asset token assigned to a third delegated contract address. In embodiments, the third delegated contract address may be of the one or more delegated contracted addresses. In embodiments, the token balance modification instructions may be similar to the optional token balance modification instructions described above in connection with Token Balance Modification Instructions Module 11847.
In embodiments, the second smart contract may further include additional authorization instructions. The additional authorization instructions may be similar to the optional PRINT LIMITER THIRD Authorization instructions described above in connection with PRINT LIMITER Third Authorization Instructions Module 11835.
In embodiments, the second smart contract may be PRINT LIMITER Smart Contract 11360 described above in connection with
In embodiments, the process of
The fourth authorization instructions, in embodiments, may authorize the issuance of instructions to the second smart contract. The issued instructions that are authorized by the fourth authorization instructions may regard token creation. In embodiments, the fourth authorization instructions designate the second designated key pair to authorize the fourth authorization instructions. In embodiments, the fourth authorization instructions designate the first key pair to authorize the fourth authorization instructions. In embodiments, the fourth authorization instructions include instructions to permit the creation of digital asset tokens above a first threshold defined by the second authorization instructions. In embodiments, the fourth authorization instructions may be similar to the authorization instructions described in connection with CUSTODIAN 2 First Authorization Instructions Module 11849.
The sixth authorization instructions, in embodiments, may designate a seventh contract address as one of the one or more delegated contract addresses. In embodiments, the seventh contract address is not the second contract address. In embodiments, the second designated key pair is designated to authorize the sixth authorization instructions. In embodiments, the first designated key pair is designated to authorize the sixth authorization instructions. In embodiments, the sixth authorization instructions may be similar to the authorization instructions described in connection with CUSTODIAN 2 Second Authorization Instructions Module 11851.
In embodiments, the third smart contract may be CUSTODIAN 2 Smart Contract 11350 described above in connection with
In embodiments, the process of
The token creation instructions may, in embodiments, be instructions to create tokens of the digital asset tokens. In embodiments, the token creation instructions may create tokens in accordance with the conditions set forth by the print limiter token creation instructions of the second smart contract. The token creation instructions may be similar to instructions described in connection with the IMPL Token Creation Instructions Module 11865.
The second delegation instructions, in embodiments, may delegate data storage operations to at least a fifth contract address. In embodiments, the fifth contract address may be associated with Contract Address 4 of STORE Smart Contract 11330. For example, the second delegation instructions may cause STORE Smart Contract 11330 to execute storage instructions of Storage Instructions Module 11853. The second delegation instructions may be similar to instructions described in connection with IMPL Delegation Instructions Module 11861.
In embodiments, the token transfer instructions may be related to transferring issued tokens of the digital asset token. The transfer of tokens may be from a first designated contract address to a second designated contract address. For example, issued tokens may be transferred from a contract address associated with a digital asset token issuer system to a user public address associated with a user attempting to purchase tokens of the underlying digital asset. The token transfer instructions may be similar to instructions described in connection with IMPL Token Transfer Instructions Module 11859.
In embodiments, the token destruction instructions may be related to destroying and/or burning one or more issued tokens of the digital asset token. For example, if a user is attempting to exchange a token for, as an example, fiat, the token being exchanged may be burned once the token is exchanged for fiat.
In embodiments, the fourth smart contract may be IMPL Smart Contract 11320 described above in connection with
In embodiments, the process of
The data storage instructions, in embodiments, may include instructions to store transaction data related to the digital asset token. Transaction data, in embodiments, may include transaction information for one or more of the issued tokens of the digital asset token. The transaction information, may include at least one of: (1) respective public address information associated with the blockchain of the underlying digital asset, and/or (2) corresponding respective token balance information which may be associated with the aforementioned respective public address information. In embodiments, the transaction data may include transaction information for all of the issued tokens of the digital asset token. In embodiments, the data storage instructions may be similar to instructions described in connection with Storage Instructions Module 11853.
The fifth authorization instructions may include authorization instructions to modify the transaction data in response to a request. In embodiments, the request may be received from the fourth contract address. The fifth authorization instructions may be similar to instructions described above in connection with STORE Authorization Instructions 11855.
In embodiments, the fifth smart contract may be STORE Smart Contract 11330 described above in connection with
In embodiments, the process of
Referring to
In embodiments, the first request may be to decrease the total supply of digital asset tokens to a third amount. This example may follow the same process described in connection with
The process may continue with a step S13922. In embodiments, at step S13922, the first transaction request may be sent by the digital asset token issuer system, from the first designated public address to the fourth contract address. In embodiments, the first transaction request may be sent via the blockchain of the underlying digital asset. In embodiments, the first transaction request may be sent via network 15.
The process may continue with step S13924 where the first transaction request may be sent from the fourth contract address to the second contract address via the blockchain for the underlying digital asset. In embodiments, once the first transaction request is received by the second contract address, the second smart contract may execute the first transaction request. The execution of the first transaction request may, in embodiments, be to return a first unique lock identifier associated with the first transaction request. In embodiments, the first transaction request is executed via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain for the underlying digital asset.
In embodiments, the process may continue with step S13926, where the digital asset token issuer system may obtain the first unique lock identifier. In embodiments, the first unique lock identifier may be obtained based on reference to the blockchain for the underlying digital asset.
In embodiments, the process may continue with step S13928 where a second transaction request may be generated by the digital asset token issuer system. In embodiments, the second transaction request may be generated in response to the first unique lock identifier being obtained. The second transaction request may, in embodiments, include a second message which may include a second request to unlock the total supply of the digital asset tokens. The second request may be in accordance with the first request. Moreover, in embodiments, the second request may include the first unique lock identifier. In embodiments, the second transaction request may be digitally signed by the first designated private key. In embodiments, the second transaction request may be digitally signed by the second designated private key. In embodiments, the second transaction request may include second transaction fee information for minors associated with the plurality of geographically distributed computer systems in the peer-to-peer network. The second transaction fee information may be a predetermined amount of currency which may be related to the cost of processing the second transaction request.
The process of
The process may continue with step S13932 where, in embodiments, the first unique request hash may be obtained by the digital asset token issuer system. In embodiments, the first unique request hash may be obtained based on reference to the blockchain for the underlying digital asset.
At a step S13934, in embodiments, a third transaction request may be generated. The third transaction request may, in embodiments, be generated to be digitally signed by at least the second designated private key. In embodiments, the third transaction request may include the first unique request hash. The third transaction request, in embodiments, may be generated in response to the digital asset token issuer system obtaining the first unique request hash.
In embodiments, at a step S13936, the third transaction request may be transferred to a first portable memory device. In embodiments, the third transaction request may be transferred to the first portable memory device by an administrator (e.g. an administrator of administrator system 1801). In embodiments, the third transaction request may be transferred from the digital asset token issuer system to the first portable memory device. In embodiments, the first portable memory device, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the third transaction request. For example, the third transaction request may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the process may continue with step S13938 where the third transaction request may be transferred from the first portable memory device to the second computer system. In embodiments, the third transaction request may be transferred to the second computer system by an administrator (e.g. an administrator of administrator system 1801).
In embodiments, the process of
In embodiments, once the third digitally signed transaction request is generated, the third digitally signed transaction request may be transferred from the second computer system to a second portable memory device. The second portable memory device may, in embodiments, be the first portable memory device (e.g. the first and second portable memory device are the same portable memory device). In embodiments, the second portable memory device may be physically and operatively separate from the first portable memory device. In embodiments, the second portable memory device, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the third transaction request. For example, the third transaction request may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the process may continue with step S13942 where the third digitally signed transaction request may be sent from the portable memory device to the third contract address using the digital asset token issuer system, via the blockchain for the underlying digital asset. In embodiments, the portable memory device may be the second portable memory device. To send the third digitally signed transaction request, in embodiments, the third digitally signed transaction request may be first transferred from the second portable memory device to the digital asset token issuer system. Once transferred, in embodiments, the third digitally signed transaction request may be sent by the digital asset token issuer system to the third contract address.
In response to receiving the third digitally signed transaction request, in embodiments, the third smart contract may execute the third digitally signed transaction request. In embodiments, the execution of the third digitally signed transaction request may result in a request to validate the second request to unlock the total supply of digital asset tokens based on the third digitally signed transaction request and/or the first unique request hash. In embodiments, the execution may also result in a first call to the second contract address. The first call may be to increase the total supply of the digital asset tokens from the first amount to the second amount. In embodiments, the third smart contract may execute the third digitally signed transaction request via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
The first call sent by the third smart contract to the second contract address of the second smart contract may, in embodiments, result in the second contract address returning the first call to the fourth contract address. The fourth contract address may, in response to receiving the returned first call, execute a second call to the fifth contract address. The second call, in embodiments, may be to set the total supply of the digital asset tokens to the second amount of digital asset tokens. In embodiments, the fourth smart contract may execute the second call via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
The second call sent by the fourth smart contract to the fifth contract address of the fifth smart contract may, in embodiments, result in the fifth smart contract executing the second call to set the total supply of the digital asset tokens to the second amount of digital asset tokens. In embodiments, the fifth smart contract may execute the second call via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
In embodiments, the steps of the process described in connection with
Referring back to
In embodiments, the digital asset token issuer system may determine that the total supply of digital asset tokens is not the second amount of digital asset tokens. For example, the digital asset token issuer system may determine that the total supply of digital asset tokens is set to a third amount, the third amount being different than the second amount of digital asset tokens. In these embodiments, the digital asset token issuer system may generate and/or send a warning message for an administrator (e.g. an administrator of administrator system 1801). In embodiments, the administrator system may be the token issuer system. In embodiments, the administrator system may not be the token issuer system. The warning message may include a notification stating that the amount of tokens is incorrect and/or needs to be fixed. Additionally, the warning message may include a transaction ledger (e.g. Network Digital Asset Transaction Ledger 3228). Moreover, the warning message may include the third amount of digital asset tokens. Furthermore, the warning message may include the intended amount of digital asset tokens (e.g. the second amount of digital asset tokens). In embodiments, if the digital asset token issuer system determines the total supply of tokens is incorrect, the digital asset token issuer system may repeat one or more of the steps of the processes described above in connection with
In embodiments, the steps of the process described in connection with
In embodiments, a process for increasing a total supply of digital asset tokens including may begin with providing a first designated key pair. The first designated key pair, in embodiments, may include a first designated public key and a corresponding first designated private key. The first designated private key may also correspond to a first designated public address associated with an underlying digital asset. In embodiments, the underlying digital asset is maintained on a distributed public transaction ledger maintained in the form of a blockchain by a plurality of geographically distributed computer systems in a peer-to-peer network in the form of a blockchain network. In embodiments, the first designated private key is stored on a first computer system which is connected to the distributed public transaction ledger through the Internet (e.g. network 15).
In embodiments, the process may continue with providing a second designated key pair. In embodiments, the second designated key pair includes a second designated public key and a corresponding second designated private key. In embodiments, the second designated public key also corresponds to a second designated public address associated with the underlying digital asset. In embodiments, the second designated private key is stored on a second computer system which is physically separated from the first computer system and is not operatively and/or physically connected to the distributed public transaction ledger or the Internet.
In embodiments, the process may continue with providing first smart contract instructions associated with a first smart contract associated with a digital asset token associated with a first contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the first smart contract instructions are saved as part of the blockchain for the underlying digital assets. In embodiments, the first smart contract instructions include first delegation instructions to delegate one or more first functions associated with the digital asset token to one or more delegated contract addresses associated with the blockchain associated with the underlying digital asset. The one or more delegated contract addresses, in embodiments, is different from the first contract address. In embodiments, a second contract address is designated as one of the one or more delegated contract addresses. In embodiments, the first smart contract instructions include first authorization instructions for the second designated key pair.
The process may continue, in embodiments, with providing second smart contract instructions associated with a second smart contract associated with the digital asset token associated with the second smart contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the second smart contract instructions are saved as part of the blockchain for the underlying digital asset. In embodiments, the second smart contract instructions may include: (1) print limiter token creation instructions indicating conditions under which tokens of the digital asset token are created; (2) second authorization instructions to create tokens of the digital asset token, wherein the first designated key pair is designated to authorize said second authorization instructions to create tokens of the digital asset token; and (3) third authorization instructions with respect to token creation of the digital asset token; wherein the third authorization instructions designate a first designated custodian address with respect to token creation of the digital asset token, to name a few.
In embodiments, the process may continue with providing third smart contract instructions associated with a first designated custodian smart contract associated with the digital asset token associated with a third contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the third contract address is the first designated custodian contract address. In embodiments, the third smart contract instructions are saved as part of the blockchain associated with the underlying digital asset. In embodiments, the third smart contract instructions include fourth authorization instructions to authorize issuance of instructions to the second smart contract regarding token creation. In embodiments, the fourth authorization instructions designate the second designated key pair to authorize the fourth authorization instructions.
In embodiments, the process may continue with providing fourth smart contract instructions associated with a fourth smart contract associated with the digital asset token associated with a fourth contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the fourth contract address is one of the one or more delegated contract addresses and not: (i) the first contract address, (ii) the second contract address, and/or (iii) the third contract address. In embodiments, the fourth smart contract instructions are saved as part of the blockchain associated with the underlying digital assets. In embodiments, the fourth smart contract instructions include: (1) token creation instructions to create tokens of the digital asset token in accordance with conditions set forth by the print limiter token creation instructions; and/or (2) second delegation instructions delegating data storage operations to at least a fifth contract address, to name a few.
In embodiments, the process may continue with providing fifth smart contract instructions associated with a fifth smart contract associated with the digital asset token associated with the fifth contract address associated with the blockchain associated with the underlying digital asset. In embodiments, the fifth smart contract address is one of the one or more designated store contract addresses. In embodiments, the fifth smart contract instructions are saved as part of the blockchain for the underlying digital assets. In embodiments, the fifth smart contract instructions include: (1) data storage instructions for transaction data related to the digital asset token, said transaction data includes for all issued tokens of the digital asset token: (A) respective public address information associated with the blockchain associated with the underlying digital asset; and (B) corresponding respective token balance information associated with said respective public address information; and/or (2) fifth authorization instructions to modify the transaction data in response to requests from the fourth contract address;
In embodiments, the process may continue with receiving, by a digital asset token issuer system, a request to generate and assign to the first designated public address a first amount of digital asset tokens;
In embodiments, the process may continue with generating, by the digital asset token issuer system, the first amount of digital asset tokens and assigning said first amount of digital asset tokens to the first designated public address increasing the total supply of the digital asset tokens. In embodiments, generating the first amount of digital asset tokens and assigning said first amount of digital asset tokens to the first designated public address may include a sub-process.
The sub-process may begin with the step of generating, by the digital asset token issuer system, and sending, using the digital asset token issuer system via the blockchain network, a first transaction request: (A) to the fourth contract address; and (B) including a first message including a first request to generate the first amount of digital asset tokens and assign said first amount of digital asset tokens to the first designated public address. In embodiments; the first transaction request is digitally signed by the first designated private key. In embodiments, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the first transaction request to: (i) validate the first request and the authority of the first designated private key to call the second smart contract to execute the first request; and (ii) send a first call to the fourth contract address to generate and assign to the first designated public address the first amount of digital asset tokens. In embodiments, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the first call to generate a first unique lock identifier, and return to the second smart contract address, the first unique lock identifier. In embodiments, in response to the return of the first unique lock identifier, the second smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, a call to the fourth smart contract address to confirm the first call with the first lock identifier. In embodiments, in response, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the first call to execute a second call to the fifth contract address to obtain the total supply of digital asset tokens in circulation. In embodiments, in response, the fifth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the second call and returns, to the fourth contract address, a second amount of digital asset tokens corresponding to the total supply of digital asset tokens in circulation. In embodiments, in response to the return of the second amount, the fourth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, a third call request to the fifth contract address to set a new total supply of digital asset tokens in circulation to a third amount, which is the total of the first amount and the second amount. In embodiments, in response to the third call, the fifth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the third call and sets a new total supply of digital asset tokens in circulation at the third amount. In embodiments, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, a fourth call to the fifth contract address to add the first amount of digital asset tokens to a respective balance associated with the first designated public address. In embodiments, in response, the fifth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the fourth call to set the balance of digital asset tokens in the first designated public address at a fourth amount which includes the addition of the first amount to the previous balance.
The process for increasing the total supply of digital asset tokens may continue with confirming, by the digital asset token issuer system, that the balance of digital asset tokens associated with the first designated public address is set to include the first amount of digital asset tokens based on reference to the blockchain.
In embodiments, the second computer system is a hardware storage module.
In embodiments, the second designated key set includes an additional designated key set including an additional designated public address and an additional designated private key.
In embodiments, the second authorization instructions for the first designated key set with respect to token creation of the digital asset token include instruction limiting token creation above a first threshold over a first period of time.
In embodiments, the fourth authorization instructions for the second designated key set to authorize the issuance of instructions to the second smart contract instructions with respect to token creation include instructions to allow for creation of digital asset tokens above the first threshold during the first period of time.
In embodiments, the third smart contract instructions further include: (2) sixth authorization instructions to designate a seventh contract address as one of the one or more delegated contract addresses. In embodiments, the seventh contract address is not the second contract address. In embodiments, the second designated key set is designated to authorize the sixth authorization instructions. In embodiments, the fourth smart contract instructions further include: (3) token transfer instructions related to transferring tokens of the digital asset token from a first designated contract address to a second designated contract address. In embodiments, the fourth smart contract instructions further include: (3) token destruction instructions related to destroying one or more digital asset token. In embodiments, the fourth smart contract instructions further include: (3) token balance modification instructions related to modifying a total number of tokens of the digital asset token assigned to a third designated public address. In embodiments, the fourth smart contract instructions further include: (3) token transfer instructions related to transferring tokens of the digital asset token from a first designated contract address to a second designated contract address; and (4) token destruction instructions related to destroying one or more tokens of the digital asset token.
In embodiments, the process further includes receiving, prior to generating the first amount of digital asset tokens, a validating request. In embodiments, the process further includes determining the first designated key set has authority to process the request to generate the first amount of digital tokens.
In embodiments, the first transaction request includes first transaction fee information for miners in the plurality of geographically distributed computer systems in the peer-to-peer network to process the first transaction request.
In embodiments, the fifth contract returns the balance of digital asset tokens to the fourth smart contract address. In embodiments, the fifth contract returns the balance of digital asset tokens to the second smart contract address.
In embodiments, the process further for increasing the total supply of digital asset tokens continues with receiving, by the plurality of geographically distributed computer systems in the peer-to-peer network, from a first user device associated with the first designated public address, via the underlying blockchain, a second transaction request: (A) from the first designated public address; (B) to the first contract address; and (C) including a second message including a second request to transfer a fifth amount of digital assets from the first designated public address to a third designated public address. In embodiments, the first transaction request is digitally signed by the first designated private key, which is mathematically related to the first designated public address. In embodiments, the first user device had access to the first designated private key prior to sending the second transaction request. In embodiments, the first smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, the second transaction request to execute, via the plurality of geographically distributed computer systems in the peer-to-peer network, a sixth call request to the fourth contract address to transfer a fifth amount of digital assets from the first designated public address to the third designated public address. In embodiments, in response to the sixth call request, the fourth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network, sixth authorization instructions to verify the sixth call came from an authorized contract address, and upon verification, to execute a seventh call request to the fifth contract address to obtain a sixth amount of digital asset tokens which reflect a current balance of digital asset tokens associated with the first designated public address. In embodiments, in response to the seventh call request, the fifth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network, the seventh call request to return the sixth amount of digital asset tokens In embodiments, in response to the return of the sixth amount of digital asset, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network: (1) a balance verification instruction to confirm that the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens, and (2) in the case where the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens, execute, via the plurality of geographically distributed computer systems in the peer-to-peer network, a seventh call request to the fifth contract address to set a new balance for the digital asset tokens in the first designated public address to a seventh amount which equals the sixth amount less the fifth amount. In embodiments, in response to the seventh call, the fifth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, the seventh call to set and store the new balance for the first designated public address as the seventh amount and returns a new balance for the first designated public address as the seventh amount. In embodiments, in response to the return of the new balance, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, an eighth call to add the second amount of digital asset tokens to the balance associated with the third designated public address. In embodiments, in response to the eighth call request, the fifth smart contract executes, via the blockchain network, the eighth call request to set the balance of digital asset tokens associated with the third designated public address at a seventh amount which includes the addition of the second amount to a previous balance associated with the third designated public address; and wherein the first user device confirms that the balance of digital asset tokens associated with the first designated public address is the sixth amount of digital asset tokens based on reference to the blockchain.
In embodiments, the second transaction request includes second transaction fee information for miners in the plurality of geographically distributed computer systems in the peer-to-peer network to process the second transaction request. In embodiments, the balance of digital asset tokens associated with the third designated public address is returned to the fourth contract address. In embodiments, the balance of digital asset tokens associated with the third public address is returned to the first smart contract address. In embodiments, a second user device confirms that the balance of the digital asset tokens associated with the third designated public address is the seventh amount of digital asset tokens based on reference to the blockchain.
In embodiments, the process of increasing the total supply of digital asset tokens further includes providing a third designated key set, including a third designated public address associated with the underlying digital asset and a corresponding third designated private key, and wherein the third designated private key is stored on a third computer system which is connected to the distributed public transaction ledger through the Internet.
In embodiments, the process continues with receiving, by the plurality of geographically distributed computer systems in the peer-to-peer network, from the third computer system, via the blockchain, a second transaction request: (A) from the third designated public key address; (B) to the fifth contract address; and (C) including a second message including a request to burn a fifth amount of digital asset tokens from a balance associated with the third designated public address. In embodiments, the second transaction request is digitally signed by the third designated private key. In embodiments, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, the second transaction request to execute, via the plurality of geographically distributed computer systems in the peer-to-peer network, a sixth call request to the fifth contract address to obtain a sixth amount of digital asset tokens which reflect a current balance of digital asset tokens associated with the third designated public address. In embodiments, in response to the sixth call request, the fifth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network, the seventh call request to return the sixth amount of digital asset tokens; wherein, in response to the return of the sixth amount of digital asset, the fourth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network: (1) a balance verification instruction to confirm that the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens; and (2) in the case where the fifth amount of digital asset tokens is less than or equal to the sixth amount of digital asset tokens, execute, via the plurality of geographically distributed computer systems in the peer-to-peer network, a seventh call request to the fifth contract address to set a new balance for the digital asset tokens associated with the third designated public key address to a seventh amount which equals the sixth amount less the fifth amount. In embodiments, in response to the seventh call, the fifth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, the seventh call to set and store the new balance for the third designated public key address as the seventh amount and returns the new balance for the third designated public key address as the seventh amount. In embodiments, in response to the return of the new balance, the fourth smart contract executes, via the blockchain network, an eighth call request to the fifth contract address to obtain a total supply of digital asset tokens in circulation. In embodiments, in response to the eighth call request, the fifth smart contract executes, via the plurality of geographically distributed computer systems in the peer-to-peer network, the eighth call request and returns, to the fourth contract address, an eighth amount of digital asset tokens corresponding to the total supply of digital asset tokens in circulation. In embodiments, in response to the return of the eighth amount, the fourth smart contract, executes via the plurality of geographically distributed computer systems in the peer-to-peer network, a ninth call request to the fifth contract address to set a new total supply of digital asset tokens in circulation to a ninth amount, which is the eighth amount less the fifth amount. In embodiments, in response to the ninth call request, the fifth smart contract, executes via the blockchain network, the ninth call request and sets a new total supply of digital asset tokens in circulation at the ninth amount, and returns to the fourth contract address.
In embodiments, the third designated key set is the first designated key set. In embodiments, the third designated key set is not the second designated key set. In embodiments, the third designated key set is the second designated key set. In embodiments, the third designated key set is not the first designated key set. In embodiments, the third computer system is the first computer system. In embodiments, the third computer system is not the first computer system. In embodiments, the administrator computer system (e.g. Administrator 1801) includes the first computer system and the third computer system. In embodiments, the administrator computer system includes the first computer system and the second computer system.
In embodiments, the underlying digital asset is a stable value token. In embodiments, the underlying digital asset is Neo. In embodiments, the underlying digital asset is Ether. In embodiments, the underlying digital asset is Bitcoin.
In embodiments, the first designated private key is mathematically related to the first designated public key.
In embodiments, wherein the first designated public address includes the first designated public key.
In embodiments, the first designated public address includes a hash of the first designated public key.
In embodiments, the first designated public address includes a partial hash of the first designated public key.
In embodiments, the second designated private key is mathematically related to a second designated public key.
In embodiments, the second designated public address includes the second designated public key.
In embodiments, the second designated public address includes a hash of the second designated public key.
In embodiments, the second designated public address includes a partial hash of the second designated public key.
In embodiments, the second smart contract instructions include sixth authorization instructions related to modifying a token supply of the digital asset token.
Withdrawing funds, including in the context of digital assets, is associated with many security concerns. For example, security concerns may include: hacking, fraudulent transactions, to name a few. The aforementioned security concerns, in embodiments, are addressed (either completely or partially) in the context of withdrawing funds by customer and/or administrator created whitelists. A whitelist, in embodiments, may be a list which may include a list of addresses that a customer has pre-authorized to withdraw digital assets. For example, a whitelist associated with a first customer may include a first user public address associated with the first user and a second user public address associated with the first user's family member. As another example, a whitelist may only contain a user's public address which may limit all withdrawals to the user's public address. As another example, a whitelist may not be submitted by the user, and, instead, may be generated by an administrator (e.g. exchange computer system 3230, administrator system 6801, and/or SVCoin administrator 6809, to name a few). The generated whitelist, in embodiments, may be a default security measure implemented by the administrator, which may limit withdrawals to a public address associated with the customer's account. Alternatively, in embodiments, a whitelist may be a list which may include a list of public addresses that a user may not want digital asset tokens withdrawn to. For example, a whitelist may contain a user's old business partner's public address, limiting withdrawals to public addresses that are not the user's old business partner's public address.
A whitelist may be implemented in the process described in connection with
In embodiments, a digital asset exchange computer system (e.g. exchange computer system 3230, administrator system 6801, and/or SVCoin administrator 6809, to name a few) may store a plurality of whitelists for a plurality of customers on memory operably connected to the digital asset exchange computer system. Additionally, in embodiments, the digital asset exchange computer system may store a plurality of whitelists for a plurality of customers on a whitelist database on memory operably connected to the digital asset exchange computer system.
In embodiments, a whitelist may be used by the digital asset exchange computer system to verify a public address associated with a withdrawal request in accordance with the process of
The process may continue at step S14004. At step S14004, a plurality of designated key pairs is provided. The plurality of key pairs, in embodiments, may each include a respective designated public key of an underlying digital asset and a corresponding designated private key. In embodiments, each respective designated public key is mathematically related to a respective corresponding designated private key. The underlying digital asset, in embodiments, may be a digital math-based asset, such as bitcoins, Namecoins, Litecoins, PPCoins, Tonal bitcoins, bitcoin cash, zcash, IxCoins, Devcoins, Freicoins, I0coins, Terracoins, Liquidcoins, BBQcoins, BitBars, PhenixCoins, Ripple, Dogecoins, Mastercoins, BlackCoins, Ether, Nxt, BitShares-PTS, Quark, Primecoin, Feathercoin, Peercoin, Facebook Global Coin, Stellar, Top 100 Tokens, Tether; Maker; Crypto.com Chain; Basic Attention Token; USD Coin; Chainlink; BitTorrent; OmiseGO; Holo; TrueUSD; Pundi X; Zilliqa; Augur; Ox; Aurora; Paxos Standard Token; Huobi Token; IOST; Dent; Qubitica; Enjin Coin; Maximine Coin; ThoreCoin; MaidSafeCoin; KuCoin Shares; Crypto.com; SOLVE; Status; Mixin; Waltonchain; Golem; Insight Chain; Dai; VestChain; aelf; WAX; DigixDAO; Loom Network; Nash Exchange; LATOKEN; HedgeTrade; Loopring; Revain; Decentraland; Orbs; NEXT; Santiment Network Token; Populous; Nexo; Celer Network; Power Ledger; ODEM; Kyber Network; QASH; Bancor; Clipper Coin; Matic Network; Polymath; FunFair; Bread; IoTeX; Ecoreal Estate; REPO; UTRUST; Arcblock; Buggyra Coin Zero; Lambda; iExec RLC; STASIS EURS; Enigma; QuarkChain; Storj; UGAS; RIF Token; Japan Content Token; Fantom; EDUCare; Fusion; Gas; Mainframe; Bibox Token; CRYPTO20; Egretia; Ren; Synthetix Network Token; Veritaseum; Cortex; Cindicator; Civic; RChain; TenX; Kin; DAPS Token; SingularityNET; Quant; Gnosis; INO COIN; Iconomi; MediBloc [ERC20]; and/or DEW, to name a few. In embodiments, the underlying digital asset may be a digital asset that is supported by its own digital asset network (like ether supported by the Ethereum Network). The digital asset token, in embodiments, may be a stable value or fiat-backed token (such as Gemini Dollar), security tokens, and/or non-fungible token (such as Cryptokitties), to name a few. The digital asset, in embodiments, may be a fiat-backed digital asset, for example, a Libra or Gemini Dollar.
In embodiments, the plurality of designated key pairs may be provided with the process described in connection with
In embodiments, the first designated key pair may include a plurality of key pairs (e.g. on-line keyset N 11362N). For example, the first designated key pair may further include a first additional designated public key and a corresponding first additional designated private key. In embodiments, each key pair of the aforementioned plurality of key pairs of the first designated key pair may each correspond to a designated public address. For example, a first key pair of the plurality of key pairs may correspond to a first designated public address associated with the underlying digital asset. Continuing the example, an additional key pair of the plurality of key pairs may correspond to an additional designated public address associated with the underlying digital asset. In embodiments, each key pair of the aforementioned plurality of key pairs may correspond to the same designated public address. For example, the first and additional key pairs mentioned in the examples above may be associated with the same designated public address.
In embodiments, the first designated public address may be derived by using and/or applying a cryptographic hash function of the first designated public key. In embodiments, the first designated public address is a result of the cryptographic hash function, or, in embodiments, at least a part of the result of the cryptographic hash function. A cryptographic hash function may be a hash function that is a mathematical algorithm which maps data of arbitrary size to a bit string of a fixed size (e.g. a hash). In embodiments, the cryptographic hash function may be designed to be a one-way function (e.g. a function that is infeasible to invert). The cryptographic hash function, may include one or more of the following properties: (1) deterministic such that the same message produces results in the same hash; (2) high speed, such that the hash value for a message is computed in a manner that does not slow the process down; (3) infeasible to generate a message from the hash, such that generating a message from the hash value would require attempting all possibilities (e.g. a brute force approach); and (4) unique, such that messages to not have the same hash value and/or small changes to a message alter the hash value such that the values do not correlate, to name a few. In embodiments, and as used herein, algorithm, hash algorithm, hash function, and/or cryptographic hash function may refer to one or more of the following: (1) a mathematical algorithm; (2) a one-way hash function; (3) a cryptographic hash function; (4) a one-way function; (5) a trapdoor one-way function; (6) a Data Encryption Standard encryption algorithm; (7) a Blowfish encryption algorithm; (8) An Advanced Encryption Standard or Rijndael encryption algorithm; (9) a Twofish encryption algorithm; (10) an IDEA encryption algorithm; (11) an MD5 encryption algorithm; (12) an MD4 encryption algorithm; (13) a SHA 1 hashing algorithm; (14) an HMAC hashing algorithm; and/or (15) an RSA Security algorithm, to name a few.
The process of
In embodiments, the second designated key pair may be stored on a second computer system. The second computer system may be physically and/or operationally separated from the first computer system. Additionally, the second computer system may be physically and/or operationally separated (e.g. not connected to) from the distributed public transaction ledger and/or the internet (e.g. network 15). This separation, as described above in connection with
In embodiments, the second computer system may be a hardware security module. The hardware security module may be located in a vault (e.g. Vault 70-A1) Location A, Location B, Location C . . . Location N described above in connection with
In embodiments, the hardware security module, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the second designated key pair. For example, the second designated key pair may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the second designated key pair may include a plurality of key pairs (e.g. off-line keyset N 11803N). For example, the second designated key pair may further include a first additional designated public key and a corresponding first additional designated private key. In embodiments, each key pair of the aforementioned plurality of key pairs of the second designated key pair may each correspond to a designated public address. For example, a first key pair of the plurality of key pairs may correspond to a first designated public address associated with the underlying digital asset. A second key pair of the plurality of key pairs may correspond to a second designated public address associated with the underlying digital asset. In embodiments, each key pair of the aforementioned plurality of key pairs may correspond to the same designated public address. For example, the first and second key pairs mentioned in the examples above may be associated with the same designated public address.
In embodiments, the second designated public address may be derived by using and/or applying a cryptographic hash function of the second designated public key. In embodiments, the second designated public address is a result of the cryptographic hash function, or, in embodiments, at least a part of the result of the cryptographic hash function. The cryptographic hash function applied may be similar and/or the same cryptographic hash function applied to the first designated key pair. In embodiments, the cryptographic hash function applied to the second designated key pair may be different than the cryptographic hash function applied to the first key pair. A different cryptographic hash function may be used, in embodiments, as an additional security measure.
Referring back to
Referring to
The first authorization instructions, in embodiments, may be associated with the second designated key pair. In embodiments, first authorization instructions may be similar to the authorization instructions described above in connection with PROXY Authorization Instructions Module 11831.
In embodiments, the first smart contract may be PROXY smart contract 11310 described above in connection with
The process or
The print limiter token creation instructions, in embodiments, may indicate one or more conditions under which digital asset tokens of the underlying digital asset are created. In embodiments, the print limiter token creation instructions may be similar to the PRINT LIMITER token creation instructions described above in connection with the PRINT LIMITER Token Creation Instructions Module 11833.
The second authorization instructions, in embodiments, may include instructions to create tokens of the digital asset token. In embodiments, the first designated key pair is designated to authorize the second authorization instructions. In embodiments, the second designated key pair is designated to authorize the second authorization instructions. The second authorization instructions, in embodiments, may include instructions limiting the creation of digital asset tokens. The limitation placed on token creation may prevent the creation of tokens above a first threshold. For example, the second authorization instructions may limit the creation of tokens to 100,000 tokens. In embodiments, the first threshold may be relative to a first period of time. For example, the second authorization instructions may limit the creation of tokens to 500,000 tokens per day. In embodiments, the second authorization instructions may be similar to the first authorization instructions described above in connection with PRINT LIMITER First Authorization Instructions Module 11839.
The third authorization instructions, in embodiments, may also include instructions with respect to token creation. In embodiments, the third authorization instructions may designate a first designated custodian address (e.g. a custodian address associated with CUSTODIAN 2 Smart Contract 11350) with respect to token creation of the digital asset token. In embodiments, the third authorization instructions may be similar to the second authorization instructions described above in connection with PRINT LIMITER Second Authorization Instructions Module 11841.
In embodiments, the second smart contract instructions may also include token balance modification instructions (e.g. instructions of the Token Balance Modification Instructions Module 11847). The token balance modification instructions may be related to modifying the total balance of tokens of the digital asset token assigned to a third delegated contract address. In embodiments, the third delegated contract address may be of the one or more delegated contracted addresses. In embodiments, the token balance modification instructions may be similar to the optional token balance modification instructions described above in connection with Token Balance Modification Instructions Module 11847.
In embodiments, the second smart contract may further include additional authorization instructions. The additional authorization instructions may be similar to the optional PRINT LIMITER THIRD Authorization instructions described above in connection with PRINT LIMITER Third Authorization Instructions Module 11835.
In embodiments, the second smart contract may be PRINT LIMITER Smart Contract 11360 described above in connection with
In embodiments, the process of
The fourth authorization instructions, in embodiments, may authorize the issuance of instructions to the second smart contract. The issued instructions that are authorized by the fourth authorization instructions may regard token creation. In embodiments, the fourth authorization instructions designate the second designated key pair to authorize the fourth authorization instructions. In embodiments, the fourth authorization instructions designate the first key pair to authorize the fourth authorization instructions. In embodiments, the fourth authorization instructions include instructions to permit the creation of digital asset tokens above a first threshold defined by the second authorization instructions. In embodiments, the fourth authorization instructions may be similar to the authorization instructions described in connection with CUSTODIAN 2 First Authorization Instructions Module 11849.
The sixth authorization instructions, in embodiments, may designate a seventh contract address as one of the one or more delegated contract addresses. In embodiments, the seventh contract address is not the second contract address. In embodiments, the second designated key pair is designated to authorize the sixth authorization instructions. In embodiments, the first designated key pair is designated to authorize the sixth authorization instructions. In embodiments, the sixth authorization instructions may be similar to the authorization instructions described in connection with CUSTODIAN 2 Second Authorization Instructions Module 11851.
In embodiments, the third smart contract may be CUSTODIAN 2 Smart Contract 11350 described above in connection with
In embodiments, the process of
The token creation instructions may, in embodiments, be instructions to create tokens of the digital asset tokens. In embodiments, the token creation instructions may create tokens in accordance with the conditions set forth by the print limiter token creation instructions of the second smart contract. The token creation instructions may be similar to instructions described in connection with the IMPL Token Creation Instructions Module 11865.
The second delegation instructions, in embodiments, may delegate data storage operations to at least a fifth contract address. In embodiments, the fifth contract address may be associated with Contract Address 4 of STORE Smart Contract 11330. For example, the second delegation instructions may cause STORE Smart Contract 11330 to execute storage instructions of Storage Instructions Module 11853. The second delegation instructions may be similar to instructions described in connection with IMPL Delegation Instructions Module 11861.
In embodiments, the token transfer instructions may be related to transferring issued tokens of the digital asset token. The transfer of tokens may be from a first designated contract address to a second designated contract address. For example, issued tokens may be transferred from a contract address associated with a digital asset token issuer system to a user public address associated with a user attempting to purchase tokens of the underlying digital asset. The token transfer instructions may be similar to instructions described in connection with IMPL Token Transfer Instructions Module 11859.
In embodiments, the token destruction instructions may be related to destroying and/or burning one or more issued tokens of the digital asset token. For example, if a user is attempting to exchange a token for, as an example, fiat, the token being exchanged may be burned once the token is exchanged for fiat.
In embodiments, the fourth smart contract may be IMPL Smart Contract 11320 described above in connection with
In embodiments, the process of
The data storage instructions, in embodiments, may include instructions to store transaction data related to the digital asset token. Transaction data, in embodiments, may include transaction information for one or more of the issued tokens of the digital asset token. The transaction information, may include at least one of: (1) respective public address information associated with the blockchain of the underlying digital asset, and/or (2) corresponding respective token balance information which may be associated with the aforementioned respective public address information, to name a few. In embodiments, the transaction data may include transaction information for all of the issued tokens of the digital asset token. In embodiments, the data storage instructions may be similar to instructions described in connection with Storage Instructions Module 11853.
The fifth authorization instructions may include authorization instructions to modify the transaction data in response to a request. In embodiments, the request may be received from the fourth contract address. The fifth authorization instructions may be similar to instructions described above in connection with STORE Authorization Instructions 11855.
In embodiments, the fifth smart contract may be STORE Smart Contract 11330 described above in connection with
Referring back to
In embodiments, the list of designated public addresses may include one or more of the following: a designated public address, a digital asset type, a digital asset amount, and/or a timestamp, to name a few. The digital asset type may refer to the type of digital asset the customer is seeking to withdraw. While only one type of digital asset is shown in Table 1 (Gemini Dollar), one or more types of digital assets may be included in a list of designated public addresses. The timestamp, in embodiments, may refer to the time at which: (1) the customer sent the request for withdrawal; (2) the customer's request was received; (3) the customer would like to receive their withdrawal; and/or (4) a combination thereof, to name a few.
In embodiments, the process of obtaining a list of designated public addresses may be accomplished in one or more manners. For example, the digital asset exchange computer system may receive a plurality of requests to withdraw an amount of digital asset tokens. In embodiments, each request may include a designated public address, a digital asset type, a digital asset amount, and/or a timestamp, to name a few. Once the plurality of requests is received, the digital asset exchange computer system may generate and store the list of designated public addresses.
As another example, to obtain the list of designated public addresses, the digital asset exchange computer system may first receive a request to distribute a payment amount to one or more designated public addresses in exchange for an asset. The asset, having a corresponding value, as described herein, may not be the digital asset token and/or may be one or more of the following: stocks, bonds, equities, fixed-income securities, fiat, commodities, and/or marketable securities, to name a few. For example, the request to withdraw may be in the form of a request to pay stockholders a dividend based on the amount of stocks the stockholder owns. The request to distribute a payment amount may be received from a digital asset issuer (e.g. the digital asset token issuer system described above in connection with
In embodiments, continuing the example, the digital asset exchange computer system may access a digital asset security token database for the purposes of determining each respective designated public address of the one or more designated public addresses and/or a respective digital asset security token amount associated with each respective designated public address. In embodiments, the digital asset security token may be a digital asset that represents the asset. For example, if a user associated with a designated public address owns 50 stocks of Corporation A, the user may also own a corresponding 50 Security Tokens representing the ownership of 50 stocks.
Continuing the example, the digital asset exchange computer system may determine the amount of the digital asset that corresponds to the amount of digital asset security tokens. In embodiments, to determine the amount of digital asset, the digital asset exchange computer system may determine the values of the digital asset and the digital asset security token. After determining the values of the digital asset and the digital asset security token, the digital asset exchange computer system may determine a difference between the two values. The difference between the two values, along with the two values, may be used to determine a respective amount of digital assets that each designated public address is requesting. The respective amount, in embodiments, may be assigned to the respective designated public address, creating the list of designated public addresses. The list of designated public addresses may be stored by the digital asset exchange computer system on memory operably connected to the digital asset exchange computer system.
Continuing the process of withdrawing digital assets, optionally, in embodiments, at step S14010, the digital asset exchange computer system may verify the list of designated public addresses. The verification process, in embodiments, may be based on one or more whitelists associated with one or more of the designated public addresses. The digital asset exchange computer system, in embodiments, may verify that each designated public address is verified. In embodiments, the digital asset exchange computer system may verify only the designated public addresses that have one or more whitelists associated therewith.
In embodiments, the one or more designated public addresses may be verified by the process described in connection with
If one or more whitelists associated with one or more customers, the process may continue with Step S14506. At step S14506, the digital asset exchange computer system may access the one or more whitelists. The one or more whitelists may include one or more authorized public addresses, as described above. The one or more whitelists may be accessed and/or obtained to determine, at step S14508, whether each respective one or more authorized public addresses is the respective designated public address associated with the customer seeking to withdraw digital assets. In embodiments, the digital asset exchange computer system may make the aforementioned determination by comparing the one or more authorized public addresses to the designated public addresses. If the designated public addresses, in embodiments, match at least one of the one or more authorized public addresses, the designated public address may be verified as an authorized public address. In embodiments, if the designated public addresses are authorized, and therefore verified, the process for withdrawing digital assets may continue with
Referring to
In embodiments, increasing the supply of digital asset tokens may begin with the digital asset exchange computer system determining whether the first designated private key has the authority to increase the total supply by the amount requested by the designated public addresses. As mentioned above, the plurality of smart contract instructions may limit the total amount of digital assets that the first designated key pair has the authority to generate. For example, the first designated key pair may only have the authority to generate 25 Bitcoin. Thus, continuing the example, if the third amount is 50 Bitcoin, the first designated key pair would not have the authority to generate the third amount. If the first designated key pair does not have the authority to generate the third amount, the process for withdrawing digital assets, in embodiments, may continue with
Referring to
In embodiments, the first request may be to decrease the total supply of digital asset tokens to a third amount. This example may follow the same process described in connection with
The process of increasing the total supply of the digital asset token may continue with step S14304. In embodiments, at step S14304, the first transaction request may be sent by the digital asset token issuer system from the first designated public address to the fifth contract address. In embodiments, the first transaction request may be sent via the blockchain of the underlying digital asset. In embodiments, the first transaction request may be sent via network 15.
The process for increasing the total supply of the digital asset token may continue with step S14306 where the first transaction request may be sent from the fifth contract address to the second contract address via the blockchain for the underlying digital asset. The first transaction request, in embodiments, may be sent to the second contract address by the fifth contract address in response to the fifth contract address receiving the first transaction request. In embodiments, the first transaction request may be sent by the fifth contract address in response to the fifth contract address determining that the first transaction request requires additional authority. The aforementioned determination, in embodiments, may be made based on the plurality of smart contract instructions.
In embodiments, once the first transaction request is received by the second contract address, the second smart contract may execute the first transaction request. The execution of the first transaction request may, in embodiments, cause the second contract address to return a first unique lock identifier associated with the first transaction request to the digital asset exchange computer system (e.g. via a public address associated with the digital asset exchange). In embodiments, the first transaction request is executed via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain for the underlying digital asset.
In embodiments, the process may continue with step S14308, where the digital asset exchange computer system may obtain the first unique lock identifier. The first lock identifier, as mentioned above, may be obtained from the second smart contract address via a public address associated with the digital asset exchange (e.g. the public address associated with the first designated public key). In embodiments, the first unique lock identifier may be obtained based on reference to the blockchain for the underlying digital asset.
In embodiments, the process for increasing the total supply of the digital asset may continue with step S14310 where a second transaction request may be generated by the digital asset exchange computer system. In embodiments, the second transaction request may be generated in response to the first unique lock identifier being obtained. In embodiments, the second transaction request may be generated at the same time and/or substantially the same time that the first transaction request is generated. The second transaction request may, in embodiments, include a second message which may include a second request to unlock the total supply of the digital asset tokens. The second request may be in accordance with the first request. In embodiments, the second request, may also include the first unique lock identifier. In embodiments, the second transaction request may be digitally signed by the first designated private key and/or the second designated private key. In embodiments, the second transaction request may include second transaction fee information for minors associated with the plurality of geographically distributed computer systems in the peer-to-peer network. The second transaction fee information may be a predetermined amount of currency which may be related to the cost of processing the second transaction request.
The process may continue with step S14312 where the second transaction request may be sent from the first designated public address (the public address associated with the first designated public key) to the third contract address by the digital asset exchange computer system via the blockchain for the underlying digital asset. In embodiments, in response to receiving the second transaction request, the third smart contract may execute the second transaction request. Executing the second transaction request, in embodiments, may include returning a first unique request hash associated with the second transaction request to the first designated public address. The first unique request hash, in embodiments, may be an algorithm as described above, the description of which applying herein. In embodiments, the second transaction request may be executed via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain associated with the underlying digital asset.
The process for increasing the total supply of the digital asset token may continue with
Continuing the process, at step S14316, in embodiments, a third transaction request may be generated by the digital asset exchange computer system. The third transaction request may, in embodiments, be generated to be digitally signed by the first designated private key and/or the second designated private key. In embodiments, the third transaction request may include the first unique request hash. In embodiments, the third transaction request may be generated at the same time and/or substantially the same time that the first transaction request and/or second transaction request is generated. The third transaction request, in embodiments, may be generated in response to the digital asset token issuer system obtaining the first unique request hash.
In embodiments, at step S14318, the third transaction request may be transferred to a first portable memory device. In embodiments, the third transaction request may be transferred to the first portable memory device by an administrator (e.g. an administrator of administrator system 1801, administrator of the digital asset exchange computer system, to name a few). In embodiments, the third transaction request may be transferred from the digital asset exchange computer system to the first portable memory device. In embodiments, the first portable memory device, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the third transaction request. For example, the third transaction request may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the process may continue with step S14320 where the third transaction request may be transferred from the first portable memory device to a first computer system. The first computer system, as mentioned above, may be a hardware security module. In embodiments, the third transaction request may be transferred to the second computer system by an administrator (e.g. an administrator of administrator system 1801, administrator of the digital asset exchange computer system, to name a few).
At step S14322, in embodiments, the computer system may generate a third digitally signed transaction request by digitally signing the third transaction request. The digital signature used by the computer system, in embodiments, may be one or more of: the first designated private key and/or the second designated private key. In embodiments, the digital signature may be a private key of the plurality of designated key pairs provided in step S14004.
In embodiments, once the third digitally signed transaction request is generated, at step S14324, the third digitally signed transaction request may be transferred from the computer system to a second portable memory device. The second portable memory device may, in embodiments, be the first portable memory device (e.g. the first and second portable memory device are the same portable memory device). In embodiments, the second portable memory device may be physically and operatively separate from the first portable memory device. In embodiments, the second portable memory device, may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store the third transaction request. For example, the third transaction request may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof, to name a few.
In embodiments, the process for increasing the total supply of the digital asset may continue with step S14326 where the third digitally signed transaction request may be sent from the second portable memory device to the third contract address using the digital asset exchange computer issuer system, via the blockchain for the underlying digital asset. To send the third digitally signed transaction request, in embodiments, the third digitally signed transaction request may be first transferred from the second portable memory device to the digital asset exchange computer system. Once transferred, in embodiments, the third digitally signed transaction request may be sent by the digital asset exchange computer system, from the first designated public address (associated with the first designated key pair) to the third contract address.
In response to receiving the third digitally signed transaction request, in embodiments, the third smart contract may execute the third digitally signed transaction request. In embodiments, the execution of the third digitally signed transaction request may result in a request to validate the second request to unlock the total supply of digital asset tokens based on the third digitally signed transaction request and/or the first unique request hash. In embodiments, the execution may also result in a first call being sent to the second contract address. The first call may be to increase the total supply of the digital asset tokens from the first amount to the second amount. In embodiments, the third smart contract may execute the third digitally signed transaction request via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
The first call sent by the third smart contract to the second contract address of the second smart contract may, in embodiments, result in the second contract address returning the first call to the fourth contract address. The fourth contract address may, in response to receiving the returned first call, execute a second call to the fifth contract address. The second call, in embodiments, may be to set the total supply of the digital asset tokens to the second amount of digital asset tokens. In embodiments, the fourth smart contract may execute the second call via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
The second call sent by the fourth smart contract to the fifth contract address of the fifth smart contract may, in embodiments, result in the fifth smart contract executing the second call to set the total supply of the digital asset tokens to the second amount of digital asset tokens. In embodiments, the fifth smart contract may execute the second call via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain of the underlying digital asset.
In embodiments, the fifth contract address may also return the total balance of the digital asset token to the second contract address and/or the fourth contract address.
In embodiments, the steps of the process described in connection with
As another example, a process for increasing the total supply of the digital asset may be performed by the steps of
The first request may, at step S14404, be sent by the digital asset exchange computer system to the fifth contract address associated with the fifth smart contract. The first request may be sent from a public address associated with the digital asset exchange (e.g. the first designated public address).
Once received, at step S14406, the fifth contract address may execute the first transaction request via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain. In embodiments, the execution of the first transaction request may cause the fifth smart contract to: (1) validate the authority of the first designated key pair of the plurality of designated key pairs; and/or (2) send a first call to the fourth smart contract address to generate the third amount of the digital asset. In embodiments, in response to receiving the first call, the fourth smart contract may execute, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the first call to generate the first unique lock identifier. In embodiments, once generated, the fourth contract address may send a return including the first unique lock identifier to the second smart contract address.
In embodiments, the second smart contract may execute a second call to the fourth contract address in response to the return of the first unique lock identifier. In embodiments, the second call may be executed via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain. The second call, in embodiments, may be to confirm the first call with the first lock identifier. In embodiments, in response to receiving the second call, the fourth smart contract may execute, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the first call to execute a third call to the fifth contract address to obtain the total supply of digital asset tokens in circulation.
In embodiments, the fifth contract address, in response, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, may execute the third call and return, to the fourth contract address, the second amount of digital asset tokens corresponding to the total supply of digital asset tokens in circulation. In embodiments, for example, the total supply of digital asset tokens may be the first amount of the digital asset token.
In response to the return, in embodiments, the fourth smart contract may execute, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, a fourth call request to the fifth contract address to set a new total supply of digital asset tokens in circulation to the second amount. In embodiments, in response to the fourth call, the fifth smart contract may execute, via the plurality of geographically distributed computer systems in the peer-to-peer network with reference to the blockchain, the fourth call and set the new total supply of digital asset tokens in circulation to the second amount.
In embodiments, the steps of the process described in connection with
Referring back to
Once the respective amounts of the digital asset have been assigned, the digital asset exchange computer system, at step S14016, may confirm that each designated public address was assigned the respective amount of the digital asset token. For example, referring to Table 2 above, the digital asset exchange computer system may confirm the following: designated public address 123456 received 45 Gemini Dollars; designated public address 543456 received 65 Gemini Dollars; designated public address 654692 received 24 Gemini Dollars; designated public address 687128 received 17 Gemini Dollars; designated public address 357981 received 8 Gemini Dollars; and/or designated public address 354651 received 104 Gemini Dollars. In embodiments, the digital asset exchange computer system may make the confirmation based on one or more of the following: each respective digital asset security token amount, each respective payment amount, each respective designated public address, and/or the list of designated public addresses, to name a few.
Each respective amount, in embodiments, may be confirmed by the digital asset exchange computer system by sending a call to each designated public address. The call, in embodiments, may be sent from a public address associated with the digital asset exchange. Each designated public address, in embodiments, may return the amount assigned and/or the total amount of digital assets assigned to the respective designated public address. The return may be used by the digital asset exchange computer system to confirm that each respective amount was received. In embodiments, the returns may be stored by the digital asset exchange computer system.
In embodiments, the digital asset token issuer system may determine that each respective amount is not confirmed as received and/or is unable to confirm that each amount is received. For example, the digital asset token issuer system may determine that the designated public address 123456 received 13 Gemini Dollars, instead of 45. In these embodiments, the digital asset exchange computer system may generate and/or send a warning message for an administrator (e.g. an administrator of administrator system 1801) and/or the respective designated public address. In embodiments, the administrator system may be the digital asset exchange. In embodiments, the administrator system may not be the digital asset exchange. The warning message may include a notification stating that the amount of tokens that were assigned is incorrect and/or needs to be fixed. Additionally, the warning message may include a transaction ledger (e.g. Network Digital Asset Transaction Ledger 3228). Furthermore, the warning message may include the intended amount of digital asset tokens (e.g. 45 Gemini Dollars). In embodiments, if the digital asset exchange computer system determines that each respective amount is not confirmed as received and/or is unable to confirm that each amount is received, the digital asset token issuer system may repeat one or more of the steps of the processes described above in connection with
In embodiments, as mentioned above, the digital asset exchange computer system may determine that one or more designated public addresses of the list of designated public addresses is not authorized to withdraw digital assets. If one or more designated public addresses are not authorized, the digital asset exchange computer system, in embodiments, may perform the steps of the process illustrated in
At step S14020, the digital asset exchange computer system may send the notification to a user device associated with the request to withdraw. Additionally, in embodiments, the notification may also be sent to: a third party computer system and/or an administrator associated with the digital asset exchange. The notification, in embodiments, may also be stored by the digital asset exchange computer system.
The digital asset exchange computer system, at step S14022, may cancel the respective request to withdraw the respective amount of digital asset token. Alternatively, if the option to override is utilized, the process may continue with
In embodiments, the steps of the process described in connection with
As shown in the above table, each digital asset address may have a respective security token amount. Each digital asset address may be associated with one or more users. For example, digital asset address 1CC3X2gu58d6wXUWMffpuzN9JAfTUWu4Kj may be associated with User 1. Each user, in embodiments, may be associated with a public key and a mathematically related private key. A public key in embodiments may be used to generate a digital asset public address. For example, the digital asset address associated with User 3 may be generated by applying a hash algorithm to the public key associated with User 3. The result of the application of the hash on the public key may be the digital asset address.
In embodiments, the security token amount may be any number of security tokens, including zero security tokens. The security tokens, in embodiments, may represent ownership in an asset. For example, a security token may represent a user's ownership interest in: a security registered with a government authority; a security; a stock; a bond; a debt security; an equity security; intellectual property rights; and/or real estate, to name a few. As an example, the security token may represent stocks in Corporation A. Continuing the example, User 4, having a digital asset address of 0032JKLIUOINViunlalsiune82_1lkasjfh.10, may own 50 stocks of Corporation A. Thus, in this example, the each of the stock holders, Users 1-5, may be receiving a dividend payment proportional to the amount of stock each User owns.
In embodiments, each respective address of the first set of digital asset addresses may be tied to a distributed transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network. The peer-to-peer network, in embodiments, may be: the Ethereum Network, the Libra Network, the Neo Network, the Bitcoin Network, and/or the Stellar Network, to name a few. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of work. The peer-to-peer network, in embodiments, may be based on a mathematical protocol for proof of stake. The peer-to-peer network, in embodiments, may be based on a cryptographic mathematical protocol. In embodiments, the peer-to-peer network may be based on a mathematical protocol that is open sourced. In embodiments, the digital asset security token database, in embodiments, may be stored on computer readable media associated with a digital asset security token issuer system (e.g. memory of the digital asset security token issuer system). In embodiments, the digital asset security token database may be maintained and stored on the plurality of geographically distributed computer systems in the peer-to-peer network.
In embodiments, the digital asset security token database may be maintained on a sidechain. A sidechain, in embodiments, may refer to a portion of the distributed transaction ledger. For example, an administrator, user, and/or trusted entity may maintain a portion of the distributed transaction ledger and/or an electronic copy of a portion of the distributed transaction ledger. In embodiments, a portion of the distributed transaction ledger, in the context of a Merkel Tree, may refer to one or more “leafs” of the Merkel Tree, one or more statuses of the Merkel Tree, and/or a complete Merkel Tree with one or more past transactions being “pruned.” In the context of a blockchain, the portion of the distributed transaction ledger may be one or more blocks of the blockchain. The information on the sidechain may be updated periodically or aperiodically. For example, the information on the sidechain may be updated, published, and stored on the peer-to-peer network at predetermined times (e.g. twice a day, once a day, once a week, once a month, and/or once a quarter, to name a few). As another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the execution of a transaction and/or the execution of a batch of transactions. As yet another example, the information on the sidechain may be updated, published and stored on the peer-to-peer network after the commitment of a transaction and/or the commitment of a batch of transactions. A transaction, for example, may be committed by a consensus of trusted entities of the peer-to-peer network.
In embodiments, the peer-to-peer network may utilize one or more protocols and/or programs for security purposes. For example, the peer-to-peer network may utilize a byzantine fault tolerance protocol as a consensus mechanism. As another example, the peer-to-peer network may utilize a whitelist for the execution of a transaction and/or the transfer of funds. As yet another example, the peer-to-peer network may also utilize one or more of the following: encryption, point-to-point encryption, two-factor authentication, and/or tokenization, to name a few.
The process for issuing electronic payments using a fiat-backed digital asset may continue at step S14604. At step S14604, a fiat-backed digital asset database is provided. The fiat-backed digital asset, in embodiments, may be stored on the distributed transaction ledger and include a log of fiat backed digital assets. The log of fiat backed digital assets may include a second set of digital asset addresses, each associated with one or more users. The digital asset addresses, in embodiments, may also include a respective amount of fiat-backed digital asset amounts. A simplified example of the second set of digital asset addresses and respective fiat-backed digital asset amounts is shown in the below table.
As shown in the above table, each digital asset address may have a respective fiat-backed digital asset amount. The fiat-backed digital asset amount may refer to the amount of fiat-backed digital assets that are owned by the digital asset address. In embodiments, each digital asset address may be associated with one or more users. For example, digital asset address LN1afnjas9gh98y2t3ndne may be associated with User 8. Each user, in embodiments, may be associated with a public key and a mathematically related private key. A public key in embodiments may be used to generate a digital asset public address. For example, the digital asset address associated with User 2 may be generated by applying a hash algorithm to the public key associated with User 2. The result of the application of the hash on the public key may be the digital asset address. In embodiments the first set of digital asset addresses may be the same as or associated with the second set of digital asset addresses.
In embodiments, the fiat-backed digital asset amount may be any number of security tokens, including zero fiat-backed digital assets. The fiat-backed digital asset tokens may be backed by one or more assets and/or types of assets that are maintained by one or more entities. The one or more entities may refer to, for example, one or more: trusted entities, administrators, token issuers, verifiers, corporations, and/or banks, to name a few.
In embodiments, the fiat-backed digital asset may be backed by one or more amounts of one or more types of the following assets: one or more types of fiats (e.g., U.S. Dollars, Euro, Yen, Brittish Pound, Swiss Franc, Canadian Dollar, Australian Dollar, New Zealand Dollar, Kuaiti Dinar, Bahrain Dinar, Oman Rial, Jordan Dinar, Cayman Island Dollar, South African Rand, Mexican Pesos, Renmembi, to name a few); bank accounts in such fiat; one or more government securities denominated in such fiats (e.g., U.S. treasury certificates); municipal bonds or other government issued bonds, shares in exchange trade funds holding currencies or currency future contracts, one or more stocks; one or more bonds; one or more certificate of deposits (“CD”); to name a few. In embodiments, other forms of backed digital assets may also be used, where the assets may also include other digital assets, other physical assets (like real estate and/or inventors), securities, equities, bonds, commodities (e.g., gold, silver, diamonds, crops, oil, to name a few), or financial instruments (e.g., futures, puts, calls, credit default swaps, to name a few) one or more pieces of real estate; gold; diamonds; and/or a combination thereof, to name a few. In embodiments may be only one kind of asset (e.g., dollars held in a bank or government security or CD, to name a few) or a basket of assets (e.g., multiple fiats, e.g., dollars, euros, yet, to name a few). In embodiments, the value of the fiat-backed digital asset may fluctuate with the value of the assets backing the fiat-backed digital assets. The underlying value of the fiat-backed digital asset, in embodiments, may be updated in real-time, substantially real-time, periodically, and/or aperiodically, to name a few.
In embodiments, the fiat-backed digital assets may be issued by a fiat-backed digital asset issuer. The process of issuing fiat-backed digital assets may be similar to one or more of the processes discussed in connection with the processes of issuing digital assets described above, the descriptions of which applying herein. In embodiments, the fiat-backed digital asset issuer may issue fiat-backed digital assets in response to fluctuations in demand of the fiat-backed digital asset. For example, if the demand of the fiat-backed digital asset increases, the fiat-backed digital asset issuer may print fiat-backed digital assets. Continuing the example, the fiat-backed digital asset issuer may print fiat-backed digital assets in proportion to the increase in demand. Alternatively, the fiat-backed digital asset issuer may print fiat-backed digital assets based on a predetermined number, instructions, rules associated with printing fiat-backed digital assets, and/or not in proportion to the increase of demand, to name a few. As another example, if the demand of the fiat-backed digital asset decreases, the fiat-backed digital asset issuer may burn fiat-backed digital assets. Continuing the example, the fiat-backed digital asset issuer may burn fiat-backed digital assets in proportion to the decrease in demand. Alternatively, the fiat-backed digital asset issuer may burn fiat-backed digital assets based on a predetermined number, instructions, rules associated with burning fiat-backed digital assets, and/or not in proportion to the decrease of demand, to name a few. In embodiments, the fiat-backed digital asset issuer may require that a commensurate fiat and/or asset(s) deposit be made to account for the printed fiat-backed digital asset.
In embodiments, the digital asset security issuer system may receive one or more payment requests from one or more digital asset security token holders. For example, a stock holder may request a payment of dividends based on the amount of security tokens the stock holder owns. The payment request, in embodiments, may have rules and/or instructions that control when the one or more security token holders may receive a payment. Continuing the example, Corporation A may only pay dividends after January 2 of each year. Thus, the digital asset security token issuer system may only accept payment requests on or after January 3. As another example, Corporation A may only pay dividends in the month of January. Thus, a payment request, in this example, may only be accepted and processed during the month of January.
In embodiments, a payment request may include the digital asset address of the digital asset security token holder requesting the payment and/or a request to transfer a payment amount of fiat-backed digital assets to the digital asset address of the digital asset security token holder requesting the payment. The payment request may further include a designated address to receive the payment, the amount of security tokens the security token holder owns, and/or a timestamp indicating one or more of the following: the time and/or date at which the payment request was sent, the time and/or date at which the payment request was received, and/or the time and/or date the security token holder wishes to receive the payment.
In embodiments, after receiving the one or more payment requests, the digital asset security token issuer system may verify the one or more payment requests. Verifying the one or more payment requests may include confirming one or more of the following: the validity of the digital asset address of the digital asset security token holder, the digital asset security token amount owned by the security token holder, that the security token holder owns more than zero security token assets, the designated address is not prohibited from receiving a payment on behalf of the security token holder, and/or the security token holder is entitled to receive a payment, to name a few. For example, to confirm the digital asset address, the digital asset security token issuer system may compare the digital asset address included in the payment request to the first set of digital asset addresses. Continuing the example, if the digital asset address included in the payment request is one of the digital asset addresses of the first set of digital asset addresses, the digital asset security token issuer system may verify the digital asset address. If the digital asset address included in the payment request is not verified, the payment request may be denied and/or a notification may be generated and sent by the digital asset security token issuer system to the digital asset address included in the payment request. The notification may indicate that the digital asset address was not confirmed and the payment request has been denied. As another example, if the payment request includes a designated address, the digital asset security token issuer system may verify whether the designated address is on a whitelist associated with the digital asset address that sent the payment request. Continuing the example, if the digital asset address has a whitelist associated with it, the digital asset security token issuer system may compare the designated address to the whitelist. If the designated address is on the whitelist, the designated address may be verified. If the designated address included in the payment request is not verified, the payment request may be denied and/or a notification may be generated and sent by the digital asset security token issuer system to the digital asset address included in the payment request. The notification may indicate that the designated address is not authorized to receive payment and the payment request has been denied. The process of verifying designated addresses in the context of a whitelist may be similar to the process described in connection with
The process of issuing electronic payments using a fiat-backed digital asset may continue with step S14608. At step S14608, a trusted entity system may obtain a first sum of fiat-backed digital assets. A trusted entity, in embodiments, may be similar to the trusted entities described in this disclosure, the description of which applying herein. In embodiments the trusted entity may be a regulated digital asset exchange (e.g. Gemini). The trusted entity system may be a plurality of trusted entities of the peer-to-peer network. The trusted entity system, in embodiments, may include one or more third-parties and/or government agencies. The first sum, in embodiments, may be obtained by one or more of the following means: purchase, transfer, trade, receive and/or print, to name a few. In embodiments, the fiat-backed digital assets may be issued by a fiat-backed digital asset issuer. For example, the fiat-backed digital assets may be issued through one or more nodes associated with the fiat-backed digital asset issuer. As noted above, the process of issuing fiat-backed digital assets may be similar to one or more of the processes for issuing digital assets discussed above, the descriptions of which applying herein.
The process of
The process of
Referring back to
In embodiments, the trusted entity system may obtain the first sum of fiat-backed digital assets by printing the first sum of fiat-backed digital assets. In embodiments, the first sum may correspond to the sum of the respective payment amounts. In embodiments, the fiat-backed digital asset database may be updated to reflect the newly minted fiat-backed digital assets (and/or just the new transfer of fiat-backed digital assets) via transaction instructions sent to the peer-to-peer system which request the fiat-backed digital asset database be updated to reflect the addition of new fiat-backed digital assets in the amount of the first sum and the corresponding digital asset address associated with each new fiat-backed digital asset.
The process of issuing electronic payments using a fiat-backed digital asset may continue with step S14614. At step S14614, the trusted entity system may generate transaction instructions to transfer each respective payment amount to each respective digital asset address. The transaction request, in embodiments, may include a transfer request of each respective payment amount to be transferred from an account associated with the digital asset security token issuer system to each respective digital asset address. In embodiments, the transaction instructions may further include instructions to update the fiat-backed digital asset database to reserve enough fiat-backed digital assets to cover each respective payment amount (e.g. the first sum of fiat-backed digital assets). For example, the transfer request may include the data listed in the below table.
In embodiments, the transfer request may include a digital signature of the trusted entity system. The digital signature may be a combined digital signature based on of one or more private keys associated with one or more trusted entities of the trusted entity system. The digital signature, in embodiments, may further include one or more private keys associated with the digital asset addresses.
The process of issuing electronic payments using a fiat-backed digital asset may continue with step S14616. At step S14616, the trusted entity system may publish the generated transaction instructions associated with crediting the respective payment amount. In embodiments, the trusted entity system may publish the transaction instructions to the peer-to-peer network via a network (e.g. Network 15). In embodiments, publishing the transaction instructions may cause the peer-to-peer network to go through a process of executing and/or committing the transaction instructions (e.g. a consensus protocol) which may result in the transfer of each respective amount of fiat-backed digital assets to each respective digital asset address. In embodiments, the execution and/or commitment of the transaction instructions may not affect ownership of the digital asset security tokens. In embodiments, the execution and/or commitment of the transaction instructions may affect ownership of the digital asset security tokens. For example, if the digital asset security tokens represent ownership interest in a settlement of a lawsuit, the payment may be a one-off payment, resulting in the burning of the digital asset security tokens.
The process of issuing electronic payments using a fiat-backed digital asset may continue with step S14618. At step S14618, each digital address is notified of each respective transfer. In embodiments, the trusted entity system may generate and send a notification to each respective digital address notifying them of the transfer. In embodiments, prior to sending the notification, the trusted entity system may confirm that each digital asset address received the correct amount of fiat-backed digital assets. The confirmation process may be a call/return to and from each respective digital asset address. In embodiments, the confirmation process may be a query to the peer-to-peer system for a status of the distributed ledger, which may result in a receipt of the status of the ledger which may include each transfer.
In embodiments, the steps of the processes of
While the present application primarily discusses digital currency, the proof of custody method discussed herein may be used in conjunction with other products as well. Proof of custody systems and methods discussed herein, may be implemented for any type of financial product or service in which custodial wallets are used. Other embodiments of the present invention may also be used in conjunction with other financial products, such as using pricing discussions involving indices created with blended digital asset prices and/or auctions as benchmarks for financial products, such as an exchange traded product, a fund, an exchanged traded note, an exchange traded product, a call, a put, an option, an exchange traded derivative product, a fund, a company, an exchange traded fund, a note, an exchange traded note, a security, a debt instrument, a convertible security, an instrument comprising a basket of assets including one or more digital math-based assets and an over-the-counter product, an interest rate future, a future on swaps, an option on interest rate futures, an interest rate swap, a bond forward, a floating rate agreement (FRA), a structured, product such as a note bond or bill, a foreign exchange future, a foreign exchange forward, a foreign exchange listed option, a currency linked note and a currency swaption, to name a few.
Now that embodiments of the present invention have been shown and described in detail, various modifications and improvements thereon can become readily apparent to those skilled in the art. Accordingly, the exemplary embodiments of the present invention, as set forth above, are intended to be illustrative, not limiting. The spirit and scope of the present invention is to be construed broadly.
This application is a continuation in part of U.S. patent application Ser. No. 16/421,975, filed on May 24, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS which in turn is a continuation of U.S. patent application Ser. No. 16/293,531, filed on Mar. 5, 2019 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS which claims the benefit of and priority to each of U.S. Provisional Application No. 62/638,679, filed on Mar. 5, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/647,353, filed on Mar. 23, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/660,655, filed on Apr. 20, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/683,412, filed on Jun. 11, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application No. 62/689,563, filed on Jun. 25, 2018 and entitled SYSTEM, METHOD AND PROGRAM PRODUCT FOR GENERATING AND UTILIZING STABLE VALUE DIGITAL ASSETS; U.S. Provisional Application Ser. No. 62/764,977, filed on Aug. 17, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; U.S. Provisional Patent Application Ser. No. 62/721,983, filed on Aug. 23, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS; and U.S. Provisional Patent Application Ser. No. 62/728,441, filed on Sep. 7, 2018 and entitled SYSTEM, METHOD, AND PROGRAM PRODUCT FOR MODIFYING A SUPPLY OF STABLE VALUE DIGITAL ASSET TOKENS, the entire content of each of which is hereby incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4790431 | Reel et al. | Dec 1988 | A |
| 5675649 | Brennan et al. | Oct 1997 | A |
| 5799287 | Dembo | Aug 1998 | A |
| 5950176 | Keiser et al. | Sep 1999 | A |
| 6021257 | Chikauchi | Feb 2000 | A |
| 6157920 | Jakobsson et al. | Dec 2000 | A |
| 6505174 | Keiser et al. | Jan 2003 | B1 |
| 6523012 | Glassman et al. | Feb 2003 | B1 |
| 6583712 | Reed et al. | Jun 2003 | B1 |
| 7136834 | Adcock et al. | Nov 2006 | B1 |
| 7167565 | Rajasekaran | Jan 2007 | B2 |
| 7308428 | Federspiel et al. | Dec 2007 | B1 |
| 7330538 | Dunsmuir | Feb 2008 | B2 |
| 7356500 | Waelbroeck et al. | Apr 2008 | B1 |
| 7391865 | Orsini et al. | Jun 2008 | B2 |
| 7428506 | Waelbroeck et al. | Sep 2008 | B2 |
| 7487123 | Keiser et al. | Feb 2009 | B1 |
| 7565313 | Waelbroeck et al. | Jul 2009 | B2 |
| 7647264 | Hatheway et al. | Jan 2010 | B2 |
| 7677974 | Van Luchene | Mar 2010 | B2 |
| 7680715 | Waelbroeck et al. | Mar 2010 | B2 |
| 7685052 | Waelbroeck et al. | Mar 2010 | B2 |
| 7693775 | Korhammer et al. | Apr 2010 | B2 |
| 7716484 | Kaliski, Jr. | May 2010 | B1 |
| 7747515 | Merrin et al. | Jun 2010 | B1 |
| 7769678 | Toffey | Aug 2010 | B2 |
| 7778919 | Waelbroeck et al. | Aug 2010 | B2 |
| 7814000 | Waelbroeck et al. | Oct 2010 | B2 |
| 7831507 | Merrin et al. | Nov 2010 | B2 |
| 7848991 | Buck | Dec 2010 | B1 |
| 7848993 | Buck | Dec 2010 | B1 |
| 7865425 | Waelbroeck et al. | Jan 2011 | B2 |
| 7870058 | Maltzman | Jan 2011 | B2 |
| 7870059 | Shapiro et al. | Jan 2011 | B2 |
| 7870062 | Waelbroeck et al. | Jan 2011 | B2 |
| 7873573 | Realini | Jan 2011 | B2 |
| 7877318 | Shapiro et al. | Jan 2011 | B2 |
| 7882013 | Shapiro et al. | Feb 2011 | B2 |
| 7882014 | Shapiro et al. | Feb 2011 | B2 |
| 7882015 | Shapiro et al. | Feb 2011 | B2 |
| 7890417 | Hanson et al. | Feb 2011 | B2 |
| 7895112 | Richmann et al. | Feb 2011 | B2 |
| 7899726 | Harris | Mar 2011 | B2 |
| 7904376 | Shapiro et al. | Mar 2011 | B2 |
| 7908203 | Shapiro et al. | Mar 2011 | B2 |
| 7908205 | Waelbroeck et al. | Mar 2011 | B2 |
| 7908206 | Waelbroeck et al. | Mar 2011 | B2 |
| 7917425 | Waelbroeck et al. | Mar 2011 | B2 |
| 7933827 | Richmann et al. | Apr 2011 | B2 |
| 7996261 | Waelbroeck et al. | Aug 2011 | B1 |
| 7999748 | Ligtenberg et al. | Aug 2011 | B2 |
| 8005743 | Tupper et al. | Aug 2011 | B2 |
| 8010438 | Waelbroeck et al. | Aug 2011 | B2 |
| 8015099 | Reid | Sep 2011 | B2 |
| 8019665 | Hausman | Sep 2011 | B2 |
| 8041628 | Waelbroeck et al. | Oct 2011 | B2 |
| 8046290 | Fitzpatrick et al. | Oct 2011 | B2 |
| 8055576 | Merrin et al. | Nov 2011 | B2 |
| 8065217 | Beddis | Nov 2011 | B2 |
| 8069106 | Waelbroeck et al. | Nov 2011 | B2 |
| 8073763 | Merrin et al. | Dec 2011 | B1 |
| 8082205 | Lutnick et al. | Dec 2011 | B2 |
| 8095455 | Shapiro et al. | Jan 2012 | B2 |
| 8095456 | Waelbroeck et al. | Jan 2012 | B2 |
| 8103579 | Berkeley, III et al. | Jan 2012 | B1 |
| 8108278 | Tzekin et al. | Jan 2012 | B2 |
| 8108283 | Dimitri et al. | Jan 2012 | B2 |
| 8108299 | Waelbroeck et al. | Jan 2012 | B1 |
| 8117105 | Ford et al. | Feb 2012 | B2 |
| 8117609 | Lantz et al. | Feb 2012 | B2 |
| 8139770 | Zheng et al. | Mar 2012 | B2 |
| 8156036 | Waelbroeck et al. | Apr 2012 | B1 |
| 8165954 | Waelbroeck et al. | Apr 2012 | B2 |
| 8224702 | Mengerink et al. | Jul 2012 | B2 |
| 8229855 | Huang et al. | Jul 2012 | B2 |
| 8229859 | Samid | Jul 2012 | B2 |
| 8239330 | Montero et al. | Aug 2012 | B2 |
| 8244622 | Hughes, Jr. et al. | Aug 2012 | B2 |
| 8249965 | Tumminaro | Aug 2012 | B2 |
| 8255297 | Morgenstern et al. | Aug 2012 | B2 |
| 8266045 | Waelbroeck et al. | Sep 2012 | B2 |
| 8271375 | Mahoney et al. | Sep 2012 | B2 |
| 8275692 | Cartledge et al. | Sep 2012 | B2 |
| 8280797 | Hatheway et al. | Oct 2012 | B2 |
| 8285629 | Lutnick et al. | Oct 2012 | B2 |
| 8301542 | Adcock et al. | Oct 2012 | B2 |
| 8306910 | Wilkes | Nov 2012 | B2 |
| 8311920 | Lutnick et al. | Nov 2012 | B2 |
| 8321323 | Lutnick et al. | Nov 2012 | B2 |
| 8326751 | Driemeyer et al. | Dec 2012 | B2 |
| 8346651 | Freitas et al. | Jan 2013 | B2 |
| 8352326 | Betzler et al. | Jan 2013 | B2 |
| 8359253 | Waelbroeck et al. | Jan 2013 | B2 |
| 8359260 | Merrin et al. | Jan 2013 | B2 |
| 8380612 | Hanson et al. | Feb 2013 | B2 |
| 8386362 | Failla et al. | Feb 2013 | B2 |
| 8386373 | Fitzpatrick et al. | Feb 2013 | B2 |
| 8452703 | O'Leary et al. | May 2013 | B2 |
| 8494949 | Gilbert et al. | Jul 2013 | B2 |
| 8515857 | Lutnick et al. | Aug 2013 | B2 |
| 8521627 | Ford et al. | Aug 2013 | B2 |
| 8548898 | Merrin et al. | Oct 2013 | B2 |
| 8560431 | Lutnick et al. | Oct 2013 | B2 |
| 8566213 | Sweeting et al. | Oct 2013 | B2 |
| 8577772 | Heckman et al. | Nov 2013 | B2 |
| 8583544 | Ford et al. | Nov 2013 | B2 |
| 8606685 | Keiser et al. | Dec 2013 | B2 |
| 8620759 | Virgilio et al. | Dec 2013 | B1 |
| 8630951 | Wilkes | Jan 2014 | B2 |
| 8635144 | Waelbroeck et al. | Jan 2014 | B2 |
| 8688525 | Minde | Apr 2014 | B2 |
| 8688563 | Mehew et al. | Apr 2014 | B2 |
| 8712903 | Lutnick et al. | Apr 2014 | B2 |
| 8712914 | Lyons et al. | Apr 2014 | B2 |
| 8719131 | Roth | May 2014 | B1 |
| 8732065 | Hayes, Jr. | May 2014 | B1 |
| 8738518 | Rodin | May 2014 | B2 |
| 8744952 | Mortimer et al. | Jun 2014 | B2 |
| 8744954 | Buck | Jun 2014 | B2 |
| 8751362 | Lutnick | Jun 2014 | B1 |
| 8768819 | Lutnick et al. | Jul 2014 | B2 |
| 8775298 | Waelbroeck et al. | Jul 2014 | B2 |
| 8886561 | Gilbert et al. | Nov 2014 | B2 |
| 8959031 | Merrin et al. | Feb 2015 | B2 |
| 8977565 | Alderucci et al. | Mar 2015 | B2 |
| 9064256 | Foley et al. | Jun 2015 | B2 |
| 9727909 | Mackay | Aug 2017 | B2 |
| 9794074 | Toll et al. | Oct 2017 | B2 |
| 10084762 | Versteeg et al. | Sep 2018 | B2 |
| 20020143614 | MacLean et al. | Oct 2002 | A1 |
| 20020171546 | Evans et al. | Nov 2002 | A1 |
| 20030009413 | Furbush et al. | Jan 2003 | A1 |
| 20030014749 | Simons et al. | Jan 2003 | A1 |
| 20030225672 | Hughes et al. | Dec 2003 | A1 |
| 20040049464 | Ohmori et al. | Mar 2004 | A1 |
| 20040143710 | Walmsley | Jul 2004 | A1 |
| 20040193657 | Saito et al. | Sep 2004 | A1 |
| 20040243488 | Yamamoto et al. | Dec 2004 | A1 |
| 20050044022 | Spirgel et al. | Feb 2005 | A1 |
| 20050240510 | Schweickert et al. | Oct 2005 | A1 |
| 20070117615 | Van Luchene | May 2007 | A1 |
| 20070146797 | Sakai et al. | Jun 2007 | A1 |
| 20070219869 | Haines et al. | Sep 2007 | A1 |
| 20070271455 | Nakano et al. | Nov 2007 | A1 |
| 20080109280 | Csoka | May 2008 | A1 |
| 20080120221 | Toneguzzo | May 2008 | A1 |
| 20080140578 | Felt et al. | Jun 2008 | A1 |
| 20080167965 | Von Nothaus et al. | Jul 2008 | A1 |
| 20080215474 | Graham et al. | Sep 2008 | A1 |
| 20080243703 | Al-Herz et al. | Oct 2008 | A1 |
| 20080249957 | Masuyama et al. | Oct 2008 | A1 |
| 20080281444 | Krieger et al. | Nov 2008 | A1 |
| 20090089168 | Schneck | Apr 2009 | A1 |
| 20090094134 | Toomer et al. | Apr 2009 | A1 |
| 20090098939 | Hamilton, II et al. | Apr 2009 | A1 |
| 20090119200 | Riviere | May 2009 | A1 |
| 20090132830 | Haga et al. | May 2009 | A1 |
| 20090265268 | Huang et al. | Oct 2009 | A1 |
| 20100094771 | VanderPal | Apr 2010 | A1 |
| 20100169205 | Labuszewski | Jul 2010 | A1 |
| 20100174646 | Cole et al. | Jul 2010 | A1 |
| 20100228674 | Ogg et al. | Sep 2010 | A1 |
| 20100250360 | Ball et al. | Sep 2010 | A1 |
| 20100306084 | Ciptawilangga | Dec 2010 | A1 |
| 20110110516 | Satoh | May 2011 | A1 |
| 20110112662 | Thompson et al. | May 2011 | A1 |
| 20110231913 | Feng et al. | Sep 2011 | A1 |
| 20110270748 | Graham, III et al. | Nov 2011 | A1 |
| 20110302412 | Deng et al. | Dec 2011 | A1 |
| 20120078693 | Wilkes | Mar 2012 | A1 |
| 20120101886 | Subramanian et al. | Apr 2012 | A1 |
| 20120123924 | Rose et al. | May 2012 | A1 |
| 20120185395 | Wilkes | Jul 2012 | A1 |
| 20120239543 | Ryan | Sep 2012 | A1 |
| 20120278200 | van Coppenolle et al. | Nov 2012 | A1 |
| 20130036373 | Alderfer et al. | Feb 2013 | A1 |
| 20130041773 | Muse | Feb 2013 | A1 |
| 20130054471 | Samid | Feb 2013 | A1 |
| 20130061049 | Irvine | Mar 2013 | A1 |
| 20130159699 | Torkkel | Jun 2013 | A1 |
| 20130166455 | Feigelson | Jun 2013 | A1 |
| 20130191277 | O'Leary et al. | Jul 2013 | A1 |
| 20130226827 | Stevens | Aug 2013 | A1 |
| 20130232023 | Muse | Sep 2013 | A2 |
| 20130238478 | Bruno | Sep 2013 | A1 |
| 20130246233 | Hakim | Sep 2013 | A1 |
| 20130254052 | Royyuru et al. | Sep 2013 | A1 |
| 20130311266 | Vichich et al. | Nov 2013 | A1 |
| 20130311348 | Samid | Nov 2013 | A1 |
| 20130317972 | Morgenstern et al. | Nov 2013 | A1 |
| 20130317984 | O'Leary et al. | Nov 2013 | A1 |
| 20130325701 | Schwartz | Dec 2013 | A1 |
| 20140025473 | Cohen | Jan 2014 | A1 |
| 20140032267 | Smith et al. | Jan 2014 | A1 |
| 20140040157 | Cohen et al. | Feb 2014 | A1 |
| 20140081710 | Rabie | Mar 2014 | A1 |
| 20140122903 | Endo et al. | May 2014 | A1 |
| 20140141869 | Shore | May 2014 | A1 |
| 20140156497 | Mehew et al. | Jun 2014 | A1 |
| 20140164251 | Loh | Jun 2014 | A1 |
| 20140233740 | Niamut et al. | Aug 2014 | A1 |
| 20140297504 | Bergenudd | Oct 2014 | A1 |
| 20140310527 | Veugen et al. | Oct 2014 | A1 |
| 20140344015 | Puertolas-Montanes et al. | Nov 2014 | A1 |
| 20150032591 | Jacob | Jan 2015 | A1 |
| 20150033301 | Pianese | Jan 2015 | A1 |
| 20150120567 | Van Rooyen et al. | Apr 2015 | A1 |
| 20150120569 | Belshe | Apr 2015 | A1 |
| 20150170112 | DeCastro | Jun 2015 | A1 |
| 20150193744 | Adleman | Jul 2015 | A1 |
| 20150227897 | Loera | Aug 2015 | A1 |
| 20150244690 | Mossbarger | Aug 2015 | A1 |
| 20150262137 | Armstrong | Sep 2015 | A1 |
| 20150262138 | Hudon | Sep 2015 | A1 |
| 20150262139 | Shtylman | Sep 2015 | A1 |
| 20150262140 | Armstrong | Sep 2015 | A1 |
| 20150262141 | Rebernik | Sep 2015 | A1 |
| 20150262168 | Armstrong | Sep 2015 | A1 |
| 20150262171 | Langschaedel | Sep 2015 | A1 |
| 20150262172 | Rebernik | Sep 2015 | A1 |
| 20150262173 | Durbin et al. | Sep 2015 | A1 |
| 20150262176 | Langschaedel et al. | Sep 2015 | A1 |
| 20150310424 | Myers | Oct 2015 | A1 |
| 20150324787 | Schaffner | Nov 2015 | A1 |
| 20150332283 | Witchey | Nov 2015 | A1 |
| 20150341422 | Farnlof et al. | Nov 2015 | A1 |
| 20150348169 | Harris et al. | Dec 2015 | A1 |
| 20150356523 | Madden | Dec 2015 | A1 |
| 20150356555 | Pennanen | Dec 2015 | A1 |
| 20150363777 | Ronca et al. | Dec 2015 | A1 |
| 20150363783 | Ronca et al. | Dec 2015 | A1 |
| 20150379510 | Smith | Dec 2015 | A1 |
| 20160027229 | Spanos et al. | Jan 2016 | A1 |
| 20160028552 | Spanos et al. | Jan 2016 | A1 |
| 20160078219 | Hernan | Mar 2016 | A1 |
| 20160080156 | Kaliski, Jr. et al. | Mar 2016 | A1 |
| 20160086187 | Joao | Mar 2016 | A1 |
| 20160092988 | Letourneau | Mar 2016 | A1 |
| 20160112200 | Kheterpal et al. | Apr 2016 | A1 |
| 20160125040 | Kheterpal et al. | May 2016 | A1 |
| 20160162873 | Zhou et al. | Jun 2016 | A1 |
| 20160203448 | Metnick et al. | Jul 2016 | A1 |
| 20170005804 | Zinder | Jan 2017 | A1 |
| 20170017955 | Stern et al. | Jan 2017 | A1 |
| 20170091750 | Maim | Mar 2017 | A1 |
| 20170124535 | Juels et al. | May 2017 | A1 |
| 20170132630 | Castinado | May 2017 | A1 |
| 20180191503 | Alwar | Jul 2018 | A1 |
| 20180218176 | Voorhees | Aug 2018 | A1 |
| 20190108232 | Calcaterra | Apr 2019 | A1 |
| 20190130399 | Wright | May 2019 | A1 |
| 20190236564 | Cantrell et al. | Aug 2019 | A1 |
| 20190273725 | Allen | Sep 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2627540 | Sep 2009 | CA |
| 103927656 | Jul 2014 | CN |
| 2634738 | Apr 2013 | EP |
| WO 0026745 | May 2000 | WO |
| WO2000026745 | May 2000 | WO |
| WO 0167409 | Sep 2001 | WO |
| WO 0186373 | Nov 2001 | WO |
| WO 2008127428 | Oct 2008 | WO |
| WO2011008630 | Jan 2011 | WO |
| WO2013034278 | Mar 2013 | WO |
| WO 2015059669 | Apr 2015 | WO |
| WO 2015085393 | Jun 2015 | WO |
| WO 2015113519 | Aug 2015 | WO |
| WO 2015179020 | Nov 2015 | WO |
| 2016-015041 | Jan 2016 | WO |
| WO 2016088659 | Jan 2016 | WO |
| WO 2016022864 | Feb 2016 | WO |
| WO 2016029119 | Feb 2016 | WO |
| Entry |
|---|
| Corporate Governance and bloackchain by David Yermack p. 7-31 (Year: 2017). |
| Unblocking the Blockchain by Conrad G. Bahlke vol. 36, issue 10, Nov. 2016 (Year: 2016). |
| Nick Szabo, Bit gold, unenumerated.blogspot.com (Mar. 29, 2006) Internet Archive, https://web.archive.org/web/20060329122942/http://unenumerated.blogspot.com/2005/12/bit-gold.html. |
| Notice of References Cited, U.S. Appl. No. 12/192,809 (Oct. 10, 2012). |
| Online auctions: An in-depth look, National Consumers League, http://www.nclnet.org/personal-finance/121-online-auctions/279online-auctions-an-in-depth-look (last visited May 30, 2014). |
| PPCoin Proof of Stake Minting Setup Guide, Bitcoin Forum (Apr. 25, 2013) https://bitcointalk.org/index.php?topic=187714.0 (last visited Jul. 22, 2013). |
| PPCoin, Wikipedia, http://en.wikipedia.org/wiki/PPCoin (last visited Jul. 22, 2013). |
| Private Bitcoin Insurance, Inscrypto, http://go.inscrypto.com (last visited Jan. 24, 2014). |
| Proof-of-stake, Wikipedia, http://en.wikipedia.org/wiki/Proof-of-stake (last visited Jul. 22, 2013). |
| Proof-of-work System, Wikipedia, http://en.wikipedia.org/wiki/Proof-of-work (last visited Jul. 22, 2013). |
| Protocol of Bitcoin, Wikipedia, http://en.wikipedia.org/wiki/Bitcoin_mining (last visited Jul. 22, 2013). |
| Rachel Abrams, Winklevoss Twins to List Bitcoin Fund on Nasdaq, The New York Times DealB%k, http://dealbook.nytimes.com/2014/05/08/winklevoss-twins-to-list-bitcoin-fund-on-nasdaq/ (last visited May 8, 2014). |
| Rob Wile, Shares of No-Name Tech Company Go Crazy After It Announces It's Getting Into The Bitcoin Game, Business Insider, http://www.businessinsider.com/wpcs-bitcoin-2013-12?nr_email_referer=1&utm_source=Triggermail&utm_medium=email&utm_content=emailshare (last visited Dec. 30, 2013). |
| Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System (Oct. 31, 2008). |
| Securing Your Wallet, Bitcoin.org (Jul. 21, 2013) Internet Archive, http://web.archive.org/web/20130721194621/http://bitcoin.org/en/secure-your-wallet. |
| Security for Your Peace of Mind, Coinbase, https://coinbase.com/security (last visited Oct. 28, 2013). |
| Shamir's Secret Sharing, Wikipedia, http://en.wikipedia.org/wiki/Shamir's_Secret_Sharing (last visited Jul. 22, 2013). |
| Some Things You Need To Know, Bitcoin.org (May 2, 2013) Internet Archive, http://web.archive.org/web/20130502051011/http://bitcoin.org/en/you-need-to-know. |
| Stephen Foley & Alice Ross, Bitcoin bubble grows and grows, Financial Times, http://www.ft.com/intl/cms/s/0/b4be7d8e-9c73-11e2-9a4b-00144feabdc0/html (last visited Oct. 30, 2013). |
| Sunny King & Scott Nadal, PPCoin: Peer-to-Peer Crypto-Currency with Proof-of-Stake, (Aug. 19, 2012). |
| TigerDirect.com Now Accepts Bitcoin Payments!, TigerDirect, http://www.tigerdirect.com/bitcoin/ (last visited Feb. 6, 2014). |
| U.S. Appl. No. 60/884,172, filed Jan. 9, 2007. |
| U.S. Appl. No. 61/225,256, filed Jul. 14, 2009. |
| USD Average Price History, BitcoinAverage, https://bitcoinaverage.com/charts.htm@USD-averages-all (last visited Feb. 24, 2014). |
| Using Offline Wallets in Armory, Armory (May 20, 2013) Internet Archive, http://web.archive.org/web/20130520100213/https://bitcoinarmory.com/using-offline-wallets-in-armory/. |
| Victoria Turk, Bitcoin ‘Banks’ Are Trying to Rebrand Cryptocurrencies for the Mainstream, Motherboard, http://motherboard.vice.com/en_ca/read/bitcoin-banks-try-to-rebrand-cryptocurrencies-for-the-mainstream (last visited May 5, 2014). |
| Why Bitcoin is Changing the World, Bitcoin.org (Jun. 20, 2013) Internet Archive, http://web.archive.org/web/20130620062218/http://bitcoin.org/en/innovation. |
| Winklevoss Bitcoin Trust Amendment No. 3 to Form S-1 Registration Statement, SEC (May 8, 2014), available at http://www.sec.gov/Archives/edgar/data/1579346/000119312514190365/d721187ds1a.htm. |
| World Gold Council, How SPDR Gold Shares (2840 HK) are Created and Redeemed (Mar. 2013). |
| Bitcoin, A Primer for Policymakers(2013). |
| Bitcoin: a first assessment, FX and Rates | Global, Bank of America Merrill Lynch (Dec. 5, 2013). |
| Bitcoin: Questions, Answers, and Analysis of Legal Issues, Congressional Research Service (Dec. 20, 2013). |
| The audacity of bitcoin, Risks and opportunities for corporates and investors,Global Rates & FX Research, J.P. Morgan (Feb. 11, 2014), http://www.jpmorganmarkets.com/GlobalFXStrategy. |
| John Heggestuen, BITCOIN: How it Works, and How it Could Fundamentally Change How Companies and Individuals Handle Payments, BI Intelligence (Jan. 30, 2014). |
| Bitcoin: Intrinsic Value as Conduit for Disruptive Payment Network Technology, Wedbush, Computer Services Financial Technology (Dec. 1, 2014). |
| Digitizing Trust: Leveraging the Bitcoin Protocol Beyond the “Coin”, Wedbush, Computer Services: Financial Technology (Jan. 2, 2014). |
| Bitcoin: Watch the Innovation, Not the Price, Wedbush, Computer Services: Financial Technology (Feb. 14, 2014). |
| “How Bitcoin is Driving Digital Innovation in Entertainment, Mediaand Communications (EMC), PwC Consumer Intelligence Series, Digital Disruptor, (Jan. 27, 2014).” |
| Bitcoins and Banks: Problematic currency, interesting payment system, UBS, Global Research (Mar. 28, 2014). |
| François R. Velde, Bitcoin: A primer, The Federal Reserve Bank of Chicago, Chicago Fed Letter (Dec. 2013). |
| David Andolfatto, Bitcoin and Beyond: The Possibilities and Pitfalls of Virtual Currencies, Federal Reserve Bank of St. Louis, Dialogue With the Fed, Beyond Today's Financial Headlines (Mar. 31, 2014). |
| All About Bitcoin, Goldman Sachs, Global Macro Research, Top of Mind, Issue 21 (Mar. 11, 2014). |
| Julieta Duek and Demian Brener, Bitcoin: Understanding and Assessing potential Opportunities, Quasar Ventures, (Jan. 2014). |
| “Yacine Ghalim and Max Niederhofer, bitcoin: Primer, State of Play, Discussion, Courmayeur, Sunstone Capital (Jan. 24, 2014)”. |
| Timing and Sizing the Era of Bitcoin, Wedbush, Computer Services: Financial Technology (May 27, 2014). |
| State of Bitcoin 2014, CoinDesk (Feb. 26, 2014). |
| Ronald A. Glantz, Pantera Primer, (Mar. 11, 2014). |
| Anton Badev and Matthew Chen, Bitcoin: Technical Background and Data Analysis, Finance and Economics Discussion Series, Divisions of Research & Statistics and Monetary Affairs, Federal Reserve Board, Washington, D.C. (Oct. 7, 2014). |
| Bitcoin Moves Closer to Regulation, Stratfor Flobal Intelligence (Jan. 29, 2015), https://www.stratfor.com/sample/analysis/bitcoin-moves-closer-regulation#axzz/ (last visited Jan. 30, 2015). |
| Blocktrail|Bitcoin Block Explorer, Blocktrail (Aug. 18, 2014), https://www.blocktrail.com/. |
| Jerry Bito and Andrea Castillo, BITCOIN a Primer for Policymakers, Mercatus Center, George Mason University (2013). |
| Daniel Palmer, Coinfloor Plans Europe's First Bitcoin EIF, Adds USD Support, CoinDesk (Oct. 21, 2014), http://www.coindesk.com/coinfloor-launch-bitcoin-trading-fund-adds-new-currencies/ (last visited Oct. 22, 2014). |
| “What is Blockchain Technology?” Quora. N.p. Jan. 15, 2009. Web. Jun. 9, 2017. <https://www.quora.com/What-is-blockchain-technology-1>. |
| Bankex Proof-of-Asset Protocol—The Smart White Paper, version 0.3.1 beta (Oct. 19, 2017) 36 pgs. |
| ATMIA ATM Industry Association Position Paper, www.atmia.com, Internet. |
| Winklevosses' Gemini to Offer Cryptocurrency Block Trading, Olga Kharif and Matthew Leising, Bloomberg.com (Apr. 9, 2018) https://www.bloomberg.com/news/articles/2018-04-09/winklevoss-s-gemini-to-offer-cryptocurrency-block-trading, Internet. |
| A block chain based decentralized exchange, Harsh Patel. |
| Marketplace—Gemini, web.archive.org (Last modified Jan. 8, 2018) http://web.archive.org/web/20180125115941/https://gemini.com/marketplace/, Internet. |
| Marketplace—Gemini, web.archive.org (Last modified Nov. 25, 2017) http://web.archive.org/web/20171211092415/https://gemini.com/marketplace/, Internet. |
| Marketplace, Gemini.com (Last modified Sep. 20, 2018) https://gemini.com/marketplace/, Internet. |
| The Ripple Network Review—What is Ripple?, Donald McIntyre—Etherplan (Aug. 1, 2013) https://etherplan.com/2013/08/01/the-ripple-network-review-what-is-ripple/4103/, Internet. |
| World Bank taps Australia's CBA for blockchain bond, Reuters (Aug. 9, 2018) https://www.reuters.com/article/us-worldbank-cba-blockchain/world-bank-taps-australias-cba-for-blockchain-bond-idUSKBN1KV02D, Internet. |
| Facebook's Libra Vs. Bitcoin: 5 Key Differences, Daniel Amerman, CFA, seekingalpha.com (Dated Jun. 20, 2019), https://seekingalpha.com/article/4271247-facebooks-libra-vs-bitcoin-5-key-differences?ifp=0, internet. |
| State Machine Replication in the Libra Blockchain, Mathieu Baudet et al., Libra Association, (2019) 41 pages. |
| Move: A Language With Programmable Resources, Sam Blackshear et al., Libra Association, (2019) 26 pages. |
| An Introduction to Libra—White Paper, Libra Association Members (2019), 12 pages. |
| Moving Toward Permissionless Consensus, libra.org, (Accessed Jun. 20, 2019), 12 pages, internet. |
| Facebook announces Libra cryptocurrency: All you need to know, Josh Constine, techcrunch.com (Jun. 18, 2019), https://techcrunch com/2019/06/18/facebook-libra/, internet. |
| The Ambitious Plan Behind Facebook's Cryptocurrency, Libra, Steven Levy and Gregory Barber, Wired.com (Jun. 18, 2019), https://www.wired.com/story/ambitious-plan-behind-facebooks-cryptocurrency-libra/, internet. |
| The Libra Reserve, Libra.org, https://libra.org/en-US/about-currency-reserve/#the_reserve, (2019) 10 pages, internet. |
| The Libra Blockchain, Amsden et al., Libra Association Members (2019), 29 pages. |
| International Search Report and Written Opinion issued in Application No. PCT/US16/25189 dated Jul. 1, 2016 (15 pp.). |
| “Digital Currency Exchange Goes Live to Public in Melbourne, Australia,” AlphaPoint, https://globenewswire.com/news-release/2015/12/10/794524/0/en/Digital-Currency-Exchange-Goes-Live-to-Public-in-Melbourne-Australia.html, Dec. 10, 2015, 3 pages. |
| “Nasdaq Linq Enables First-Ever Private Securities Issuance Documented with Blockchain Technology,” Nasdaq, https://globenewswire.com/news-release/2015/12/30/798660/0/en/Nasdaq-Linq-Enables-First-Ever-Private-Securities-Issuance-Documented-With-Blockchain-Technology.html, Dec. 30, 2015, 3 pages. |
| International Search Report and Written Opinion issued in Application No. PCT/US16/040711 dated Oct. 4, 2016 (14 pages). |
| “Blockchain Technologies Corp Makes History, 2016 Iowa Caucus Results Forever Documented on Blockchain”, https://globenewswire.com/news-release/2016/02/06/808320/10159855/en/Blockchain-Technologies-Corp-Makes-History-2016-Iowa-Caucus-Results-Forever-Documented-on-Blockchain.html, Feb. 5, 2016, 2 pages. |
| “AlphaPoint Announces Blockchain Solution Custom-Built for Financial Institutions,” AlphaPoint, https://globenewswire.com/news-release/2015/10/U.S. Appl. No. 26/779,929/0/en/AlphaPoint-Announces-Blockchain-Solution-Custom-Built-for-Financial-lnstitutions.html, Oct. 26, 2015, 3 pages. |
| “Nasdaq Launches Enterprise-Wide Blockchain Technology Initiative”, Nasdaq, https://globenewswire.com/news-release/2015/05/11/734456/10133665/en/Nasdaq-Launches-Enterprise-Wide-Blockchain-Technology-Initiative.html, May 11, 2015, 3 pages. |
| “RR Donnelley to Pursue New Blockchain-Enabled Capabilities for Publishing Industry,” https://globenewswire.com/news-release/2016/03/14/819355/0/en/RR-Donnelley-to-Pursue-New-Blockchain-Enabled-Capabilities-for-Publishing-Industry.html, Mar. 14, 2016, 3 pages. |
| Nakamoto, S., “Bitcoin: A Peer-to-Peer Electronic Cash System,”www.bitcoin.org, 9 pages. |
| [ANN] M-of-N “Fragmented Backups” now in Armory (command-line only), Bitcoin Forum (Mar. 6, 2013), https://bitcointalk.org/index.php?topic=149820.0 (last visited Dec. 4, 2013). |
| 2-of-3 Paper Wallets, Bitcoin Forum (published Jan. 29, 2013), https://bitcointalk.org/index.php?topic=139625.msg1487254 (last visited Dec. 4, 2013). |
| A Physical Price Tag for a Digital Currency. Introducing Bittag., BitTag, http://bittag.net/ (last visited Feb. 5, 2014). |
| A powerful trading platform for Bitcoin traders, BTXTrader.com (Aug. 13, 2013) Internet Archive, https://web.archive.org/web/201 30813052513/http://www.btxtrader.com/. |
| About Bitcoin, Bitcoin.org (May 2, 2013) Internet Archive, http://web.archive.org/web/20130502214154/http://bitcoin.org/en/about. |
| An Open Source P2P Digital Currency, Bitcoin.org, http://bitcoin.org/en/ (last visited Jul. 22, 2013). |
| Ashlee Vance & Brad Stone, The Bitcoin-Mining Arms Race Heats Up, BloombergBusinessweek, http://www.businessweek.com/articles/2014-01-09/bitcoin-mining-chips-gear-computing-groups-competition-heats-up (last visited Jan. 9, 2014). |
| Bitcoin Fund Exclusively Available on EXANTE's Platform, EXANTE, https://exante.eu/press/news/266/ (last visited Det. 10, 2013). |
| Bitcoin Now on Bloomberg, Bloomberg Now (Apr. 30, 2014) Internet Archive, https://web.archive.org/web/20140430184511/http://www.bloomberg.com/now/2014-04-30/bitcoin-now-bloomberg/. |
| Bitcoin Theft Insurance, Ecoin Club (published Dec. 3, 2013), http://ecoinclub.com/bitcoin-insurance/ (last visited Dec. 5, 2013). |
| Bitcoin, Wikipedia (Jun. 24, 2013), Internet Archive http://web.archive.org/web/20130624030646/http://en.wikipedia.org/wiki/Bitcoin. |
| Bitcoinaverage code repository, GitHub, https://github.com/bitcoinaverage/bitcoinaverage/commits/master?page=134 (last visited Feb. 24, 2014). |
| BitcoinAverage.com—independent bitcoin price, Bitcoin Forum, https://bitcointalk.org/index.php?topic=270190.0 (last visited Feb. 24, 2014). |
| BitcoinAverage.com, Reddit, http://www.reddit.eom/r/Bitcoin/comments/1jl9c2/ (last visited Feb. 24, 2014). |
| Bitcoin's First Kiosk, Robocoin (Jul. 2, 2013) Internet Archive, https://web.archive.org/web/20130702171110/https://robocoinkiosk.com/. |
| Bitcoin's First Real ATM, Robocoin Blog, http://blog.robocoinkiosk.com/ (last visited Nov. 11, 2013). |
| Bitflash Weekly Review (Apr. 14, 2014), Pantera, https://panteracapital.com/bitflash/ (last visited Apr. 15, 2014). |
| Bob Sullivan, ‘Deadbeat bidders’ dog eBay sellers, NBCNews.com (published Sep. 5, 2002), http://www.nbcnews.com/id/3078738/ns/technology_and_sciencetech_and_gadgets/t/deadbeat-bidders-dog-ebay-sellers/#.U4inz_ldXuS (last visited May 30, 2014). |
| Brian Cohen, JPMorgan Chase Building Bitcoin-Killer, Lets Talk Bitcoin (published Dec. 9, 2013) http://letstalkbitcoin.com/jpmorgan-chase-building-bitcoin-killer/ (last visited Dec. 10, 2013). |
| Buying and Selling Linden Dollars, Second Life, http://community.secondlife.com/t5/English-Knowledge-Base/Buying-and-selling-Linden-dollars/ta-p/700107 (last visited Dec. 9, 2013). |
| Charts, Bitcoin Charts (May 10, 2013) Internet Archive, https://web.archive.org/web/20130510172057/http://bitcoincharts.com/charts/. |
| Choose Your Wallet, Bitcoin.org (May 30, 2013) Internet Archive, http://web.archive.org/web/20130530072551/http://bitcoin.org/en/choose-your-wallet. |
| Circle (May 19, 2 014) Internet Archive, https://web.archive.org/web/20140519175717/https://www.circle.com/. |
| Coinbase, Bitcoin Wallet (Jul. 22, 2013) Internet Archive, http://web.archive.org/web/20130722200359/https://coinbase.com/. |
| Coinbase, Bitcoin Wallet, https://coinbase.com/ (last visited Aug. 15, 2013). |
| CoinDesk Bitcoin Price Index, CoinDesk, http://www.coindesk.com/price/ (last visited Oct. 23, 2013). |
| CoinDesk, This week we released the first version of our mobile app on iPhone, Twitter (published May 2, 2014), https://twitter.com/coindesk/status/462255287177453568?refsrc=email (last visited May 5, 2014). |
| Durnford, Barter network aims to help Mile End's cash-strapped live well, The Gazette [Montreal, Que] (Jan. 23, 1996). |
| Electrum, Bitcoin wiki, https://en.bitcoin.it/wiki/Electrum (last visited Jul. 22, 2013). |
| Elliptic Vault Secure, Worry-free Storage for Your Bitcoins, Elliptic.co (Jan. 12, 2014) Internet Archive, https://web.archive.org/web/20140112043128/https://www.elliptic.co/vault. |
| FAQ: What's The Difference Between PPCoin and Bitcoin?, GitHub, https://github.com/ppcoin/ppcoin/wiki/FAQ (last visited Jul. 22, 2013). |
| First Bitcoin Capital Corp.(otc markets:BITCF) Launches Digital Currency Exchange, CoinQX.com in Beta, The Wall Street Journal MarketWatch, http://www.marketwatch.com/story/first-bitcoin-capital-corpotc-markets-bitcf-launches-digital-currency-exchange-coinqxcom-in-beta-2014-05-21 (last visited May 21, 2014). |
| How Bitcoin Works Under the Hood, Imponderable Things (Scott Driscoll's Blog) (published Jul. 14, 2013), http://www.imponderablethings.com/2013/07/how-bitcoin-works-under-hood.html (last visited Oct. 10, 2013). |
| How DigiCash Blew Everything, NEXT (published Jan. 1999), http://cryptome.org/jya/digicrash.htm (last visited Jan. 9, 2014). |
| How Does Bitcoin Work?, Bitcoin.org, (May 1, 2013) Internet Archive, http://web.archive.org/web/20130501092121/http://bitcoin.org/en/how-it-works. |
| How is Mt.Gox weighted average calculated?, Bitcoin Forum (Mar. 18, 2013), https://bitcointalk.org/index.php?topic=154548.0 (last visited Jul. 25, 2013). |
| Ina Steiner, eBay Mulls New Feature to Eliminate Deadbeat Bidders, Ecommerce Bytes Blog (published May 12, 2012), http://www.ecommercebytes.com/C/blog/blog.pl?/pl/2012/5/1336831866.html (last visited May 30, 2014). |
| Independent Bitcoin Price, BitcoinAverage, https://bitcoinaverage.com/explain.htm (last visited Mar. 4, 2014). |
| Introducing BDIC: Bitcoin's decentralized, privately-funded version of the FDIC, Reddit (published Dec. 4, 2013), http://www.reddit.com/r/Bitcoin/comments/1s365o/introducing_bdic_bitcoins_decentralized/ (last visited Dec. 5, 2013). |
| James Ball, Meet the seven people who hold the keys to worldwide internet security, The Guardian, http://www.theguardian.com/technology/2014/feb28/seven-people-keys-woridwide-intemet-security-web (last visited Mar. 7, 2014). |
| Jeremy Allaire, What We Have Been Up to at Circle, The Circle Blog (May 19, 2014) Internet Archive, https://web.archive.org/web/20140519162958/https://wwwcircle.com/2014/05/15/circle-update/. |
| Joe Adler, Bitcoin Backers Seek FDIC-Style Insurance, American Banker (Jan. 22, 2014), http://www.americanbanker.com/issues/179_15/bitcoin-backers-seek-fdic-style-insurance-1065089-1.html?zkPrintable-true. |
| John Biggs, Xapo Raises $20 Million to Bury Your Bitcoin Underground, TechCrunch (Mar. 14, 2014) Internet Archive, https://web.archive.org/web/20140314042301/http://techcrunch.com/2014/03/13/xapo-raises-20-million-to-bury-your-bitcoin-underground/. |
| Jon Matonis, CoinDesk Launches Proprietary Bitcoin Price Index, CoinDesk (published Sep. 11, 2013), http://www.coindesk.com/coindesk-launches-proprietary-bitcoin-price-index/ (last visited Oct. 30, 2013). |
| Jon Southurst, ATM Industry Association Publishes Report on Bitcoin ATMs, CoinDesk (published Mar. 20, 2014), http://www.coindesk.com/atm-industry-association-publishes-report-bitcoin-atms/ (last visited Mar. 21, 2014). |
| Jonathan Shieber, Circle Emerges From Stealth to Bring Bitcoin to the Masses, TechCrunch (May 18, 2014) Internet Archive, https://web.archive.org/web/20140518130248/http://techcrunch.com/2014/05/15/circle-emerges-from-stealth-to-bring-bitcoin-to-the-masses/. |
| Larry Ren, Proof of Stake Velocity: Building the Social Currency of the Digital Age, www.reddcoin.com (Apr. 2014). |
| Lisa Fleisher, London's New Bitcoin Exchange Hopes to Avoid Mt. Gox Fate, The Wall Street Journal (published Apr. 30, 2014), http://blogs.wsj.com/digits/2014/04/30/londons-new-bitcoin-exchange-hopes-to-avoid-mt-gox-fate/ (last visited May 1, 2014). |
| Markets API, Bitcoin Charts (Jun. 3, 2013) Internet Archive, https://web.archive.org/web/20130603091557/http://bitcoincharts.com/about/markets-api. |
| Max Raskin, Cameron and Tyler Winklevoss on Bitcoin and Their Public Persona, BloombergBusinessweek, http://www.businessweek.com/articles/2013-08-08/cameron-and-tyler-winklevoss-on-bitcoin-and-their-public-persona (last visited Aug. 8, 2013). |
| U.S. Appl. No. 61/954,434, filed Mar. 17, 2014. |
| U.S. Appl. No. 61/990,017, filed May 7, 2014. |
| U.S. Appl. No. 62/042,676, filed Aug. 27, 2014. |
| U.S. Appl. No. 62/056,100, filed Sep. 26, 2014. |
| U.S. Appl. No. 62/086,669, filed Dec. 2, 2014. |
| U.S. Appl. No. 62/099,992, filed Jan. 15, 2015. |
| David Harper, Exploring the Exponentially Weighted Moving Average, Investopedia (Mar. 18, 2007) Internet Archive, https://web.archive.org/web/20070318160651/http://www.investopedia.com/articles/07/EWMA.asp. |
| Ken Hawkins, Exchange-Traded Funds (ETFs), Investopedia (May 12, 2013) Internet archive, https://web.archive.org/web/20130512125447/http://www.investopedia.com/university/exchange-traded-fund/. |
| Proof of stake instead of proof of work, Bitcoin Forum, https://bitcointalk.org/index.php?topic=27787 (last visited Nov. 3, 2015). |
| Trading Namecoins for Bitcoins, Bitcoin Forum, https://bitcointalk.org/index.php?topic=6289.0 (last visited Nov. 6, 2015). |
| Daniel Cawrey, Eschewing Price, Pantera Launches Bitindex to Track Bitcoin, CoinDesk (Jul. 10, 2014), http://www.coindesk.com/eschewing-price-pantera-launches-bitindex-track-bitcoin/ (last visited Jul. 11, 2014). |
| “Coinsetter Launches Out of Beta, Platform Now a Full U.S.Bitcoin Exchange, Coinsetter blog (Jul. 24, 2014), http://www.coinsetter.com/blog/2014/07/24/coinsetter-launches-beta-platform-now-full-us-bitcoin-exchange/ (last visited Jul. 24, 2014).” |
| Request for Administrative Ruling on the Application of FinCEN's Regulations to a Virtual Currency Trading Platform, United States Department of the Treasury, FinCEN, (Oct. 27, 2014). |
| Request for Administrative Ruling on the Application of FinCEN's Regulations to a Virtual Currency Payment System, United States Department of the Treasury, FinCEN, (Oct. 27, 2014). |
| Daniel Roberts, On Winklevoss Bitcoin index, it's open season for developers, FORTUNE, (Jul. 22, 2014). |
| Evan L. Greebel et al., Recent Key Bitcoin and Virtual Currency Regulatory and Law Enforcement Developments, Virtual Currency Advisory, Katten Muchin Rosenman LLP (Nov. 13, 2014). |
| BTC, Google Finance, https://www.google.com/finance?q=CURRENCY%3ABTC&ei=T-euU7jVFZOUwQPNklHYCQ (last visited Jul. 11, 2014). |
| Sanjay Panikkar et al., ADEPT: An IoT Practitioner Perspective, IBM (2015). |
| Bitcoins the hard way: Using the raw Bitcoin protocol, Ken Shirriff's blog, (Feb. 3, 2014) Internet Archive, https://web.archive.org/web/20140203192446/http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bitcoin.html. |
| NYC Bitcoin Exchange Coinsetter Launches Out of Beta With Institutional and Consumer Trading, MarketWatch (published Jul. 24, 2014), http://www.marketwatch.com/story/nyc-bitcoin-exchange-coinsetter-launches-out-of-beta-with-institutional-and-consumer-trading-2014-07-24 (last visited Jul. 24, 2014). |
| Major Bitcoin Investment Firm Launches Bitindex, The Crypto Crimson, (published Jul. 10, 2014), http://cryptocrimson.com/2014/07/major-bitcoin-investment-firm-launches-bitindex/ (last visited Jul. 11, 2014). |
| “We make it easy to build secure, high-level services on topof the Bitcoin protocol, Trusted Coin (Dec. 26, 2013) Internet Archive, https://web.archive.org/web/20131226232433lhttps://api.trustedcoin.com/f.” |
| WINKBTCO Index, Bloomberg Finance L.P. (Jun. 16, 2014). |
| Number | Date | Country | |
|---|---|---|---|
| 62867091 | Jun 2019 | US | |
| 62732347 | Sep 2018 | US | |
| 62728441 | Sep 2018 | US | |
| 62721983 | Aug 2018 | US | |
| 62764978 | Aug 2018 | US | |
| 62764977 | Aug 2018 | US | |
| 62702265 | Jul 2018 | US | |
| 62689563 | Jun 2018 | US | |
| 62767977 | Nov 2018 | US | |
| 62728411 | Sep 2018 | US | |
| 62689563 | Jun 2018 | US | |
| 62683412 | Jun 2018 | US | |
| 62660655 | Apr 2018 | US | |
| 62647353 | Mar 2018 | US | |
| 62638679 | Mar 2018 | US | |
| 62689563 | Jun 2018 | US | |
| 62684023 | Jun 2018 | US | |
| 62683412 | Jun 2018 | US | |
| 62680775 | Jun 2018 | US | |
| 62647353 | Mar 2018 | US | |
| 62638679 | Mar 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16293531 | Mar 2019 | US |
| Child | 16421975 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16452187 | Jun 2019 | US |
| Child | 16518660 | US | |
| Parent | 16437841 | Jun 2019 | US |
| Child | 16452187 | US | |
| Parent | 16421975 | May 2019 | US |
| Child | 16437841 | US | |
| Parent | 16293531 | Mar 2019 | US |
| Child | 16421975 | US | |
| Parent | 16282955 | Feb 2019 | US |
| Child | 16293531 | US | |
| Parent | 16437841 | Jun 2019 | US |
| Child | 16452187 | US | |
| Parent | 16063469 | Jun 2018 | US |
| Child | 16293531 | US | |
| Parent | 16020534 | Jun 2018 | US |
| Child | 16063469 | US | |
| Parent | 16280788 | Feb 2019 | US |
| Child | 16282955 | US | |
| Parent | 16036469 | Jul 2018 | US |
| Child | 16280788 | US | |
| Parent | 15973140 | May 2018 | US |
| Child | 16280788 | US | |
| Parent | 15973175 | May 2018 | US |
| Child | 15973140 | US | |
| Parent | 15960040 | Apr 2018 | US |
| Child | 15973175 | US | |
| Parent | 15920042 | Mar 2018 | US |
| Child | 15960040 | US |
