Method and system for providing reserves to a tokenized platform

Abstract

A computer-implemented system uses a distributed ledger to provide a tokenization platform collateralized by an asset-based reserve. The system provides a central entity that stores respective quantities for a plurality of instruments. The central entity is coupled to a distributed network of nodes that persistently store transaction data based on token values. Processing circuitry of the central entity calculates a token value based on the respective quantities for the plurality of instruments and updates the token value based on information received by a server of the central entity. The token value is provided to one or more nodes of the distributed network for use in transactions.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 343,525, filed May 18, 2022, which is incorporated by reference in its entirety. [Background technology]

[0002] The present disclosure relates generally to communication systems, network infrastructures, and processing systems for use in providing reserves to a tokenization platform. Summary of the Invention [Means for solving the problem]

[0003] According to one aspect of the disclosure, a computer-implemented method is provided for coordinating data exchanges between entities on a distributed network of nodes, the nodes persistently storing transaction data based on a value of a token associated with the distributed network. The central entity is coupled to the distributed network. A storage device of the central entity stores respective quantities for a plurality of commodities. A plurality of servers receive information about the plurality of commodities via one or more data communication channels. A processing circuit calculates a value of the token based on the respective quantities and information for the plurality of commodities. The plurality of servers also receive updated information about the plurality of commodities via one or more data communication channels. The processing circuit also updates the value of the token based on the updated information. The value of the token is provided to one or more nodes of the distributed network for use in transactions.

[0004] In another aspect of the disclosure, storing a quantity for one of the plurality of items includes storing a quantity of zero for each item of the plurality of items.

[0005] In yet another aspect of the disclosure, the central entity includes at least one node of the distributed network of nodes.

[0006] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0007] In yet another aspect of the present disclosure, the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

[0008] In yet another aspect of the present disclosure, respective quantities for a plurality of items are determined.

[0009] In yet another aspect of the present disclosure, the multiple underlying assets collateralizing the tokens are monitored to ensure that reserve requirements for the tokens are met.

[0010] In yet another aspect of the present disclosure, receiving the information includes receiving the information from sources in different time zones, and calculating the token value is also based on the sources in the different time zones.

[0011] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0012] In yet another aspect of the present disclosure, a central entity creates multiple instances of multiple products.

[0013] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0014] In yet another aspect of the present disclosure, the updated information received for the plurality of instruments causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0015] In yet another aspect of the disclosure, the central entity is located in at least one of a private or public decentralized network of nodes.

[0016] In yet another aspect of the disclosure, the tokens are of a first type, and the method also includes exchanging other tokens of a second type for the tokens of the first type based on an associated exchange rate.

[0017] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0018] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0019] In yet another aspect of the disclosure, in response to providing value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, a central entity allocates reserve assets to collateralize the tokens.

[0020] According to another aspect of the disclosure, a system for coordinating data exchanges between entities on a distributed network of nodes is provided, the nodes persistently storing transaction data based on a value of a token associated with the distributed network, the system being coupled to the distributed network. The system includes a storage device for storing respective quantities for a plurality of commodities. The system also includes a transceiver for receiving information about the plurality of commodities from a plurality of servers via one or more data communication channels. The system also includes a processing circuit for calculating a value of the token based on the respective quantities and information about the plurality of commodities. The transceiver is also used to receive updated information about the plurality of commodities from the plurality of servers via one or more data communication channels. The processing circuit is also used to update the value of the token based on the updated information and provide the value of the token to one or more nodes of the distributed network for use in transactions.

[0021] In another aspect of the disclosure, the processing circuitry is also used to determine a quantity for one of the multiple items, which may include determining a quantity of zero for the item.

[0022] In yet another aspect of the present disclosure, a system for coordinating data exchange includes at least one node of a distributed network of nodes.

[0023] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0024] In yet another aspect of the present disclosure, the information includes a market value associated with at least one of the plurality of instruments.

[0025] In yet another aspect of the present disclosure, the processing circuitry is also used to determine quantities for a plurality of items.

[0026] In yet another aspect of the present disclosure, the processing circuitry may also be used to monitor multiple underlying assets collateralizing the tokens with respect to ensuring that reserve requirements for the tokens are met.

[0027] In yet another aspect of the present disclosure, the instruments are associated with different time periods and the processing circuitry is used to calculate values ​​of the tokens based on the different time periods.

[0028] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0029] In yet another aspect of the present disclosure, a distributed network of nodes stores multiple instances of multiple products.

[0030] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0031] In yet another aspect of the present disclosure, the processing circuitry causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0032] In yet another aspect of the disclosure, the distributed network of nodes is located in at least one of a private or a public distributed network of nodes.

[0033] In yet another aspect of the disclosure, the tokens are of a first type, and the system also includes exchanging other tokens of a second type for the tokens of the first type based on an associated exchange rate.

[0034] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0035] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0036] In yet another aspect of the disclosure, in response to providing value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, a central entity allocates reserve assets to collateralize the tokens.

[0037] According to another aspect of the disclosure, a non-transitory computer readable medium having programmed instructions for performing a method for coordinating data exchanges between entities on a distributed network of nodes, the nodes persistently storing transaction data based on a value of a token associated with the distributed network with a central entity coupled to the distributed network. The method includes storing respective quantities for a plurality of commodities. The method also includes receiving information about the plurality of commodities from a plurality of servers via one or more data communication channels. The method also includes calculating a value of the token based on the respective quantities and information about the plurality of commodities. The method also includes receiving updated information about the plurality of commodities from the plurality of servers via one or more data communication channels. The method also includes updating a value of the token based on the updated information. The method also includes providing the value of the token to one or more nodes of the distributed network for use in transactions.

[0038] In another aspect of the disclosure, determining a quantity for an item of the plurality of items includes determining a quantity of zero for the item.

[0039] In yet another aspect of the disclosure, the central entity includes at least one node of the distributed network of nodes.

[0040] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0041] In yet another aspect of the present disclosure, the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

[0042] In yet another aspect of the present disclosure, the method also includes determining quantities for the plurality of items.

[0043] In yet another aspect of the present disclosure, the method also includes monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements of the tokens are met.

[0044] In yet another aspect of the present disclosure, receiving the information includes receiving the information from sources in different time zones, and calculating the value of the tokens is also based on the different time zones.

[0045] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0046] In yet another aspect of the present disclosure, a distributed network of nodes stores multiple instances of multiple products.

[0047] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0048] In yet another aspect of the present disclosure, the updated information received for the plurality of instruments causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0049] In yet another aspect of the disclosure, the distributed network of nodes is located in at least one of a private or a public distributed network of nodes.

[0050] In yet another aspect of the disclosure, the tokens are of a first type and the medium also includes exchanging other tokens of a second type for the tokens of the first type based on an associated exchange rate.

[0051] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0052] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0053] In yet another aspect of the disclosure, in response to providing value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, a central entity allocates reserve assets to collateralize the tokens.

[0054] According to another aspect of the disclosure, a computer-implemented method is provided that is executed by a central entity on a distributed network of nodes, the central entity coupled to the distributed network, to persistently store transaction data based on a token value associated with the distributed network. The method includes receiving, by the central entity, a request associated with an account to issue or redeem at least a portion of tokens having a token value, the token value being based on a plurality of instruments and respective quantities. The method also includes determining a payment amount based on the token value. The method also includes causing, by processing circuitry at the central entity, to transfer the payment amount to the account. The method also includes causing the distributed network of nodes to be updated based on the payment.

[0055] In another aspect of the disclosure, the method also includes adding a value indicative of the fragment to the fragmented token count when at least a portion of the token comprises a fragment of the token. The method also includes updating the distributed network of nodes after the fragmented token count reaches a full token, decrementing the count by one, and updating the distributed network of nodes to store information indicative of one token being issued or redeemed.

[0056] In yet another aspect of the present disclosure, causing the payment amount to be transferred to the account includes causing at least one of the plurality of items to be transferred up to the payment amount.

[0057] In yet another aspect of the disclosure, the quantity for one item of the plurality of items includes a quantity of zero for each item of the plurality of items.

[0058] In yet another aspect of the disclosure, the central entity includes at least one node of the distributed network of nodes.

[0059] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0060] In yet another aspect of the present disclosure, the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

[0061] In yet another aspect of the present disclosure, the method also includes determining quantities for the plurality of items.

[0062] In yet another aspect of the present disclosure, the method also includes monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements of the tokens are met.

[0063] In yet another aspect of the present disclosure, receiving the information includes receiving the information from sources in different time zones, and the calculating is also based on the different time zones.

[0064] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0065] In yet another aspect of the present disclosure, a central entity creates multiple instances of multiple products.

[0066] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0067] In yet another aspect of the present disclosure, the updated information received for the plurality of instruments causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0068] In yet another aspect of the disclosure, the central entity is located in at least one of a private or public decentralized network of nodes.

[0069] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0070] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0071] In yet another aspect of the disclosure, in response to providing value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, a central entity allocates reserve assets to collateralize the tokens.

[0072] According to another aspect of the present disclosure, a system is provided coupled to a distributed network of nodes for persistently storing transaction data based on a token value associated with the distributed network. The system includes a transceiver for receiving a request associated with an account to issue or redeem at least a portion of tokens having a token value, the token value being based on a plurality of commodities and respective quantities. The system also includes processing circuitry configured to determine a payment amount based on the token value, cause the payment amount to be transferred to the account, and cause the distributed network of nodes to be updated based on the payment.

[0073] In another aspect of the disclosure, the processing circuitry is also configured to: add a value indicative of the fragment to the fragmented token count if at least a portion of the token comprises a fragment of a token; after the fragmented token count reaches a full token, decrement the count by one; and update the distributed network of nodes to store information indicating that one token has been issued or redeemed.

[0074] In yet another aspect of the present disclosure, the processing circuitry is also configured to cause the transfer of at least one of the plurality of items amounting to a payment amount.

[0075] In yet another aspect of the disclosure, the quantity for one item of the plurality of items includes a quantity of zero for each item of the plurality of items.

[0076] In yet another aspect of the disclosure, a system includes at least one node of a distributed network of nodes.

[0077] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0078] In yet another aspect of the present disclosure, the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

[0079] In yet another aspect of the disclosure, a system coupled to the distributed network of nodes also includes determining quantities for a plurality of commodities.

[0080] In yet another aspect of the present disclosure, a system coupled to the distributed network of nodes also includes monitoring multiple underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

[0081] In yet another aspect of the present disclosure, the transceiver is also used to receive information, including information from sources in different time periods, and the processing circuitry is also used to calculate values ​​of the tokens based on the different time periods.

[0082] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0083] In yet another aspect of the present disclosure, a system coupled to a distributed network of nodes creates multiple instances of multiple commodities.

[0084] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0085] In yet another aspect of the present disclosure, the updated information received for the plurality of instruments causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0086] In yet another aspect of the present disclosure, a system coupled to a distributed network of nodes is located in at least one of a private or public distributed network of nodes.

[0087] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0088] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0089] In yet another aspect of the present disclosure, in response to determining the payment amount, the buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, the central entity allocates reserve assets to collateralize the tokens.

[0090] According to another aspect of the disclosure, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed, perform a method by a central entity on a distributed network of nodes, the nodes persistently storing transaction data based on a token value associated with the distributed network, the central entity coupled to the distributed network. The method includes receiving, by the central entity, a request associated with an account to issue or redeem at least a portion of tokens having a token value, the token value being based on a plurality of commodities and respective quantities. The method also includes determining a payment amount based on the token value, causing the payment amount to be transferred to the account, and causing the distributed network of nodes to be updated based on the payment.

[0091] In another aspect of the disclosure, the method also includes adding a value indicative of the fragment to the fragmented token count if at least a portion of the token comprises a fragment of the token, and decrementing the count by one after the fragmented token count reaches a full token, and updating the distributed network of nodes includes updating the distributed network of nodes to store information indicating that one token has been issued or redeemed.

[0092] In yet another aspect of the present disclosure, the method also includes causing a transfer of the payment amount to the account, including causing the transfer of at least one of the plurality of items amounting to the payment amount.

[0093] In yet another aspect of the present disclosure, storing a quantity for one of the plurality of items includes storing a quantity of zero for each item of the plurality of items.

[0094] In yet another aspect of the disclosure, the central entity includes at least one node of the distributed network of nodes.

[0095] In yet another aspect of the present disclosure, the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

[0096] In yet another aspect of the present disclosure, the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

[0097] In yet another aspect of the present disclosure, the method also includes determining quantities for the plurality of items.

[0098] In yet another aspect of the present disclosure, the method also includes monitoring the value of the tokens with respect to reserve assets collateralizing the tokens.

[0099] In yet another aspect of the present disclosure, the information associated with the token value includes information from sources in different time periods, and calculating the value of the token is also based on the different time periods.

[0100] In yet another aspect of the present disclosure, the value of the token is specific to each of the multiple commodities.

[0101] In yet another aspect of the present disclosure, a central entity creates multiple instances of multiple products.

[0102] In yet another aspect of the present disclosure, one or more tokens are associated with multiple products.

[0103] In yet another aspect of the present disclosure, the updated information received for the plurality of instruments causes changes in respective quantities for the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the changes in respective quantities for the plurality of instruments.

[0104] In yet another aspect of the disclosure, the central entity is located in at least one of a private or public decentralized network of nodes.

[0105] In yet another aspect of the present disclosure, the tokens are redeemable for multiple goods.

[0106] In yet another aspect of the present disclosure, the tokens are redeemable for an equivalent value in units of a single product which may or may not be in multiple products.

[0107] In yet another aspect of the present disclosure, in response to determining the payment amount, the buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, the central entity allocates reserve assets to collateralize the tokens.

[0108] The above and other objects and advantages of the present disclosure will become apparent from the following detailed description considered in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout. [Brief description of the drawings]

[0109] [Figure 1] FIG. 1 is an illustrative block diagram showing a system for providing reserves to a tokenization platform, according to some embodiments of the present disclosure. [Diagram 2] FIG. 2 is an illustrative block diagram showing an example of a central entity for providing reserves to a tokenization platform, according to some embodiments of the present disclosure. [Diagram 3]FIG. 13 is an illustrative block diagram showing another example of a central entity for providing reserves to the tokenization platform, in accordance with some embodiments of the present disclosure. [Figure 4] FIG. 13 is an illustrative block diagram showing yet another example of a central entity for providing reserves to a tokenized platform, according to some embodiments of the present disclosure. [Diagram 5] FIG. 2 is an illustrative block diagram showing an example of a pricing engine, according to some embodiments of the present disclosure. [Figure 6] FIG. 1 is an illustrative block diagram showing an example of token evaluation, according to some embodiments of the present disclosure. [Figure 7] FIG. 2 is an illustrative block diagram showing an example of a token exchange rate, according to some embodiments of the present disclosure. [Figure 8] 1 is an illustrative flowchart of a process for providing reserves to a tokenized platform according to some embodiments of the present disclosure. [Figure 9] 1 is an illustrative flowchart of another process for providing reserves to a tokenized platform according to some embodiments of the present disclosure. [Figure 10] 1 is an illustrative flowchart of a process for processing a token issuance or redemption request according to some embodiments of the present disclosure. [Figure 11] 11 is an illustrative flowchart of another process for processing a token issuance or redemption request according to some embodiments of the present disclosure. [Figure 12] 1 is an illustrative flowchart of a process for determining the ability to fulfill a token issuance request according to some embodiments of the present disclosure. [Figure 13] 1 is an illustrative flowchart of a process for redemption of fragment tokens according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0110] Modern networks and systems generally face the problem of tokens on a distributed network of nodes (e.g., blockchain) having no inherent value or basis for valuation; such tokens typically do not represent ownership of any real-world assets ("Untethered Tokens"), and therefore they are limited in their ability to be used for real-world transactions. Untethered tokens typically cannot be valued based on any real-world asset-based metrics, and instead can typically only be valued based on speculation and some perception of projected future value, which is also not based on any real-world asset-based metrics. Market transactions have shown that these problematic attributes can result in highly volatile token prices, problematic exchange rates, and liquidity issues, all of which limit the ability and desirability of untethered tokens to be used in commercial transactions. (The terms "token" and "coin" are used interchangeably herein.)

[0111] In some embodiments, a system is provided that allows certain tokens to be reliably valued by having them represent ownership interests in real-world assets without actual ownership of the real-world assets. These tokens can be issued by institutions that have each token track a given real-world asset, but do not collateralize the token ownership with the corresponding real-world asset ownership. However, such simplified tokens have limitations and problems that dramatically reduce their ability to become a universal payment solution and asset protection vehicle, such as not including token collateralization and therefore being each tied to a single asset that no longer provides security of value while retaining all of the risks of the respective underlying assets. Furthermore, on the payment side, these simple tokens are similar to stored value cards (which only have the value of the respective underlying assets) and cannot provide universal payment applications.

[0112] In some embodiments, modern networks and systems face the additional problem of protecting token ownership. Tokens are often tied to an identification code, or private key, that is stored in a digital system often referred to as a "wallet." If a token owner's wallet and / or private key is lost, hacked, or otherwise compromised, the token owner may effectively lose ownership of their tokens. Although more extensive systems have been developed that purportedly protect wallets, there remains a lack of insurance or other mechanisms to protect token ownership in the event that the private key is compromised.

[0113] To solve these problems, a system is needed that provides tokens that can be valued and priced in real time and are fluidly convertible into a myriad of currencies and financial instruments. Tokens with these properties can be transparently valued (i.e., have inherent value) by anyone at any time. Such tokens can be used for commerce because both their buyers and sellers can be sure of their value both at the time of exchange and in the future. The system also needs to perform functions that support token ownership and trading, including market regulation, token valuation, token insurance, etc.

[0114] In some embodiments, buyers can exchange different financial instruments (e.g., US dollars, gold, silver, euros, Norwegian krona, Swiss francs, Australian dollars, Singapore dollars, British pounds, other global currencies, asset-backed cryptocurrencies, or commodities) to purchase tokens collateralized by reserves created by and held by a central entity. The tokens can be converted back into these or other financial instruments. The tokens can be transparently and dynamically valued based on an underlying basket of financial instruments. In some embodiments, the basket can be rebalanced by the central entity at any time for any number of reasons, such as to protect against government deductions or quantitative easing, to hedge against inflation, to stabilize the security of the central entity and the tokens held therein, or for other reasons. In some embodiments, reserves, transaction fees, and processing fees can be stored to provide liquidity that ensures orderly conversion and reliable ownership.

[0115] In some embodiments, the system enables valuation and pricing, issuance by a central entity ("Issuance"), redemption by a central entity ("Redemption"), and exchange between two or more third parties ("Exchange"), where one or more unique types of tokens (or fractional tokens) are collateralized by a reserve ("Reserve") of underlying highly liquid globally traded currencies, commodities, asset-backed cryptocurrencies, and / or other assets. Issuances, redemptions, and exchanges may collectively be referred to as "Transactions." In some embodiments, a transaction involves one or more unique tokens being exchanged for fiat currency or other unique tokens. In some embodiments, the central entity may manage, coordinate, facilitate, handle, or otherwise enable all transactions and all reserves.

[0116] In some embodiments, the central entity may implement a new token basket design, including the selection of multiple products and their respective quantities, and integrate with third-party stakeholders for issuance, redemption, exchange, and reserve functions. A given third-party stakeholder may hold a token specifically designed for the given third-party stakeholder, which may be referred to as a third-party token. Following issuance, the central entity may maintain dynamic token valuation and notify the third-party stakeholder of required reserves, as described above and below. The third-party stakeholder may hold reserves and facilitate redemptions and exchanges. These actions performed by the third-party stakeholder may be in lieu of redemptions and exchanges of their own tokens, or they may be performed in a custodial capacity, for example, on behalf of their own clients. The central entity may explicitly design a unique token for a given third-party stakeholder.

[0117] To enable the system to value tokens and facilitate transactions, the system sources and / or maintains information from and about multiple global market exchanges, such information may include, among other things, information regarding exchange rates, trading volumes, exchange hours, connectivity, etc.

[0118] Unique Tokens: In some embodiments, the primary parameters of each unique type of token are its “Asset Mix” (defined below) and its “Reserve Requirement” (defined below).

[0119] Asset Mix: In some embodiments, each unique type of token is associated with an explicitly pre-configured underlying basket comprised of a pre-specified mix of multiple highly liquid, globally traded currencies, commodities, asset-backed cryptocurrencies, and / or other assets (each, an “Underlying Asset”), with a pre-specified and potentially different (and potentially fractional) number of units of each such Underlying Asset being included in the basket (the “Asset Mix”). In some embodiments, any financial instrument or other value-bearing asset may be an Underlying Asset. For example, the asset mix of a unique type of token may be 100 US dollars, 64 euros, and 0.044 ounces of gold. In some embodiments, the asset mix associated with each unique type of token may be modified as discussed herein.

[0120] Reserve Requirements: In some embodiments, each unique type of token will be associated with a pre-specified "reserve requirement," which is, among other features, a pre-specified minimum reserve asset that must be held to collateralize the central entity's obligations with respect to that token. In some embodiments, one or more third-party stakeholders hold some or all of the reserve assets.

[0121] In some embodiments, the reserve requirement for any given unique type of token may require that a pre-specified percentage number (the "Reserve Percentage") be applied to determine the number of units (or decimals) of that token's underlying asset that must be held in the reserve. For example, if the reserve requirement for any given unique type of token requires a fixed reserve percentage of 25% and the asset mix of that token is as described above, then a minimum of 25 US dollars (25% of 100 US dollars), 16 euros (25% of 64 euros), and 0.011 ounces of gold (25% of 0.044 ounces of gold), among other things, must be held in the reserve to collateralize the central entity's obligations with respect to that token. The reserve requirement may be dynamically updated according to, among other information, real-time information from multiple global market exchanges and real-time information regarding the token value and quantity of outstanding issued tokens. In some embodiments, the reserve percentage may be 100%.

[0122] In some embodiments, the reserve requirements may dictate that, for any given unique type of token, different reserve percentages are applied to different tranches of outstanding tokens. For example, for any given unique type of token, the reserve requirements may require that a 30% reserve percentage be applied to the first 1 million tokens outstanding, a 17.5% reserve percentage be applied to the next 10 million tokens outstanding, and a 5% reserve percentage be applied to all additional tokens outstanding. The reserve percentages in the foregoing example may also depend on the value of each unique type of token. For example, the reserve percentages for any tranche of outstanding tokens may decrease if the token value increases, and these same reserve percentages may increase if the token value decreases.

[0123] In some embodiments, different reserve percentages may also be applied to each underlying asset in the asset mix. For example, as described above, if there are different reserve requirements for each underlying asset in the asset mix, a 30% reserve percentage may be applied to the US dollar, a 17.5% reserve percentage may be applied to the euro, and a 5% reserve percentage may be applied to gold.

[0124] In some embodiments, there are multiple unique types of tokens, each with its own brand name and each characterized by its own unique asset mix and reserve requirements. Each such unique type of token is referred to as a "Unique Token." Each such Unique Token can be designed to address a particular goal of the token holder, such as stability against inflation, value appreciation, protection against particular market dynamics, or other financial reasons.

[0125] Valuation of Unique Tokens: In some embodiments, the system provides a real-time value of each unique token quoted in units of other assets. The real-time value of each unique token may depend on dynamic market information obtained and incorporated by the system.

[0126] "Denominated Quoted Token Value" means the value of a unique token quoted in units of another asset (more generally, "Denominated Quoted Value" means the value of any given asset quoted in units of another asset). "Denominated Quoted Asset" means an asset in which any value is quoted. As an example of how some of the above terms may be used, the nominal quoted token value of one "Numi" token may be 100 US dollars, 96 euros, or 0.0551907 ounces of gold. In this example, the nominal quoted asset is US dollars, euros, or gold, respectively. In some embodiments, the nominal quoted token value and the nominal quoted asset are used by a central entity and / or token holders to facilitate exchanges (e.g., to create a token market). In some embodiments, values ​​as described by the above sections may depend on dynamic market information obtained and incorporated by the system.

[0127] In some embodiments, the system's valuation and pricing engine automatically determines the nominal quotation token value of any unique token, as expressed in units of any given nominal quotation asset, by: (i) collecting and processing exchange rates for the nominal quotation asset, on the one hand, and for each of the underlying assets for that unique token, on the other hand; (ii) applying those exchange rates to determine a nominal quotation value of each of those underlying assets; and (iii) adding all the resulting amounts together to determine the nominal quotation value of the unique token's entire asset mix, and thus the nominal quotation token value of that unique token.

[0128] The following is an exemplary discussion of a process for collecting and processing exchange rates with respect to each of the nominal market assets and / or underlying assets for that unique token to better contextualize step (i) as described above: As discussed in step (i) above, as one of the first steps in determining the nominal market token value of any unique token, as expressed in units of any nominal market asset, the system's valuation and pricing engine collects and processes exchange rates with respect to the nominal market asset on the one hand, and each of the unique token's underlying assets on the other hand.

[0129] As used herein, the following terms have the meanings indicated below. "Asset Pair" means any pairing of two assets maintained within the System. For example, the United States Dollar and the Euro may be an Asset Pair. When one wishes to determine the value of an asset as quoted in units of another asset, the asset being valued is called the "Base Asset." As discussed above, an asset whose value is quoted in units is a "nominal asset." For example, if one wishes to determine the value of 1 Euro in United States dollars, then the Euro would be the Base Asset and the United States dollar would be the nominal asset. "Exchange pair" means a one-way pairing of two assets in any asset pair, which can be used, among other things, when one wants to determine an exchange rate for valuing the base asset in units of the nominal-rate asset. For any asset pair, there are two exchange pairs: (A) one exchange pair in which one of the two assets is the base asset and the other is the nominal-rate asset, and (B) a second exchange pair in which the base asset from the first exchange pair is instead the nominal-rate asset and the nominal-rate asset from the first exchange pair is instead the base asset. For example, for an asset pair consisting of the US dollar and the euro, the two exchange pairs are: (A) euro (base asset) - US dollar (nominal-rate asset), (B) US dollar (base asset) - euro (nominal-rate asset).

[0130] In some embodiments, the system maintains a separate trading pair for each asset pair.

[0131] In some embodiments, the system determines a real-time exchange rate for each exchange pair based on, for example, information accessible from multiple global market exchanges. If the system has access to information from multiple global market exchanges at the time of the determination and such global market exchanges offer different real-time exchange rates for any given trading pair, the system uses the real-time exchange rate that results in the largest amount of notional quoted assets in the trade for the underlying asset in question.

[0132] Based on the above, the system's valuation and pricing engine can quote any one asset in units of any other asset, provided that the system can determine the exchange rates for the applicable asset pairs from the global market.

[0133] For example, the system can quote any number of euros in units of dollars (the exchange rate used to determine the value of 1 euro in U.S. dollars can be hypothetically determined to be 1.04), and the system can quote any number of British pounds in units of dollars (the exchange rate used to determine the value of 1 British pound in U.S. dollars can be hypothetically determined to be 1.23).

[0134] To better contextualize step (ii) as described above, the following is an exemplary discussion of a process for applying exchange rates to determine a notional market value of an underlying asset of a unique token: As discussed in subsection (ii) above, once the system's valuation and pricing engine has collected and processed exchange rates with respect to the notional market asset, on the one hand, and with respect to each of the unique token's underlying assets, on the other hand, the system's valuation and pricing engine applies those exchange rates to determine a notional market value of each of those underlying assets.

[0135] Specifically, for each underlying asset for the unique token in question, the system multiplies (a) the number of units of the underlying asset by (b) an exchange rate used to value that particular underlying asset in units of the nominal quotient asset, with the product of each such calculation resulting in a nominal quotient value of each underlying asset in units of the nominal quotient asset.

[0136] For example, if a unique token's asset mix consists solely of (a) 100 Euros and (b) 200 British Pounds, and the US Dollar is the nominal asset in which the system seeks to value the underlying asset, the system would: (a) Multiply 100 (the number of euros) by the exchange rate used to determine the value of 1 euro in U.S. dollars, which hypothetically would be 1.04, thus yielding 104 U.S. dollars as the nominal exchange value for the underlying asset in euros. (b) Multiply 200 (the number of British pounds) by the exchange rate used to determine the value of 1 British pound in United States dollars, which is hypothetically 1.23, thus yielding 246 United States dollars as the nominal exchange rate value for the underlying asset of British pounds.

[0137] To better contextualize step (iii) as described above, the following is an exemplary discussion of the process of adding together the nominal market value of all underlying assets to determine the nominal market value of the entire asset mix of a unique token: As discussed in subsection (iii) above, once the system's valuation and pricing engine has determined the nominal market value of each underlying asset for any given unique token, it adds all of those nominal market values ​​together to determine the nominal market value of the entire asset mix for that unique token.

[0138] This nominal market value of the entire asset mix, as quoted in units of the nominal market assets, is the final nominal market token value, or “Denominated Token Price,” of the unique token in question.

[0139] To illustrate, in the immediate example, the system would add US$104 (as the nominal quotation value for the underlying asset in British Pounds) and US$246 (as the nominal quotation value for the underlying asset in British Pounds) to determine that the nominal quotation value of the unique token's entire asset mix was US$350. Thus, the system would determine that the nominal quotation token value, or "nominal token price," of the unique token was US$350. The system may use this value in coordination with the central entity and / or token holders to facilitate purchases or redemptions of tokens.

[0140] The following is an exemplary discussion of the pricing transaction process: In some embodiments, once the nominal token price for the unique tokens is determined, as quoted in units of the nominal market asset, the system's valuation and pricing engine determines (i) the total number of tokens (or fractional tokens) that will be issued to buyers in exchange for any given amount of consideration (the "Denominated Total Consideration"), and (ii) the nominal total consideration that will be paid to sellers in connection with the redemption of any given number (or fraction) of tokens.

[0141] Issuance: An issuance may include a completed token design, including its underlying asset mix and reserve requirements. In some embodiments, an issuance may also include an initial sale of tokens to token buyers, with this aspect of the issuance possibly being performed by or in concert with a third-party stakeholder (e.g., acting as an administrative entity that controls a portion of the central entity). For any issuance of tokens by the central entity, the exact number of tokens (or tokens of a fraction) that the buyer receives is equal to the result obtained by dividing (a) the notional total consideration paid by the buyer by (b) the notional token price, each such amount (a) and (b) being quoted in units of the notional quoted asset. For example, if the notional total consideration to be paid by the buyer is 100 euros and the notional token price is 400 euros, the buyer will receive exactly 0.25 tokens in the transaction (100 euros / 400 euros=0.25 tokens). With respect to the buyer, the notional total consideration may not include additional costs, including fees, as discussed further below.

[0142] Redemption: For any redemption of tokens by the central entity, the exact notional total consideration received by the seller is equal to the result of the quoted price in units of the nominal market asset, which is obtained by multiplying (a) the exact number of tokens (or fractional tokens) offered by the seller by (b) the nominal token price quoted in units of the nominal market asset. For example, if exactly 0.25 tokens are to be offered by the seller and the nominal token price is 400 euros, the seller will receive exactly 100 euros in the transaction (0.25 tokens x 400 euros = 100 euros). With respect to the seller, the notional total consideration may not include additional costs, including commission, as discussed further below.

[0143] Selection of Nominal Exchange Asset: In some embodiments, a party transacting with a central entity is permitted to select a nominal exchange asset, i.e., determine the exact asset type to be provided as consideration for tokens, whether the transaction involves the party providing units of that asset type to the central entity in consideration for the issuance of tokens by the central entity, or whether the transaction involves the central entity providing units of that asset type to the party in consideration for the redemption of tokens by the central entity, i.e., in all cases, provided that the asset type the party wishes to use is on a pre-configured list of forms of consideration that the system deems acceptable.

[0144] Fees: In some embodiments, the system may charge certain fees, including transaction fees. In some embodiments, such fees are separate from and do not affect the valuation of any tokens or the pricing of any transactions.

[0145] Modifying or rebalancing the asset mix of any unique token: In some embodiments, the system may enable a central entity to modify or rebalance the asset mix of any unique token. In some embodiments, any such modifying or rebalancing is done in a manner that maintains the aggregate market value of the unique token's asset mix as quoted in units of any nominal market asset. In some embodiments, modifying or rebalancing may serve to maintain the reserve requirements of the unique token and / or the reserve percentage of the underlying asset. In some embodiments, rebalancing may automatically change the reserve asset collateralizing the unique token.

[0146] Maintaining Minimum Aggregate Reserves: In some embodiments, the system automatically determines and maintains at all times the minimum aggregate reserve of the underlying assets that must be held in reserve in order to secure the central entity's obligations with respect to the entire outstanding float of any given unique token, in accordance with the reserve requirements of that unique token. In some embodiments, the system automatically determines and maintains the reserves in response to information accessible, for example, from multiple global market exchanges. The reserve requirement of any unique token may depend on the entire outstanding float of that unique token, which is calculated as the product of (a) the unique token value and (b) the total number of outstanding unique tokens.

[0147] In some embodiments, when there is an issuance of a unique token, thereby increasing the minimum aggregate amount of underlying assets that must be held in the reserve for that unique token, the system may automatically purchase additional underlying assets that must be held in the reserve on one or more global market exchanges, or otherwise ensure that the reserve meets the reserve requirement (e.g., by specifically allocating reserve assets already managed by the system). In some embodiments, when a third-party stakeholder holds a reserve, the system may automatically instruct the third-party stakeholder to purchase additional underlying assets that must be held in the reserve, or otherwise ensure that the reserve meets the reserve requirement. In some embodiments, when there is any redemption of a unique token, thereby decreasing the minimum aggregate amount of underlying assets that must be held in the reserve for that unique token, the system may automatically sell, on one or more global market exchanges, the amount of underlying assets that no longer need to be held in the reserve due to the redemption. In some embodiments, when a third-party stakeholder holds a reserve, the system automatically instructs the third-party stakeholder to sell on one or more global market exchanges additional underlying assets that no longer need to be held in the reserve. In some embodiments, the system's automated purchases and / or sales are performed in a manner that maintains an aggregate market value of the unique token's asset mix as quoted in units of any nominal quoted asset. In some embodiments, any one or more of these functions for automatically updating the reserve assets collateralizing the unique token may be performed by a central entity in response to changes in market conditions (e.g., changes in the market value of the unique token and / or its underlying assets).

[0148] Third Party Verification: In some embodiments, the system will provide a specific third party verification service by providing a third party with access to information regarding, for example, the total number of tokens outstanding for any given type of unique token, the asset mix for that type of unique token, the reserve requirement for that type of unique token, the aggregated underlying assets actually reserved for that unique token, or other financial information. In some embodiments, the system provides a specific third party with the ability to audit the aforementioned information and attest that required reserves have actually been maintained for any given type of unique token. In some embodiments, certain third party stakeholders may hold reserves for the unique tokens, and in such cases, the central entity may have the ability to audit these third party stakeholders to attest that required reserves have actually been maintained for any given type of unique token. In some embodiments, the system may automatically amend or rebalance any of the unique token reserves, the asset mix for the unique token, the reserve requirement for the unique token, the aggregated underlying assets actually reserved for that unique token, or other financial instruments in response to a third party audit.

[0149] Rounding: In some embodiments, the system rounds certain numbers that contain too many digits to the right of any decimal point according to determined rules. Such rounding can occur with respect to various types of numbers and can affect various calculations and other matters, including but not limited to those involving token value and pricing.

[0150] Records: In some embodiments, the system has the ability to post records of all issuances and redemptions and of certain exchanges to third party systems, such as private and public blockchain ledgers or other forms of data storage. Configuration of posting to third party external systems is specified for each unique type of token configured. In some embodiments, the private and public blockchain ledgers may be stored within a central entity.

[0151] In some embodiments, the system maintains a record for a particular transaction, which may include the following types of information: -Transaction ID, - Information about digital wallets, - information about the type of assets offered in the transaction; -The amount of assets offered in exchange for tokens; - the number of tokens (or token fragments) provided in the transaction, -An asset mix ID associated with the type of token offered in the transaction, and -Details regarding the reserve requested for the tokens offered in the transaction.

[0152] In some embodiments, at every occurrence of issuance and redemption, the system records the above information in an internal ledger that maintains a running total calculation of the total number of tokens of the applicable type subsequently in circulation. The internal ledger may be replicated on a public or private blockchain.

[0153] System Operation: In some embodiments, a central entity operates the system. In some embodiments, a third party stakeholder may control a portion of the central entity and operate the system in part within it.

[0154] In some embodiments, the central entity may, at its sole discretion, authorize certain third-party stakeholders to provide depository, issuance, exchange, reserve, or other services, or may outsource such services to such third parties.

[0155] In some embodiments, operational decisions regarding how assets are stored are determined by a central entity and any contractual / fiduciary responsibilities that exist with token holders.

[0156] FIG. 1 shows an illustrative block diagram of a system 100 for providing a tokenization platform with a reserve, according to some embodiments of the present disclosure. In one aspect, the system 100 includes a central entity 102, a distributed node(s) 103, a server(s) 104, an account(s) 114, a communication channel(s) 124, and system links 126 and 128. In particular, the central entity 102 may include a processing circuit 108 for calculating the value of the tokens. The central entity 102 may be controlled by any suitable one or more stakeholders. For example, the central entity may be at least partially controlled by an administrative entity and at least partially controlled by one or more third-party stakeholders. The processing circuit 108 may also update the value of the tokens and provide the value of the tokens to the distributed node(s) 103 for use in transactions via the system link 128. The processing circuit 108 may also be for executing commands, performing actions, and otherwise processing information. The central entity 102 may include a storage device 109 for storing respective quantities for the multiple items. The storage device 109 (e.g., memory) may also be for storing information. The central entity 102 may include a transceiver 110 for receiving information about the multiple items. The transceiver 110 may also receive updated information regarding the multiple items. The transceiver 110 may also receive information from the multiple server(s) 104 via the data communication channel(s) 124. The transceiver 110 may also be for transmitting and receiving signals, as well as for linking to the account(s) 114 via a system link 126 and to the distributed node(s) 103 via a system link 128. In some embodiments, the central entity 102 may be a suitable part or the entirety of a device located either at one location or at distributed locations, e.g., located at the distributed node(s) 103, or located at one or more sites managed by one or more third party stakeholders.In some embodiments, the instrument may be a financial asset. Although Figure 1 illustrates a particular number of each component, in various examples, system 100 may include more than one of the illustrated components.

[0157] In some embodiments, the server(s) 104 of the system 100 includes processing circuitry 111 for executing commands, performing actions, and otherwise processing information. The server(s) 104 may include a storage device 112 (e.g., memory) for storing information. The server(s) 104 may include a transceiver 113 for transmitting and receiving signals and for linking to the central entity 102 via communication channel(s) 124. In some embodiments, the server(s) 104 may be within the central entity 102. In some embodiments, the server(s) 104 may be managed and operated by the central entity 102.

[0158] In some embodiments, the distributed node(s) 103 include processing circuitry 105 for executing commands, performing operations, and otherwise processing information. The distributed node(s) 103 may include a storage device 106 (e.g., memory) for storing information. The distributed node(s) 103 may include a transceiver 107 for transmitting and receiving signals and for linking to the central entity 102 via a system link 128.

[0159] In some embodiments, the account(s) 114 include a crypto exchange 116, a foreign exchange exchange 118, and a commodity exchange 120. In some embodiments, these exchanges can provide real-time information, for example, for dynamic token valuation, rebalancing, or correction. In some embodiments, some of these account(s) 114 can be under escrow of one or more third-party stakeholders. The account(s) 114 can also include consumers 122, escrows 130, and reserves 132. In some embodiments, these consumers 122 can purchase tokens, for example, via issuance by the central entity 102. The consumers 122 can be individuals, institutions, or both, such as, for example, banks, funds, or corporations. In some embodiments, these consumers 122 can sell tokens, for example, via redemption by the central entity 102. Any account(s) 114 can initiate a transaction or request a transaction from a central entity 102 configured to initiate a transaction and provide the value of the token to the decentralized node(s) 103. A escrow 130 can facilitate token issuance, redemption, or exchange on behalf of token buyers and redeemers, e.g., consumers 122. A reserve 132 can hold an amount of the underlying assets sufficient to meet the reserve requirements of the token(s). The reserve 132 can be adjusted in response to dynamic reassessment of reserve requirements by the central entity 102.

[0160] Through the transceivers 110 and 107, the account(s) 114 are each linked to the central entity 102 via a system link 128. In some embodiments, the account(s) 114 can initiate or request transactions from the central entity 102. In some embodiments, the central entity 102 stores records of transactions and confirms transactions. In some embodiments, the central entity 102 can request information from the server(s) 104 related to transactions associated with the token.

[0161] In some embodiments, the network entities (e.g., distributed nodes 103, servers 104, central entity 102, or accounts 114) may be implemented using a multi-tenancy configuration. For example, two distributed nodes may be associated with a particular computing device and node application, but may process data in a partitioned and separate manner. In some embodiments, the multi-tenancy configuration may include integration with and management of various network entities by third-party stakeholders. These third-party stakeholders may host distributed node(s) 103, server(s) 104, account(s) 112, or any combination thereof. In implementations of such a configuration, the third-party stakeholders may automatically integrate with and follow instructions from the central entity 102 (or components thereof). In some embodiments, the third-party stakeholders may exchange tokens using an exchange rate provided by the central entity 102. Such exchanges may occur via the central entity 102 or may occur directly between the third-party stakeholders. In some embodiments, a particular token may be dedicated to a respective third-party stakeholder (i.e., a third-party token) upon issuance or redemption, or through its subsequent use in a transaction.

[0162] In some embodiments, a network entity (e.g., distributed node 103, server 104, or central entity 102) may be implemented using a virtual machine. For example, distributed node(s) 103 and account(s) 112 or third party stakeholders may be represented by network entities implemented using a common computing device, each using a separate application implemented on a respective virtual machine implemented on the computing device.

[0163] In some embodiments, the system 100 implements a blockchain system configured to store immutable records among nodes. In some embodiments, the blockchain system includes distributed node(s) 103.

[0164] In some embodiments, the distributed node(s) 103 can initiate or request a transaction from the central entity 102. In some embodiments, the central entity stores a record of the transaction and validates the transaction.

[0165] As shown in FIG. 2, a system 200 in which a central entity 202 operates includes executing a transaction using a computer-implemented system according to some embodiments of the present disclosure. In some embodiments, the central entity 202 is the central entity 102. In the example system 200, a token buyer 204 executes a currency transaction(s) 210 with the central entity 202, and a currency 206 (e.g., U.S. dollar, gold, silver, euro, Norwegian krona, Swiss franc, Australian dollar, Singapore dollar, British pound, other global currencies, asset-backed cryptocurrencies, or commodities) and / or token(s) 208 are traded through the central entity 202. The currency transaction(s) 210 may include a token issuance or a token redemption. In response to a request for the currency transaction(s) 210, the central entity executes a token transaction(s) 216 using a token account(s) 218. The token transaction(s) include an exchange of token(s) 238, which may be token(s) 208, and major revenue 212, which may be currency 206, via token account(s) 218. The token buyer 204 and token account(s) 218 ​​may be one or more of the account(s) 114. In addition to the token and currency transaction(s), the central entity 202 may process token transaction fee(s) 220, which may include minor revenue 214, which is less than the major revenue 212.

[0166] In some embodiments, the system 200 includes a computer-implemented pricing engine 222. The pricing engine is used by the central entity 202 to execute transactions via a system link 228. In some embodiments, the pricing engine is included within the central entity. The pricing engine 222 can determine a unique token value (e.g., a nominal total consideration, a nominal quote token value, a nominal token value / price) based on information including, but not limited to, an asset mix, an underlying asset(s), an asset pair, an exchange pair, fees, reserve requirements, and a reserve percentage. The pricing engine 222 is linked to the blockchain ledger 224 and the token basket 226 via system links 232 and 234, respectively. The pricing engine can initiate or request transactions from the blockchain ledger 224. The pricing engine can collect unique token information from the token basket 226. In some embodiments, the pricing engine can be implemented by the processing circuitry 108 and the storage device 109, or the processing circuitry 111 and the storage device 112.

[0167] In some embodiments, the system 200 includes a computer-implemented blockchain ledger 224. The blockchain ledger is used by the central entity 202 to execute transactions via the system link 230. In some embodiments, the blockchain ledger is included within the central entity and is responsible for the central entity's reconciliation functions, which may include reconciling ledgers or accounts of one or more third-party stakeholders. The blockchain ledger 224 may store a copy of the issuance of the tokens. The blockchain ledger may be public or private. In some embodiments, the blockchain ledger 224 is a distributed node(s) 103. In response to receiving a request to initiate a transaction from the central entity, the blockchain ledger 224 may be updated to reflect the transaction, for example in response to the currency transaction(s) 210 or the token transaction(s) 216.

[0168] In some embodiments, the system 200 includes a computer-implemented token basket 226. The token basket is used by the central entity 202 to execute transactions via the system link 236. In some embodiments, the token basket is included within the central entity. The token basket 226 may store information about the unique token(s), including, but not limited to, asset mix, underlying asset(s), asset pair, exchange pair, reserve requirement, and reserve percentage. The token basket can dynamically receive real-time information related to the characteristics of the unique token (e.g., nominal total consideration, nominal quoted token value, nominal token value / price) and update accordingly. In some embodiments, the token basket can be implemented by the processing circuitry 108 and storage device 109, or the processing circuitry 111 and storage device 112. In some embodiments, the reserves underlying the token basket can be updated and maintained by a third-party stakeholder.

[0169] 3, the system 300 includes a central entity 302, which includes processing, storage, networking, and communication equipment 304 according to some embodiments of the present disclosure. The central entity 302 may be the central entity 202 or the central entity 102.

[0170] The processing, storage, networking and communications device 304 performs functions including a custody service 306. The custody service 306 may include executing transactions, such as currency transaction(s) 210 or token transaction 216, on behalf of accounts 114, including consumers 122, or on behalf of token buyers 204 or token account(s) 218. The custody service 306 may also include updating the blockchain ledger 224, distributed node(s) 103, or other accounting of the transaction in response to receiving a request to initiate the transaction.

[0171] The processing, storage, networking and communications device 304 performs additional functions including capturing, converting, and / or reconverting funds 308. Capturing, converting, and / or reconverting funds may represent a step in the execution of a transaction, such as currency transaction(s) 210 or token transaction(s) 216, on behalf of an account(s) 114, including a consumer 122, or on behalf of a token buyer 204 or token account(s) 218. Capturing, converting, and / or reconverting funds may also include processing of currency 206, token(s) 208, major earnings 212, minor earnings 214, token(s) 238, and token transaction fee(s) 220.

[0172] The processing, storage, networking, and communications device 304 performs additional functions including replicating the issuance of tokens on a public blockchain 310 and / or issuing tokens on a private blockchain 312. These functions may represent one or more steps in the execution of a transaction, such as currency transaction(s) 210 or token transaction(s) 216, on behalf of account(s) 114, including consumers 122, or on behalf of a token buyer 204 or token account(s) 218. These functions 310 and 312 may include updating the blockchain ledger 224, distributed node(s) 103, or other accounting of the transaction in response to receiving a request to initiate the transaction.

[0173] The processing, storage, networking and communications equipment 304 performs additional functions including calculation of the prices of the tokens and instruments 314. In some embodiments, the pricing engine 222 performs the calculation of the prices of the tokens and instruments. The calculation of the prices of the tokens and instruments can determine the value of the unique token (e.g., the notional total consideration, the notional quote token value, the notional token value / price) based on information including, but not limited to, the asset mix, the underlying asset(s), the asset pair, the exchange pair, the fees, the reserve requirements, and the reserve percentage. This functionality 314 can include valuation of the token(s) 208 and the token(s) 238. In some embodiments, the functionality 314 automatically updates the prices of the tokens and instruments in response to updated information received about these aspects or features thereof.

[0174] The processing, storage, networking, and communications equipment 304 performs additional functions, including designing, maintaining, and controlling the basket of instruments 316. These functions may include determining, rebalancing, or modifying the asset mix, underlying asset(s), asset pair, exchange pair, fees, reserve requirements, and / or reserve percentages of the unique token(s). In some embodiments, the functions 316 automatically update the basket of instruments in response to updated information received about the instruments or their characteristics.

[0175] 4, according to some embodiments of the present disclosure, system 400 includes a central entity 402, which includes a reserve platform 404, a token 406, an exchange system(s) 420, and a data source(s) 422. Central entity 402 may be central entity 302, central entity 202, or central entity 102.

[0176] The reserve platform 404 includes a blockchain 408, security services 410, escrow 412, and account management 414. The blockchain 408 may be a blockchain ledger 224 or a distributed node(s) 103. The security services 410 may include holding the currency 206, the token(s) 208, the major earnings 212, the minor earnings 214, and / or the token(s) 238. In some embodiments, the security services 410 are implemented on the storage device 106, the storage device 109, or the storage device 112. The escrow 412 may be a escrow service 306. The escrow 412 may include executing transactions, such as the currency transaction(s) 210 or the token transaction(s) 216, on behalf of the account(s) 114, including the consumer 122, or on behalf of the token buyer 204 or the token account(s) 218. Depositing 412 may also include updating the blockchain 408, blockchain ledger 224, distributed node(s) 103, or other accounting of the transaction in response to receiving a request to initiate the transaction. Account management 414 may include taking, converting, and / or reconverting 308 funds. Account management may also include reporting token ownership and dynamic token values ​​on behalf of token buyers 204, consumers 122, or other stakeholders transacting with the central entity 402. The reserve platform 404 performs one or more of these operations via exchange system(s) 420.

[0177] The token 406 includes a digital currency development 416 and a cryptocurrency exchange 418. The digital currency development 416 may include determining, rebalancing, or amending the asset mix, underlying asset(s), asset pair, exchange pair, fees, reserve requirements, and / or reserve percentages of the unique token(s). The cryptocurrency exchange 418 may be the crypto exchange 116 or other marketplace for the issuance and redemption of tokens, coins, currencies, or other financial instruments. The token 406 uses data source(s) 422 to receive dynamic information regarding the characteristics of the unique token (e.g., to update the digital currency development 416) and dynamic information regarding the cryptocurrency exchange 418.

[0178] As described above and herein, FIG. 5 illustrates a system 500 including a pricing engine 222 including a token value calculator 502 and a market exchange(s) 504 according to some embodiments of the present disclosure. Specific to each unique token, the token value calculator includes an exchange rate calculator 506 and a commodity value calculator 508. The exchange rate calculator includes information regarding the underlying asset value, such as real-time unit pricing. The token value calculator 502 calculates the value of the token based on the characteristics of the token including the nominal total consideration, the nominal quotient asset, the nominal token price, and the nominal quotient token value based on the underlying asset value and the asset mix. Through communication channel(s) 510, the token value calculator 502 receives information from the market exchange(s) 504 to inform its calculation. In some embodiments, the token value calculator receives market exchange(s) information in real-time and automatically updates the token value.

[0179] As shown in FIG. 6, the method 600 for token valuation 612 includes consideration of an underlying commodity 602, a quantity 604, an exchange rate 606, and a commodity value 608. The commodity 602 may include a currency 206 or other asset-backed commodity or financial instrument, such as an asset-backed cryptocurrency, precious metals, fuels, physical assets, other commodities, or other commodities actively traded on an open market exchange, according to some embodiments of the present disclosure. A commodity may be an underlying asset of a unique token. Each respective commodity of the commodity 602 is assigned a respective quantity from the quantity 604. Each respective quantity for each respective commodity may be reported as the number of units of that respective commodity held in the token's underlying asset mix. Each respective commodity of the commodity 602 is also assigned an exchange rate from the exchange rate 606. Each respective exchange rate of each respective commodity may be reported as the unit price of the commodity with respect to the underlying asset. For example, considering the US dollar as the underlying asset and gold as the underlying asset, the exchange rate of gold may correspond to the market exchange rate of gold expressed as US dollars per ounce of gold. This market exchange rate may be determined from the account(s) 114, data source(s) 422, market exchange(s) 504, or an equivalent real-time market that trades the relevant underlying asset. Thus, the respective commodity value 608 for each respective commodity is determined by multiplying the respective commodity quantity 604 by the respective commodity exchange rate 606. Finally, the token valuation 610 is determined by summing the respective commodity values ​​for each respective commodity.

[0180] As shown in FIG. 7 , according to some embodiments of the present disclosure, a method 700 for determining token exchange rates (i.e., token to nominal market asset exchange rate 714 and nominal market asset to token exchange rate 718) includes consideration of an underlying asset 702, a nominal market asset 704, an exchange market 706, an exchange rate 708, units 710, and a nominal market value 712. In some embodiments, the underlying asset 702 may be a commodity 602. For a given underlying asset of the underlying assets 702, the respective nominal market value is equal to the product of the respective units of the given underlying asset and the respective exchange rate. The token to nominal market asset exchange rate 714 is equal to the sum 716 of the nominal market values ​​712. The nominal market asset to token exchange rate 718 is equal to the reciprocal 720 of the sum 716.

[0181] 8 is a flowchart 800 of a process for providing reserves to a tokenization platform according to some embodiments of the disclosure. At 802, a central entity (i.e., 102, 202, 302, or 402) stores respective quantities for a plurality of instruments. The respective quantities may be stored in a storage device 109 or 112, a token basket 226, a processing, storage, networking, and communications device 304, a data source(s) 422, or any combination thereof. Each of the plurality of instruments may constitute a token, e.g., a token 208, 238, or 406. An instrument of the plurality of instruments may be traded on a crypto exchange 116, a foreign exchange 118, a commodity exchange 120, a market exchange(s) 504, or any combination thereof.

[0182] At 804, the central entity receives information about the multiple instruments. The information may be received using transceivers 107, 110, or 113. The information may be received from distributed node(s) 103, account(s) 114, blockchain ledger 224, data source(s) 422, market exchange(s) 504, or any combination thereof. The information may be received from sources at different time periods. The information may include details of the underlying assets, such as price, trading volume, market capitalization, or other financial information. The central entity may automatically receive the information at predetermined intervals, and these intervals may be very short (e.g., less than one second).

[0183] At 806, the central entity calculates a value for the token. This value may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. This value may be calculated using the method 600 or 700 and may result in a token valuation 612, or an exchange rate 714 or 718. The token value may be calculated to effect token issuance, redemption, exchange, or any combination thereof. The token value may be calculated to establish reserve requirements and / or reserve percentages. The token value may depend on multiple instruments, underlying assets, asset mix, and financial information related to multiple instruments, underlying assets, or asset mix.

[0184] At 808, the central entity receives updated information regarding the multiple instruments. The updated information may be received using transceivers 107, 110, or 113. The updated information may be received from distributed node(s) 103, account(s) 114, blockchain ledger 224, data source(s) 422, market exchange(s) 504, or any combination thereof. The updated information may be received from sources at different time periods. The updated information may include details of the underlying assets, such as price, trading volume, market capitalization, or other financial information. The central entity may automatically receive the updated information at predetermined intervals, which may be very short (e.g., less than one second).

[0185] At 810, the central entity updates the value of the token. This updated value may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communication equipment 304, or any combination thereof. This updated value may be calculated using the method 600 or 700 and may result in the token valuation 612, or the exchange rate 714 or 718. The updated token value may be calculated to effect token issuance, redemption, exchange, or any combination thereof. The updated token value may also be calculated to establish reserve requirements and / or reserve percentages. The updated token value may depend on multiple instruments, underlying assets, asset mix, or financial information thereof. Upon receiving the updated information 808, the central entity may automatically update the calculated token value 806 to the updated token value.

[0186] At 812, the central entity provides the value of the tokens to one or more nodes. This process may include providing the value using a transceiver 107, 110, or 113 to a distributed node(s) 103, a blockchain ledger 224, a blockchain 408, or a cryptocurrency exchange 116 or 418. This process may also include providing the value using a processing, storage, networking, and communications device 304 via a token issuance on the public blockchain 310 or a replica of the token issuance on the private blockchain 312. Providing the value of the tokens to one or more nodes may result in or enable the execution of a token issuance, redemption, exchange, or any combination thereof.

[0187] 9 is a flowchart 900 of another process for providing reserves to a tokenization platform according to some embodiments of the present disclosure. At 902, a central entity (i.e., 102, 202, 302, or 402) stores token information, e.g., tokens 208, 238, or 406, or token basket 226. The token information may include multiple unique tokens. The token information may be stored in storage device 109 or 112, token basket 226, processing, storage, networking, and communications device 304, data source(s) 422, or any combination thereof. The token information may include multiple instruments, underlying assets, asset mix, reserve requirements, reserve percentages, or any combination thereof. The token information may be made available to the distributed node(s) 103, the account(s) 114, the token buyers 204, the token account(s) 218, the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, the market exchange(s) 504, or any combination thereof. The information may be available to third parties on a permanent basis or may be made available upon request.

[0188] At 904, the central entity receives a request to issue or redeem at least a portion of the tokens having the token value. The request may be received through a transceiver 107, 110, 113, or any combination thereof, or through the processing, storage, networking, and communication equipment 304 or the exchange system(s) 420. The request may be generated from a distributed node(s) 103, an account(s) 114, a token buyer 204, a token account(s) 218, a blockchain ledger 224, a blockchain 408, a cryptocurrency exchange 418, a marketplace exchange(s) 504, or any combination thereof. Receiving the request may be an aspect of the escrow service 306 or the escrow 412.

[0189] At 906, the central entity determines the payment amount. The determination of the payment amount may be performed using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communication device 304, or any combination thereof. The determination of the payment amount may incorporate the token value, e.g., determined at 806 or 810, e.g., using the method 600 or 700, and may also incorporate the token transaction fee(s) 220. According to the dynamically adjusted token value, the central entity may automatically determine the payment amount in response to receiving the request 904. The payment amount may be categorized with respect to major revenue 212 and minor revenue 214, where the major revenue may correspond to the token(s), e.g., 208, 238, or 406, and the minor revenue may correspond to the transaction fee(s) 220. The payment amount may be stored, e.g., in the storage device 109 or 112, until the payment amount is transferred, e.g., to execute a transaction.

[0190] At 908, the central entity transfers the amount to the account. The transfer of the amount to the account may be performed using the transceiver 110 or 113, or the processing, storage, networking, and communication equipment 304. The account may be the account(s) 114, the token buyer 204, the token account(s) 218, or any combination thereof, or the account information may be integrated with the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, the market exchange(s) 504, or any combination thereof. The transfer of the amount may be performed pursuant to the issuance, redemption, or exchange of the token. The transfer of the amount may be an aspect of the currency transaction(s) 210, the token transaction(s) 216, the escrow service 306, the funds intake conversion and / or reconversion 308, the escrow 412, the account management 414, the exchange system(s) 420, or any combination thereof.

[0191] At 910, the central entity updates the distributed network of nodes. The update may be performed using the transceiver 110 or 113, or the processing, storage, networking, and communications device 304. The distributed network of nodes may be the distributed node(s) 103, the crypto exchange 116, the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, or any combination thereof. The update may include replicating the token issuance on the public blockchain 310 or the token issuance on the private blockchain 312. The distributed network of nodes may be updated to store records of transactions involving tokens, e.g., the token transactions 216, which may be stored using the storage device 106.

[0192] 10 is a flowchart 1000 of a process for processing a token issuance or redemption request according to some embodiments of the present disclosure. At 1002, a central entity (i.e., 102, 202, 302, or 402) receives a request to issue or redeem at least a portion of the tokens. This request may be a request 904. The request may be received through a transceiver 107, 110, 113, or any combination thereof, or through a processing, storage, networking, and communication device 304 or an exchange system(s) 420. The request may be generated from a distributed node(s) 103, an account(s) 114, a token buyer 204, a token account(s) 218, a blockchain ledger 224, a blockchain 408, a cryptocurrency exchange 418, a marketplace exchange(s) 504, or any combination thereof. Receiving the request may be an aspect of the escrow service 306 or the escrow 412.

[0193] At 1004, the central entity calculates a token value. This calculation may be a calculation step 806 or an update step 810. The value may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. The value may be calculated using the method 600 or 700 and may result in a token valuation 612, or an exchange rate 714 or 718. The token value may be calculated to effect issuance, redemption, exchange, or any combination thereof. The token value may be calculated to establish reserve requirements and / or reserve percentages. The token value may depend on multiple instruments, underlying assets, asset mix, and financial information related to multiple instruments, underlying assets, or asset mix.

[0194] At 1006, the central entity determines a request value based on the token value and the quantity of tokens requested. The request value may be equal to the product of the token value and the quantity of tokens requested. The value may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. The value may be calculated using the method 600 or 700 and may result in an exchange rate 714 or 718.

[0195] At 1008, the central entity determines a fee based on the requested value. The fee amount may correspond to the token value, the quantity of tokens requested, the product of the token value and the quantity of tokens requested, or other factors related to the transaction. The fee amount may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. The fee amount may be miner revenue 214 and / or token transaction fee(s) 220. In some embodiments, the fee may be zero. A non-zero fee amount may support the operation of the central entity, for example, as shown at 100, 200, 300, 400, or any combination thereof.

[0196] At 1010, the central entity determines a payment amount based on the request value and the fee amount. The payment amount may be the sum of the request value and the fee amount. The payment amount may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. Determining the payment amount may be a determination step 906.

[0197] 11 is a flowchart 1100 of another process for processing a token issuance or redemption request according to some embodiments of the disclosure. At 1102, a central entity (i.e., 102, 202, 302, or 402) stores token information, e.g., a token 208, 238, or 406, or a token basket 226. Storing the token information may be the storing step 902. The token information may include multiple unique tokens. The token information may be stored in a storage device 109 or 112, a token basket 226, a processing, storage, networking, and communications device 304, a data source(s) 422, or any combination thereof.

[0198] At 1104, the central entity receives a request to issue or redeem at least a portion of the tokens. Receiving the request may be the receiving step 904 or 1002. The request may be received through a transceiver 107, 110, 113, or any combination thereof, or through the processing, storage, networking, and communications equipment 304 or the exchange system(s) 420. The request may be generated from a distributed node(s) 103, an account(s) 114, a token buyer 204, a token account(s) 218, a blockchain ledger 224, a blockchain 408, a cryptocurrency exchange 418, a market exchange(s) 504, or any combination thereof.

[0199] At 1106, the central entity calculates a request value. The calculation may be calculation step 1006. The request value may be equal to the product of the token value and the quantity of tokens requested. The value may be calculated using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. The value may be calculated using method 600 or 700 and may result in an exchange rate 714 or 718.

[0200] At 1108, the central entity determines whether the requested value can be issued or redeemed. The determination may be performed using the processing circuitry 108 or 111 in conjunction with the storage device 109 or 112. The determination may depend on the value of the account(s) 114 and may be performed using the transceiver 110 and the system link 126. The determination may be made taking into account the tokens, funds, or other financial instruments held by the token buyer 204 and the token account(s) 218. The determination may be made in response to a request from the decentralized node(s) 103, the account(s) 114, the token buyer 204, the token account(s) 218, the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, the market exchange(s) 504, or any combination thereof. The determination may result in a determination that the requested value can or cannot be issued or redeemed.

[0201] If the requested value can be issued or redeemed, at 1110, the central entity transfers the value to the account. Transferring the value may be a transferring step 908. The transfer of the amount to the account may be performed using the transceiver 110 or 113, or the processing, storage, networking, and communication equipment 304. The account may be the account(s) 114, the token buyer 204, the token account(s) 218, or any combination thereof, or the account may be integrated with the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, the market exchange(s) 504, or any combination thereof. The transfer of the amount may be performed pursuant to the issuance or redemption of the token. The transfer of the amount may be an aspect of the currency transaction(s) 210, the token transaction(s) 216, the escrow service 306, the funds intake conversion and / or reconversion 308, the escrow 412, the account management 414, the exchange system(s) 420, or any combination thereof.

[0202] At 1112, the central entity updates the distributed network of nodes. The update may be an update step 910. The update may be performed using the transceiver 110 or 113, or the processing, storage, networking, and communications equipment 304. The distributed network of nodes may be the distributed node(s) 103, the crypto exchange 116, the blockchain ledger 224, the blockchain 408, the cryptocurrency exchange 418, or any combination thereof. The update may include replicating token issuances or redemptions on the public blockchain 310 or token issuances or redemptions on the private blockchain 312. The distributed network of nodes may be updated to store records of transactions involving tokens, e.g., token transactions 216, which may be stored using the storage equipment 106.

[0203] FIG. 12 is a flowchart 1200 of a process for determining the ability to fulfill a token issuance request according to some embodiments of the present disclosure. At 1202, a central entity (i.e., 102, 202, 302, or 402) stores a token value and account information. The token information may be the stored information of step 902 or step 1102. The token information may include multiple unique tokens. The token information may be stored in a storage device 109 or 112, a token basket 226, a processing, storage, networking, and communication device 304, a data source(s) 422, or any combination thereof. The account information may be an account(s) 114, a token buyer 204, a token account(s) 218, or any combination thereof, or the account may be integrated with a blockchain ledger 224, a blockchain 408, a cryptocurrency exchange 418, a market exchange(s) 504, or any combination thereof. The account information may be stored in the storage device 109 or 112, the storage, networking, and communications device 304, the data source(s) 422, or any combination thereof.

[0204] At 1204, the central entity receives a request by an account to issue at least a portion of the tokens. Receiving the request may be the receiving step 904, 1002, or 1104. The request may be received through a transceiver 107, 110, 113, or any combination thereof, or through the processing, storage, networking, and communications equipment 304 or the exchange system(s) 420. The request may be generated from a distributed node(s) 103, an account(s) 114, a token buyer 204, a token account(s) 218, a blockchain ledger 224, a blockchain 408, a cryptocurrency exchange 418, a market exchange(s) 504, or any combination thereof.

[0205] At 1206, the central entity determines a payment amount based on the request. The determination may be determination step 906. The payment amount determination may be performed using the processing circuitry 108 or 111, the pricing engine 222, the processing, storage, networking, and communications equipment 304, or any combination thereof. The payment amount determination may incorporate the token value, e.g., as determined in step 806 or 810, e.g., using method 600 or 700, and may also incorporate the token transaction fee(s) 220.

[0206] At 1208, the central entity compares the payment amount to the account value. The comparison may be step 1208. The comparison may be performed using the processing circuitry 108 or 111 in conjunction with the storage device 109 or 112. The comparison may depend on the token and the account value.

[0207] At 1210, the central entity determines that the issuance request is feasible if the account value is greater than or equal to the payment amount. The determination may be a decision step 1210. The payment amount may or may not include transaction fee(s) 220. The determination may be performed using processing circuitry 108 or 111 in conjunction with storage device 109 or 112.

[0208] FIG. 13 is a flowchart 1300 of a process for redemption of a fragment token, according to some embodiments of the present disclosure. At 1302, a central entity (i.e., 102, 202, 302, or 402) stores token value and fragmented token count information. At 1304, the central entity receives a request by an account to redeem a fragment of a token. At 1306, the central entity adds the fragment value to the fragmented token count. In some embodiments, this fragmented token count may be stored in the storage device 106, 109, or 112, the blockchain ledger 224, the processing, storage, network, and communication device 304, or the blockchain 408. At 1308, the central entity decreases the fragmented token count by one after the fragmented token count reaches a full token. In some embodiments, the central entity increases the associated token count by one. At 1310, the central entity updates the distributed network of nodes (e.g., the distributed node(s) 103, the blockchain ledger 224, or the blockchain 408).

[0209] The following examples, in accordance with the foregoing drawings and several embodiments of the present disclosure, illustrate aspects of the present disclosure.

[0210] The following examples are illustrative of an escrow service 306, escrow 412, or similar functionality performed by at least one central entity 102, 202, 302, or 402, possibly in coordination with at least one third party stakeholder. The examples assume the use of relational database tables to maintain the information required for the three unique tokens. The table tbl_TokenConfiguration has one entry for each unique token. Each entry in the table must contain, at a minimum, the indicated fields, creating a relationship for the indicated unique token reference. 1. Find the current asset mix of the unique token using the key AssetMixID in tbl_AssetMixDetails, and 2. ReserveTerms to get the current reserve requirement for a unique token using the key AssetMixID [Table 1]

[0211] The ReserveTermsID value corresponds to a file containing requirements and restrictions on any reserves that may be held as collateral for the issuance of unique tokens. These values ​​contain the reserve requirements and will be dynamically communicated to reserve holders (e.g., central entities and / or third party stakeholders).

[0212] The table tbl_AssetType contains a unique record for each type of asset (USD, EUR, GOLD, etc.) that may be used in the system. An asset type must exist in the table before it can be included in the asset mix of any unique token. Once added, an asset type cannot be removed from this table. The same exact list of asset types can apply to more than one unique token. [Table 2]

[0213] The following examples are illustrative of the design, maintenance, and control of the token account(s) 218, the token basket 226, the basket of instruments 316, the tokens 406, or similar functions performed by at least one central entity 102, 202, 302, or 402. These examples assume the use of relational database tables to maintain the information required for the underlying assets, asset pairs, and exchange pairs.

[0214] The table tbl_AssetMixDetail contains details about all asset types, and the number of units of all such asset types, associated with a unique token. [Table 3]

[0215] The asset mix of each unique token can be determined by combining the data from the three tables above and filtering the results on the asset mix ID associated with the unique token. [Table 4]

[0216] In some embodiments, the following table and chart show the process for an illustrative unique token called Numi: Numi (TokenID3) is associated with AssetMixID101, resulting in the asset mix shown below: [Table 5]

[0217] Data from tbl_AssetType can be used to generate asset pairs. [Table 6]

[0218] Asset pairs can be used to create exchange pairs. [Table 7]

[0219] The following examples are illustrative of account(s) 114 (e.g., crypto exchange 116, foreign exchange exchange 118, or commodity exchange 120), data source(s) 422, or similar systems linked to at least one central entity 102, 202, 302, or 402. These examples use relational database tables to maintain the information required for the underlying assets.

[0220] The table tbl_ExchangeMarkets contains information about the global exchange of assets in tbl_AssetType. Additional data about market hours is stored using Greenwich Mean Time (GMT). [Table 8]

[0221] The feed from each market exchange that is open at any given time is paired with asset pairs where the underlying asset and the nominal asset are not the same. For example, at 1PM GMT, the German and Tokyo market exchanges are open. The pricing engine 222 establishes real-time trading prices for all exchange pairs from these two exchanges. [Table 9]

[0222] The data is then smoothed to represent the best market exchange rate and a general record is added for all assets where the base asset and the nominal asset are equal at an exchange rate of one. [Table 10]

[0223] The following illustrates an exchange rate calculation method, for example as described in methods 600 or 700. The exchange rate to value ratio of any unique asset type in the asset mix expressed in the nominal units of another unique asset type in the same asset mix can be calculated using the data above by (1) pricing the nominal quoted assets in the asset mix in the nominal units of the base asset, and (2) dividing 1.000 by the total cost determined in (1) above.

[0224] For example, pricing a token in Euros would use the feed data from the middle row of the previous table. [Table 11]

[0225] In some embodiments, the system allows for unlimited divisibility. In some embodiments, the central entity may limit redemptions to certain fractions, such as because some of the assets in the basket are only divisible by certain decimals. The system may receive a desired quantity for conversion and return both the converted amount and the remainder.

[0226] In some embodiments, the system is a ledger-based system for distributing, redeeming, and reissuing tokens that represent fragmented ownership of tangible and intangible assets held by a central entity. In some embodiments, the central entity can use a computer-implemented model to act as a depository for the assets and generate and distribute tokens that represent the depository's partial interest in the assets. In some embodiments, the computer-implemented method performed by the central entity can direct corresponding activities performed by third-party stakeholders.

[0227] In some embodiments, the system maintains information about an asset and all associated tokens that represent an accounting of all (outstanding) fractional interests in the asset.

[0228] In some embodiments, tokens may represent various ownership interests in the same underlying asset and may further (1) be subdivided by a central entity into two or more tokens representing distributions of the divided token interests; or (2) two or more tokens of the same asset may be consolidated into a single token representing the sum of the combined tokens.

[0229] In some embodiments, the system embodies the ability for a central entity to redeem outstanding tokens in whole or in part in exchange for deposited assets unencumbered by the outstanding tokens, such redemptions being calculated using computer-aided pricing data representing the market value of the fractional interest represented by the tokens.

[0230] In some embodiments, each unique token may be associated with one or more third-party stakeholders that act as authorized depository parties responsible for holding reserve requirement assets that collateralize the unique token. A relational database for such a configuration may include at least two data structures associated with authorized depository parties (e.g., financial institutions) and the underlying token basket (e.g., as provided by a central entity), respectively. In some embodiments, the database is implemented as a blockchain ledger, which may be public or private. In some embodiments, the database and / or the blockchain ledger further includes transaction and reference numbers (e.g., for the depository parties to verify information about the asset mix via the central entity). For example, contemporaneous with the token issuance, the depository parties may be financial institutions defined within the ledger and responsible for facilitating the token issuance by issuing tokens to customers, purchasing collateral assets that meet reserve requirements, maintaining transaction and reference numbers, etc.

[0231] In some embodiments, a third-party stakeholder (e.g., acting as an authorized escrow party) may be a reserve depositing party, a unique token depositing party, a different escrow party, or any combination thereof. In some embodiments, a reserve depositing party may hold reserve assets. In some embodiments, a unique token depositing party may hold one or more types of unique tokens on behalf of an owner. In some embodiments, a reserve depositing party holds one or more sets of reserves corresponding to each reserve requirement for each unique token held by the reserve depositing party. In some embodiments, a reserve depositing party holds one or more sets of reserves corresponding to one or more unique tokens owned by a single unique token holder.

[0232] In some embodiments, a token holder may request that a quantity of tokens be transferred from a first depository party to a second depository party. In some embodiments, in response to the transfer, the first ledger may be updated to decrease the quantity of tokens for the token holder with the first depository party, and the second ledger may be updated to increase the quantity of tokens for the token holder with the second depository party. In some embodiments, a single ledger indicates that the quantity of tokens for the token holder has been transferred from the first depository party to the second depository party.

[0233] In some embodiments, the central authority may transfer a quantity of tokens from a first depository party to a second depository party, which may be done at the direction of the central entity, such as in response to the first depository party losing authorization. In some embodiments, the central authority may update its internal records to reflect a change in the depository of the unique tokens, such as in response to the depositor indicating an increase or decrease in the ability to operate in a deposited capacity.

[0234] The following is an exemplary discussion of how multiple third-party stakeholders may coordinate with a central entity to trade and hold multiple unique tokens and the underlying reserve requirement. In this example, each third-party stakeholder (e.g., a financial institution), including token holders, may freely trade the unique tokens bidirectionally. In response to each transaction, one or more internal ledgers (e.g., ledgers hosted by the central entity and / or each third-party stakeholder) may be updated to store a record of the transaction or a transaction request log. At some particular periodic frequency (e.g., daily), the one or more internal ledgers may be adjusted (i.e., any outstanding debits / credits are adjusted) so that the central entity and / or each respective third-party stakeholder holds an appropriate amount of each unique token. In response to each internal ledger being adjusted, each responsible party (e.g., each respective third-party stakeholder, including the central entity and / or authorized depositary parties) of each internal ledger may buy, sell, or otherwise guarantee the holding of reserve assets, satisfying the net reserve requirement across all unique tokens held by the responsible party.

[0235] In some embodiments, an iterative optimization algorithm is applied to efficiently reconcile the data at some regular frequency. For example, a central authority can map all escrow parties according to their outstanding debits / credits, with the relative position on the map corresponding to the amount of the debit or credit. The central authority can then run an iterative algorithm (e.g., greedy algorithm, stochastic gradient descent algorithm, evolutionary algorithm, brute force algorithm) that converges all escrow debits or credits to zero (i.e., reconcile all ledgers and direct all reconciliation payments).

[0236] In some embodiments, authorized depository parties send and complete transaction requests with other authorized depository parties. The sending and completing of requests may occur automatically in response to a request by a token holder. In some embodiments, at least one of the sending or receiving depository parties confirms proper execution of the transaction with the central entity, and one or more internal ledgers at the central entity are immediately updated by the central entity.

[0237] In the following examples, data structures and systems for transferring tokens are provided. In response to a request to transfer a token, a central entity generates a request identification and records it on the blockchain. In some embodiments, the central entity records the request identification and corresponding transaction using the InterPlanetary File System (IPFS) or a similar data sharing protocol. In some embodiments, the data stored by the central entity is hashed, such as for cryptographic digital verification, and the central entity associates the hashed data with one or more batch transactions. To inspect the value of a previous request or transaction, the central entity can use the request identification to find the corresponding batch transaction and then return the associated hashed data.

[0238] It will be understood that capitalized and / or defined terms contained in this disclosure may be applicable to some embodiments. In some embodiments, the capitalized and / or defined terms may take on different meanings.

Claims

1. 1. A computer-implemented method executed by a central entity for coordinating data exchanges between entities on a decentralized network of nodes, the nodes persistently storing transaction data based on values ​​of tokens associated with the decentralized network, the central entity coupled to the decentralized network, the method comprising: storing respective quantities of a plurality of items in a storage device at said central entity; receiving information about the plurality of products from a plurality of servers via one or more data communication channels; calculating, using a processing circuit, a value of the token based on the information and the respective quantities of the plurality of commodities; receiving updated information regarding the plurality of products from the plurality of servers via the one or more data communication channels; updating the value of the token based on the updated information using a processing circuit; providing the value of the token to one or more nodes of the decentralized network for use in a transaction.

2. The method of claim 1 , wherein storing the quantities for the items of the plurality of items comprises storing a quantity of zero for each item of the plurality of items.

3. The method of claim 1 , wherein the central entity comprises at least one node of the distributed network of nodes.

4. 2. The method of claim 1, wherein the plurality of instruments comprises at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

5. The method of claim 1 , wherein the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

6. The method of claim 1 , further comprising determining the quantity for the plurality of items.

7. 10. The method of claim 1, further comprising monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements of the tokens are met.

8. The method of claim 1 , wherein the receiving of the information includes receiving the information from sources in different time zones, and the calculating is further based on the different time zones.

9. The method of claim 1 , wherein the value of the token is specific to each of the plurality of commodities.

10. The method of claim 1 , wherein the central entity creates multiple instances of multiple products.

11. The method of claim 1 , wherein one or more tokens are associated with the plurality of products.

12. 2. The method of claim 1 , wherein the updated information received for a plurality of instruments causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

13. The method of claim 1 , wherein the central entity is located in at least one of a private or public decentralized network of nodes.

14. 2. The method of claim 1 , wherein the tokens are of a first type, the method further comprising exchanging other tokens of a second type for the first type tokens based on an associated exchange rate.

15. The method of claim 1 , wherein the tokens are redeemable for the plurality of goods.

16. 10. The method of claim 1, wherein the tokens are redeemable for an equivalent value in units of a single commodity that may or may not be within the plurality of commodities.

17. 2. The method of claim 1, wherein in response to providing the value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, the central entity allocates reserve assets collateralizing the tokens.

18. 1. A system for coordinating data exchanges between entities on a decentralized network of nodes, the nodes persistently storing transaction data based on a value of a token associated with the decentralized network, the system being coupled to the decentralized network, the system comprising: a storage device for storing respective quantities of a plurality of products; a transceiver for receiving information about the plurality of products from a plurality of servers via one or more data communication channels; and a processing circuit for calculating a value of the token based on the respective quantities and the information of the plurality of commodities; The transceiver further receives updated information regarding the plurality of products from the plurality of servers via the one or more data communication channels, and the processing circuitry further comprises: and for updating the value of the token based on the updated information and providing the value of the token to one or more nodes of the decentralized network for use in transactions.

19. 20. The system of claim 18, wherein the processing circuitry is further used to determine a quantity for one of the plurality of items, including determining a quantity of zero for the item.

20. 20. The system of claim 18, wherein the system includes at least one node of the distributed network of nodes.

21. 20. The system of claim 18, wherein the plurality of instruments comprises at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

22. The system of claim 18 , wherein the information includes a market value associated with at least one of the plurality of instruments.

23. 20. The system of claim 18, wherein the processing circuitry is further adapted to determine the quantities for the plurality of items.

24. 20. The system of claim 18, wherein the processing circuitry is further used to monitor multiple underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

25. 20. The system of claim 18, wherein the instruments are associated with different time periods, and the processing circuitry is used to calculate the value of the token based on the different time periods.

26. 20. The system of claim 18, wherein the value of the token is specific to each of the plurality of commodities.

27. 20. The system of claim 18, wherein the distributed network of nodes stores multiple instances of multiple products.

28. 20. The system of claim 18, wherein one or more tokens are associated with the plurality of items.

29. 20. The system of claim 18, wherein the processing circuitry causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

30. 20. The system of claim 18, wherein the distributed network of nodes is located in at least one of a private or a public distributed network of nodes.

31. 20. The system of claim 18, wherein the tokens are of a first type, the system further comprising exchanging other tokens of a second type for the first type tokens based on an associated exchange rate.

32. 20. The system of claim 18, wherein the tokens are redeemable for the plurality of goods.

33. 20. The system of claim 18, wherein the tokens are redeemable for an equivalent value in units of a single commodity that may or may not be within the plurality of commodities.

34. 20. The system of claim 18, wherein in response to providing the value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, the central entity allocates reserve assets collateralizing the tokens.

35. 1. A non-transitory computer readable medium having instructions programmed to execute a method for coordinating data exchanges between entities on a decentralized network of nodes, the nodes persistently storing transaction data based on values ​​of tokens associated with the decentralized network, a central entity coupled to the decentralized network, the method comprising: storing respective quantities of a plurality of products; receiving information about the plurality of products from a plurality of servers via one or more data communication channels; calculating the value of the token based on the respective quantities and the information of the plurality of commodities; receiving updated information regarding the plurality of products from the plurality of servers via the one or more data communication channels; updating the value of the token based on the updated information; and and providing the value of the token to one or more nodes of the decentralized network for use in a transaction.

36. 36. The non-transitory computer readable medium of claim 35, wherein determining a quantity for one of the plurality of items comprises determining a quantity of zero for the item.

37. 36. The non-transitory computer-readable medium of claim 35, wherein the central entity comprises at least one node of the distributed network of nodes.

38. 36. The non-transitory computer-readable medium of claim 35, wherein the plurality of instruments comprises at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

39. 36. The non-transitory computer-readable medium of claim 35, wherein the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

40. 36. The non-transitory computer readable medium of claim 35, further comprising determining the quantity for the plurality of items.

41. 36. The non-transitory computer-readable medium of claim 35, further comprising monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

42. 36. The non-transitory computer-readable medium of claim 35, wherein the receiving of the information includes receiving the information from sources in different time zones, and the calculating is further based on the different time zones.

43. 36. The non-transitory computer-readable medium of claim 35, wherein the value of the token is specific to each of the plurality of commodities.

44. 36. The non-transitory computer-readable medium of claim 35, wherein the distributed network of nodes stores multiple instances of multiple commodities.

45. 36. The non-transitory computer-readable medium of claim 35, wherein one or more tokens are associated with the plurality of goods.

46. 36. The non-transitory computer-readable medium of claim 35, wherein the updated information received for a plurality of instruments causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

47. 36. The non-transitory computer-readable medium of claim 35, wherein the distributed network of nodes is located in at least one of a private or a public distributed network of nodes.

48. 36. The non-transitory computer-readable medium of claim 35, wherein the tokens are of a first type, the medium further comprising exchanging other tokens of a second type for the first type tokens based on an associated exchange rate.

49. 36. The non-transitory computer-readable medium of claim 35, wherein the tokens are redeemable for the plurality of goods.

50. 36. The non-transitory computer-readable medium of claim 35, wherein the token is redeemable for an equivalent value in units of a single commodity that may or may not be within the plurality of commodities.

51. 36. The non-transitory computer-readable medium of claim 35, wherein in response to providing the value for the token, a buyer purchases rights to the token via the decentralized network, and in response to the rights to the token being purchased, the central entity allocates reserve assets collateralizing the token.

52. 1. A computer-implemented method executed by a central entity on a decentralized network of nodes, the nodes persistently storing transaction data based on token values ​​associated with the decentralized network, the central entity coupled to the decentralized network, the method comprising: receiving, by the central entity, a request associated with an account to issue or redeem at least a portion of tokens having a token value, the token value being based on a plurality of instruments and respective quantities; determining a payment amount based on the token value; causing processing circuitry at the central entity to transfer the payment amount to the account; and updating the distributed network of nodes based on the payment.

53. when said at least a portion of said token comprises a fragment of said token, adding a value indicative of said fragment to a fragmented token count; After the fragmented token count reaches a full token, and decreasing the count by one.

53. The method of claim 52, wherein updating the distributed network of nodes comprises updating the distributed network of nodes to store information indicating a token has been issued or redeemed.

54. 53. The method of claim 52, wherein said causing the transfer of said payment amount to said account includes causing the transfer of at least one of said plurality of items amounting to said payment amount.

55. 53. The method of claim 52, wherein the quantities for the items of the plurality of items include a quantity of zero for each item of the plurality of items.

56. 53. The method of claim 52, wherein the central entity comprises at least one node of the distributed network of nodes.

57. 53. The method of claim 52, wherein the plurality of instruments comprises at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

58. 53. The method of claim 52, wherein the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

59. 53. The method of claim 52, further comprising determining the quantity for the plurality of items.

60. 53. The method of claim 52, further comprising monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

61. 53. The method of claim 52, wherein the receiving of the information includes receiving the information from a source at a different time period, and the calculating is further based on the different time periods.

62. 53. The method of claim 52, wherein the value of the token is specific to each of the plurality of commodities.

63. 53. The method of claim 52, wherein the central entity creates multiple instances of multiple products.

64. 53. The method of claim 52, wherein one or more tokens are associated with the plurality of items.

65. 53. The method of claim 52, wherein the updated information received for a plurality of instruments causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

66. 53. The method of claim 52, wherein the central entity is located in at least one of a private or public decentralized network of nodes.

67. 53. The method of claim 52, wherein the tokens are redeemable for the plurality of goods.

68. 53. The method of claim 52, wherein the tokens are redeemable for the equivalent value of a single item which may or may not be within the plurality of items.

69. 53. The method of claim 52, wherein in response to providing the value for the tokens, a buyer purchases interests in the tokens via the decentralized network, and in response to the interests in the tokens being purchased, the central entity allocates reserve assets collateralizing the tokens.

70. A system coupled to a decentralized network of nodes, the nodes persistently storing transaction data based on token values ​​associated with the decentralized network, the system comprising: a transceiver for receiving a request associated with an account to issue or redeem at least a portion of the tokens having the token value, the token value being based on a number of commodities and respective quantities; and a processing circuit, the processing circuit comprising: determining a payment amount based on the token value; transferring said payment amount to said account; and updating the distributed network of nodes based on the payment.

71. The processing circuitry includes: when said at least a portion of said token comprises a fragment of said token, adding a value indicative of said fragment to a fragmented token count; After the fragmented token count reaches a full token, Decrementing the count by one; 71. The system of claim 70, further configured to update the distributed network of nodes to store information indicating a token has been issued or redeemed.

72. 71. The system of claim 70, wherein the processing circuitry is further configured to cause a transfer of at least one of the plurality of items amounting to the payment amount.

73. 71. The system of claim 70, wherein the quantities for the items of the plurality of items include a quantity of zero for each item of the plurality of items.

74. 71. The system of claim 70, wherein the system includes at least one node of the distributed network of nodes.

75. 71. The system of claim 70, wherein the plurality of instruments includes at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

76. 71. The system of claim 70, wherein the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

77. 71. The system of claim 70, further comprising determining the quantity for the plurality of items.

78. 71. The system of claim 70, further comprising monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

79. 71. The system of claim 70, wherein the transceiver is further used to receive information including information from sources in different time periods, and the processing circuitry is further used to perform calculations based on the different time periods.

80. 71. The system of claim 70, wherein the value of the token is specific to each of the plurality of commodities.

81. 71. The system of claim 70, wherein the system creates multiple instances of multiple products.

82. 71. The system of claim 70, wherein one or more tokens are associated with the plurality of items.

83. 71. The system of claim 70, wherein the updated information received for a plurality of instruments causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

84. 71. The system of claim 70, wherein the system is located in at least one of a private or public decentralized network of nodes.

85. 71. The system of claim 70, wherein the tokens are redeemable for the plurality of goods.

86. 71. The system of claim 70, wherein the tokens are redeemable for an equivalent value of a single item which may or may not be within the plurality of items.

87. 71. The system of claim 70, wherein in response to determining a payment amount, a buyer purchases rights to the tokens via the decentralized network, and in response to the rights to the tokens being purchased, the central entity allocates reserve assets collateralizing the tokens.

88. A non-transitory computer readable medium having instructions stored thereon that, when executed, perform a method by a central entity on a decentralized network of nodes, the nodes persistently storing transaction data based on a token value associated with the decentralized network, the central entity coupled to the decentralized network, the method comprising: receiving, by the central entity, a request associated with an account to issue or redeem at least a portion of tokens having a token value, the token value being based on a plurality of instruments and respective quantities; determining a payment amount based on the token value; transferring said payment amount to said account; and updating the distributed network of nodes based on the payment.

89. The method comprises: when said at least a portion of said token comprises a fragment of said token, adding a value indicative of said fragment to a fragmented token count; After the fragmented token count reaches a full token, and decreasing the count by one.

90. The non-transitory computer-readable medium of claim 88, wherein updating the distributed network of nodes includes updating the distributed network of nodes to store information indicating a token has been issued or redeemed.

90. 90. The non-transitory computer-readable medium of claim 88, wherein causing the transfer of the payment amount to the account includes causing the transfer of at least one of the plurality of items amounting to the payment amount.

91. 90. The non-transitory computer-readable medium of claim 88, wherein storing the quantities for the items of the plurality of items includes storing a quantity of zero for each item of the plurality of items.

92. 90. The non-transitory computer-readable medium of claim 88, wherein the central entity comprises at least one node of the distributed network of nodes.

93. 90. The non-transitory computer-readable medium of claim 88, wherein the plurality of instruments comprises at least two of currencies, commodities, securities, tangible assets, asset-backed cryptocurrencies, or any combination thereof.

94. 90. The non-transitory computer-readable medium of claim 88, wherein the information regarding the plurality of instruments includes a market value associated with at least one of the plurality of instruments.

95. 90. The non-transitory computer readable medium of claim 88, further comprising determining the quantity for the plurality of items.

96. 90. The non-transitory computer-readable medium of claim 88, further comprising monitoring a plurality of underlying assets collateralizing the tokens with respect to ensuring reserve requirements for the tokens are met.

97. 90. The non-transitory computer-readable medium of claim 88, wherein the information associated with the token value includes information from sources in different time periods, and the calculating is further based on the different time periods.

98. 90. The non-transitory computer-readable medium of claim 88, wherein the value of the token is specific to each of the plurality of commodities.

99. 90. The non-transitory computer-readable medium of claim 88, wherein the central entity creates multiple instances of multiple goods.

100. 90. The non-transitory computer-readable medium of claim 88, wherein one or more tokens are associated with the plurality of goods.

101. 90. The non-transitory computer-readable medium of claim 88, wherein the updated information received for a plurality of instruments causes a change in the respective quantities of the plurality of instruments and causes an automatic change in the reserve assets collateralizing the tokens in response to the change in the respective quantities of the plurality of instruments.

102. 90. The non-transitory computer-readable medium of claim 88, wherein the central entity is located in at least one of a private or public decentralized network of nodes.

103. 90. The non-transitory computer-readable medium of claim 88, wherein the tokens are redeemable for the plurality of goods.

104. 90. The non-transitory computer-readable medium of claim 88, wherein the token is redeemable for an equivalent value in units of a single commodity that may or may not be within the plurality of commodities.

105. 90. The non-transitory computer-readable medium of claim 88, wherein in response to determining the payment amount, a buyer purchases rights to the tokens via the decentralized network, and in response to the rights to the tokens being purchased, the central entity allocates reserve assets collateralizing the tokens.

Images