Trippy

Screenshots

Problem Statement

The project works in three steps. First, a user deposits capital into a Gateway which emits a deposit event, including the amount, the block number at the time of inclusion and the desired bridge destination chainId. Second, we use the AxiomSDK to prove inclusion of this event over a set of proven block headers. The Axiom prover then provides us a callback into a specified contract of our choice that includes the amount deposited and the destination chainId. Finally, we use this destination chainId to figure out the correct destination contract and we send the callback data (amount, and the depositor's address) to the destination chain, where we can then use these values.

Solution

The proving layer is built on Axiom using the AxiomSDK, the arbitrary message passing is built on Hyperlane.We also have initial implementations of a more trustless header oracle using Shoyu Bashi from Gnosis Hashi, a header relay using Hashi and a proof relay using Hyperlane.