Real-time interaction using digital tokens

Abstract

A method for providing an interactive recording network is disclosed. A plurality of separate local networks may be connected over a central network. The digital token may be used to perform a transfer from the first local network across the central network to the second local network. The digital token may be redeemed, and the digital token may be validated using a counter value.

Description

[0001] Cross-referencing related applications

[0002] none Background Technology

[0003] There are numerous networks and applications used for recording information. For example, there are multiple systems and networks designed to record patient medical information, such as various hospital-specific networks and insurance provider-specific networks. Similarly, there are multiple different networks used to manage voter registration data (e.g., at different local, state, and national levels). Additional networks exist for recording information about the transfer of assets and data. For example, there are various networks used for transferring access credentials, event tickets, property rights, currency, game points, tokens, mobile phone minutes, digital media, etc. In the case of event tickets, if someone wants to transfer an event ticket to a friend, they can choose from several ticket transfer networks and applications.

[0004] Unifying and simplifying networks for recording various types of information can be beneficial. For example, combining all networks used for transferring mobile phone call time, currency, etc., into a single global network simplifies the transfer process. Participants can have only one application configured for said network. Furthermore, this simplifies record keeping, as this single network can track the location of all mobile phone call time.

[0005] However, unified record networks may present new challenges. For example, coordinating all new records and / or transfers can be a massive task, potentially overwhelming a single network coordinator.

[0006] The embodiments of the present invention address these and other problems individually and collectively. Summary of the Invention

[0007] Embodiments of the present invention provide systems and methods for enabling different networks to interact. In some embodiments, multiple independent local networks may be established, rather than providing a single global network. Each local network may be configured to interact with a central network. For example, a central authority of a local network may also act as a participating node in the central network, thereby relaying information between the local and central networks in real time. If each local network interacts with the central network, the different local networks can be indirectly connected to each other through the central network. This allows for real-time value transfer between participants in different local networks.

[0008] Additionally, the embodiments provide a digital token that can serve as an intermediate value between local values. A first local network can transfer values ​​using a first exchange medium (e.g., a first type of currency), a second local network can transfer values ​​using a second exchange medium (e.g., a second type of currency), and a central network can transfer values ​​using a digital token that can represent and / or be exchanged for both the first and second exchange mediums. The digital token can also be monitored and verified based on counter values ​​and recorded previous usage of the digital token. Furthermore, the digital token can be destroyed after being exchanged for a token value in a local exchange medium.

[0009] One embodiment of the present invention relates to a method. The method includes a first node computer, operated by a first entity, transferring a first value of an exchange medium to a first central authority computer. The first central authority computer then sends a message to a network processing computer, notifying the network processing computer of the transfer of the first value. The method further includes receiving a digital token from the network processing computer, the digital token including a digital token identifier, an owner identifier identifying the first entity, a counter value, a token value, and a first digital signature. The method further includes updating the digital token by incrementing the counter value, changing the owner to a second entity, and adding a second digital signature from the first node computer to transfer the digital token to a second node computer operated by the second entity. The method also includes broadcasting the updated digital token to nodes in a blockchain network. The blockchain network includes the first node computer, the second node computer, the first central authority computer, and the network processing computer. The nodes record the updated digital token in their respective blockchains.

[0010] Another embodiment of the present invention relates to a first node computer configured to perform the above-described methods.

[0011] Another embodiment of the present invention relates to a method. The method includes receiving, by a network processing computer, a message regarding the transfer of a first value of an exchange medium from a first node computer operated by a first entity to a first central authority computer. The method further includes transferring a digital token to the first node computer, the digital token including a digital token identifier, an owner identifier identifying the first entity, a counter value, a token value, and a first digital signature. The first node computer updates the digital token to transfer it to a second node computer operated by the second entity by incrementing the counter value, changing the owner to a second entity, and adding a second digital signature of the first node computer. The method also includes receiving a broadcast message including the updated digital token, and updating a blockchain stored in the network processing computer with the updated digital token. The network processing computer is in a blockchain network that includes the first node computer, the second node computer, the first central authority computer, and the network processing computer.

[0012] Another embodiment of the present invention relates to a network processing computer configured to perform the above-described methods.

[0013] More detailed information about embodiments of the present invention can be found in the detailed description and accompanying drawings. Attached Figure Description

[0014] Figure 1 A block diagram of a system according to an embodiment of the present invention is shown.

[0015] Figure 2 A block diagram of a network processing computer according to an embodiment of the present invention is shown.

[0016] Figure 3 A block diagram of a first node computer according to an embodiment of the present invention is shown.

[0017] Figure 4 An example of a node in a network according to an embodiment of the present invention is shown.

[0018] Figure 5 A diagram showing a portion of a blockchain according to an embodiment of the present invention.

[0019] Figure 6 A block diagram illustrating the data fields of a digital token according to some embodiments is shown.

[0020] Figure 7 A flowchart illustrating a method for issuing digital tokens according to an embodiment of the present invention is shown.

[0021] Figure 8 A flowchart illustrating a method for transferring digital tokens according to an embodiment of the present invention is shown.

[0022] Figure 9 A flowchart illustrating a method for exchanging or redeeming digital tokens according to an embodiment of the present invention is shown.

[0023] Figure 10 A flowchart illustrating a method for handling failed digital token verification according to an embodiment of the present invention is shown. Detailed Implementation

[0024] Embodiments of the present invention provide systems and methods for hierarchical and interactive recording networks. In some embodiments, multiple local networks and a central network may be established. The central network and each local network may operate independently and may maintain their own distinct sets of records. Local networks may interact with each other through the central network.

[0025] For example, the central authority of a local network can also act as a participant (e.g., a node) within the central network. Thus, each local network coordinator can communicate with the central network. Local networks can be indirectly connected through the central network. Therefore, individual local networks can maintain privacy and allow for the customization of local rules and procedures while establishing global-level connectivity.

[0026] Additionally, the embodiments provide a digital token that can be used as an intermediate value between local values. A first local network can transfer values ​​using a first exchange medium, a second local network can transfer values ​​using a second exchange medium, and a central network can transfer values ​​using a digital token, which can represent and / or be replaced by both the first and second exchange media.

[0027] According to an embodiment, within a central network, digital tokens can be monitored and verified based on counter values ​​and / or recorded previous usage, thereby providing a secure mechanism for value transfers across the network. Digital tokens can be transferred multiple times to multiple different owners, and the counter value can be incremented each time a transfer and / or ownership change occurs.

[0028] Furthermore, the digital token can be exchanged for token value on a local exchange medium. At that point, the digital token can be destroyed and removed from circulation. Thus, the central network provides a secure, temporary, exchangeable, and disposable medium for cross-network exchange.

[0029] Before discussing specific embodiments of the present invention, some terms may be described in detail.

[0030] "Interaction" can include mutual action or influence. "Interaction" can include communication, contact, or exchange between parties, devices, and / or entities. Exemplary interactions include transactions between two parties and data exchange between two devices. In some embodiments, interaction can include a user requesting access to secure data, secure web pages, secure locations, etc. In other embodiments, interaction can include payment transactions, in which two devices can interact to facilitate payment. Interaction can be the transfer of resources from a first entity to a second entity.

[0031] "Value" can include amounts, assets, or sets of information that have value. For example, value can include monetary amounts, access permissions, or login credentials. Ownership of value can change from a first owner to a second owner. Examples of value transfers include payment transactions that transfer currency (e.g., physical or digital currency), point transfers that transfer game credits or mobile phone minutes, and property transfers that transfer event tickets or property deeds.

[0032] "Exchange medium" can include intermediary tools used to facilitate interaction. For example, exchange mediums can include physical currency, digital currency, cryptocurrency, tokens, points, or credits. Different types of exchange mediums can be used in different situations, regions, or environments. For example, different fiat currencies can be used in different countries.

[0033] A "digital token" can be a digital substitute value or a digital representation value. A digital token can be a string of numbers, letters, other suitable characters, or information existing in binary format. In some embodiments, a digital token may include information about a value that can be transferred during interaction.

[0034] The term "node" can refer to a connection point. In some embodiments, a node can be a physical electronic device capable of creating, receiving, or sending data. In other embodiments, a node can be a software module on a computing device that is a connection point in a communication network. In some embodiments, a node can be a computing device within a record-keeping network. A node is capable of creating records, verifying records, and / or performing any other suitable functions. Different types of nodes are capable of performing different sets of functions within a record-keeping network. In some embodiments, a node may be associated with and / or operated by a financial institution computer (e.g., a bank), a payment processor computer, a third-party computer, or any other suitable entity.

[0035] A “record” can refer to evidence of one or more interactions, changes, or events. A digital record can be an electronic document of an interaction, change, or event. A record can include a record identifier and record information. For example, record information can include information describing one or more interactions and / or information associated with the interaction (e.g., a digital signature). An example of a record is a block in a blockchain. A single block can be a single record, and a blockchain can be a series of records. A blockchain header is an example of a record identifier, and a blockchain body is an example of record information.

[0036] A "blockchain" can be a distributed database that maintains a constantly growing list of records to prevent tampering and revision. A blockchain can be a digital token blockchain, a central bank digital currency blockchain, or a combination thereof. A blockchain can include multiple blocks of interaction records. Each block in a blockchain can also include a timestamp and a link to the previous block. In other words, interaction records in a blockchain can be stored as a series of "blocks" or a persistent file containing records of multiple interactions that occurred within a given time period. Blocks can be appended to the blockchain by appropriate nodes after they create a block and the block is verified. Each block can be associated with a block header. In embodiments of the invention, the blockchain can be distributed, and a copy of the blockchain can be maintained at each full node in the verification network. Any node within the verification network can then use the blockchain to verify interactions. The blockchain can be stored, maintained, and updated in a distributed manner within a peer-to-peer network. For example, in cryptocurrency applications such as Bitcoin or Ethereum, Ripple, Dash, Litecoin, Dogecoin, Zcash, Tether, Bitcoin Cash, Cardano, Stellar, EOS, NEO, NEM, BitShares, Dexcoin, Augur, Komodo, PIVX, Poloniex, Slim, Monero, Golem, Stratis, Bytecoin, Adorcoin, or in digital currency exchanges such as Coinbase, Kraken, CEX.IO, Shapeshift, Poloniex, Bitstamp, Coinmama, Bisq, LocalBitcoins, Gemini, etc., where a distributed ledger represents each transaction and where units of cryptocurrency are transferred between entities.

[0037] A “blockchain network” can include a computer network that maintains a blockchain.

[0038] A "block header" can be a header that includes information about a block in a blockchain. A block header can be used to identify a specific block on the blockchain. A block header can include any suitable information, such as the previous hash, Merkle root, timestamp, and temporary number. In some embodiments, the block header may also include a difficulty value.

[0039] A "key pair" may include a pair of associated encryption keys. For example, a key pair may include a public key and a corresponding private key. In a key pair, the first key (e.g., the public key) can be used to encrypt a message, while the second key (e.g., the private key) can be used to decrypt the encrypted message. Additionally, the public key may be able to verify digital signatures created using the corresponding private key. The public key may be distributed throughout the network to allow verification of messages signed using the corresponding private key. The public and private keys can be in any suitable format, including formats based on RSA or elliptic curve cryptography (ECC). In some embodiments, asymmetric key pairing algorithms may be used to generate the key pair. However, as those skilled in the art will understand, other means may also be used to generate key pairs.

[0040] The term "digital signature" can refer to an electronic signature of a message. A digital signature can be a digital data value, an alphanumeric data value, or any other type of data, including graphical representations. A digital signature can be a unique data value generated from a message and a private key using a cryptographic algorithm. In some embodiments, a verification algorithm using a public key can be used to verify the signature.

[0041] A “network processing computer” may include a server computer for interactive processing. In some embodiments, the network processing computer may be coupled to a database and may include any hardware, software, other logic, or combinations thereof for serving requests from one or more client computers. The network processing computer may include one or more computing devices and may use any of a variety of computing architectures, arrangements, and compilations to serve requests from one or more client computers. In some embodiments, the network processing computer may include a data processing subsystem, network, and operations for supporting and delivering authorization services, exception file services, and clearing and settlement services. Exemplary network processing computers may include… .include The network can process credit card transactions, debit card transactions, and other types of business transactions. Specifically, this includes the integrated payment system (IPS) that processes authorization requests and the services that perform clearing and settlement. The system. A network-processing computer can use any suitable wired or wireless network, including the Internet.

[0042] The network processing computer can process interaction-related messages (e.g., authorization request messages and authorization response messages) and determine the appropriate destination computer (e.g., the issuing computer) for the interaction-related messages. In some embodiments, the network processing computer can authorize the interaction on behalf of the issuing computer. The network processing computer can also process and / or facilitate the clearing and settlement of the interaction.

[0043] The term "verification" and its derivatives can include the process of using information to determine whether an underlying subject is valid under a given set of conditions. Verification can include any comparison of information to ensure that certain data or information is correct, valid, accurate, legitimate, and / or credible.

[0044] "User" can include an individual. In some embodiments, a user can be associated with one or more personal accounts and / or mobile devices. In some embodiments, a user can also be referred to as a cardholder, account holder, or consumer.

[0045] A “processor” can include means for performing a task. In some embodiments, a processor can include any suitable one or more data computing means. A processor can include one or more microprocessors that work together to perform a desired function. A processor can include a CPU that includes at least one high-speed data processor sufficient to execute program components for performing user and / or system-generated requests. A CPU can be a microprocessor, such as AMD’s Athlon, Duron, and / or Opteron; IBM and / or Motorola’s PowerPC; IBM and Sony’s Cell processors; Intel’s Celeron, Itanium, Pentium, Xeon, and / or XScale; and / or similar processors.

[0046] "Memory" can be any suitable device or devices capable of storing electronic data. Suitable memory can include non-transitory computer-readable media whose storage can be executed by a processor to implement desired methods. Examples of memory can include one or more memory chips, disk drives, etc. Such memory can be operated using any suitable electrical, optical, and / or magnetic modes of operation.

[0047] A "server computer" can include a powerful computer or cluster of computers. For example, a server computer can be a mainframe, a small cluster of computers, or a group of servers that work like cells. In one example, a server computer can be a database server coupled to a web server. A server computer can be coupled to a database and can include any hardware, software, other logic, or a combination of the foregoing for servicing requests from one or more client computers.

[0048] Figure 1A system 100 comprising multiple components is illustrated. System 100 includes a blockchain network 110 comprising multiple network nodes. Network nodes may include a first node computer 161, a second node computer 162, a third node computer 163, a fourth node computer 164, a first central computer 151, a second central computer 152, and / or a network processing computer 120. In some embodiments, blockchain network 110 may be a central network acting as an intermediary between two or more additional local blockchain networks. For example, some nodes in the central blockchain network 110 (e.g., the first central computer 151 and / or the second central computer 152) may also be associated with and / or operate separate local blockchain networks (e.g., a first local blockchain network 111 and a second local blockchain network 112). Such nodes may utilize the central blockchain network 110 to transfer information from the first local blockchain network 111 to the second local blockchain network 112.

[0049] All computers shown in System 100 can communicate operationally with each other via any suitable communication channel or communication network. A suitable communication network can be any one and / or a combination of the following: direct interconnection; the Internet; a local area network (LAN); a metropolitan area network (MAN); an Operational Mission as a node on the Internet (OMNI); a secure custom connection; a wide area network (WAN); a wireless network (e.g., using protocols such as, but not limited to, Wireless Application Protocol (WAP), I-mode, etc.).

[0050] Secure communication protocols, such as, but not limited to, File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), and ISO (e.g., ISO 8583), can be used to send messages between computers, networks, and devices.

[0051] System 100 can be used to process, approve, and record any suitable type of information. For example, System 100 can be used to record information about new or updated digital tokens, transactions, projects and activities, medical patient data, academic achievements, etc. System 100 can be configured to create and maintain any suitable type of record. For example, one or more digital tokens and / or transactions can be recorded in blocks on a blockchain.

[0052] Some or all network nodes can create new block records and / or verify new block records received from other network nodes. Network nodes can collectively build and maintain a public blockchain record. According to an embodiment, some or all network nodes can maintain a local copy of the blockchain.

[0053] Each network node may be associated with and / or operated by a corresponding entity. For example, the first node computer 161 may be operated by a first entity. The first entity may be a financial institution, hospital, government agency, academic institution, mobile phone service provider, or any other suitable service provider. The first entity may operate the first node computer 161 to maintain one or more accounts on behalf of one or more users. The accounts may store identification information, medical records, academic records, financial information, or any other suitable details, depending on the type of service provider. The first entity may be associated with a first country, a first region, a first currency, and / or a first central authority, and / or located within a first country, a first region, a first currency, and / or a first central authority.

[0054] In an embodiment where the first node computer 161 is operated by a first financial institution, the first node computer 161 may store values ​​on behalf of a user. The first node computer 161 may also be able to transfer values ​​on behalf of a user (e.g., provide payments). An example of a financial institution is an issuer, which can generally refer to a corporate entity (e.g., a bank) that issues and maintains accounts (e.g., bank accounts) for users.

[0055] In some embodiments, the first node computer 161 may represent multiple associated computers. For example, the functionality described above for network participation and the functionality associated with banking services can be divided among several collaborating computers.

[0056] Similar to the first node computer 161, the second node computer 162 may be associated with a second entity. The second entity may be a service provider, such as a bank. Therefore, the second node computer 162 may host a second user account and may store, send, and / or receive values ​​on behalf of the second user. As an example, the second node computer 162 may be associated with an acquirer, which is typically a business entity (e.g., a commercial bank) that has a business relationship with a specific resource provider or other entity. Some entities may perform the functions of both an issuer and an acquirer. Some embodiments may cover such a single entity as an issuer-acquirer. The second entity may be associated with a second country, a second region, a second currency, and / or a second central authority, and / or be located within a second country, a second region, a second currency, and / or a second central authority.

[0057] Users can be individuals, businesses, organizational record update administrators, or any other suitable type of user. For example, the first user can be an individual, and the second user can be a resource provider (e.g., a merchant) participating in the transaction, and can sell goods or services or provide access to goods or services.

[0058] The first central institution node computer 151 may be operated by a first central institution. For example, the first central institution may be a first central bank. A central bank may be associated with a specific country, region, and / or currency type. A central bank may manage, issue, and / or otherwise control one or more types of exchange media, such as physical money and / or digital currency. For example, the first central bank (e.g., via the first central institution node computer 151 or a separate computer) may issue, manage, and / or otherwise control a first fiat currency (e.g., physical US dollars). The first central bank (e.g., via the first central institution node computer 151 or a separate computer) may also issue, manage, and / or otherwise control a first type of central bank digital currency (CBDC), such as a digital US dollar. The first type of CBDC may be referred to as CBDC-A.

[0059] A CBDC (Central Bank Digital Currency) can be a digital liability of a government's central bank. A CBDC can be a digital form of central bank money. "Central bank money" can refer to the currency for which a central bank is a liability. In the United States, there are currently two types of central bank money: physical money issued by the Federal Reserve and digital balances held by commercial banks at the Federal Reserve. Using CBDCs, central bank computers can issue and record ownership and transactions of CBDCs on a local blockchain network.

[0060] In some embodiments, in addition to participating in blockchain network 110 (which may be referred to as a central blockchain network, intermediate blockchain network, or main blockchain network), a first central authority may also (e.g., via a first central authority node computer 151) operate and / or manage a first local blockchain network 111. For example, the first local blockchain network 111 may be used to store records regarding the generation, transfer, and ownership of CBDC-A.

[0061] The second central institution node computer 152 may be operated by a second central institution. For example, the second central institution may be a second central bank. The second central bank may (e.g., via the second central institution node computer 152 or a separate computer) issue, manage, and / or otherwise control a second legal tender (e.g., a physical euro). The second central bank (e.g., via the second central institution node computer 152 or a separate computer) may also issue, manage, and / or otherwise control a second type of CBDC (e.g., a digital euro), which may be referred to as CBDC-B.

[0062] In some embodiments, in addition to participating in the central blockchain network 110, the second central authority may also (e.g., via a second central authority node computer 152) operate and / or manage a second local blockchain network 112. For example, the second local blockchain network 112 may be used to store records regarding the generation, transfer, and ownership of CBDC-B.

[0063] As mentioned above, in some embodiments, blockchain network 110 may act as an intermediary between two or more additional local blockchain networks. For example, a first central computer 151 and / or a second central computer 152 may use the central blockchain network 110 to forward information between a first local blockchain network 111 and a second local blockchain network 112.

[0064] Network processing computer 120 may be operated by a central network processor or administrator. Network processing computer 120 may act as a node for creating and / or verifying new blocks on the blockchain. Additionally, network processing computer 120 may track transactions from beginning to end and provide communication updates to participating entities and nodes. For example, the blockchain may primarily be used to record new digital tokens, changes to digital tokens, and transfers of digital tokens. However, a complete transaction may involve steps and communications beyond digital tokens, such as the issuance and transfer of CBDC. Therefore, according to some embodiments, separate from the blockchain, network processing computer 120 may maintain additional records and / or accounts regarding transactions. For example, network processing computer 120 may provide interaction identifiers for transactions, monitor and track each step involved in a transaction, notify one or more entities when relevant transfer steps are completed, maintain and update escrow accounts for transactions, and / or otherwise coordinate transaction activities.

[0065] Figure 2 A block diagram of a network processing computer 120 according to an embodiment is shown. The exemplary network processing computer 120 may include a processor 120A. The processor 120A may be coupled to a memory 120C, a network interface 120B, and a computer-readable medium 120E. The computer-readable medium 120E may include a token issuance module 120M, an authentication module 120J, and a record update module 120K.

[0066] Memory 120C can be used to store data and code. For example, memory 120C may store one or more public keys associated with one or more nodes, private keys associated with network processing computer 120A, one or more digital tokens, one or more blockchain records, one or more escrow account records, etc. Memory 120C may be coupled internally or externally to processor 120A (e.g., a cloud-based data storage device) and may include any combination of volatile and / or non-volatile memory such as RAM, DRAM, ROM, flash memory, or any other suitable memory device.

[0067] Computer-readable medium 120E may include a token issuance module 120M, a verification module 120J, a record update module 120K, and any other suitable software modules. Computer-readable medium 120E may also include code executable by processor 120A to implement a method comprising: receiving a message regarding the transfer of a first value of an exchange medium from a first node computer operated by a first entity to a first central authority computer; transferring a digital token to the first node computer, the digital token including a digital token identifier, an owner identifier identifying the first entity, a counter value, a token value, and a first digital signature, wherein the first node computer updates the digital token by incrementing the counter value, changing the owner to a second entity, and adding a second digital signature of the first node computer to transfer the digital token to a second node computer operated by a second entity; receiving a broadcast message including the updated digital token; and updating a blockchain stored in a network processing computer with the updated digital token, wherein the network processing computer is in a blockchain network including the first node computer, the second node computer, the first central authority computer, and the network processing computer.

[0068] The token issuance module 120M may include code that causes the processor 120A to issue digital tokens. For example, the token issuance module 120M may contain logic that causes the processor 120A to generate a digital token having one or more data fields, which may include a token identifier, an owner identifier, a counter value, an interaction identifier, a currency amount, a currency denomination, and / or a digital signature.

[0069] Verification module 120J may include code that enables processor 120A to verify digital tokens and / or blockchain blocks. For example, verification module 120J may contain logic that enables processor 120A to check whether a record of the received digital token exists in the blockchain and / or whether the received digital token includes the expected counter value. Additionally, verification module 120J may contain logic that enables processor 120A to verify a new block received from another network node.

[0070] The verification module 120J may also include code that enables the processor 120A to verify the authenticity of one or more digital signatures. For example, the verification module 120J may contain logic that enables the processor 120A to use the public key of the node computer to verify the authenticity of a digital signature associated with the node computer.

[0071] The record update module 120K may include code that causes the processor 120A to maintain and update a set of records. For example, the record update module 120K may contain logic that causes the processor 120A to record information about a new or updated digital token. In some embodiments, the record update module 120K may include instructions for generating a new blockchain block that includes the new or updated digital token.

[0072] Network interface 120B may include an interface that allows network processing computer 120 to communicate with external computers. Network interface 120B enables network processing computer 120 to transmit data to and from another device (e.g., first node computer 161, second node computer 162, etc.). Some examples of network interface 120B may include a modem, a physical network interface (e.g., an Ethernet card or other network interface card (NIC)), a virtual network interface, a communication port, a PCMCIA 120B and card, etc. Wireless protocols supported by network interface 120B may include Wi-Fi™. Data relayed via network interface 120B may be in the form of signals, which may be electrical signals, electromagnetic signals, optical signals, or any other signals that can be received by an external communication interface (collectively, "electronic signals" or "electronic messages"). These electronic messages, which may include data or instructions, may be provided between network interface 120B and other devices via a communication path or channel. As mentioned above, any suitable communication path or channel can be used, such as wires or cables, optical fibers, telephone lines, cellular links, radio frequency (RF) links, WAN or LAN networks, the Internet, or any other suitable medium.

[0073] Figure 3 A block diagram of a first node computer 161 according to an embodiment is shown. In some embodiments, the first node computer 161 may include an HSM (Hardware Security Module). An exemplary first node computer 161 may include a processor 161A. The processor 161A may be coupled to a memory 161C, a network interface 161B, and a computer-readable medium 161E. The computer-readable medium 161E may include a token transfer module 161M, an authentication module 161J, and a record update module 161K. Some or all of the components, modules, and / or functions described with respect to the first node computer 161 may also be applicable to other network nodes, such as a second node computer 162, a third node computer 163, a fourth node computer 164, a first central authority computer 151, and / or a second central authority computer 152.

[0074] Memory 161C can be used to store data and code. For example, memory 161C can store one or more public keys associated with one or more nodes, a private key associated with the first node computer 161A, one or more digital tokens, one or more blockchain records, etc. Memory 161C can be coupled internally or externally to processor 161A (e.g., a cloud-based data storage device) and can include any combination of volatile and / or non-volatile memory such as RAM, DRAM, ROM, flash memory, or any other suitable memory device.

[0075] The computer-readable medium 161E may include a token transfer module 161M, a verification module 161J, a record update module 161K, and any other suitable software modules. The computer-readable medium 161E may also include code executable by a processor 161A to implement a method comprising: transferring a first value of an exchange medium to a first central authority computer, the first central authority computer sending a message to a network processing computer notifying the network processing computer of the transfer of the first value; receiving a digital token from the network processing computer, the digital token including a digital token identifier, an owner identifier identifying a first entity, a counter value, a token value, and a first digital signature; updating the digital token by incrementing the counter value, changing the owner to a second entity, and adding a second digital signature of the first node computer to transfer the digital token to a second node computer operated by the second entity; and broadcasting the updated digital token to nodes in a blockchain network including the first node computer, the second node computer, the first central authority computer, and the network processing computer, wherein the nodes record the updated digital token to their respective blockchains.

[0076] The token transfer module 161M may include code that causes the processor 161A to transfer digital tokens. For example, the token transfer module 161M may contain logic that causes the processor 161A to obtain digital tokens, update digital tokens (e.g., counter values ​​and owner identifiers) for transactions, and broadcast the updated digital tokens and / or blockchain updates that include the updated digital tokens.

[0077] Verification module 161J may include code that enables processor 161A to verify digital tokens and / or blockchain blocks. For example, verification module 161J may contain logic that enables processor 161A to check whether a record of the received digital token exists in the blockchain and / or whether the received digital token includes the expected counter value. Additionally, verification module 161J may contain logic that enables processor 161A to verify new blocks received from another network node.

[0078] The verification module 161J may also include code that enables the processor 161A to verify the authenticity of one or more digital signatures. For example, the verification module 161J may contain logic that enables the processor 161A to use the public key of the node computer to verify the authenticity of a digital signature associated with the node computer.

[0079] The record update module 161K may include code that causes the processor 161A to maintain and update a set of records. For example, the record update module 161K may contain logic that causes the processor 161A to record information about new or updated digital tokens. In some embodiments, the record update module 161K may include instructions for generating new blocks for the blockchain.

[0080] Network interface 161B may include an interface that allows first node computer 161 to communicate with external computers. Network interface 161B enables first node computer 161 to transmit data to and from another device (e.g., network processing computer 161, second node computer 162, etc.). Some examples of network interface 161B may include a modem, a physical network interface (e.g., an Ethernet card or other network interface card (NIC)), a virtual network interface, a communication port, a PCMCIA 161B and card, etc. Wireless protocols supported by network interface 161B may include Wi-Fi™. Data relayed via network interface 161B may be in the form of signals, which may be electrical signals, electromagnetic signals, optical signals, or any other signals that can be received by an external communication interface (collectively, "electronic signals" or "electronic messages"). These electronic messages, which may include data or instructions, may be provided between network interface 161B and other devices via a communication path or channel. As mentioned above, any suitable communication path or channel can be used, such as wires or cables, optical fibers, telephone lines, cellular links, radio frequency (RF) links, WAN or LAN networks, the Internet, or any other suitable medium.

[0081] In some embodiments, system 100 may include different types of network nodes. Figure 4 An example of a node in a network according to an embodiment of the present invention is shown. As shown, the blockchain network 410 may include a plurality of network nodes, including validator node computers 431-437, edge node computers 441-444, and network processing computer 420.

[0082] Validator nodes and edge nodes can have different roles and perform different sets of functions within the blockchain network 410. For example, validator node computers 431-437 can verify new records on the network (e.g., blocks, digital tokens, and / or transactions). Maintaining network integrity in this way utilizes computational resources and can therefore typically be performed by a larger entity with more available infrastructure (e.g., a central bank, a larger bank). Figure 1 The first central computer 151 and / or the second central computer 152 can be used as validator nodes in the blockchain network 110.

[0083] Edge node computers 441-444 can create and / or submit new records (e.g., blocks, digital tokens, and / or transactions) to the network. However, in some embodiments, edge nodes may not verify new records and may therefore rely on validator nodes for storing and maintaining the blockchain. Edge nodes can typically be operated by smaller entities, such as small banks or regional banks. Figure 1 The first node computer 161, the second node computer 162, the third node computer 163 and / or the fourth node computer 164 can act as edge nodes in the blockchain network 110.

[0084] Figure 5 A block diagram illustrating a blockchain according to an embodiment is shown. Blockchain 500 may include a list of token blocks, which are cryptographically linked together, such as... Figure 5 As shown in the diagram. Blocks are created through a computationally intensive process called Proof-of-Work, where valid blocks need to demonstrate sufficient "difficulty" (e.g., enough computing power to create them on average). In some embodiments, a blockchain may utilize a Proof-of-Stake process instead of a Proof-of-Work process. If more than one blockchain exists, network participants (e.g., nodes) need to download all blocks from all chains and follow the chain with the highest overall difficulty. This mechanism guarantees that the network will eventually reach consensus on a single, valid chain.

[0085] Figure 5 An example blockchain format is shown. However, it should be understood that other formats and data structures can be used. Blockchain 500 may include multiple blocks, such as block 502A and block 502B. Each block may include a block header; for example, block 502A includes block header 504.

[0086] The block header 504 may include multiple data elements, such as the previous block hash 506 and the Merkle root 508. The previous block hash 506 may be a hash of the header of the previous block. The Merkle root 508 may be the root of a Merkle tree, a tree in which each leaf node is labeled with a hash of a data block, such as digital tokens 510, 512, and 514. Each leaf of the Merkle tree may represent one of the digital tokens 510, 512, and 514.

[0087] Figure 6 A block diagram of a digital token according to some embodiments is shown. Figure 6 An example digital token 600 and the data it includes are shown. The digital token 600 includes a token identifier 601, an owner identifier 602, a counter value 603, an interaction identifier 604, a token value 605, a currency denomination (currency and value) 606, and a digital signature 607.

[0088] The digital token 600 may be identified by a token identifier 601. The token identifier 601 may be an alphanumeric value unique to a digital token. In some embodiments, the token identifier 601 is a GUID (Globally Unique Identifier). In some embodiments, the token identifier 601 is a static value indicating the validity period of the digital token.

[0089] Ownership of the digital token 600 can be managed through a token identifier 601 and an owner identifier 602. In some embodiments, the owner identifier may be a specific alphanumeric value unique to the owner. In some embodiments, the owner identifier 602 is a GUID (Globally Unique Identifier). In some embodiments, the owner identifier may be a public address (e.g., a public key) associated with the owning entity. When the digital token 600 is transferred to a new entity, the owner identifier 602 may be updated to indicate that entity. The private key corresponding to the public key can be used as proof of ownership of the digital token 600. A digital signature created from the private key corresponding to the public key to which the digital token 600 is assigned can serve as proof that the entity providing the signature owns the digital token 600.

[0090] A counter value is used to track the number of times the digital token 600 has been transferred, owned, or otherwise utilized. The counter value can initially be set to 1 or a random value. The counter value increments by one with each transfer of the digital token 600. For example, on the first transfer of the digital token 600, the counter value can increase from value 1 to value 2, and on the second transfer, the counter value can increase from value 2 to value 3. Each change in the counter value is recorded in the blockchain. Therefore, the counter value in the received digital token 600 can be compared with the expected counter value indicated in the blockchain, and this comparison can be used to confirm that the digital token 600 is valid and not fraudulent or counterfeit.

[0091] The interaction identifier 604, which can be an alphanumeric value or a globally unique identifier (GUID), identifies the current transaction. Each time the digital token 600 is transferred, the transfer can be associated with the unique interaction identifier. The interaction identifier 604 can be updated or changed for each subsequent transaction.

[0092] According to an embodiment, the interaction identifier 604, counter value 603, and / or owner identifier 602 can all be updated simultaneously for a new transaction. Each time a data field of the digital token 600 is updated or changed, the changing entity (e.g., the current owner of the digital token 600) can provide a digital signature 607 (e.g., generated based on a private key and some or all of the data from the digital token 600) to prove the change. The current digital signature 607 and / or one or more previous digital signatures can be included as data fields in the digital token 600.

[0093] Digital token 600 may represent a commitment to transfer value or a value to be transferred. Therefore, a token value 605 data field may be included in digital token 600. In some embodiments, token value 605 may take the form of currency. The token value 605 data field may represent a monetary amount (e.g., 100, 1000, 10000, 100000, 1000000). Furthermore, digital token 600 may include a currency denomination 606 data field (e.g., US dollars, CBDC-A, CBDC-B, etc.). Token value 605 and / or currency denomination 606 may indicate a specific serial number, coin number, CBDC identifier, or other identifier for a specific value.

[0094] Issuing digital tokens

[0095] For reference Figure 7 A method 700 for issuing digital tokens according to an embodiment of the present invention is described. Reference is also made to some elements in other accompanying drawings. In embodiments of the invention, the steps shown in method 700 may be performed sequentially or in any suitable order. In some embodiments, one or more of the steps may be optional.

[0096] The various messages described below can be used with any suitable form of communication. In some embodiments, requests or responses may be in electronic message formats, such as email, Short Message Service (SMS) messages, Multimedia Messaging Service (MMS) messages, Hypertext Transfer Protocol (HTTP) request messages, Transmission Control Protocol (TCP) packets, or web form submissions. Requests or responses may point to any suitable location, such as an email address, telephone number, Internet Protocol (IP) address, or Uniform Resource Locator (URL). In some embodiments, requests or responses may include a mixture of different message types, such as email messages and SMS messages.

[0097] A first user may wish to transfer value to a second user for interaction. The first user may have a first user account provided by a first entity (e.g., a first bank in a first country), and the second user may have a second user account provided by a second entity (e.g., a second bank in a second country). The first entity may operate a first node computer 161 participating in the network, and the second entity may operate a second node computer 162 participating in the network. The first node computer 161 may initiate a process for transferring value via the network. First, the first node computer 161 may obtain a digital token, which can then be used to transfer value to the second node computer 162.

[0098] In step S701, the first node computer 161 transfers the first value of the first exchange medium to the first central authority computer 151, which may be operated by the first central bank in the first country or region. For example, the first node computer 161 may send a message to the first central authority computer 151 requesting the exchange of the first value of the first fiat currency for CBDC-A.

[0099] In step S702, the first central authority computer 151 may generate and / or issue a first amount of CBDC-A to the first node computer 161. For example, the first central authority computer 151 may reduce the first value of the first exchange medium (e.g., the first fiat currency) in a first entity current account at a first central bank, and the first central authority computer 151 may generate and / or assign a corresponding value of CBDC-A to the first node computer 161. CBDC-A may include an indicator indicating that the owner is the first node computer 161, an indication of the first amount, and any other suitable information. Thus, the first node computer 161 may exchange the first fiat currency for CBDC-A, which is more easily transferred than the first fiat currency. In some embodiments, instead of using a current account, the first node computer 161 may electronically transfer the first value of the first exchange medium to the first central authority computer 151 via, for example, an Automated Clearing House (ACH) transfer.

[0100] In some embodiments, a first local blockchain network (e.g., Figure 1 The first local blockchain in the first local blockchain network (111) records the generation and / or ownership of CBDC-A.

[0101] In step S703, the first central computer 151 may send a message to the network processing computer 120 to notify the network processing computer of the transfer of the first value and / or CBDC-A assigned to the first node computer 161.

[0102] In step S704, network processing computer 120 updates the network ledger or record to indicate that the first amount of CBDC-A is assigned to first node computer 161 (or first entity). At this time, value custody may be considered because the first exchange medium (e.g., fiat currency) is no longer owned by first node computer 161, and CBDC-A is ready for real-time transfer.

[0103] In some embodiments, the blockchain may be used primarily or solely for recording digital tokens. The network processing computer 120 may maintain separate ledgers or records for the escrowed interactions and transfer status. These separate records may be referred to as escrow accounts. In other embodiments, instead of maintaining separate records, the central blockchain may be updated with information about some or all of the transfer steps of the interaction.

[0104] The network processing computer 120 can manage, coordinate, or follow the interaction from start to finish, and can check whether each iterative step of the transfer has been executed, ensuring the interaction is completed. The network processing computer 120 can track progress through updates to the escrow account. If the first value remains in escrow (e.g., in the form of an issued CBDC-A), a token representing the first value can now be issued.

[0105] In step S705, the first node computer 161 sends a request for a digital token to the network processing computer 120, which can then be used to transfer a value to the second node computer. The token request may include information about a CBDC-A owned by the first node computer 161, and the requested digital token may represent the CBDC-A.

[0106] In step S706, network processing computer 120 issues a digital token and sends it to first node computer 161. The digital token may include a token identifier, a token value, an owner identifier indicating that the first node computer 161 possesses the digital token, a counter value, a first digital signature generated by network processing computer 120, and / or any other suitable information. The token value may indicate a first amount of CBDC-A. In some embodiments, the token value may be less than the first amount of CBDC-A to account for transaction fees and / or exchange fees, for example.

[0107] In step S707, the network processing computer 120 may update the blockchain ledger to include the digital token. For example, the network processing computer 120 generates a new block for the blockchain, which includes a copy of the digital token or information about the digital token.

[0108] In steps S708A-C, network processing computer 120 may broadcast information about the digital token and / or the updated blockchain to other nodes in the blockchain network, which may include first node computer 161, first central authority computer 151, second node computer 162, and / or any other suitable entity. Thus, the network may be notified about the digital token held by first node computer 161, and that the digital token represents a first amount of CBDC-A.

[0109] In steps S709A-C, one or more of the first node computer 161, the first central computer 151, the second node computer 162, and / or any other suitable network participants may verify the new block received from the network processing computer 120 and update the corresponding copy of the blockchain to include the new block.

[0110] Transfer digital token

[0111] A method 800 for transferring tokens according to an embodiment of the present invention may be referred to. Figure 8 The description is as follows. Reference is also made to some elements in the other accompanying drawings. In embodiments of the invention, the steps shown in method 800 may be performed sequentially or in any suitable order. In some embodiments, one or more of the steps may be optional.

[0112] As explained above, a first user may wish to transfer value to a second user for interaction. The first user may have a first user account provided by a first entity (e.g., a first bank in a first country), and the second user may have a second user account provided by a second entity (e.g., a second bank in a second country). The first entity can operate a first node computer 161 participating in the network, and the second entity can operate a second node computer 162 participating in the network. The first node computer 161 can initiate a process for transferring value via the network. First, the first node computer 161 can obtain a digital token, which can then be used to transfer the value to the second node computer 162.

[0113] Following method 700 described above, the first node computer 161 can continue the interaction process by transferring digital tokens.

[0114] In step S801, the first node computer 161 may request an interaction identifier from the network processing computer 120. The request may include any suitable information about the expected transaction, such as the value sent, the sender (e.g., the first user, the first entity, and / or the first node computer 161), the receiver (e.g., the second user, the second entity, and / or the second node computer 162), the token identifier, whether the transaction is a cross-network transaction and / or a cross-border transaction, etc.

[0115] In step S802A, the network processing computer 120 generates and / or provides an interaction identifier to the first node computer 161. Additionally, in step S802B, the network processing computer 120 may send the interaction identifier to the second node computer 162, thereby notifying the second node computer 162 that an interaction has been initiated.

[0116] In step S803, the first node computer 161 may update the digital token in preparation for transferring the digital token to the second node computer 162 operated by the second entity. For example, the first node computer 161 may increment a counter value, change the owner identifier to indicate that the second node computer 162 now owns the digital token, add an interaction identifier to the digital token, and / or add a second digital signature generated by the first node computer 161.

[0117] In step S804, the first node computer 161 may record the updated digital token to a local copy of the blockchain. For example, the first node computer 161 may generate a new block for the blockchain, wherein the new block includes the digital token update and / or a complete copy of the digital token.

[0118] In steps S805A-D, the first node computer 161 may broadcast information about the updated digital token and / or the updated blockchain to other nodes in the blockchain network, which may include the network processing computer 120, the first central authority computer 151, the second node computer 162, the second central authority computer 152, and / or any other suitable network participants. Thus, ownership of the changed digital token can be communicated to the network.

[0119] In steps S806A-D, other nodes in the blockchain network, including network processing computer 120, first central computer 151, second node computer 162, and / or any other suitable network participants, may record the updated digital token to the corresponding blockchain of said node. For example, each node may verify a new block received from the first node computer 161 and update its local copy of the blockchain to include the new block.

[0120] According to some embodiments, when ownership of the digital token changes, this can trigger a transfer of the token value, which can be indicated by the digital token but is stored separately from the digital token. For example, when the token value is a first amount of CBDC-A, a transfer of the digital token to another entity (e.g., to a second node computer 162) can trigger a transfer of the CBDC-A identified in the digital token to the same entity (e.g., to the second node computer 162) or to a suitable intermediary entity (e.g., a second central authority computer 152).

[0121] Therefore, in step S807, in response to the broadcast update regarding the digital token in step S805C, the first central authority computer 151 can transfer ownership of the first amount of CBDC-A from the first node computer 161 to the second central authority computer 152. In some embodiments, the transfer of CBDC-A can be recorded in the first local blockchain of the first local blockchain network.

[0122] Ownership of the CBDC-A can change to the second central computer 152 instead of the second node computer 162, because the second node computer 162 may be located in a second country and / or belong to a second local network. The second central computer 152 can manage the second local network and is able to provide a second switching medium for the second network. Therefore, interaction values ​​can first be transferred to the second central computer 152, which can then be able to provide the interaction values ​​to the second node computer 162 in different desired forms, as further discussed below.

[0123] In step S808, the network processing computer 120 updates the escrow account to indicate that the first amount of CBDC-A has been transferred from the first node computer 161 to the second central agency computer 152.

[0124] At step S809, the network processing computer 120 notifies the first central agency computer 151 that the ownership of CBDC-A has been marked as transferred in the escrow account.

[0125] In step S810, the network processing computer 120 notifies the second central agency computer 152 that it now possesses CBDC-A.

[0126] In step S811, after receiving ownership of the first amount of CBDC-A, the second central agency computer 152 may generate and / or allocate a second amount of CBDC-B to the second node computer 162. The second amount of CBDC-B may have a value equal to or less than the first amount of CBDC-A (e.g., due to transaction fees and / or exchange fees). CBDC-B may include an indicator indicating that the owner is the second node computer 162, an indication of the second amount, and any other suitable information.

[0127] In some embodiments, a second local blockchain network (e.g., Figure 1 The generation and / or ownership of CBDC-B are recorded in the second local blockchain (112) of the second local blockchain network. CBDC-B can be a second digital currency of a second country or region. Therefore, the generation of CBDC-B can represent a cross-border transfer step.

[0128] In step S812, the second central computer 152 notifies the network processing computer 120 that the second amount of CBDC-B has been assigned to the second node computer 162.

[0129] In step S813, the network processing computer 120 updates the escrow account to indicate that the second amount of CBDC-B has been assigned to the second node computer 162.

[0130] In step S814, the network processing computer 120 notifies the second central agency computer 152 that CBDC-B has been marked in the escrow account and assigned to the second node computer 162.

[0131] In step S815, network processing computer 120 notifies second node computer 162 that it possesses a second amount of CBDC-B. Therefore, even if the second entity has not yet received the value in the form of the second fiat currency, second node computer 162 can now at least possess the interactive value in its local form.

[0132] In step S816, the network processing computer 120 notifies the first node computer 161 that the second amount of CBDC-B has been assigned to the second node computer 162, which effectively indicates the settlement or completion of the value transfer from the first node computer 161 to the second node computer 162.

[0133] Therefore, the second node computer 162 may have received a value transfer in the form of a digital token and / or a second monetary amount of CBDC-B. The second node computer 162 is capable of utilizing this value in one or more ways. For example, as described below... Figure 10 As discussed, the second-node computer 162 can exchange digital tokens and / or CBDC-B for fiat currency.

[0134] Alternatively, the second node computer 162 may retain the digital token and / or CBDC-B as a payment instrument for future interactions, since the digital token can be reusable. When needed, the second node computer 162 may provide the reusable digital token and / or CBDC-B to the third node computer 163 (or any other suitable node) during a second transaction between the second node computer 162 and the third node computer 163.

[0135] Some or all of the methods in 800 can be repeated for subsequent interactions. For example, similar to step S801, the second node computer 162 may request a second interaction identifier. Similar to step S803, the second node computer 162 may further update the digital token by incrementing a counter value, changing the owner identifier to indicate that the third node computer 163 now owns the digital token, adding a second interaction identifier and / or removing a previous interaction identifier and / or adding another digital signature generated by the second node computer 162, thereby transferring the digital token to the third node computer 163. Similar to steps S804-S806, the further updated digital token may be recorded to the blockchain. Similar to step S807, CBDC-B may be transferred from the second node computer 162 to the third central authority computer, and similar to step S811, the third central authority computer may generate a third amount of a third type of CBDC (which may be referred to as CBDC-C) and / or assign it to the third node computer 163.

[0136] Exchange digital tokens

[0137] A method 900 for exchanging digital tokens according to an embodiment of the present invention may be referred to. Figure 9 The description is as follows. Reference is also made to some elements in the other accompanying drawings. In embodiments of the invention, the steps shown in method 900 may be performed sequentially or in any suitable order. In some embodiments, one or more of the steps may be optional.

[0138] Following method 800 described above, the second node computer 162 may be the owner of a second amount of digital tokens and / or CBDC-B. The second node computer 162 may then continue to exchange the second amount of digital tokens and / or CBDC-B for a second value in a second exchange medium (e.g., a second fiat currency native to the second entity).

[0139] In step S901, the second node computer 162 may send a request to the network processing computer 120 to exchange the digital token for a second value of the second exchange medium. The exchange request may include a copy of the digital token.

[0140] In step S902, the network processing computer 120 can verify the authenticity of the digital token. For example, the network processing computer 120 can check whether a record of the digital token exists in the blockchain, and / or whether the second node computer 162 is the owner of the digital token based on the blockchain (e.g., based on the owner identifier in the digital token, such as a public key), and / or whether the received digital token includes the expected counter value. Each time the counter value increments, the network processing computer 120 can be notified and / or the blockchain can be updated.

[0141] In step S903, the network processing computer 120 may update the digital token in preparation for exchanging digital tokens. For example, the network processing computer 120 may change the owner identifier to indicate that the network processing computer 120 now owns the digital token, change the token value to zero, mark the digital token for destruction (e.g., by adding a flag or destruction indicator to the digital token), and / or add a third digital signature generated by the network processing computer 120.

[0142] In step S904, the network processing computer 120 may record the updated digital token to a local copy of the blockchain. For example, the network processing computer 120 may generate a new block for the blockchain, wherein the new block includes the digital token update and / or a complete copy of the digital token.

[0143] In steps S905A-B, the network processing computer 120 may broadcast information about the updated digital token and / or the updated blockchain to other nodes in the blockchain network, including the second node computer 162, the second central authority computer 152, the first node computer 161, the first central authority computer 151, and / or any other suitable network participants. Thus, the network is notified of changes to the digital token.

[0144] In steps S906A-B, other nodes in the blockchain network, including one or more of the second node computer 162, the second central authority computer 152, the first node computer 161, the first central authority computer 151, and / or any other suitable network participants, may record the updated digital token to the corresponding blockchain of said node. For example, each node may verify a new block received from the network processing computer 120 and update its local copy of the blockchain to include the new block.

[0145] In step S907, the network processing computer 120 may destroy the digital token. For example, the network processing computer 120 may update the blockchain to indicate that the digital token is no longer valid. This may include repeating steps S904-S906 to provide additional updates to the digital token to indicate that it is no longer working, valid, or available, and further updating the blockchain.

[0146] In step S908, network processing computer 120 notifies second central computer 152 that the digital token has been exchanged and / or destroyed. Therefore, second central computer 152 can be certain that no other party can exchange the digital token after second node computer 162 has exchanged it.

[0147] In step S909, in response to token exchange and / or destruction, the second central computer 152 may transfer ownership of the second amount of CBDC-B from the second node computer 162 to the second central computer 152. Therefore, when the second node computer 162 chooses to receive the token value in the form of a second exchange medium, the second central computer 152 may revoke the second amount of CBDC-B previously belonging to the second node computer 162 (e.g., as mentioned above regarding...). Figure 8 (During step S811 as discussed). In some embodiments, CBDC-B transfers may be recorded in a second local blockchain of a second local blockchain network.

[0148] In step S910, the second central authority computer 152 may provide a second value (e.g., a second amount in fiat currency) in the form of a second exchange medium to the second node computer 162. For example, the second central authority computer 152, which may be operated by a second central bank of a second country or region, may add a second value in the second exchange medium (e.g., a second fiat currency) to a second entity current account of the second central bank. In another example, the second central authority computer 152 may transfer the second value in the second exchange medium electronically from the second central bank to the second entity (e.g., via an automated clearinghouse transfer). In some embodiments, the second value in the form of a second exchange medium may be equivalent to a first value in the form of a first exchange medium. In other embodiments, the second value may be less than the first value due to one or more service fees, currency exchange fees, etc.

[0149] In step S911, the second central computer 152 notifies the second node computer 162 that the second value of the second exchange medium has been provided to the second node computer 162 (e.g., via the current account of the second entity at the second central bank).

[0150] In step S912, the network processing computer 120 may record the final details indicating the completion of the transaction. For example, the network processing computer 120 may record that: CBDC-B is now owned by the second central authority computer 152, the second value of the second exchange medium has been provided to the second node computer 162, and / or the custody process has been completed in other ways.

[0151] The above text is about Figure 7-9 The steps described are exemplary, and many alternatives are possible. For example, instead of using CBDC to transfer values ​​between entities, current bank accounts with fiat currencies can be used to transfer values ​​between each of the aforementioned entities.

[0152] Additionally, in some embodiments, instead of the above regarding Figure 9The discussed method of replacing digital tokens and / or CBDC-B with a second exchange medium allows the second node computer 162 to retain the digital tokens and / or CBDC-B as payment instruments for future transactions. When needed, the second node computer 162 can send the digital tokens and / or CBDC-B to the third node computer 163 during future transactions between the second node computer 162 and the third node computer 163 (e.g., repeating the process). Figure 8 (Some or all of the steps shown). For example, the second node computer 162 may further update the digital token by further increasing the counter value and / or changing the owner to the third node computer 163, and the further updated digital token may be recorded to the blockchain to transfer the digital token to the third node computer 163.

[0153] Additionally, in some embodiments, two or more digital tokens may be provided together for a single transaction. For example, a second node computer 162 may simultaneously request one or more additional digital tokens (e.g., each with a corresponding token value) and send them together with the original digital tokens to a third node computer 163 to provide the third node computer 163 with a total value greater than the value included in the original digital tokens.

[0154] Additionally, in some embodiments, the first portion of the digital token can be reused, while the second portion can be retained. For example, a second node computer 162 may be permitted to send the first portion of the token value (e.g., a fraction or percentage) to a third node computer 163, while retaining ownership of the remaining second portion of the token value.

[0155] Failed verification

[0156] For reference Figure 10 A method 1000 according to an embodiment of the present invention is described. Reference is also made to some elements in the other accompanying drawings. In embodiments of the invention, the steps shown in method 1000 may be performed sequentially or in any suitable order. In some embodiments, one or more of the steps may be optional.

[0157] The embodiments include various technologies for detecting and preventing counterfeit digital tokens. For example, as described above... Figure 9 As described in step S902, the network processing computer 120 can verify the authenticity of the digital token. If authenticity cannot be verified, the transaction can be cancelled. Method 1000 provides steps for managing digital tokens that cannot be verified as authentic.

[0158] In step S1001, the first node computer 161 may provide a digital token to another node, such as the second node computer 162 (or the network processing computer 120), for verification. For example, step S1001 may be similar to step S901, wherein the second node computer 162 sends a request to the network processing computer 120 to exchange digital tokens.

[0159] In step S1002, a network node, such as the second node computer 162, may attempt to verify the authenticity of the digital token. For example, step S1002 may be similar to step S902, wherein the network processing computer 120 checks whether a record of the digital token exists in the blockchain, and / or whether one or more details in the received digital token match details indicated in the blockchain (e.g., matching a counter value, matching an owner, etc.).

[0160] In step S1003, a network node, such as the second node computer 162, may determine that the verification failed and the token is not authentic (e.g., it is counterfeit, outdated, previously destroyed, etc.). For example, the counter value in the received digital token may be out of order or otherwise incorrect, or the digital signature may be unverifiable. The network node may determine not to perform any requested task (e.g., update the digital token input into the blockchain) and may continue to alert one or more other network nodes of the failed verification.

[0161] In step S1004, a network node, such as the second node computer 162, may send a report about the failed verification to the network processing computer 120. The report message may include information about the digital token and / or the reason for the verification failure (e.g., the counter value in the provided digital token is incorrect).

[0162] In step S1005, the network processing computer 120 may attempt to verify the digital token again. For example, the network processing computer 120 may repeat steps S1002-S1003 to confirm that the digital token is invalid.

[0163] In step S1006, network processing computer 120 may take one or more actions based on the failed verification. For example, network processing computer 120 may suspend the activity of network nodes (e.g., first node computer 161) that submitted invalid digital tokens. The activity may be suspended for a predetermined amount of time (e.g., one hour, one day, or one week), or until the problem is resolved.

[0164] In steps S1007A-B, the network processing computer 120 broadcasts information about failed verifications and / or response actions taken (e.g., suspension of activity of the violating node and the duration of the suspension). Additionally, the network processing computer 120 may notify network nodes that they should not record any attempts to update the blockchain with invalid tokens.

[0165] The embodiments of the present invention offer several advantages. For example, in embodiments of the present invention, multiple local networks can interact with each other through a central network. Therefore, individual local networks can maintain privacy and allow for the customization of local rules and procedures, while simultaneously establishing real-time connectivity at a global level.

[0166] Additionally, the embodiments provide digital tokens that can act as intermediary values ​​between local exchange media, thereby enabling value transfer across networks and exchange media types. Even if local networks utilize different exchange media, each local exchange media can be represented as or exchanged for a digital token in the central network. For example, when a value is transferred from a first local network to a second local network, the value provided in the form of a first exchange media of the first local network can be exchanged for a digital token. The digital token can then be exchanged for a second local exchange media of the second local network.

[0167] Additionally, the embodiments provide digital tokens that can be monitored and verified based on counter values ​​and / or recorded previous usage, thereby providing a security mechanism for value transfers across the network. The digital token can be transferred multiple times to multiple different owners, and the counter value can be incremented each time a transfer and / or ownership change occurs.

[0168] Furthermore, the digital token can be exchanged for token value on a local exchange medium. At that point, the digital token can be destroyed and removed from circulation. Thus, the central network provides a secure, temporary, exchangeable, and disposable medium for cross-network exchange.

[0169] A computer system that can be used to implement any of the entities or components described herein is now described. Subsystems within the computer system are interconnected via a system bus. Additional subsystems include a printer, keyboard, fixed disk, and monitor, which may be coupled to a display adapter. Peripheral devices and I / O devices that may be coupled to an input / output (I / O) controller may be connected to the computer system by any number of components known in the art, such as serial ports. For example, a serial port or external interface may be used to connect computer devices to a wide area network, such as the Internet, a mouse input device, or a scanner. The interconnection via the system bus allows the central processing unit to communicate with each subsystem and control the execution of instructions from system memory or fixed disk, as well as the exchange of information between subsystems. System memory and / or fixed disk may embody a computer-readable medium.

[0170] As described, the services of the present invention may involve implementing one or more functional, process, operational, or method steps. In some embodiments, the functional, process, operational, or method steps may be implemented as the result of executing an instruction set or software code by a suitably programmed computing device, microprocessor, data processor, etc. The instruction set or software code may be stored in memory or other forms of data storage elements accessed by the computing device, microprocessor, etc. In other embodiments, the functional, process, operational, or method steps may be implemented by firmware or a dedicated processor, integrated circuit, etc.

[0171] Any software component or function described in this application may be implemented as processor-executable software code using any suitable computer language, such as Java, or other conventional or object-oriented technologies. Or Perl. Software code can be stored as a series of instructions or commands on a computer-readable medium, such as random access memory (RAM), read-only memory (ROM), magnetic media such as a hard disk drive or a floppy disk, or optical media such as a CD-ROM. Any such computer-readable medium can reside on or within a single computing device, and can exist on different computing devices or within a system or network.

[0172] Although certain exemplary embodiments have been described in detail and shown in the accompanying drawings, it should be understood that such embodiments are merely illustrative of the invention and not limiting, and that the invention is not limited to the specific arrangements and constructions shown and described, as various other modifications will be apparent to those skilled in the art.

[0173] As used herein, unless explicitly indicated otherwise, the use of “a / an” or “the” is intended to mean “at least one”.

Claims

1. A method comprising: A first node computer operated by a first entity transfers a first value of the exchange medium to a first central computer, and the first central computer sends a message to a network processing computer, notifying the network processing computer of the transfer of the first value; The first node computer receives a digital token from the network processing computer. The digital token includes a digital token identifier, an owner identifier that identifies the first entity, a counter value, a token value, and a first digital signature. The first node computer updates the digital token by incrementing the counter value, changing the owner identifier to identify the second entity, and adding a second digital signature of the first node computer to transfer the digital token to the second node computer operated by the second entity; as well as The first node computer broadcasts the updated digital token to nodes in the blockchain network, which includes the first node computer, the second node computer, the first central authority computer, and the network processing computer, wherein the nodes record the updated digital token to their respective blockchains.

2. The method of claim 1, wherein the token value is based on the first value.

3. The method of claim 2, wherein the token value is less than the first value.

4. The method according to claim 1, further comprising: The updated digital token is recorded by the first node computer to a copy of the blockchain at the first node computer.

5. The method of claim 1, wherein the first central computer transfers the first value of the exchange medium to a second central computer.

6. The method of claim 1, wherein the exchange medium is a first exchange medium, and the second central computer transfers a second value of the second exchange medium to the second node computer operated by the second entity.

7. The method of claim 6, wherein the blockchain network is a central blockchain network, the first exchange medium is associated with a first local blockchain network, and the second exchange medium is associated with a second local blockchain network.

8. The method of claim 6, wherein the second node computer provides the digital token in exchange for the second value of the second exchange medium.

9. The method of claim 8, wherein the network processing computer destroys the digital token.

10. The method of claim 1, wherein the second node computer further updates the digital token to transfer the digital token to the third node computer operated by the third entity by incrementing the counter value, changing the owner identifier to identify the third entity, and adding a third digital signature of the second node computer.

11. The method of claim 10, wherein the second node computer broadcasts the further updated digital token to the nodes in the blockchain network, and wherein the nodes record the further updated digital token to their respective blockchains.

12. The method of claim 1, wherein the node in the blockchain network verifies the updated digital token before recording the updated digital token into its respective blockchain.

13. The method of claim 1, wherein verification includes determining, based on records in the blockchain, that the counter value in the updated digital token is correct.

14. The method of claim 1, wherein the digital token is a first digital token, and the method further comprises: The first node computer receives from the network processing computer a plurality of digital tokens including the first digital token, wherein each of the plurality of digital tokens includes a corresponding token value, the plurality of digital tokens together representing a total value, the total value being based on the first value.

15. A first-node computer, comprising: processor; as well as A computer-readable medium comprising code executable by the processor to perform a method comprising: A first value of the exchange medium is transferred to a first central computer, and the first central computer sends a message to a network processing computer, notifying the network processing computer of the transfer of the first value; The network processing computer receives a digital token, the digital token including a digital token identifier, an owner identifier identifying a first entity, a counter value, a token value, and a first digital signature; The digital token is updated by incrementing the counter value, changing the owner identifier to identify the second entity, and adding a second digital signature to the first node computer to transfer the digital token to the second node computer operated by the second entity; as well as The updated digital token is broadcast to nodes in a blockchain network, which includes a first node computer, a second node computer, a first central authority computer, and the network processing computer, wherein the nodes record the updated digital token to their respective blockchains.

16. A method comprising: The network processing computer receives a message regarding the transfer of a first value of the exchange medium from the first node computer operated by the first entity to the first central computer. The network processing computer provides a digital token to the first node computer. The digital token includes a digital token identifier, an owner identifier that identifies the first entity, a counter value, a token value, and a first digital signature. The first node computer updates the digital token by incrementing the counter value, changing the owner identifier to identify the second entity, and adding a second digital signature of the first node computer to transfer the digital token to the second node computer operated by the second entity. The network processing computer receives a broadcast message including the updated digital token; as well as The network processing computer updates the blockchain stored in the network processing computer with the updated digital token. The network processing computer is located in a blockchain network, which includes the first node computer, the second node computer, the first central authority computer, and the network processing computer.

17. The method of claim 16, wherein the message is received from the first central authority computer, and the method further comprises: The digital token is generated by the network processing computer, including generating the first digital signature using a first private key, wherein the first node computer generates the second digital signature using a second private key.

18. The method of claim 16, further comprising: The network processing computer receives the digital token from the second node computer in exchange for a second value on the second exchange medium. as well as The digital token is destroyed by the network processing computer.

19. The method of claim 16, further comprising: Verify the updated digital token, wherein verification includes determining that the counter value is correct based on records in the blockchain.

20. The method of claim 16, wherein the token value is based on the first value.

Images