# US 2025/0061446 A1 · Method and system for escrow-free atomic cross-chain swap with recipient's confirmation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0061446 A1
- Document ID: US20250061446A1
- Status: Published application
- Kind: A1
- Application number: 18/537,839
- Filed: 2023-12-13
- Published: 2025-02-20
- Earliest claimed: 2023-08-16
- Assignees: Jinan University
- Applicants: Jinan University
- Inventors: Yongdong WU; Tong LI; Shishi HUANG; Jiao LU; Jian WENG; Ming LI; Zhiquan LIU
- Web page: https://patentgrep.com/patent/US20250061446A1

## CPC

- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/223: {based on the use of peer-to-peer networks}
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3829: {involving key management}
- G06Q 20/401: {Transaction verification}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- 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

A system for enabling escrow-free, secure, and convenient atomic asset swaps between blockchains are provided. In detail, when any group of users reach an agreement on the content of cross-chain asset swap transactions, each participant creates an individual signature on the content of each transaction, employs a reversible signature aggregate function to produce an aggregate signature from all his/her individual signatures, and optionally generates a proof to prove the relationship between the aggregated signature and the transaction contents. Sequentially, all the participants exchange these aggregated signatures and optional proofs. Once a participant publishes one of his/her individual signature, the other parties can use both signatures—one from the sender and the other from the recipient—to construct a complete transaction. Once a transaction is broadcast, its corresponding transactions are constructed, and broadcast. Upon all transactions being confirmed by the blockchain nodes or miners, the asset swap between participants is completed.

## Claims

### Claim 1

A method for asset swapping between blockchains supporting recipient's confirmation in a transaction, comprising:
negotiating to determine content of asset swapping transactions;
producing individual signatures on the transaction content by each participant;
creating aggregate signatures from the individual signatures by each participant;
exchanging the aggregate signatures between the participants;
verifying the aggregate signatures; if negative, quit;
constructing a first transaction by a second participant;
broadcasting the first transaction by the second participant;
constructing a second transaction by a first participant;
broadcasting the second transaction by the first participant;
validating the broadcast transactions by blockchain node or miners.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the step that participants negotiate and determine the transaction contents comprise a locking script of the referenced previous transaction, transaction amounts, a flag indicating whether a recipient's signature is comprised in the transaction.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the participants sign the transaction contents according to a signature scheme comprising Boneh-Lynn-Shacham (BLS) or Schnorr signature scheme.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the aggregate signature is generated using a reversible signature aggregate function to secure against forgery.

### Claim 5 (depends on 4)

The method according to claim 4, wherein the reversible signature aggregate function is constructed with a BLS signature scheme given that public keys are authenticated.

### Claim 6 (depends on 4)

The method according to claim 4, wherein the reversible signature aggregate function is constructed with a Schnorr signature scheme given that public keys are authenticated, and each ephemeral public key for signing a transaction content is fixed in a swap process.

### Claim 7 (depends on 1)

The method according to claim 1, wherein a swap process quits if the verification of the aggregate signature is negative.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the operation of constructing the first transaction comprises
means for a first party to send an individual signature on the transaction content to a second party; if the individual signature is for payment, a signature aggregation of the first party is allowed to be optional;
means for the second party to recover all the individual signatures of the first party;
means for the second party to construct a transaction comprising the transaction content in favor of the second party and its individual signatures from all the parties.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the operation of constructing the second transaction comprises:
means for a first party to verify the first transaction; if a verification result is negative, the swap process is terminated;
means for the first party to recover all the individual signatures of a second party;
means for the first party to construct a transaction comprising the transaction content in favor of the first party and its individual signatures from all the parties.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the operation of validating the transaction comprises:
upon receiving the transaction, wherein the blockchain miners check a format of the transaction according to a blockchain specification;
verifying, by the miners, the signature from a transaction payer; if a verification result is negative, the transaction is rejected;
verifying, by the miners, the signature from a transaction payee if a flag is set; if a verification result is negative, the transaction is rejected;
packing, by the miners, the accepted transaction into a block and broadcasting the block to a blockchain network.

### Claim 11

A system for facilitating asset swapping between blockchains, comprising:
a module for participants to negotiate and determine the transaction content;
a module for participants to use their private keys to sign the transaction content on blockchains to provide individual signatures;
a module for generating aggregate signatures from the individual signatures;
a module for carrying out verification on the aggregate signature;
a module for constructing a first transaction;
a module for broadcasting the first transaction on the blockchain;
a module for constructing a second transaction;
a module for broadcasting the second transaction on the blockchain;
a module for validating the transactions.

### Claim 12 (depends on 11)

The system according to claim 11, wherein the negotiation on the transaction contents is off-chain.

### Claim 13 (depends on 11)

The system according to claim 11, wherein the transaction content comprise information related to a locking script of a referenced previous transaction, a transaction amount, a flag indicating whether a recipient's signature is comprised in the transaction, and other relevant information.

### Claim 14 (depends on 11)

The system according to claim 11, wherein the individual signature is produced with a homomorphic signature scheme, wherein an output is either immutable due to some restrictions or deterministic.

### Claim 15 (depends on 11)

The system according to claim 11, wherein the aggregate signature is produced from the individual signatures from the same signer using a reversible signature aggregate function.

### Claim 16 (depends on 15)

The system according to claim 15, wherein the reversible signature aggregate function is secure against signature forgery, wherein the reversible signature aggregate function is constructed from BLS or half-aggregated Schnorr signature scheme.

### Claim 17 (depends on 11)

The system according to claim 11, wherein if an aggregate signature verification fails, the transaction is rejected.

### Claim 18 (depends on 11)

The system according to claim 11, wherein the operation of constructing the first transaction comprises:
sending, by a first party, an individual signature on the transaction content to a second party; if the individual signature is for payment, a signature aggregation of the first party is allowed to be optional;
recovering, by the second party, all the individual signatures of the first party;
constructing a transaction comprising the transaction content in favor of the second party and its individual signatures from all the parties.

### Claim 19 (depends on 11)

The system according to claim 11, wherein the operation of constructing the second transaction comprises:
verifying, by a first party, the first transaction; if negative, a swap process is terminated;
recovering, by the first party, all the individual signatures of a second party;
constructing a transaction comprising the transaction content in favor of the first party and its individual signature from all the parties.

### Claim 20 (depends on 11)

The system according to claim 11, wherein the operation of verifying the transaction comprises:
upon receiving the transaction, wherein the blockchain miners check a format of the transaction according to a blockchain specification;
verifying, by the miners, the signature from a transaction payer; if a verification result is negative, the transaction is rejected;
verifying, by the miners, the signature from a transaction payee if a flag is set; if a verification result is negative, the transaction is rejected;
packing, by the miners, the accepted transaction into a block, and broadcasting the block to a blockchain network.
