US 12,271,898 B1
System, method and program product for modifying a supply of stable value digital asset tokens
Brandon Arvanaghi, New York, NY (US); Eric Neiman Winer, New York, NY (US); Daniel William Halley James, Brooklyn, NY (US); Stephen Judkins, Portland, OR (US); Alex Parkinson, Portland, OR (US); Cameron Howard Winklevoss, New York, NY (US); and Tyler Howard Winklevoss, New York, NY (US)
Assigned to Gemini IP, LLC, New York, NY (US)
Filed by Gemini IP, LLC, New York, NY (US)
Filed on Aug. 23, 2019, as Appl. No. 16/550,152.
Application 16/550,152 is a continuation in part of application No. 16/518,660, filed on Jul. 22, 2019, granted, now 11,334,883.
Application 16/518,660 is a continuation in part of application No. 16/452,187, filed on Jun. 25, 2019, granted, now 11,200,569.
Application 16/550,152 is a continuation in part of application No. 16/452,187, filed on Jun. 25, 2019, granted, now 11,200,569.
Application 16/452,187 is a continuation in part of application No. 16/437,841, filed on Jun. 11, 2019, granted, now 10,540,654.
Application 16/437,841 is a continuation in part of application No. 16/421,975, filed on May 24, 2019, granted, now 10,540,653.
Application 16/518,660 is a continuation in part of application No. 16/421,975, filed on May 24, 2019, granted, now 10,540,653.
Application 16/421,975 is a continuation of application No. 16/293,531, filed on Mar. 5, 2019, granted, now 10,373,158.
Application 16/293,531 is a continuation in part of application No. 16/282,955, filed on Feb. 22, 2019, granted, now 11,522,700.
Application 16/282,955 is a continuation in part of application No. 16/280,778, filed on Feb. 20, 2019, abandoned.
Application 16/293,531 is a continuation in part of application No. 16/036,469, filed on Jul. 16, 2018, granted, now 10,929,842.
Application 16/293,531 is a continuation in part of application No. 16/020,534, filed on Jun. 27, 2018, granted, now 10,373,129.
Application 16/036,469 is a continuation in part of application No. 16/020,534, filed on Jun. 27, 2018, granted, now 10,373,129.
Application 16/280,778 is a continuation in part of application No. 15/973,140, filed on May 7, 2018, abandoned.
Application 16/020,534 is a continuation in part of application No. 15/600,040, filed on Apr. 23, 2018, granted, now 10,438,290.
Application 16/293,531 is a continuation in part of application No. 15/600,040, filed on Apr. 23, 2018, granted, now 10,438,290.
Claims priority of provisional application 62/867,091, filed on Jun. 26, 2019.
Claims priority of provisional application 62/732,347, filed on Sep. 17, 2018.
Claims priority of provisional application 62/728,441, filed on Sep. 7, 2018.
Claims priority of provisional application 62/721,983, filed on Aug. 23, 2018.
Claims priority of provisional application 62/764,977, filed on Aug. 17, 2018.
Claims priority of provisional application 62/764,978, filed on Aug. 17, 2018.
Claims priority of provisional application 62/702,265, filed on Jul. 23, 2018.
Claims priority of provisional application 62/689,563, filed on Jun. 25, 2018.
Claims priority of provisional application 62/684,023, filed on Jun. 12, 2018.
Claims priority of provisional application 62/683,412, filed on Jun. 11, 2018.
Claims priority of provisional application 62/680,775, filed on Jun. 5, 2018.
Claims priority of provisional application 62/660,655, filed on Apr. 20, 2018.
Claims priority of provisional application 62/647,353, filed on Mar. 23, 2018.
Claims priority of provisional application 62/643,931, filed on Mar. 16, 2018.
Claims priority of provisional application 62/643,946, filed on Mar. 16, 2018.
Claims priority of provisional application 62/638,679, filed on Mar. 5, 2018.
Int. Cl. G06Q 20/38 (2012.01)
CPC G06Q 20/3829 (2013.01) 28 Claims
OG exemplary drawing
 
1. A method of issuing electronic payments using an amount of fiat-backed digital asset comprising the steps of:
(a) providing a digital asset security token database stored on a first set of one or more computer readable media associated with a digital asset security token issuer system associated with a digital asset security token issuer, wherein the digital asset security token database utilizes at least one smart contract code associated with a contract address of the digital asset security token database and comprises a log of digital asset security tokens including:
(i) a first set of digital asset addresses including a respective digital asset address for each respective digital asset security token holder; and
(ii) a respective digital asset security token amount associated with each respective digital asset address, wherein each respective digital asset address of the first set of digital asset addresses is tied to a distributed transaction ledger maintained by a plurality of geographically distributed computer systems in a peer-to-peer network;
(b) providing a fiat-backed digital asset database stored on the distributed transaction ledger maintained by the plurality of geographically distributed computer systems in the peer-to-peer network, wherein the fiat-backed digital asset database comprises a log of fiat-backed digital assets including:
(i) a second set of digital asset addresses including a second respective digital asset address for each respective fiat-backed digital asset holder; and
(ii) a respective fiat-backed digital asset amount for each respective fiat-backed digital asset holder, wherein the fiat-backed digital assets are issued by a fiat-backed digital asset issuer;
(c) obtaining, via the contract address, by a trusted entity system associated with a trusted entity, and using a first application program interface, a first sum of fiat-backed digital assets, wherein the first sum of fiat backed digital assets are backed by a plurality of assets comprising at least a second amount of a first fiat maintained by a custodian;
(d) accessing, by the trusted entity system, using the first application program interface, the digital asset security token database to determine:
(i) each respective digital asset address of the first set of digital asset addresses for each respective digital asset security token holder; and
(ii) the respective digital asset security token amount associated with each respective digital asset address;
(e) determining a respective payment amount in fiat-backed digital assets to be made to each respective digital asset address of the first set of digital asset addresses based at least in part on a fixed notional amount, the first sum of fiat-backed digital assets and, the respective digital asset security token amount associated with each respective digital asset address of the first set of digital asset addresses, the fixed notional amount being based at least in part on a notional pegged rate including a fixed proportional value associated with the fiat-backed digital asset and the first fiat;
(f) generating, by the trusted entity system operably connected as a node of a decentralized digital asset network including a peer-to-peer network, transaction instructions including computer code configured to cause the trusted entity system to initiate a transfer of the respective payment amount of fiat-backed digital assets to each respective digital asset address of the first set of digital asset addresses from the digital asset security token issuer account to the security token holder accounts, wherein generating the transaction instructions includes generating code configured to be utilized by other nodes of the decentralized digital asset network to facilitate the transfer of the fiat-backed digital assets;
(g) publishing, by the trusted entity system to the peer-to-peer network, the transaction instructions, the publishing causing the respective payment amount of fiat-backed digital assets to be credited to each respective digital asset address of the first set of digital asset addresses where ownership of each digital asset security token remains the same;
(h) publishing, by the trusted entity system to a side ledger, the transaction instructions associated with crediting the respective payment amount of fiat-backed digital assets to each respective digital asset address of the first set of digital asset addresses and the publishing step (q) including publishing the transaction instructions from the side ledger to the distributed asset ledger periodically or aperiodically, wherein the digital asset security token database is maintained on a sidechain, separate from the peer-to-peer network, wherein information on the sidechain is published and stored on the peer-to-peer network periodically or aperiodically;
(i) confirming, by the trusted entity system, receipt of the respective amount of fiat-backed digital assets and continued ownership of each respective digital asset security token at each digital asset address of the first set of the digital asset addresses and updating the distributed transaction ledger automatically as maintained on the other nodes of the decentralized digital asset network; and
(j) notifying, by the trusted entity system, each digital asset address of the first set of the digital asset addresses of each respective transfer of fiat-backed digital assets to each respective digital asset address of the first set of digital asset addresses.