FOR PAYMENTS & BRIDGES

A payment is a lifecycle, not a transaction hash.

On-ramp, hop, swap, settle, off-ramp — one journey, currently visible only as disconnected fragments. Read the whole lifecycle, including the steps that report state without moving funds.

concept
1
on-ramp

fiat → USDC lands in wallet

12:04:11 · done
2
swap

USDC → SUI for gas + route

12:04:38 · done
3
bridge

locked on source · awaiting attestation

12:05:02 · stalled 41 min
4
destination

not yet arrived

— · pending
5
off-ramp

settlement not yet reported

— · pending
⚠ stall detected at bridge attestation

3 other journeys stalled at the same hop this hour — the corridor, not the customer. Support sees the lifecycle; the customer gets an answer instead of a hash.

3m 41s
median corridor time
2.1%
stall rate today
caught 12×
settle-vs-report gap

Where do payments stall?

What happens after the on-ramp?

Did the off-ramp settle, or only report?

already real underneath

Our window contains 982 off-ramp settlement commits and a $1M USDC transaction read to the exact cross-chain call it reached.

Would you use this? What would you ask it first?

Tell us → bartosz@research.tech
← all use cases