[go: up one dir, main page]

WO2024081843A1 - Systèmes et procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne - Google Patents

Systèmes et procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne Download PDF

Info

Publication number
WO2024081843A1
WO2024081843A1 PCT/US2023/076780 US2023076780W WO2024081843A1 WO 2024081843 A1 WO2024081843 A1 WO 2024081843A1 US 2023076780 W US2023076780 W US 2023076780W WO 2024081843 A1 WO2024081843 A1 WO 2024081843A1
Authority
WO
WIPO (PCT)
Prior art keywords
deposit
tokens
wallet address
blockchain network
account
Prior art date
Application number
PCT/US2023/076780
Other languages
English (en)
Inventor
Umar Farooq
Naveen MALLELA
Muh Hwa Lee
Sai Murali Krishna VALIVETI
Nelli ZALTSMAN
Sunil PANT
Basak TOPRAK
Emma LANDRIAULT
Joshua DANIEL
Wee Kee TOH
Original Assignee
Jpmorgan Chase Bank, N.A.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/485,664 external-priority patent/US20240127226A1/en
Application filed by Jpmorgan Chase Bank, N.A. filed Critical Jpmorgan Chase Bank, N.A.
Priority to AU2023358719A priority Critical patent/AU2023358719A1/en
Publication of WO2024081843A1 publication Critical patent/WO2024081843A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3678—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes e-cash details, e.g. blinded, divisible or detecting double spending
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3827—Use of message hashing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification

Definitions

  • Embodiments relate to systems and methods for using single or multi-chain deposit tokens.
  • a Deposit Token evidences a demand deposit claim for a fixed amount of fiat cash by the token-holder against the token issuing bank.
  • Deposit token is issued natively on distributed ledgers such as blockchain digital ledgers and may be transferred to other parties.
  • a method for deposit tokenization may include: (1) receiving, by a deposit tokenization service for a token issuer and from an authorized party, an instruction for tokenizing an amount of non-tokenized funds in a deposit account; (2) verifying, by the deposit tokenization service, an identity of the authorized party using a verifiable credential; (3) screening, by the deposit tokenization service and using an information oracle, the deposit account and/or the verifiable credential; (4) debiting, by the deposit tokenization service, the deposit account for the amount and crediting the amount to an omnibus account; (5) tokenizing, by the deposit tokenization service, the amount of the non- tokenized funds on a blockchain network as deposit tokens; and (6) crediting, by the deposit tokenization service, a wallet address on the blockchain network with the deposit tokens.
  • the screening comprises sanctions screening.
  • the method may also include: updating, by the deposit tokenization service, a transaction store with the amount of deposit tokens, wherein the transaction store updates a total number of deposit tokens for the token issuer.
  • the blockchain network may be a public blockchain network or a private blockchain network.
  • the verifiable credential attests to an identity of the authorized party.
  • a method for transferring deposit token may include: (1) receiving, from a holder of deposit tokens or an authorized party and by a token issuer, an instruction for transferring an amount of deposit tokens from a first wallet address to a second wallet address; (2) verifying an identity of the holder or the authorized party using a verifiable credential; (3) screening, using an information oracle, the first wallet address, the second wallet address, and/or the verifiable credential; (4) transferring the amount of the deposit tokens from the first wallet address to the second wallet address; and (5) storing a transfer event for the transfer in an event store.
  • the screening comprises sanctions screening.
  • the first wallet address and the second wallet address ar e on the same blockchain network.
  • the network may be a public blockchain network or a private blockchain network.
  • the first wallet address and the second wallet address ar e on different blockchain networks, and the method may also include: triggering a burn event for the amount of the deposit tokens in the first wallet address; crediting the second wallet address with the amount of the deposit tokens burned from the first wallet address; and updating a transaction store with the deposit tokens, wherein the transaction store updates a total number of deposit tokens for the token issuer.
  • the first wallet address and the second wallet address are on different public blockchain networks.
  • the first wallet address is on a public blockchain network and the second wallet address is on a private blockchain network, or the first wallet address is on the private blockchain network and the second wallet address is on the public blockchain network.
  • a method for redemption of deposit tokens may include: (1) receiving, from a holder of deposit tokens or an authorized party, a request to instruct the redemption of an amount of deposit tokens from a wallet address on a blockchain network to a banking account; (2) identifying a holder account as a bum account; (3) verifying an identity of the holder or the authorized party using a verifiable credential; (4) using an information oracle, performing screening on the wallet address from where deposit tokens are originating, the bank account, and/or the verifiable credential; (5) transferring the amount of deposit tokens to the holder account; (6) triggering a bum event on the holder account; (7) executing the bum event; and (8) crediting the banking account with the amount of the deposit token by debiting an omnibus account and crediting the banking account.
  • the screening comprises sanctions screening.
  • the method may also include updating a transaction store with the amount of the deposit tokens, wherein the transaction store updates a total number of deposit tokens for a deposit token issuer.
  • the blockchain network comprises a public blockchain network or a private blockchain network.
  • the verifiable credential attests to an identity of the holder or the authorized party.
  • a method of interest distribution for deposit tokens may include: (1) receiving a computation of interest on deposit tokens; (2) trigging an interest event in response to interest being received at an omnibus account; (3) instructing a distribution of interests to deposit token smart contracts; and (4) crediting a wallet address with an equivalent amount of deposit tokens for the interest.
  • Figure 1 depicts a system for using single or multi-chain deposit tokens according to an embodiment
  • Figure 2 depicts a system for using single or multi-chain deposit tokens according to another embodiment
  • Figure 3 depicts a method for deposit tokenization according to an embodiment
  • Figure 4A depicts a method for transferring deposit tokens on the same blockchain network according to an embodiment
  • Figure 4B depicts a method for transferring deposit tokens between blockchain networks according to an embodiment
  • Figure 5 depicts a method for interest distribution for deposit tokens according to an embodiment
  • Figure 6 A depicts a method for direct redemption of deposit tokens according to an embodiment
  • Figure 6B depicts a method for indirect redemption of deposit tokens according to an embodiment
  • Figure 7 depicts an exemplary computing system for implementing aspects of the present disclosure.
  • Embodiments relate to systems and methods for using single or multi-chain deposit tokens.
  • a deposit token may be a transferable token evidencing a demand deposit claim by the party in possession of the token against the issuing bank for a fiat cash amount.
  • a deposit token is not a Stablecoin. Instead, the demand deposit claim evidenced is an unsecured claim constituting a general liability of the issuing bank with the same credit priority as other deposits held at the issuing bank, which is accounted for in the fractional reserve requirements applicable to the issuing bank in respect of its deposit liabilities of a similar nature.
  • Deposit token may be issued and transferred on public or private blockchain networks.
  • embodiments may enable the deposit token smart contract(s) to work with a verifiable credential, or “VC”, such as a digital identity or an attestation, and/or with data oracles which may validate certain conditions, such as that the wallet address receiving the tokens is not on a sanctions list.
  • VC verifiable credential
  • VCs may attest to the identity of a party, such as the party that is receiving the deposit tokens, and may be used to verify the identity of the party. Examples of digital identities and attestations are described in U.S. Patent Application Ser. No. 16/878,457, filed May 19, 2020, and U.S. Provisional Patent Application Ser. No. 62/850,181, filed May 20, 2019, U.S. Provisional Patent Application Serial No. 62/976,262 filed February 13, 2020, U.S. Provisional Patent Application Serial No. 63/126,335 filed December 16, 2020, and U.S. Patent Application Ser. No. 17/174,650 filed February 12, 2021, the disclosures of which are hereby incorporated, by reference, in their entireties.
  • System 100 depicts one or more public blockchain-based networks (e.g., first public network 110, second public network 120).
  • System 200 depicts one or more private blockchain-based networks (e.g., first private network 110, private public network 120).
  • First public network 110, second public network 120, first private network 210, and second private network 220 may include screening oracles 112, 122, 212, 222 and deposit token smart contracts (SCs) 114, 124, 214, 224.
  • First public network 110 and second public network 120 may further include verifiable credential (VC) registry smart contracts (SCs) 116, 126.
  • VC verifiable credential
  • Deposit Token smart contracts 114, 124, 214, 224 may call additional smart contracts (not shown) that may be created by the token issuer or external parties to apply logic to limit transferability or apply controls to transferability for transfers between end holders of tokens of internal and external institutions.
  • Screening oracles 112, 122, 212, 222 may be data oracles that may interact with other data oracles (not shown), such as OFAC/sanctions list providers that indicate if a wallet or a verified credential is sanctioned. Screening oracles 112, 122, 212, and 222 may be on-chain smart contracts that may be updated with off-chain activities. Screening oracles 112, 122, 212, and 222 may maintain the same list of activities as screening list 160, 260, which are off-chain.
  • a “verifiable credential” is a digital identity tool that may be used to verify the identity of party receiving deposit tokens.
  • a deposit token smart contract (not shown) may interact with VC registry smart contracts 116, 126 as part of the transfer validation process to validate the transferability of the deposit tokens and/or the credentials of the entities involved in the transfer.
  • VCs may also be used to furnish specific proofs that are needed to meet transaction controls requirements such as sanction screening status validation, know your customer (KYC) status, type of institution transacting, etc.
  • VC registry smart contracts 116, 126 and screening oracles 112, 122, 212, 222 may be optional depending on the network type (e.g., public versus private), the preferences of the deposit token issuer, etc.
  • External services 130 may provide an interface between first public network 110/second public network 120 and deposit tokenization service 140.
  • ft may provide meta transaction relayer 132 and external service node 134.
  • Meta transaction relayer 132 may be a relayer that may pay the gas fee and submit the transaction on behalf of a financial institution.
  • External service node 134 may allow distributed applications for a financial institution to connect to the node service providers to monitor contract activities on first public network 110 and/or second public network 120.
  • Deposit token wallet 150 which may be VC enabled, may store deposit tokens for a client.
  • Deposit tokenization service 140, 240 may create tokens for fiat currency. It may further validate the account(s) involved or client for sanctions and other issues using sanction screening module 162, 262. Sanctions screening module 162, 262 may validate the account(s) and client based on screening list 160, 260. Screening list 160, 260 may be provided with information by one or more operations user.
  • a client may interface with deposit token wallet 150, 250 and channels 164, 264.
  • Channels 164, 264 may be a method over which the client may provide instructions, such as tokenization instructions, to a financial institution, such as an Application Programming Interface (API), a web user interface (UI), an application, etc.).
  • API Application Programming Interface
  • UI web user interface
  • application etc.
  • Payment services 166, 266 may be a service provided by a financial institution. Payment services 166, 266 may provide payment orchestration and related processing services. For example, payment services 166, 266 may execute controls for sanction screenings, fraud checks, anti-money laundering, etc.
  • Liquidity and account services 168, 268 may provide core banking ledger, liquidity reporting, etc.
  • Core ledger 170, 270 may be an off-chain ledger provided by a financial institution. Core ledger 170, 270 may maintain omnibus account 172, 272, which may be used as an account that may hold fiat currency temporarily during the tokenization and de-tokenization process.
  • Event store and reporting 142, 242 may receive events from deposit tokenization service 140, 240. It may further interface with other internal systems to pull information in order to meet reporting requirements. For example, it may pull client-level information from static data references to meet end of day reporting requirements, such as total liabilities in deposit tokens per client, total of all types of liabilities per client, etc.
  • Transaction store 144, 244 may keep track of the total deposit tokens in circulation. It may also track the total token supply per blockchain address (e.g., client positions).
  • Deposit tokenization service 140, 240 may validate the total value in circulation before new mint activity.
  • Reporting and data feeds 146, 246 may receive transaction data from transaction store 144, 244 and may provide reports/data feeds to external systems.
  • a method for deposit tokenization is provided according to an embodiment.
  • a client or an otherwise authorized party, may submit an instruction for the tokenization of a deposit from non-tokenized funds (e.g., taken from a standard account) via an existing channel.
  • non-tokenized funds e.g., taken from a standard account
  • step 310 the issuing bank’s payment systems may process the instruction by performing sanctions screening, postings generation, etc.
  • step 315 funds to be tokenized may be credited to an internal omnibus house account for deposit tokens (an “omnibus account”) reflecting the amount of deposit liability to be tokenized.
  • the credit may trigger an event to the deposit tokenization service.
  • the omnibus account may be used in transition; ultimately, the balances may be recorded in the deposit token ledger rather than sitting in the omnibus account.
  • the deposit tokenization service may instruct the tokenization of deposit tokens onto the relevant blockchain network, such as a private or a public blockchain network.
  • the instructed recipient wallet address may be credited with the requested deposit tokens in the applicable blockchain network.
  • the deposit tokenization service may update the transaction store with the transaction, and in step 335, the transaction store may update the total number of deposit tokens for the financial institution and may also provide reports to downstream systems.
  • the deposit tokenization service may keep a state of the total token supply and the placement of the tokens (e.g., (per blockchain address), and may provide state changes to downstream reporting systems.
  • a party may submit an instruction for the transfer of deposit tokens from one wallet address holding deposit tokens to another wallet address.
  • the instructing party may attach its verifiable credentials (VCs) with the request if required.
  • VCs verifiable credentials
  • the deposit token smart contract may optionally verify the VC with a VC registry smart contract and may reject the request if this fails.
  • deposit token smart contracts may optionally verify the sender and receiver wallet address with a screening oracle.
  • the screening oracle may further check the sender and receiver wallet addresses for sanctions.
  • step 420 upon successful validation of the sender and receiver wallet address, the transfer may be executed by a deposit token smart contract.
  • the deposit tokenization service may receive an event for transfer, and in step 430, the event may be stored in an event store.
  • the deposit tokenization service may update the transaction store with the transaction, and in step 440, the transaction store may update the total number of deposit tokens for the financial institution and may also provide reports to downstream systems, such as a FDIC part 370 calculator, end of day anti-money laundering reporting, general ledger reporting, etc.
  • a client may request that the deposit token service authorize issuing bank to debit up to authorized amount.
  • the issuing bank may generate a proof and respond back to the client. If required, the client may attach the bank given proof and its verifiable credentials (VCs) with the request.
  • the deposit token smart contract may already recognize bank as a party authorized to debit.
  • the deposit token smart contract may optionally verify the VC with a VC registry smart contract, and may reject the request if this fails.
  • the deposit token smart contract may optionally verify the submitted proof and may reject the request if this fails.
  • the client may instruct the financial institution, for example by invoking the deposit token API, to move a deposit balance from one network to other (e.g., from a first network to a second network).
  • the deposit tokenization service may validate the instruction.
  • the issuer’s payment systems may process the instruction and may execute the instruction by performing sanctions screening and other required validations.
  • the deposit tokenization service may instruct the deposit token small contract on the first network to debit the wallet address from which deposit tokens are being sent and bum the amount.
  • the deposit token smart contract on the first network may debit the originating wallet address and bum the amount and emits an event.
  • the deposit tokenization service may receive the bum event and the deposit tokenization service may instmct the tokenization of deposit tokens onto the relevant receiving blockchain network (e.g., the second network).
  • the deposit tokenization service may call a deposit token smart contract on the receiving blockchain network to perform the tokenization.
  • the receiving wallet address may be credited with the requested deposit tokens in the applicable blockchain network (e.g., the second network for this example).
  • the deposit token smart contract on the receiving blockchain network may credit the receiving wallet address with the deposit tokens.
  • deposit tokenization service may store the event in an event store.
  • the deposit tokenization service may update the transaction store with the transaction, and the transaction store may update the total number of deposit tokens for the financial institution and may also provide reports to downstream systems.
  • step 505 core banking interest calculation systems may periodically compute interest on deposit tokens in the relevant network, and may transfer the interest amounts to be distributed to an omnibus account from funds of the deposit token issuer.
  • step 510 upon credit of funds to the omnibus account, an event may be triggered to the deposit tokenization service.
  • the deposit tokenization service may instruct the distribution of interests to deposit token smart contracts on the relevant network.
  • step 520 the wallet addresses on the relevant network holding the deposit tokens to which interest has accrued may be credited with an equivalent amount of deposit tokens.
  • step 520 a method for direct redemption of deposit tokens is provided according to an embodiment.
  • a client of the deposit token issuing bank, or other authorized party may submit a request to instruct the redemption of deposit token balance from an eligible digital wallet on a blockchain network to a banking account.
  • the recipient wallet may be identified as a specific “bum account” as defined by the deposit token issuer.
  • the instructing party may optionally attach its VCs with the request.
  • the deposit token smart contract may optionally verify the VC with VC registry and rejects the request if this fails.
  • step 615 upon successful verification of VC, the deposit token smart contracts may check if the credit is to a bum account.
  • step 620 the transfer may be executed by the deposit token smart contract and a bum event is emitted by the smart contract.
  • the deposit tokenization service may receive the bum event and triggers the client credit process. This reduces the total number of tokens in circulation.
  • the deposit tokenization service may update the transaction store with transaction, and in step 635, the transaction store may update the number of deposit tokens in circulation.
  • the transaction store may also perform any reporting to downstream systems as needed.
  • a credit to client banking account may be triggered by existing systems.
  • the issuer core ledger may reflect the debit of Omnibus Account and credit to the client banking account.
  • a method for indirect redemption of deposit tokens is provided according to an embodiment.
  • the holder of the deposit tokens is not a customer of the issuing bank.
  • a holder of deposit tokens may submit a request for redemption of deposit tokens to a banking account at an authorized institution.
  • the holder may not be a customer of the deposit token issuing bank.
  • the request may be to a request to redeem a deposit token balance from an eligible digital wallet on a blockchain network to the banking account.
  • the deposit token smart contract may optionally verify the VC with VC registry and rejects the request if this fails.
  • the deposit token smart contract may execute a transfer to the authorized institution’s redemption account.
  • the deposit tokenization service may receive event information and may update the transaction store with transaction information.
  • the transaction store may update client position records and the number of deposit tokens in circulation. The transaction store may also perform any reporting to downstream systems as needed.
  • step 680 once the deposit tokens are received, the authorized institution may hold the deposit tokens by transferring the deposits out of the bum account to its blockchain address, or it may directly redeem the deposit tokens using a process such as that depicted in Figure 6A.
  • Figure 7 depicts an exemplary computing system for implementing aspects of the present disclosure.
  • Figure 7 depicts exemplary computing device 700.
  • Computing device 700 may represent the system components described herein.
  • Computing device 700 may include processor 705 that may be coupled to memory 710.
  • Memory 710 may include volatile memory.
  • Processor 705 may execute computer-executable program code stored in memory 710, such as software programs 715.
  • Software programs 715 may include one or more of the logical steps disclosed herein as a programmatic instruction, which may be executed by processor 705.
  • Memory 710 may also include data repository 720, which may be nonvolatile memory for data persistence.
  • Processor 705 and memory 710 may be coupled by bus 730.
  • Bus 730 may also be coupled to one or more network interface connectors 740, such as wired network interface 742 or wireless network interface 744.
  • Computing device 700 may also have user interface components, such as a screen for displaying graphical user interfaces and receiving input from the user, a mouse, a keyboard and/or other input/ output components (not shown).
  • Embodiments of the system or portions of the system may be in the form of a “processing machine,” such as a general-purpose computer, for example.
  • processing machine is to be understood to include at least one processor that uses at least one memory.
  • the at least one memory stores a set of instructions.
  • the instructions may be either permanently or temporarily stored in the memory or memories of the processing machine.
  • the processor executes the instructions that are stored in the memory or memories in order to process data.
  • the set of instructions may include various instructions that perform a particular task or tasks, such as those tasks described above. Such a set of instructions for performing a particular task may be characterized as a program, software program, or simply software.
  • the processing machine may be a specialized processor.
  • the processing machine may be a cloudbased processing machine, a physical processing machine, or combinations thereof.
  • the processing machine executes the instructions that are stored in the memory or memories to process data.
  • This processing of data may be in response to commands by a user or users of the processing machine, in response to previous processing, in response to a request by another processing machine and/or any other input, for example.
  • the processing machine used to implement embodiments may be a general-purpose computer.
  • the processing machine described above may also utilize any of a wide variety of other technologies including a special purpose computer, a computer system including, for example, a microcomputer, mini-computer or mainframe, a programmed microprocessor, a micro-controller, a peripheral integrated circuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC (Application Specific Integrated Circuit) or other integrated circuit, a logic circuit, a digital signal processor, a programmable logic device such as a FPGA (Field-Programmable Gate Array), PLD (Programmable Logic Device), PLA (Programmable Logic Array), or PAL (Programmable Array Logic), or any other device or arrangement of devices that is capable of implementing the steps of the processes disclosed herein.
  • a programmable logic device such as a FPGA (Field-Programmable Gate Array), PLD (Programmable Logic Device), PLA (Programmable Logic Array), or PAL
  • the processing machine used to implement embodiments may utilize a suitable operating system.
  • each of the processors and/or the memories of the processing machine may be located in geographically distinct locations and connected so as to communicate in any suitable manner.
  • each of the processor and/or the memory may be composed of different physical pieces of equipment. Accordingly, it is not necessary that the processor be one single piece of equipment in one location and that the memory be another single piece of equipment in another location. That is, it is contemplated that the processor may be two pieces of equipment in two different physical locations. The two distinct pieces of equipment may be connected in any suitable manner. Additionally, the memory may include two or more portions of memory in two or more physical locations.
  • processing is performed by various components and various memories.
  • processing performed by two distinct components as described above in accordance with a further embodiment, may be performed by a single component.
  • processing performed by one distinct component as described above may be performed by two distinct components.
  • the memory storage performed by two distinct memory portions as described above may be performed by a single memory portion. Further, the memory storage performed by one distinct memory portion as described above may be performed by two memory portions.
  • various technologies may be used to provide communication between the various processors and/or memories, as well as to allow the processors and/or the memories to communicate with any other entity; i.e., so as to obtain further instructions or to access and use remote memory stores, for example.
  • Such technologies used to provide such communication might include a network, the Internet, Intranet, Extranet, a LAN, an Ethernet, wireless communication via cell tower or satellite, or any client server system that provides communication, for example.
  • Such communications technologies may use any suitable protocol such as TCP/IP, UDP, or OSI, for example.
  • a set of instructions may be used in the processing of embodiments.
  • the set of instructions may be in the form of a program or software.
  • the software may be in the form of system software or application software, for example.
  • the software might also be in the form of a collection of separate programs, a program module within a larger program, or a portion of a program module, for example.
  • the software used might also include modular programming in the form of object-oriented programming. The software tells the processing machine what to do with the data being processed.
  • the instructions or set of instructions used in the implementation and operation of embodiments may be in a suitable form such that the processing machine may read the instructions.
  • the instructions that form a program may be in the form of a suitable programming language, which is converted to machine language or object code to allow the processor or processors to read the instructions. That is, written lines of programming code or source code, in a particular programming language, are converted to machine language using a compiler, assembler or interpreter.
  • the machine language is binary coded machine instructions that are specific to a particular type of processing machine, i.e., to a particular type of computer, for example. The computer understands the machine language.
  • any suitable programming language may be used in accordance with the various embodiments.
  • the instructions and/or data used in the practice of embodiments may utilize any compression or encryption technique or algorithm, as may be desired.
  • An enciyption module might be used to encrypt data.
  • files or other data may be decrypted using a suitable decryption module, for example.
  • the embodiments may illustratively be embodied in the form of a processing machine, including a computer or computer system, for example, that includes at least one memory.
  • the set of instructions i.e., the software for example, that enables the computer operating system to perform the operations described above may be contained on any of a wide variety of media or medium, as desired.
  • the data that is processed by the set of instructions might also be contained on any of a wide variety of media or medium. That is, the particular medium, i.e., the memory in the processing machine, utilized to hold the set of instructions and/or the data used in embodiments may take on any of a variety of physical forms or transmissions, for example.
  • the medium may be in the form of a compact disc, a DVD, an integrated circuit, a hard disk, a floppy disk, an optical disc, a magnetic tape, a RAM, a ROM, a PROM, an EPROM, a wire, a cable, a fiber, a communications channel, a satellite transmission, a memory card, a SIM card, or other remote transmission, as well as any other medium or source of data that may be read by the processors.
  • the memory or memories used in the processing machine that implements embodiments may be in any of a wide variety of forms to allow the memory to hold instructions, data, or other infoimation, as is desired.
  • the memory might be in the form of a database to hold data.
  • the database might use any desired arrangement of files such as a flat file arrangement or a relational database arrangement, for example.
  • a user interface includes any hardware, software, or combination of hardware and software used by the processing machine that allows a user to interact with the processing machine.
  • a user interface may be in the form of a dialogue screen for example.
  • a user interface may also include any of a mouse, touch screen, keyboard, keypad, voice reader, voice recognizer, dialogue screen, menu box, list, checkbox, toggle switch, a pushbutton or any other device that allows a user to receive infoimation regarding the operation of the processing machine as it processes a set of instructions and/or provides the processing machine with information.
  • the user interface is any device that provides communication between a user and a processing machine.
  • the information provided by the user to the processing machine through the user interface may be in the foim of a command, a selection of data, or some other input, for example.
  • a user interface is utilized by the processing machine that performs a set of instructions such that the processing machine processes data for a user.
  • the user interface is typically used by the processing machine for interacting with a user either to convey information or receive information from the user.
  • the user interface might interact, i.e., convey and receive information, with another processing machine, rather than a human user. Accordingly, the other processing machine might be characterized as a user.
  • a user interface utilized in the system and method may interact partially with another processing machine or processing machines, while also interacting partially with a human user. It will be readily understood by those persons skilled in the art that embodiments are susceptible to broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the foregoing description thereof, without departing from the substance or scope.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Storage Device Security (AREA)

Abstract

L'invention concerne des systèmes et des procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne. Selon un mode de réalisation, un procédé de tokénisation de dépôt peut consister à : (1) recevoir, par un service de tokénisation de dépôt pour un émetteur de jeton et provenant d'une partie autorisée, une instruction de tokénisation d'une quantité de fonds non tokénisés sur un compte de dépôt ; (2) vérifier, par le service de tokénisation de dépôt, une identité de la partie autorisée à l'aide d'un justificatif d'identité vérifiable ; (3) vérifier, par le service de tokénisation de dépôt et utiliser un oracle d'informations, le compte de dépôt et/ou le justificatif d'identité vérifiable ; (4) débiter, par le service de tokénisation de dépôt, le compte de dépôt de la quantité et créditer le montant sur un compte omnibus ; (5) tokéniser, par le service de tokénisation de dépôt, la quantité des fonds non tokénisés sur un réseau de chaîne de blocs en tant que jetons de dépôt ; et (6) créditer, par le service de tokénisation de dépôt, une adresse de portefeuille sur le réseau de chaîne de blocs avec les jetons de dépôt.
PCT/US2023/076780 2022-10-14 2023-10-13 Systèmes et procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne WO2024081843A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2023358719A AU2023358719A1 (en) 2022-10-14 2023-10-13 Systems and methods for using single or multi-chain deposit tokens

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263379581P 2022-10-14 2022-10-14
US63/379,581 2022-10-14
US18/485,664 US20240127226A1 (en) 2022-10-14 2023-10-12 Systems and methods for using single or multi-chain deposit tokens
US18/485,664 2023-10-12

Publications (1)

Publication Number Publication Date
WO2024081843A1 true WO2024081843A1 (fr) 2024-04-18

Family

ID=88779950

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/076780 WO2024081843A1 (fr) 2022-10-14 2023-10-13 Systèmes et procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne

Country Status (2)

Country Link
AU (1) AU2023358719A1 (fr)
WO (1) WO2024081843A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10540640B1 (en) * 2018-03-05 2020-01-21 Winklevoss Ip, Llc System, method and program product for generating and utilizing stable value digital assets

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10540640B1 (en) * 2018-03-05 2020-01-21 Winklevoss Ip, Llc System, method and program product for generating and utilizing stable value digital assets

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QINGHUA LU ET AL: "Patterns for Blockchain-Based Payment Applications", ARXIV.ORG, CORNELL UNIVERSITY LIBRARY, 201 OLIN LIBRARY CORNELL UNIVERSITY ITHACA, NY 14853, 18 August 2021 (2021-08-18), XP091024125 *

Also Published As

Publication number Publication date
AU2023358719A1 (en) 2025-04-10

Similar Documents

Publication Publication Date Title
US11449842B2 (en) Systems and methods for private settlement of distributed ledger transactions
US7565326B2 (en) Dialect independent multi-dimensional integrator using a normalized language platform and secure controlled access
US20230206223A1 (en) Systems and methods for distributed-ledger based intercompany netting
US11763297B2 (en) Systems and method for conducting and managing cryptocurrency transactions
JP2020525904A (ja) 銀行間情報ネットワークを実装するためのシステムおよび方法
US12008564B2 (en) Distributed ledger core
WO2018081698A1 (fr) Application de grands livres distribués permettant des paiements en réseau à titre de règlement et de rapprochement d'échanges financiers
US20220374880A1 (en) Distributed ledger based multi-currency clearing and settlement
US12079801B2 (en) Systems and methods for managing third party tokens and transactions across issuer ecosystems
US20210407002A1 (en) Systems and methods for intraday foreign exchange using distributed ledger technology
RU2520410C2 (ru) Способы и системы для финансовых транзакций в среде мобильной связи
US20210174320A1 (en) Systems and methods for reconciliation of financial transactions using auditable, distributed frameworks
US20240127226A1 (en) Systems and methods for using single or multi-chain deposit tokens
US20220067728A1 (en) Distributed ledger interoperability services
WO2024081843A1 (fr) Systèmes et procédés d'utilisation de jetons de dépôt à chaîne unique ou multi-chaîne
US20210357924A1 (en) Distributed-ledger based distributed transaction processing as a brokered service
US12131312B2 (en) Integrated supplier networks
US20240370874A1 (en) Systems and methods for secure transfers
US20240394698A1 (en) Systems and methods for code-based check authentication and clearance
US20250086627A1 (en) Systems and methods for near real time blockchain based payables versus receivables reconciliation
EP4449328A2 (fr) Compensation et règlement multi-devises basés sur un registre distribué
KR100485243B1 (ko) 보안시스템을 이용하는 온라인 계좌 이체 거래를 통한 납부방법
WO2024233339A1 (fr) Systèmes et procédés pour transferts sécurisés
KR100854355B1 (ko) 종교단체용 모바일 계좌 운용방법 및 시스템과 이를 위한프로그램 기록매체
KR20090018758A (ko) 복수개의 계좌정보 운용 프로그램 제공 시스템과 이를 위한프로그램 기록매체

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23805382

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: AU2023358719

Country of ref document: AU