Unlisted
Bonds

Bond $UNLST Behind a Hook

A hook stays unlisted on Unlisted until someone bonds $UNLST behind it. The bond is the listing: the hook page shows it, the router stops asking for the extra confirmation, and every swap routed through that hook pays the bonders. If the hook's code changes after the bond, anyone can slash half of it.

  • 40%
    To the hook's bondersOf the 0.10% fee on every swap Unlisted routes through that hook, pro-rata to bond.
  • 30%
    To the hook's deployerThe address that deployed it, claimable against a weekly Merkle root. Unclaimed after 90 days is burned.
  • 30%
    Buys $UNLST and burns itOn its Pons pool. A route with no bonded hook burns 70%, a vanilla route burns 100%.
Stencil of a hand pressing a stack of coins
0.10%
of every routed swap, taken by the Universal Router's portion command, 10 bps of the output
50%
of a bond slashed when the hook's EXTCODEHASH or implementation changes after bonding
7 days
to unbond, so nobody can leave in the block before an upgrade

The slash is a fact, not a vote

bond() records the hook's code hash and, for a proxy, its implementation address. slash(hook) is open to anyone: it compares both with the chain. If either changed, 50% of every bond on that hook is cut, 10% of it goes to the caller and 90% is burned.

Why bond

Bonders earn from real routed volume on the hooks they trust. A busy hook with a clean score is the one people route through, so the bond follows the hooks that deserve it.

What bonding does not change

The score and the flags stay what the chain says. A bond lists a hook and pays its backers; it never raises a score or hides a warning.

Bond, unbond, claim

Bond rules in the docsThe UnlistedBonds contract