Skip to main content

What is Recoil Link

Recoil Link is a cross-chain messaging and proof layer by Recoil Labs. A contract on one chain sends a message; Recoil Link's validators attest to it, and its relayer delivers it to a contract on another chain. The receiving contract can then act on proof that something happened on the origin chain.

Typical uses:

  • Proving intent fills. A solver delivers funds on chain B; a message proves it on chain A, and the escrow there pays the solver. Recoil Link ships an Open Intents Framework oracle for exactly this. RecoilPay uses it.
  • Cross-chain calls and state. Any bytes you can encode: governance actions, price or state updates, cross-chain accounts.

What you get​

MailboxOne contract per chain. Apps call dispatch to send and implement handle to receive.
Security modules (ISMs)Decide whether a delivered message is valid. By default: signatures from the Recoil Link validator set.
Gas paymentSenders prepay destination gas on the origin chain; the relayer delivers prepaid messages.
AgentsValidators (sign what was sent) and a relayer (delivers it). Run by Recoil Labs today.

Status​

Recoil Link is live on testnets: Sepolia, Base Sepolia, OP Sepolia and BSC testnet. Mainnet follows a security audit and a multi-party validator set; see Security.

Relationship to Hyperlane​

Recoil Link is a fork of Hyperlane (Apache-2.0). It keeps Hyperlane's contract interfaces and message format, so code written against Hyperlane's IMailbox and IMessageRecipient works with Recoil Link's contracts. It runs its own separate deployments, validators and relayer: a message sent through a Recoil Link Mailbox is never delivered by Hyperlane, and vice versa.

Recoil Link focuses on messaging and proofs. Hyperlane's token bridging ("warp routes") is not part of Recoil Link.

Next​

  • How it works: the life of a message.
  • Quickstart: send a message between two testnets in a few minutes.
  • Examples: runnable contracts you can copy, with tests.