# US 2019/0172026 A1 · Cross blockchain secure transactions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0172026 A1 - Document ID: US20190172026A1 - Status: Published application - Kind: A1 - Application number: 16/206,713 - Filed: 2018-11-30 - Published: 2019-06-06 - Earliest claimed: 2017-12-02 - Applicants: Alchemy Limited LLC - Inventors: Peter Joseph Vessenes; Philip Hofer - Web page: https://patentgrep.com/patent/US20190172026A1 ## CPC - G06Q 20/0658: {e-cash managed locally} - G06Q 20/065: {using e-cash} - G06Q 20/363: {with the personal data of a user} - G06Q 20/3674: {involving authentication} - G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending} - G06Q 20/381: {Currency conversion} - H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - G06Q 2220/00: Business processing using cryptography - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - 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 - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Disclosed are computing devices, systems, methods to operate a cross blockchain secure token transaction engine to identify a set of one or more tokens of a first blockchain, lock the identified set of the one or more tokens of the first blockchain, and generate, based upon the locked set of the one or more tokens, a set of one or more tokens of a second blockchain, where the set of one or more tokens of the second blockchain are to be subsequently converted to tokens of the first blockchain based upon the locked set of tokens of the first blockchain. ## Claims ### Claim 1 One or more computer-readable media comprising instructions that cause a computer device, in response to execution of the instructions by one or more processors of the computer device, to operate a cross blockchain secure token transaction engine to: identify a set of one or more tokens of a first blockchain; lock the identified set of the one or more tokens of the first blockchain; and generate, based upon the locked set of the one or more tokens, a set of one or more tokens of a second blockchain; wherein the set of one or more tokens of the second blockchain are to be subsequently converted to tokens of the first blockchain based upon the locked set of tokens of the first blockchain. ### Claim 2 (depends on 1) The one or more computer-readable media of claim 1, wherein to lock the identified set of tokens of the first blockchain is further to: identify a pays to script hash (P2SH) address associated with the identified set of the one or more tokens of the first blockchain; and lock the identified set of the one or more tokens of the first blockchain to the identified P2SH address. ### Claim 3 (depends on 2) The one or more computer-readable media of claim 2, wherein the P2SH address is specified by a smart contract. ### Claim 4 (depends on 1) The one or more computer-readable media of claim 1, wherein to generate one or more tokens of the second blockchain is further to: verify ownership of the tokens of the locked identified set of tokens of the first blockchain by a user; and verify the tokens of the locked identified group of tokens of the first blockchain have been stored to a wallet of the user. ### Claim 5 (depends on 4) The one or more computer-readable media of claim 4, wherein the wallet is to store an indication of one or more tokens of the first blockchain and of one or more tokens of the second blockchain owned by a user. ### Claim 6 (depends on 4) The one or more computer-readable media of claim 4, wherein the wallet includes address pairs corresponding to the first blockchain and the second blockchain, wherein the address pairs are associated with a public key. ### Claim 7 (depends on 1) The one or more computer-readable media of claim 1, wherein the computer device is further caused to: identify a set of one or more tokens of the second blockchain; based upon the identified set of one or more tokens of the second blockchain, identify a subset of tokens of the locked set of tokens of the first blockchain; burn the identified set of tokens of the second block chain; and unlock the subset of the set tokens of the locked group of tokens on the first blockchain, based upon the identified group of tokens of the second blockchain. ### Claim 8 (depends on 7) The one or more computer-readable media of claim 7, the computer device is further caused to store an indication of the unlocked subset of the set of one or more tokens of the first blockchain in a wallet. ### Claim 9 (depends on 7) The one or more computer-readable media of claim 7, wherein to burn the identified set of tokens of the second block chain is further to: receive a plurality of responses, respectively, from a plurality validator nodes, wherein a response includes an indication of a verification of a burn event; and based upon the received plurality of responses, determine whether the identified set of tokens of the second block chain are to be burned. ### Claim 10 (depends on 9) The one or more computer-readable media of claim 9, wherein a validator node maintains a list of unspent transaction outputs in the first blockchain based upon the set of one or more tokens of the second blockchain. ### Claim 11 (depends on 9) The one or more computer-readable media of claim 9, wherein to determine whether the identified set of tokens of the second block chain are to be burned is based upon a Raft consensus algorithm for unspent transaction outputs tracking. ### Claim 12 (depends on 1) The one or more computer-readable media of claim 1, wherein the first blockchain is a Bitcoin blockchain, and the second blockchain is an Ethereum blockchain. ### Claim 13 (depends on 1) The one or more computer-readable medium of claim 1, wherein the one or more tokens of the first blockchain are one or more Bitcoins, and wherein the one or more tokens of the second blockchain are ERC20 compatible tokens for the Ethereum blockchain. ### Claim 14 (depends on 1) The one or more computer-readable media of claim 1, wherein a token includes a portion of a token. ### Claim 15 A computer-implemented method, comprising: identifying a set of one or more tokens of a first blockchain; locking the identified set of the one or more tokens of the first blockchain; and generating, based upon the locked set of the one or more tokens, a set of one or more tokens of a second blockchain; wherein the set of one or more tokens of the second blockchain are to be subsequently converted to tokens of the first blockchain based upon the locked set of tokens of the first blockchain. ### Claim 16 (depends on 15) The computer-implemented method of claim 15, wherein locking the identified set of tokens of the first blockchain further includes: identifying a P2SH address associated with the identified set of the one or more tokens of the first blockchain; and locking the identified set of the one or more tokens of the first blockchain to the identified P2SH address. ### Claim 17 (depends on 15) The computer-implemented method of claim 15, wherein the address is specified by a smart contract. ### Claim 18 (depends on 15) The computer-implemented method of claim 15, wherein generating one or more tokens of the second blockchain further includes: verifying ownership of the tokens of the locked identified set of tokens of the first blockchain by a user; and verifying the tokens of the locked identified group of tokens of the first blockchain have been stored to a wallet of the user. ### Claim 19 (depends on 15) The computer-implemented method of claim 15, wherein the wallet is to store an indication of one or more tokens of the first blockchain and of one or more tokens of the second blockchain owned by a user. ### Claim 20 (depends on 15) The computer-implemented method of claim 15, wherein the wallet includes address pairs corresponding to the first blockchain and the second blockchain, wherein the address pairs are associated with a public key. ### Claim 21 (depends on 15) The computer-implemented method of claim 15, further including: identifying a set of one or more tokens of the second blockchain; based upon the identified set of one or more tokens of the second blockchain, identifying a subset of tokens of the locked set of tokens of the first blockchain; burning the identified set of tokens of the second block chain; and unlocking, based upon the identified group of tokens of the second blockchain, the subset of the set tokens of the locked group of tokens on the first blockchain. ### Claim 22 (depends on 21) The computer-implemented method of claim 21, further including storing an indication of the unlocked subset of the set of one or more tokens of the first blockchain in the wallet. ### Claim 23 (depends on 21) The computer-implemented of claim 21, wherein burning the identified set of tokens of the second block no chain further includes: receiving a plurality of responses, respectively, from a plurality validator nodes, wherein a response includes an indication of a verification of a burn event; and based upon the received plurality of responses, determining whether the identified set of tokens of the second block chain are to be burned. ### Claim 24 (depends on 23) The computer-based method of claim 23, wherein a validator node is to maintain a list of unspent transaction outputs based upon the set of one or more tokens of the second blockchain. ### Claim 25 (depends on 24) The computer-based method of claim 24, wherein determining whether the identified set of tokens of the second block chain are to be burned is based upon a Raft consensus algorithm for unspent transaction outputs tracking. ### Claim 26 (depends on 15) The computer-based method of claim 15, wherein the first blockchain is a Bitcoin blockchain, and the second blockchain is an Ethereum blockchain. ### Claim 27 (depends on 15) The computer-based method of claim 15, wherein the one or more tokens of the first blockchain are one or more Bitcoins, and wherein the one or more tokens of the second blockchain are ERC20 compatible tokens for the Ethereum blockchain. ### Claim 28 (depends on 15) The computer-based method of claim 15, wherein a token includes a portion of a token. ### Claim 29 (depends on 15) The computer-based method of claim 15, wherein the method is performed by one or more smart contracts.