Klamp

A token issuer declares one canonical pool.

Klamp lets clients compare every proposed route against that ENSv2 record before execution.

View a verification trace

A precise boundary

The contract establishes who may write a canonical pool record. The client resolves that record and decides whether a proposed route is safe to continue.

The contract proves

  • Issuer authority through CREATE2 or LiquidityLauncher graffiti
  • The pool is deployed, initialized, and contains the token
  • The canonical record can only be written once

The client checks

  • The resolver returns a valid, unambiguous record
  • Chain, PoolManager, and PoolId match the proposed route
  • Every declared branch that touches the token is checked