JP2023026348A - Delegated off-chain payment using cryptocurrency - Google Patents

Abstract

To provide a method for securing inter-blockchain transactions.SOLUTION: A method for securing inter-blockchain transactions includes receiving, from a first user application, a registration request including a first permissioned blockchain public key and a first permissionless blockchain public key and receiving, from a second user application, through a processing circuit, a second registration request including a second permissioned blockchain public key and a second permissionless blockchain public key. The permissioned blockchain public keys are valid on a permissioned blockchain, and the permissionless blockchain public keys are valid on a permissionless public blockchain. In addition, the method includes receiving a transaction identification from the first user application, the transaction identification identifying and receiving a first transfer transaction to be performed on the permissionless public blockchain.SELECTED DRAWING: Figure 5

Description

Cross-reference to related applications
No. 63/232,671, filed Aug. 13, 2021, is claimed, the entire disclosure of which is incorporated herein by reference.

The present invention relates to methods, systems, and computer readable media for blockchain-based Layer 2 applications for secure delegated off-chain payments using cryptocurrencies.

Trading in valuable items (eg, works of art) is a complex process, usually conducted at auction houses or by professional sellers, with buyers purchasing the items through intermediaries. Trading in such items, also known as collectibles, has always required a large amount of liquidity and thus has cut off many potential buyers.

A recent development is the introduction of fractional ownership into this market. Fractional ownership allows an investor to purchase only a portion of the collectible, ie, only a share of the collectible, or only a token representing a share of the collectible. In effect, this works like a stock exchange: financial institutions holding collectibles issue shares that investors can buy. The number of shares and their price are determined by the laws of supply and demand. The process of digitizing collectibles in this way is often referred to as tokenization.

Tokenization is a concept similar to that of cryptocurrencies (e.g. Bitcoin), where coins can be viewed as tokens. Moreover, trading collectibles is a complex process requiring intermediaries and trusted third parties, an aspect addressed by blockchain technology. In fact, there are now trading platforms online that leverage blockchain to allow buyers and sellers to trade tokens representing collectibles, or shares of collectibles, using cryptocurrencies. Not all of these trading platforms allow fractional ownership and many of them use a single coin, namely Ethereum.

In one embodiment, the present disclosure provides a method for securing inter-blockchain transactions. An inter-blockchain transaction involves a first transfer on a permissioned blockchain and a second transfer on a permissionless public blockchain. receiving, by a permissioned blockchain processing circuit, from a first user application a registration request including a first permissioned blockchain public key and a first non-permissioned blockchain public key; 1 permissioned blockchain public key is valid on the permissioned blockchain and the first permissionless blockchain public key is valid on the permissionless public blockchain, performing the step of receiving Including steps. The method also includes, by the processing circuit, receiving from the second user application a second registration request including the second permissioned blockchain public key and the second non-permissioned blockchain public key; 2 the permissioned blockchain public key is valid on the permissioned blockchain and the second permissionless blockchain public key is valid on the permissionless public blockchain, performing the step of receiving Also includes steps. Additionally, the method is receiving from the first user application a transaction identification, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification comprising: The step of identifying and receiving first and second permissionless blockchain public keys is included. Additionally, the method includes verifying completion of the first transfer transaction using the transaction identification; and performing A second transfer transaction involves transferring from the second permissioned blockchain public key to the first permissioned blockchain public key.

The subject matter of the present disclosure is explained in more detail below on the basis of exemplary figures. All features described and/or illustrated in this specification may be used singly or in combination in different combinations. Features and advantages of various embodiments will become apparent by reading the following detailed description with reference to the accompanying drawings.

[0014] Fig. 4 illustrates a user registration process according to an embodiment of the present disclosure; [00130] Fig. 13 illustrates a collectibles registration process according to an embodiment of the present disclosure; [00113] Fig. 13 illustrates a collectible verification process in accordance with an embodiment of the present disclosure; [00103] Fig. 13 illustrates a process for tokenization of collectibles according to an embodiment of the present disclosure; FIG. 10 illustrates a transactional workflow for exchange via a private chain of shares of collectibles represented by tokens using cryptocurrencies held on a separate public chain. Fig. 2 shows a processing system;

This disclosure provides mechanisms for implementing permissioned blockchain-based marketplaces that enable fractional ownership of collectibles and payments using digital currency.

In permissioned private blockchain-based markets, even if the permissioned private blockchain does not have a native currency, this disclosure should be used for payment or other asset transactions, such as permissionless public blockchains. Enables the use of widely accepted tokens (e.g. cryptocurrencies) from blockchains. Aspects of the present disclosure can thus be leveraged in any blockchain use case involving on-chain payments, which is the case in the majority of use cases.

A drawback of the state-of-the-art is that it relies on public blockchains such as Ethereum and Bitcoin, where participants can join and leave at any time and have access to all data.

Aspects of the present disclosure enable the use of any digital currency for payments while still leveraging permissioned blockchains. The present disclosure uses a Simple Payment Verification (SPV) client, also called a light client, that allows investors to maintain a single wallet holding cryptocurrencies of their choice.

Other shortcomings of the state of the art include lack of full automation and reliance on unreliable third party services (eg, custody services). Reliance on third parties reduces the benefits of blockchain-based solutions.

In contrast, aspects of the present disclosure are fully automated and reliable. Specifically, aspects of the present disclosure provide a mechanism for trading collectibles that is more efficient and secure than current technical solutions. According to aspects of the present disclosure, collectibles are first converted into digital tokens, thus enabling fractional ownership, and then traded on digital marketplaces. Aspects of the present disclosure are useful because digital marketplaces should only be accessible by authenticated users, and data shared between authenticated users should not be available to outside parties, so collectibles and / Or utilize a permissioned blockchain to conduct transactions involving tokens representing that share.

Aspects of the present disclosure leverage SPV clients from within smart contracts on public blockchains to validate transactions performed on public blockchains and delegate payments on public blockchains, while Ensures security and atomicity for both sellers and buyers on-chain.

Aspects of the present disclosure may include object-based fingerprinting and face detection engines to ensure secure digitization of such objects and their owners.

A blockchain is software that runs among multiple participants and provides a common view of a set of data. Aspects of the present disclosure leverage permissioned blockchains and thus a pre-registration step is used to access blockchain software. A successful registration gives the new user a valid identity and allows them to participate in the network, engage in transactions, and query data stored on the blockchain.

A key feature of blockchains is that they are immutable, i.e. the data stored on the blockchain cannot be changed, which makes them effective against malicious tampering. However, the data can still be read by all participants. Therefore, for the sake of user privacy (e.g., the right to exercise the "right to be forgotten"), preferred embodiments of the present disclosure do not store sensitive data (e.g., user biometrics) on the blockchain, but rather Store only the commitment (eg, as a hash).

The present disclosure may be implemented to leverage a permissioned blockchain architecture, which provides high performance in both throughput (up to 100,000 transactions per second with up to 200 different participants) and scalability. can be done. Such permissioned blockchains can provide support for Internet of Things (IoT) devices, thereby reducing resource constraints without the hardware required to maintain a full blockchain node. Provide complete security for your device. Such permissioned blockchains can offer a higher degree of privacy through a technology called satellite chains. A satellite chain is a small, independent subchain with its own ledger, smart contract, consensus algorithm, and participants. Such satellite chains can communicate with each other and transfer assets as needed while still maintaining their independence. Specifically, the satellite chain runs its own blockchain and thus offers the same performance as the main chain. Such a permissioned blockchain would be fully compatible with the open source software Hyperledger Fabric and could offer the same smart contract functionality.

A smart contract is a piece of software that runs on a blockchain and provides an interface for interacting with data. In other words, a smart contract is a computer program or transaction protocol configured to automatically run and operate on the blockchain. Specifically, a smart contract is a processor-executable program (code) stored on a non-transitory processor-readable medium that, when executed by a processing circuit, causes the processing circuit to perform program functions. The code is available (ie, testable) to all members present on the network. Those skilled in the art will recognize that a "smart contract" is a technical aspect of a blockchain network used, for example, for automation, and not a legal or other means of constraining human activity. deaf.

Smart contracts are typically implemented by the nodes of the system. No single entity can bypass the rules defined by the smart contract, as it requires the consent of a majority of the participants.

The main advantage of smart contracts is the ability to automate an organization's business logic. Switching to automation can therefore eliminate the consequences of human error and misunderstandings that can lead to disputes. Legal contracts or laws are subject to individual interpretation, but software is deterministic and not subject to subjective interpretation. Smart contracts can generally be issued by any entity in the system. According to aspects of the present disclosure, only a subset of entities are authorized to issue smart contracts in the system.

A Simple Payment Verification Client, or SPV Client, is a lightweight software program that can, up to a certain degree of security, verify that a payment has been made on a public blockchain based on Proof of Work (PoW) (such as Public blockchains include Bitcoin and Ethereum blockchains). The SPV client achieves this result without the need to download the full history of the blockchain, and is therefore suitable for resource-constrained devices (e.g. mobile phones).

SPV clients typically verify that a payment has been made on the public chain by requesting that multiple nodes on the public chain retrieve information about a transaction with a specific transaction identification (TxID). The node then responds with a series of block headers (very small) and a proof that the transaction with the TxID is included in one of those headers. This can be done by exposing the part of the Merkle tree whose root is stored in the header containing the transaction. The SPV client must use the Request multiple headers.

The method enforced by the SPV client for transaction validation is to ensure that an adversary cannot break Merkle tree security (depending on the hardness of the hash function) and generate sufficiently many block headers quickly. It is safe as long as you cannot These assumptions are fair because they match the assumptions the PoW blockchain is based on. Specifically, if an adversary can break the hash function used, the entire PoW blockchain ecosystem is broken, and if an adversary can generate enough block headers, the adversary can , will have more mining power than the majority, contrary to the PoW blockchain assumption.

According to aspects of the disclosure, a system includes a user software application. User software applications are deployable, for example, on mobile devices, allowing users to register with the system, browse markets and collectibles, purchase and sell collectibles (or tokens thereof), and be owned by said user. Allows you to see an overview of your possessions. When a user software application is installed, from that point on the application generates a unique key pair (sk, pk) that identifies the user in the system.

According to aspects of the present disclosure, a format for all blockchain transactions executable within the system can be provided. According to use cases provided by aspects of the present disclosure, financial institutions can tokenize collectibles and then store collectibles in order to issue tokens so that users can trade the tokens. . In such use cases, as well as other use cases, specific blockchain transactions can include, for example:

User registration transaction:
|Pubkey _user |biometrics commit|sig _user |
where Pubkey is the public key generated by the user application, biometrics commit is the hash of the user's biometric data (used for later authentication), and sig is the authenticity and A user's digital signature that ensures integrity. A user registration transaction can be performed by a user application.

Collectibles registration transaction:
|ID _bank |collectable fingerprint|sig _bank |
In the formula, ID _bank is the unique ID of the financial institution responsible for the collectible, collectable fingerprint is the unique fingerprint of the collectible, and sig _bank guarantees the authenticity and integrity of the previous fields is a digital signature of a financial institution that The financial institution uses the NEC Object Fingerprint software to issue a collectible registration transaction after receiving a collectible's unique fingerprint.

Collectibles Verification Transaction:
|ID _collectable |ID _appraiser |auth certificate|sig _appraiser |
where ID _collectible is the unique ID of the collectible to be verified, ID _appraiser is the unique ID of the appraiser performing the verification of the collectible, auth certificate is created by the appraiser, A document certifying that a collectible is genuine (ie, not a counterfeit), and a sig _appraiser is an appraiser's digital signature that ensures the authenticity and integrity of the previous field. The appraiser creates a collectible verification transaction during the collectible verification step and broadcasts it to the nodes of the permissioned blockchain.

Collectibles tokenized transaction:
|ID _collectable |ID _owner |Nr.tokens||sig _back |
where ID _collectable is the unique ID of the collectible to be tokenized, ID _owner is the unique ID of the collectible owner, and Nr.tokens are the tokens circulated for the collectible. , and sig _back is the financial institution's digital signature that ensures the authenticity and integrity of the previous field. The financial institution creates this collectibles tokenized transaction and broadcasts it during the collectibles tokenization step.

Auction registration transaction:
|ID _collectable |ID _seller |Owner certificate _seller |sig _seller |
where ID _collectable is the unique ID of the collectible whose token is being traded, ID _seller is the unique ID of the user who currently owns the token for sale, and Owner certificate _seller is , is a document owned by the seller that proves rightful ownership of the traded token, and sig _seller is the seller's digital signature.

Coin registration transaction:

where Pubkey _{buyer_coins} is the public key corresponding to the account holding the buyer's coins on the public cryptocurrency blockchain, ID _buyer is the user's ID on the private blockchain,

is the digital signature corresponding to the key that holds the coin on the public cryptocurrency blockchain, and sig _buyer is the buyer's digital signature.

Bit registration transaction:
|ID _collectable |Nr.Coins|sig _buyer |
where ID _collectable is the ID of the collectible the buyer wishes to acquire, NR.Coins is the number of coins the buyer has bid on the collectible, and sig _buyer is the potential buyer's signature. A private blockchain smart contract “locks” the token until the transaction is completed.

Direct Trade Token Transaction:
|ID _collectable |ID _buyer |ID _seller |Owner certificate _seller |Nr.Coins|sig _buyer |sig _seller |
where ID _collectable is the unique ID of the collectible whose token is being traded, ID _buyer is the unique ID of the user who wants to purchase the collectible token, and ID _seller is the ID of the collectible sold to the buyer. The owner certificate _seller is a document owned by the buyer certifying that he/she is the rightful owner of the token being traded, Nr.Coins is the number of coins transferred from the seller to the buyer, and sig _buyer and sig _seller are the digital signatures of the buyer and seller respectively, both of which are required for a successful transaction. A private blockchain smart contract “locks” the token until the transaction is completed.

One embodiment of the present disclosure includes a method that includes at least one of the following acts.
A) Registration of new collectibles, including one or more of the following:
1) A private blockchain receives a collectible registration transaction containing the collectible's fingerprint and the ID of the bank responsible for processing it.
2) Receive collectible verification transactions to prove the validity of collectibles by private blockchain. Collectible verification transactions include collectible ID, appraiser ID, and certificate of validity.
3) Receive a tokenization request by a private blockchain to create a new token for a given collectible. The transaction contains the ID of the collectible and the ID of the owner, as well as some tokens (shares) to create for this asset (ie, collectible).
B) exchange of tokens containing one or more of the following:
1) By private blockchain, receive either:
a. A direct trade transaction including the seller's, buyer's IDs, number of tokens, price, and recipient's key.
b. An auction opening transaction containing the seller's ID, the number of tokens to sell, and the recipient's key. Auction opening transactions receive bid transactions by a private blockchain, and a Simple Payment Verification (SPV) client ensures that each respective bid does not exceed the amount of coins held by the respective bidding user. verification, tallying bids, and notifying winners.
2) Receive regular outbound transactions to send coins from one address to another by the public blockchain.
3) Private blockchain receives transaction ID from coin exchange buyer and verifies exchange validity using smart contract SPV client.
4) Upon successful verification, finalize the auction/exchange by a private smart contract and change the owner of the token.

The method may involve adding a face template to the blockchain system using a face detector to accurately identify the owner.

The method may further include utilizing the object fingerprint to ensure a 1-1 mapping between the digital object and the physical object (eg, the collectible if the collectible is a physical object).

One embodiment of the present disclosure provides a method for securing inter-blockchain transactions. An inter-blockchain transaction involves a first transfer on a permissioned blockchain and a second transfer on a permissionless public blockchain. The method includes first, on a permissioned blockchain, processor-executable program code that, when executed by a permissioned blockchain processing circuit, causes the permissioned blockchain processing circuit to perform a program function on the permissioned blockchain. Can include instantiating. The permissioned blockchain processing circuit then performs the following steps:
- receiving from a first user application a registration request comprising a first permissioned blockchain public key and a first non-permissioned blockchain public key, wherein the first permissioned blockchain public key is receiving the first permissionless blockchain public key is valid on the permissionless blockchain, and the first permissionless blockchain public key is valid on the permissionless public blockchain;
- receiving from a second user application a second registration request comprising a second permissioned blockchain public key and a second permissionless blockchain public key, the second permissioned blockchain disclosure; receiving the key is valid on a permissioned blockchain and the second permissionless blockchain public key is valid on a permissionless public blockchain;
- from the first user application, receiving a transaction identification, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification identifying the first and second identifying and receiving a permissionless blockchain public key for
- verifying completion of the first transfer transaction using the transaction identification;
- in response to verifying the completion of the first transfer transaction, executing a second transfer transaction on the permissioned blockchain, the second transfer transaction from the second permissioned blockchain public key; and performing with transfer to the first permissioned blockchain public key.

The method also verifies a cryptocurrency balance held by the first permissionless blockchain public key on the permissionless public blockchain in response to receiving the registration request from the first user application. can also include Verifying a cryptocurrency balance held by a first permissionless blockchain public key on a permissionless public blockchain is performed by a first permissionless blockchain public key on a permissionless public blockchain. It can involve calling a Simple Payment Verification (SPV) client provided by a public blockchain to verify a cryptocurrency balance held. Verifying completion of the first transfer transaction can include calling an SPV client to retrieve information corresponding to the transaction identification.

The first transfer transaction may be a transfer of native cryptocurrency of the permissionless blockchain from the first permissionless blockchain public key to the second permissionless blockchain public key. The second transfer transaction may be a transfer of a token representing a share of the collectible from the second permissioned blockchain public key to the first permissioned blockchain public key.

The method may also include registering the collectible on a permissioned blockchain. Registering a collectible on the permissioned blockchain consists of generating a unique ID that uniquely identifies the collectible on the permissioned blockchain, and pairing the unique object fingerprint to the unique ID. , storing the unique ID and the unique object fingerprint in the permissioned blockchain.

A registration request received from the first user application may include a biometric commitment. A biometric commitment may be generated by randomizing a biometric ID and applying a hash function to the randomized biometric ID to generate a biometric commitment.

2. The method of claim 1, wherein the registration request received from the second user application may include a collectibles registration. A collectibles registry may include a certificate of authenticity that the collectible has been inspected by a professional appraiser. The certificate may be signed with a professional appraiser's biometric commitment.

One embodiment of the present disclosure provides a non-transitory processor-readable medium having processor-executable instructions stored thereon for performing a method for securing inter-blockchain transactions, wherein the inter-blockchain transactions are permissioned blocks. It involves a first transfer on-chain and a second transfer on a permissionless public blockchain. The method includes receiving from a first user application a registration request including a first permissioned blockchain public key and a first non-permissioned blockchain public key. The first permissioned blockchain public key is valid on the permissioned blockchain and the first permissionless blockchain public key is valid on the permissionless public blockchain. The method further includes receiving from a second user application a second registration request including a second permissioned blockchain public key and a second non-permissioned blockchain public key. The second permissioned blockchain public key is valid on the permissioned blockchain and the second permissionless blockchain public key is valid on the permissionless public blockchain. The method also includes receiving a transaction identification from the first user application. The transaction identification identifies a first transfer transaction to be performed on the permissionless public blockchain, and the transaction identification identifies first and second permissionless blockchain public keys. Additionally, the method includes verifying completion of the first transfer transaction using the transaction identification; and performing A second transfer transaction involves transferring from the second permissioned blockchain public key to the first permissioned blockchain public key.

One embodiment of the present disclosure provides a system for securing inter-blockchain transactions. An inter-blockchain transaction involves a first transfer on a permissioned blockchain and a second transfer on a permissionless public blockchain. The system is receiving from a first user application a registration request including a first permissioned blockchain public key and a first non-permissioned blockchain public key, the first permissioned blockchain public key is valid on the permissionless blockchain and the first permissionless blockchain public key is valid on the permissionless public blockchain . The processing circuitry is also for receiving, from a second user application, a second registration request including a second permissioned blockchain public key and a second non-permissioned blockchain public key; A type blockchain public key is valid on a permissioned blockchain, and a second permissionless blockchain public key is valid on a permissionless public blockchain, configured to receive be. Further, the processing circuitry is to receive a transaction identification from the first user application, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification: configured to identify and receive first and second permissionless blockchain public keys; Additionally, the processing circuitry verifies completion of the first transfer transaction using the transaction identification and, in response to verifying the completion of the first transfer transaction, performs a second transfer transaction on the permissioned blockchain. and performing a transfer transaction. A second transfer transaction involves transferring from the second permissioned blockchain public key to the first permissioned blockchain public key.

In order to be able to trade shares of collectibles (eg, represented by tokens), prospective users obtain valid identifications for use in the system. A prospective user can obtain such identification by registering through a user application.

Figure 1 shows the user registration process. The registration process begins with the user application making a commitment (eg, a randomized hash) for the user's identity data. In the user registration process shown in Figure 1, a user creates a biometric identity at 102 with a biometric solution, e.g., running on a mobile device or distributed between a mobile device and the cloud. use the application. The process then creates a commitment at 104 . Creating a commitment at 104, for example, receives the biometric ID created at 102, randomizes the biometric ID (eg, by preprocessing the biometric ID with a random salt value), then It can involve applying a hash function to the randomized biometric ID to generate a commitment in the form of a randomized hash of the metric ID. The user then issues a user registration transaction at 106 and the smart contract records the commitment made at 104 to a shared ledger provided by permissioned blockchain 110 . The smart contract also generates a user ID from the user's public key (eg, by hashing the public key and taking the first 10 bytes).

According to some embodiments, registering and evaluating the authenticity of a collectible is a mandatory step to digitizing it and storing it on the blockchain.

Figure 2 shows the collectibles registration process. The collectible registration process illustrated in FIG. 2 utilizes object fingerprint software 202 (eg, NEC object fingerprint software) to generate a unique fingerprint 204 for collectible 206 . The financial institution 208 then has the collectibles in custody and initiates a collectibles registration transaction at 210 to store the fingerprint on the permissioned blockchain 110 . A collectible registration transaction is signed by the financial institution holding the collectible. In the collectibles registration transaction, the smart contract generates a unique ID that uniquely identifies the collectible in the system, pairs the fingerprint to the ID, and stores both on the permissioned blockchain. Storing the fingerprints on the blockchain ensures tamper-proof fingerprints and thus ensures that the ownership of physical collectibles is also tamper-proof.

According to some embodiments, collectibles cannot be traded on the platform until a trusted appraiser proves their authenticity. Such a step can prevent counterfeiting.

Figure 3 illustrates the collectible verification process. A trusted appraiser 302 inspects the collectible 206 to determine its authenticity. If the collectible passes inspection, the collectible is inspected by an expert to produce a certificate 304 certifying authenticity. At 306, the appraiser then issues and digitally signs the collectible verification transaction, including the certificate to the permissioned blockchain 110. Signing the collectible verification transaction may include signing with an appraiser's biometric commitment. The smart contract can then add the certificate to the collectible information stored on the permissioned blockchain 110 .

Tokenization is the process of converting collectibles into digital tokens. Tokens are digital units of value that can be individually traded within the platform. A collectible's total value is the total value of its tokens. Tokenization enables fractional ownership of collectibles, making them affordable to a wider range of users, who do not need to own the entire collectible to benefit from its increasing value over time. Rather, you only need to own a share of the collectibles represented by one or more tokens.

Figure 4 shows the collectibles tokenization process. The financial institution 208 holding the collectible 206 assesses its market value and issues the desired number of tokens 402 . Tokens 402 may, for example, be represented in cryptocurrency and have a value equal to the value of the collectible as a whole. Tokens 402 can then be traded on the platform, and users 406 can browse available collectibles and purchase tokens at 408 . The initial number of tokens and their value can be adjusted based on the supply/demand model, similar to stock exchanges. Financial institution 208 may also issue additional tokens at any time (if it retains some share of ownership of the collectibles following the initial issuance of tokens) and adjust their prices. be able to. Once the number of tokens and the price of each token is established, the financial institution 208 issues a collectible tokenized transaction at 404 to make the tokens available for trading on the platform. A smart contract manages each collectible's tokens and can track their quantity, value, and number of units sold.

FIG. 5 illustrates a workflow by which trading of tokens can be performed via a permissioned blockchain, such as permissioned blockchain 110 . Figure 5 shows that the seller has a private, i.e., token registered on a permissioned blockchain, and the buyer has a public cryptocurrency coin, i.e., a cryptocurrency balance held on a separate public blockchain, and the token Consider a scenario in which you are interested in purchasing A setup may be used where coins are based on a public blockchain, tokens are held on a permissioned private blockchain (ie, private chain), and private smart contract SCs handle tokens and exchanges. The workflow shown in Figure 5 includes:

Register coins.
1. In step (1), the buyer (i.e., the buyer-wallet application) sends two public keys, namely one public chain public key or crypto public key Pubkey _{buyer_coins} holding cryptocurrency coins, and a private chain Load a wallet with one registered private chain public key Pubkey _buyer .
2. In step (2), the buyer initiates registration of cryptographic public keys Pubkey _{buyer_coins} on the private chain to prove ownership of an amount of public cryptocurrency. To do so, the buyer issues a coin registration transaction.
3. ~ 5. Using the SPV client provided by the public chain where the ownership of the public cryptocurrency is recorded (and the cryptographic public key Pubkey _{buyer_coins} is valid), the smart contract SC is executed on the public chain Queries the cryptocurrency balance held by the cryptographic public key Pubkey _{buyer_coins} (step 3) and then successfully receives the held balance (step 4). Upon successful return, the balance and current date will be saved in the Pubkey _buyer 's account to complete the registration of the cryptographic public key Pubkey _{buyer_coins} on the private chain.
6. A confirmation of successful registration of the cryptographic public key Pubkey _{buyer_coins} to the private chain is returned to the buyer (i.e. buyer-wallet application).

sell tokens.
7. In step (7), the seller (ie the seller-wallet application) loads a wallet containing a second private chain public key Pubkey _seller that holds tokens on the private chain.
8. In step (8), the seller generates a new cryptographic public key Pubkey _{seller_coins} for the public cryptocurrency used to receive coins resulting from selling tokens held by the seller. A seller can be, for example, the financial institution 208 of FIGS. 1-4.
9. In step (9), the seller submits a new auction registration transaction identifying the tokens to sell, the currency accepted, and the address or public key to which the purchase funds should be sent. A private blockchain smart contract SC "locks" the token until the transaction is completed.
10. In step (10), interested buyers (ie, buyer-wallet applications) submit bids to the private chain smart contract SC.
11. In step (11), the private chain smart contract SC verifies the cryptocurrency balance held by the registered cryptographic public key Pubkey _{buyer_coins} and accepts the transaction if the balance is equal to or greater than the bid.
12. At step (12), the buyer (ie, the buyer-wallet application) is then notified that the bid has been accepted. The bidding process potentially continues with multiple buyers until the end of the auction.
13. At step (13), the smart contract SC then tallies the bids and notifies the auction winner (in this case the buyer, ie the buyer-wallet application). According to some embodiments, the actions of steps 9-13 are optional if the seller already knows the buyer.
14. In step (14), the buyer initiates a new transaction (if steps 9-13 did not occur, this would be a direct token transaction), equal to the bid amount, and public chain with the cryptographic public key Pubkey _{buyer_coins} . Send the cryptocurrency balance held above to the seller's public key Pubkey _{seller_coins} on the public blockchain.
15. In step (15), the buyer further sends to the private chain smart contract SC the transaction ID TxID of the transaction in which the cryptocurrency balance equal to the bid amount was sent to the seller.
16.~18.Using the SPV client, the smart contract SC verifies the transaction with the ID TxID on the public cryptocurrency blockchain (step 16), and if the result is successful (i.e. the SPV confirms that the transaction TxID is If properly executed, i.e. added to the public cryptocurrency blockchain can be verified), the smart contract SC transfers the seller's token to the buyer's private chain public key Pubkey _buyer (step 17 ), then notify the seller that the auction is complete and the token sale was successful.

The transaction workflow illustrated in Figure 5 enables the exchange of shares of collectibles represented by cryptocurrency tokens held on a separate public chain, via a private chain. This allows the transactional workflow shown in Figure 5 to improve interoperability of multiple blockchains and the first exchange on a private chain (i.e. transfer of tokens representing shares of collectibles from seller to buyer). and a second exchange on a separate public chain (i.e. transfer of cryptocurrency balance from buyer to seller) that can guarantee both security and reliability of transactions. Accordingly, the transactional workflows provided by the present disclosure improve both functionality and security of blockchain transactions, particularly transactions executed concurrently on multiple different blockchains.

Referring to FIG. 6, processing system 900 includes one or more processors 902, memory 904, one or more input/output devices 906, one or more sensors 908, one or more user interfaces 910, and One or more actuators 912 may be included. Processing system 900 can represent each computing system disclosed herein.

Processor 902 may include one or more separate processors, each having one or more cores. Each separate processor may have the same or different structure. Processor 902 may be one or more central processing units (CPUs), one or more graphics processing units (GPUs), circuits (eg, application specific integrated circuits (ASICs)), digital signal processors (DSPs), etc. can include Processor 902 can be mounted on a common board or multiple different boards.

Processor 902 performs a function, method or action when at least one of one or more of the separate processors is capable of performing the action embodying the function, method or action. configured to perform (eg, configured to provide performance of a function, method, or action); Processor 902 performs functions, methods, for example, by executing code (eg, interpreting scripts) stored on memory 904 and/or traffic data through one or more ASICs. , or may perform operations embodying operations. Processor 902, and thus processing system 900, can be configured to automatically perform any and all functions, methods, and acts disclosed herein. Accordingly, processing system 900 may be configured to implement any (eg, all) of the protocols, devices, mechanisms, systems, and methods described herein.

For example, when this disclosure states that a method or device performs task "X" (or task "X" is to be performed), such statements imply that processing system 900 performs task "X". It should be understood that it discloses that it can be configured to Processing system 900 is configured to perform a function, method, or operation at least when processor 902 is configured to do so.

Memory 904 can include volatile memory, nonvolatile memory, and any other medium capable of storing data. Volatile memory, non-volatile memory, and any other type of memory may each include multiple different memory devices located at multiple distinct locations, each having a different structure. Memory 904 can include remote host (eg, cloud) storage.

Examples of memory 904 include RAM, ROM, flash memory, non-transitory computer readable media such as EEPROM, optical storage discs of any kind such as DVDs, Blu-Ray discs, magnetic storage, holographic storage. , HDD, SSD, any medium that can be used to store program code in the form of instructions or data structures, and the like. Any and all of the methods, functions, and operations described herein are embodied entirely in the form of tangible and/or non-transitory machine-readable code (eg, interpretable scripts) stored in memory 904. be able to.

Input/output devices 906 can include any components for trafficking data, such as ports, antennas (ie, transceivers), printed conductive paths, and the like. The input/output device 906 can enable wired communication via USB®, DisplayPort®, HDMI®, Ethernet, and the like. Input/output devices 906 can enable electronic, optical, magnetic, and holographic communication with suitable memory 906 . The input/output device 906 may be WiFi (registered trademark), Bluetooth (registered trademark), cellular (e.g., LTE (registered trademark), CDMA (registered trademark), GSM (registered trademark), WiMax (registered trademark), NFC (registered trademark) )), which can enable wireless communication via GPS, etc. Input/output devices 906 can include wired and/or wireless communication paths.

Sensors 908 can capture physical measurements of the environment and report them to processor 902 . User interface 910 may include a display, physical buttons, speakers, microphone, keyboard, and the like. Actuators 912 can allow processor 902 to control mechanical forces.

Processing system 900 can be distributed. For example, some components of processing system 900 may reside on a remote hosted network service (eg, a cloud computing environment), while other components of processing system 900 reside on a local computing system. can do. The processing system 900 can have a modular design, with some modules containing multiple features/functions shown in FIG. For example, an I/O module may include volatile memory and one or more processors. As another example, individual processor modules may include read-only memory and/or local caches.

While the subject matter of the disclosure has been illustrated and described in detail in the drawings and foregoing description, such illustration and description are to be considered illustrative or exemplary and not restrictive. Any statements made herein that characterize the invention are also to be considered illustrative or exemplary and not limiting, as the invention is defined by the claims. It should be understood that those skilled in the art can make changes and modifications within the scope of the disclosure, which may include any combination of features from the different embodiments described above.

The terms used in the claims should be interpreted to have their broadest reasonable interpretation consistent with the foregoing description. For example, use of the articles "a" or "the" to introduce an element should not be construed as excluding a plurality of elements. Similarly, unless it is clear from the context or the foregoing description that only one of A and B is intended, the statement "or" does not exclude "A and B." , should be interpreted as inclusive. Further, references to "at least one of A, B, and C" are to be interpreted as one or more of the group consisting of A, B, and C, where A, B, and It should not be construed as requiring at least one of each of the listed elements A, B, and C, regardless of whether C is related as a category or otherwise. Further, references to "A, B, and/or C" or "at least one of A, B, or C" refer to any singular entity from the elements listed, e.g., A and B etc., or any subset from the listed elements, or the entire list of elements A, B and C.

110 Permissioned Blockchain
202 Object Fingerprint Software
204 fingerprint
206 Collectibles
208 Financial Institutions
302 Trusted Appraiser
304 certificate
402 tokens
900 processing system
902 processor
904 memory
906 input/output devices
908 sensor
910 User Interface
912 Actuator

Claims (15)

A method for securing an inter-blockchain transaction, the inter-blockchain transaction involving a first transfer on a permissioned blockchain and a second transfer on a permissionless public blockchain. , the method is
By the permission type blockchain processing circuit,
receiving from a first user application a registration request comprising a first permissioned blockchain public key and a first non-permissioned blockchain public key, wherein said first permissioned blockchain public key is: is valid on the permissioned blockchain, and the first permissionless blockchain public key is valid on the permissionless public blockchain;
receiving from a second user application a second registration request comprising a second permissioned blockchain public key and a second permissionless blockchain public key, wherein said second permissioned blockchain public a key is valid on the permissioned blockchain and the second permissionless blockchain public key is valid on the permissionless public blockchain;
receiving from the first user application a transaction identification, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification identifying and receiving first and second permissionless blockchain public keys;
verifying completion of the first transfer transaction using the transaction identification;
executing a second transfer transaction on the permissioned blockchain in response to verifying the completion of the first transfer transaction, wherein the second transfer transaction is performed on the second permissioned block; with a transfer from a chain public key to said first permissioned blockchain public key; verifying a cryptocurrency balance held by said first permissionless blockchain public key on said permissionless public blockchain in response to said receiving said registration request from said first user application; 2. The method of claim 1, further comprising steps. The step of verifying the cryptocurrency balance held by the first permissionless blockchain public key on the permissionless public blockchain is performed by the first permissionless public blockchain on the permissionless public blockchain. 3. The method of claim 2, comprising invoking a Simple Payment Verification (SPV) client to verify the cryptocurrency balance held by a type blockchain public key. 4. The method of claim 3, wherein verifying the completion of the first transfer transaction comprises calling the SPV client to retrieve information corresponding to the transaction identification. wherein said first transfer transaction is a transfer of native cryptocurrency of said permissionless blockchain from said first permissionless blockchain public key to said second permissionless blockchain public key. The method of paragraph 1. 6. The method of claim 5, wherein the second transfer transaction is the transfer of tokens representing shares of collectibles from the second permissioned blockchain public key to the first permissioned blockchain public key. Method. 7. The method of claim 6, wherein the method further comprises registering the collectible on the permissioned blockchain. registering the collectible on the permissioned blockchain generates a unique ID that uniquely identifies the collectible on the permissioned blockchain; and assigning a unique object fingerprint to the unique ID. 8. The method of claim 7, comprising pairing and storing the unique ID and the unique object fingerprint on the permissioned blockchain. 2. The method of claim 1, wherein the registration request received from the first user application includes a biometric commitment. 10. The method of claim 9, wherein the biometric commitment is generated by randomizing a biometric ID and applying a hash function to the randomized biometric ID to generate the biometric commitment. 2. The method of claim 1, wherein the registration request received from the second user application includes a collectibles registration. 12. The method of claim 11, wherein the collectibles registry includes a certificate of authenticity certifying that the collectibles have been inspected by a professional appraiser. 13. The method of claim 12, wherein the certificate is signed with the professional appraiser's biometric commitment. A non-transitory processor-readable medium having stored therein processor-executable instructions for performing a method for securing an inter-blockchain transaction, wherein the inter-blockchain transaction is a first transaction on a permissioned blockchain. with a transfer and a second transfer on a permissionless public blockchain, the method comprising:
receiving from a first user application a registration request comprising a first permissioned blockchain public key and a first non-permissioned blockchain public key, wherein said first permissioned blockchain public key is: is valid on the permissioned blockchain, and the first permissionless blockchain public key is valid on the permissionless public blockchain;
receiving from a second user application a second registration request comprising a second permissioned blockchain public key and a second permissionless blockchain public key, wherein said second permissioned blockchain public a key is valid on the permissioned blockchain and the second permissionless blockchain public key is valid on the permissionless public blockchain;
receiving from the first user application a transaction identification, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification identifying and receiving first and second permissionless blockchain public keys;
verifying completion of the first transfer transaction using the transaction identification;
executing a second transfer transaction on the permissioned blockchain in response to verifying the completion of the first transfer transaction, wherein the second transfer transaction is performed on the second permissioned block; with a transfer from a chain public key to said first permissioned blockchain public key. A system for securing an inter-blockchain transaction, the inter-blockchain transaction involving a first transfer on a permissioned blockchain and a second transfer on a permissionless public blockchain. , said system is
Receiving from a first user application a registration request including a first permissioned blockchain public key and a first non-permissioned blockchain public key, wherein the first permissioned blockchain public key is: valid on the permissioned blockchain, and the first permissionless blockchain public key is valid on the permissionless public blockchain;
Receiving from a second user application a second registration request including a second permissioned blockchain public key and a second non-permissioned blockchain public key, wherein said second permissioned blockchain disclosure receiving a key is valid on the permissioned blockchain and the second permissionless blockchain public key is valid on the permissionless public blockchain;
receiving from the first user application a transaction identification, the transaction identification identifying a first transfer transaction to be performed on the permissionless public blockchain, the transaction identification identifying and receiving first and second permissionless blockchain public keys;
verifying completion of the first transfer transaction using the transaction identification;
executing a second transfer transaction on the permissioned blockchain in response to verifying the completion of the first transfer transaction, wherein the second transfer transaction is performed on the second permissioned block; with a transfer from a chain public key to said first permissioned blockchain public key, and a processor circuit configured to perform:

Images