What an IBC Classic packet deadline and a confirmed timeout each tell you

Explainer3 min read

Read a fictional ICS-20 transfer on two chains. Tell an elapsed packet deadline from a confirmed source-chain timeout and an acknowledgement.

Brokzi compares a packet tag with a destination gate showing an elapsed deadline and a separate source-chain timeout record.
AI-assisted editorial illustration · Brokzi
On this page

An IBC Classic transfer can pass its packet deadline while the sending chain still shows no confirmed timeout. The deadline limits when the destination can receive the packet. A confirmed timeout is a separate result recorded on the sending chain. An acknowledgement follows a different path after the destination receives and processes the packet.

This example covers one ordinary ICS-20 token transfer between two fictional chains on a single unordered channel.

Which chain decides whether the deadline has passed?

An IBC Classic packet can carry a timeout height, a timeout timestamp, or both. Compare each enabled limit with the destination chain’s height or recorded time. A laptop clock or the sending chain’s height answers a different question. Once the destination reaches either enabled threshold, it rejects a fresh receipt of that packet. An earlier receipt can still be relevant when the deadline later passes. See ICS-004 packet fields and receiving rules.

What confirms a timeout on the sending chain?

A source-chain timeout is a successful onchain result for the same packet. For the unordered channel used by this example, the sending chain verifies evidence from the destination that the deadline was reached and that the packet was unreceived. An elapsed deadline alone cannot establish whether the destination received it earlier or whether the sending chain has processed the timeout.

Two snapshots of the same fictional packet

Packet P travels from Chain A to Chain B. It has a height deadline of revision 2, height 1,200, with no timestamp deadline in this example. Both snapshots show Chain B at revision 2, height 1,205.

SnapshotWhat the sending-chain record showsWhat you can conclude
ANo matching source timeout is visible.The height deadline has passed. That observation leaves the source outcome open.
BA matching, successful timeout is confirmed for Packet P.Chain A processed the timeout for that packet.

A status label may mix information from two chains. Compare the packet identifiers and the chain named in each observation before drawing a conclusion. A result for another packet answers only for that packet.

Where does the acknowledgement fit?

An acknowledgement records an application result after the destination receives and processes the packet. In ICS-20 it can indicate success or an application error. The sending chain processes acknowledgement and timeout on separate branches. Under the ICS-020 transfer specification, an error acknowledgement and a confirmed timeout both call the transfer module’s refund handling. That describes the specified application behavior. A user-facing balance or credit is a separate observation.

In Snapshot A, the deadline alone leaves both receipt history and the sending-chain result unresolved. In Snapshot B, the matching record confirms the timeout branch. For a comparison of how other bridges assign meaning to source and destination records, see lock-and-mint vs burn-and-mint.

Sources

See something wrong? Brokzi logs material changes. Prepare a correction note.

About the byline

Brokzi Editorial

The accountable byline for Brokzi’s explainers, definitions, news notes, and corrections.

Editorial responsibility →