Skip to main content

Events overview for vIBC

Disclaimer

The Polymer testnet is currently in an early public testnet phase. Please be aware that during this phase, the network may be subject to instability, downtime, and data resets. Read the full disclaimer here.

When debugging the IBC packet lifecycle, the first step to take is to track down the packet during its lifecycle and where any potential issue arises.

For example, you can find reference to these events (or rather, the transaction they were emitted from) by looking at IBC explorer.

IBC explorer packet summary

As an application developer, you'll be mostly looking at the events on the chains your application(s) live on, not Polymer itself in the middle. Below you find the sequence of events for all possible situations.

Ethereum L2 interoperability

When connecting Ethereum L2s that don't have native IBC implementations, the virtual-to-virtual case is applicable.

OP (Sepolia) to Base (Sepolia) is an example

Virtual to virtual

ActorVirtual chain APolymerVirtual Chain B
vIBC Core SCSendPacket--
IBC module-SendPacket-
IBC module-RecvPacket-
vIBC Core SC--RecvPacket
vIBC Core SC--WriteAck
IBC module-WriteAck-
IBC module-AcknowledgePacket-
vIBC Core SCAcknowledgePacket--

Virtual (sender) to IBC native

ActorVirtual chain APolymerIBC Chain B
vIBC Core SCSendPacket--
IBC module-SendPacket-
IBC module--RecvPacket
IBC module--WriteAck
IBC module-AcknowledgePacket-
vIBC Core SCAcknowledgePacket--

IBC native to Virtual (receiver)

ActorVirtual chain APolymerVirtual Chain B
IBC moduleSendPacket--
IBC module-RecvPacket-
vIBC Core SC--RecvPacket
vIBC Core SC--WriteAck
IBC module-WriteAck-
IBC moduleAcknowledgePacket--