Bridges have always been simple pipes. Tokens in, tokens out. For most of crypto, that was the point. But a new class of chain is showing up that can't afford to work that way. Privacy chains, regulated stablecoin networks, fintech-native rollups — they need to know what's crossing their border before it crosses. And until now, there hasn't been a good way to do that without building something custom.

Predicate is now available as a Hook on Hyperlane Warp Routes. The short version: any chain on Hyperlane can now require compliance verification — KYC, sanctions screening, geo checks — before a single token leaves the origin chain. Compliant users get a normal bridging experience. Non-compliant transfers are stopped before anything moves.

The Problem

Most compliance approaches try to validate at the destination, or somewhere in transit. That creates a bad failure mode. Tokens leave the user's wallet, get locked on the origin chain, and then... what? The user can't receive them on the other side. Now you have a support ticket, stuck funds, and an unhappy compliance team.

Predicate Hooks solve this by checking at the origin. If a transfer doesn't pass compliance, it never fires. The user keeps their tokens. The chain keeps its guarantees. One transaction and one clean outcome.

How It Works

When a user initiates a bridge to a chain running a Predicate Hook, an attestation is verified on-chain at the origin before dispatch. If cleared, the tokens lock, Hyperlane sends the message, and tokens mint on the destination. Not clear? Nothing happens. Funds stay in your wallet.

From the user's perspective, compliant transfers feel identical to any other Warp Route transfer. The compliance layer just hums in the background.

Why Hyperlane

This only works because of how Hooks are built. They're an extensibility mechanism in Hyperlane's message dispatch flow, meaning chains can inject custom logic (like compliance checks) into the bridging process without modifying the core protocol. Adding a Predicate Hook to a Warp Route is a configuration choice. Not a fork, not a custom deployment, not a six-month integration project.

Any chain already on Hyperlane can turn this on for its Warp Routes.

What's Next

Several teams have already piloted the Predicate Hook on Hyperlane. Some will be ready to announce their deployments soon. If you're building a chain where compliance at the bridge matters, get in touch.