​
IBC

An Overview of the Inter-Blockchain Communication Protocol
This is a summary view of IBC v2 [Eureka]. For more comprehensive details, guides and more please visit the official Eureka documentation.

​
Core Data Structures

The Packet is the primary container for cross-chain communication in IBC v2. Each packet may wrap one or more application-specific Payload objects. 
// Main container sent between chains
interface Packet {
  sourceClientId: bytes;    // Client ID for destination chain (stored on source)
  destClientId: bytes;      // Client ID for source chain (stored on destination)
  sequence: uint64;         // Monotonically increasing nonce per client-pair
  timeout: uint64;          // UNIX timestamp (seconds) for packet expiry
  data: Payload[];          // Application payload(s)
}

// Application-specific data
interface Payload {
  sourcePort: bytes;  // Sending application identifier
  destPort: bytes;    // Receiving application identifier
  version: string;    // Application version
  encoding: string;   // MIME-type for decoding
  value: bytes;       // Opaque app data
}
Timeout is measured against the destination chain’s clock, not the source. This ensures safety even under clock drift.

​
Key On-Chain Components

A light client verifies the state of a counterparty chain with cryptographic proofs against trusted consensus.Each IBC client defines a ClientState (long-term parameters) and evolving ConsensusStates (snapshots). If consensus assumptions are violated, misbehaviour evidence can freeze the client.
A Merkle-proof-capable key–value store used for commitments.
ValuePath Format
Packet Commitment{sourceClientId}0x1{bigEndianUint64Sequence}
Packet Receipt{destClientId}0x3{bigEndianUint64Sequence}
Acknowledgement{destClientId}0x2{bigEndianUint64Sequence}
These standardized paths allow counterparties to verify packet existence, receipts, and acknowledgements.
The IBC handler exposes the standard functions for packet relay: SendPacket, RecvPacket, AcknowledgePacket, and TimeoutPacket.It enforces exactly-once delivery, ensures valid ordering (ordered, unordered, or ordered-allow-timeout), and dispatches packets to the correct application.
Applications must bind to unique portId values during initialization. Ports are referenced in every Payload for routing incoming packets.

​
Application Interface (ICS-26)

An IBC-enabled application must implement these callbacks to manage the packet lifecycle:
  • OnRecvPacket(...) – Executed on the destination chain to process incoming data. Must return an Acknowledgement, which may contain success data or an error.
  • OnAcknowledgePacket(...) – Executed on the source chain once an acknowledgement is verified. Provides acknowledgement data so the sending application can finalize or revert actions.
  • OnTimeoutPacket(...) – Executed on the source chain if a timeout occurs, enabling rollback or refunds.

​
Packet Lifecycle

Application data is wrapped into a Packet, assigned a sequence, and committed at the Packet Commitment path.
Destination chain verifies the packet commitment proof via its light client. Upon success, it stores a Receipt at the Packet Receipt path and invokes OnRecvPacket.
The receiving application returns an Acknowledgement. This is committed under the Acknowledgement path, allowing proof for the source chain.
Source chain verifies the acknowledgement proof, deletes the original commitment, and calls OnAcknowledgePacket on the sending application.
If the timeout elapses before a receipt exists on the destination chain, the source verifies this via proof of non-existence, deletes the commitment, and triggers OnTimeoutPacket.