IP Library Granted Patent US 12,380,439
Granted Patent B2
US 12,380,439 · App. 18/909,109 · Granted Aug 5, 2025

Authenticated cross-subnet communication

Inventors: Michael Edmond Kaplan (New York, NY); Stephen Buttolph (Brooklyn, NY); Daniel Laine (Jersey City, NY); Alexander Dunn (New York, NY); Cameron John Schultz (Chicago, IL); Aaron Buchwald (New York, NY); Patrick Robert O'Grady (Palo Alto, CA); Bernard Wong (Waterloo, CA)
Assignee: Ava Labs, Inc.
G06Q20/3825G06Q20/3829G06Q20/401H04L9/3247
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,380,439
App. No.
18/909,109
Granted
Aug 5, 2025
Kind
B2
Abstract

Various aspects of the subject technology relate to systems, methods, and machine-readable media for cross-chain communication in a blockchain platform. Various aspects may include accepting, at a first blockchain, a first transaction including a message and a message payload. Aspects may also include validating, at the first blockchain, the message by signing the message using signature keys of one or more validators in a first set of validators of the first blockchain. Aspects may also include generating an aggregate signature based on the signature keys of the one or more validators in a first set of validators. Aspects may also include submitting a second transaction on to a second blockchain, the second transaction including the message and the aggregate signature. Aspects may include validating, at the second blockchain, the second transaction based on a shared registry.

Claims (51)

1. A computer-implemented method for cross-chain communication, the method comprising:

receiving a transaction including a message and an aggregate signature, the aggregate signature generated based on signature keys corresponding to one or more validators of a source blockchain that signed the message;

identifying the one or more validators of the source blockchain based on the aggregate signature;

determining, based on a shared registry, whether the one or more validators comprise a stake threshold percentage of validators of the source blockchain;

validating the transaction based on the one or more validators comprising the stake threshold percentage of validators; and

transmitting a receipt message to the source blockchain indicating a successful delivery of the message.

2. The computer-implemented method of claim 1 , further comprising:

verifying the message has not been executed based on a message nonce associated with the message and included in a message payload for the transaction.

3. The computer-implemented method of claim 1 , further comprising transmitting a proof to the source blockchain based on at least an expiry timestamp included in the message and a message nonce, the proof indicating that the message has not been received and will never be received at the destination blockchain.

4. The computer-implemented method of claim 1 , further comprising generating the message at the source blockchain, wherein the transaction further includes a message payload at least identifying a destination address for the message.

5. The computer-implemented method of claim 1 , wherein the signature keys of the one or more validators are stored on a distributed ledger known to both the source blockchain and a destination blockchain.

6. The computer-implemented method of claim 1 , further comprising:

querying validators of the source blockchain; and

identifying, based on the querying, the one or more validators that signed the message from the transaction from the validators.

7. The computer-implemented method of claim 1 , wherein generating an aggregate signature further comprises:

generating a bit vector with canonical ordering of the one or more validators, wherein elements corresponding to indices of validators that signed the message is set to one (1) and elements corresponding to indices of validators that did not sign the message is set to zero (0).

8. The computer-implemented method of claim 1 , further comprising:

emitting an event based on the source blockchain accepting the transaction;

scanning, by an entity, a blockchain platform for events emitted in the blockchain platform, the event containing messages to be relayed to corresponding destinations; and

selecting, by the entity, the transaction based at least on a message payload.

9. The computer-implemented method of claim 1 , further comprising delivering the message to a destination, wherein the message is delivered to the destination no more than one time, the destination including a blockchain or an application on the blockchain.

10. The computer-implemented method of claim 1 , wherein the message specifies a fee required to successfully deliver the message to a corresponding destination.

11. A system for cross-chain communication in a blockchain platform, comprising:

one or more processors; and

a memory comprising instructions stored thereon, which when executed by the one or more processors, causes the one or more processors to perform:

receiving a transaction including a message and an aggregate signature, the aggregate signature generated based on signature keys corresponding to one or more validators of a source blockchain that signed the message;

identifying the one or more validators of the source blockchain based on the aggregate signature;

determining, based on a shared registry, whether the one or more validators comprise a stake threshold percentage of validators of the source blockchain;

validating the transaction based on the one or more validators comprising the stake threshold percentage of validators; and

transmitting a receipt message to the source blockchain indicating a successful delivery of the message.

12. The system of claim 11 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform verifying the message has not been executed based on a message nonce associated with the message and included in a message payload for the transaction.

13. The system of claim 11 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to transmit a proof to the source blockchain based on at least an expiry timestamp included in the message and a message nonce, the proof indicating that the message has not been received and will never be received at the destination blockchain.

14. The system of claim 11 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform generating the message at the source blockchain, wherein the transaction further includes a message payload at least identifying a destination address for the message.

15. The system of claim 11 , wherein the signature keys of the one or more validators are stored on a distributed ledger known to both the source blockchain and a destination blockchain.

16. The system of claim 11 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform:

querying validators of the source blockchain; and

identifying, based on the querying, the one or more validators that signed the message from the transaction from the validators.

17. The system of claim 11 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform:

generating a bit vector with canonical ordering of the one or more validators, wherein elements corresponding to indices of validators that signed the message is set to one (1) and elements corresponding to indices of validators that did not sign the message is set to zero (0).

18. The system of claim 11 , further comprising stored sequences of instructions, which when executed by the one or more processors, cause the one or more processors to perform:

emitting an event based on the source blockchain accepting the transaction;

scanning, by an entity, a blockchain platform for events emitted in the blockchain platform, the event containing messages to be relayed to corresponding destinations; and

selecting, by the entity, the transaction based at least on a message payload.

19. The system of claim 11 , further comprising stored sequences of instructions, which when executed by the one or more processors, cause the one or more processors to perform delivering the message to a destination, wherein the message is delivered to the destination no more than one time, the destination including a blockchain or an application on the blockchain.

20. The system of claim 11 , wherein the message specifies a fee required to successfully deliver the message to a corresponding destination.

21. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by one or more processors, cause the one or more processors to perform operations for cross-chain communication in a blockchain platform, comprising:

receiving a transaction including a message and an aggregate signature, the aggregate signature generated based on signature keys corresponding to one or more validators of a source blockchain that signed the message;

identifying the one or more validators of the source blockchain based on the aggregate signature;

determining, based on a shared registry, whether the one or more validators comprise a stake threshold percentage of validators of the source blockchain;

validating the transaction based on the one or more validators comprising the stake threshold percentage of validators; and

transmitting a receipt message to the source blockchain indicating a successful delivery of the message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2024
From: KAPLAN, MICHAEL EDMOND; BUTTOLPH, STEPHEN; LAINE, DANIEL; DUNN, ALEXANDER; SCHULTZ, CAMERON JOHN; BUCHWALD, AARON; O'GRADY, PATRICK ROBERT; WONG, BERNARD
To: AVA LABS INC.
Reel/Frame 068902/0139 →
Continuity (3)
Continuation In Part 18615932 · Mar 25, 2024
Provisional Application 63455919 · Mar 30, 2023
Related Publication 20250037120A1 · Jan 30, 2025
References Cited (31)
US 9473945B1 · Marquardt · 2016 [cited by examiner]
US 10484343B1 · Silberman et al. · 2019 [cited by applicant]
US 11317128B1 · Perkalsky · 2022 [cited by examiner]
US 20170155515A1 · Androulaki et al. · 2017 [cited by applicant]
US 20180145836A1 · Saur et al. · 2018 [cited by applicant]
US 20180308134A1 · Manning · 2018 [cited by examiner]
US 20190354518A1 · Zochowski · 2019 [cited by applicant]
US 20200081699A1 · Majed · 2020 [cited by examiner]
US 20200082126A1 · Brown · 2020 [cited by examiner]
US 20200104294A1 · Alas · 2020 [cited by examiner]
US 20200394648A1 · Blackshear · 2020 [cited by examiner]
US 20200396081A1 · Ansel · 2020 [cited by examiner]
US 20210036858A1 · Bruso · 2021 [cited by examiner]
US 20210049600A1 · Spector · 2021 [cited by examiner]
US 20210067345A1 · Shamai et al. · 2021 [cited by applicant]
US 20210097537A1 · Guo et al. · 2021 [cited by applicant]
US 20210097538A1 · Guo et al. · 2021 [cited by applicant]
US 20210099312A1 · Guo et al. · 2021 [cited by applicant]
US 20210119807A1 · Chen et al. · 2021 [cited by applicant]
US 20210150065A1 · Qiu · 2021 [cited by applicant]
US 20210304191A1 · O'Grady · 2021 [cited by applicant]
US 20210367793A1 · Shamai et al. · 2021 [cited by applicant]
US 20220094555A1 · Roy · 2022 [cited by examiner]
US 20220156725A1 · Iwama · 2022 [cited by examiner]
US 20220374886A1 · Micali et al. · 2022 [cited by applicant]
US 20220391474A1 · Assadipour · 2022 [cited by examiner]
US 20240187263A1 · Malepati · 2024 [cited by examiner]
US 20240241714A1 · Mahajan · 2024 [cited by examiner]
WO 2022109851A1 · 2022 [cited by applicant]
[No Author Listed] Coinbase. What is the Inter-Blockchain Communication Protocol (IBC)? Jan. 26, 2022, 11 pages. Retrieved from <https://www.coinbase.com/developer-platform/discover/dev-foundations/ibc-protocol> on Jun.… [cited by applicant]
International Search Report and Written Opinion for International Patent App. No. PCT/US2024/021375, mailed Jul. 12, 2024 (16 pages). [cited by applicant]