Klamp

A token issuer declares one canonical pool.

Klamp records it in ENSv2. Routers read it with standard ENS tools and requote around look-alike hook pools before the trader signs.

View a verification traceTry it with your wallet →

A precise boundary

The contract establishes who may write a canonical pool record, once. The client resolves that record, judges the quoted route, requotes when needed and checks the calldata it signs.

The contract proves

  • Issuer authority: the CREATE2 launchpad, or the Pools.trade creator via LiquidityLauncher graffiti (direct or through a disposable contract)
  • The token is deployed, is in the PoolKey, and the pool is initialized
  • The canonical record can only be written once; no upgrades

The client checks

  • The pinned resolver answers, and the text and data records agree
  • Declared and static pools pass; other hook pools are requoted
  • The Universal Router calldata names the judged PoolKey before signing