Skip to content

Clear Signing coverage tracker Aggregators

Enso

4 contracts of Enso on Ethereum, Base, Arbitrum One and OP Mainnet, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered
Website
enso.build

Contracts

0 of 4

contracts here have a descriptor in the registry

  • 0 covered
  • 0 partial
  • 4 uncovered

Recent traffic

0%

of recent transactions a wallet could clear-sign

0% of recent senders

Transactions count every call. Senders count each address once per function, so a relayer bot counts once however many calls it sends.

Registry at ef582c2, committed 4 November 2026On-chain reads 6 November 2026202 transactions a day across 4 contractsThe data, as JSON
Contracts

4 contracts, busiest first

For each: its address and where it came from, the registry's descriptor for it, the functions it formats, and which of its recent calls a wallet could clear-sign.

Base

Enso Router V2

Entry point for Enso swaps, zaps and shortcuts sent from EOAs

Uncovered
Address
0xF755…22CfEnsoRouter · v2
Descriptor
None for this deployment
Described elsewhere
calldata-EnsoRouter.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 5% of what recent senders called here.
Functions
0 of 4 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders106 transactions, 5 – 6 November 2026 · 108 a day
Sourcify
Verified, exact match

Most-called functions

  1. routeSingle((uint8,bytes),bytes)98%Not formatted · 17 sendersTry it: a real call of routeSingle((uint8,bytes),bytes) in the playground
  2. safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes)1%Not formatted · 1 senderTry it: a real call of safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes) in the playground
  3. routeMulti((uint8,bytes)[],bytes)1%Not formatted · 1 senderTry it: a real call of routeMulti((uint8,bytes)[],bytes) in the playground

Ethereum

Enso Router V2

Entry point for Enso swaps, zaps and shortcuts sent from EOAs

Uncovered
Address
0xF755…22CfEnsoRouter · v2
Descriptor
None for this deployment
Described elsewhere
calldata-EnsoRouter.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 1% of what recent senders called here.
Functions
0 of 4 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 25 October – 6 November 2026 · 79 a day
Sourcify
Verified, exact match

Most-called functions

  1. routeSingle((uint8,bytes),bytes)94%Not formatted · 472 sendersTry it: a real call of routeSingle((uint8,bytes),bytes) in the playground
  2. safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes)3%Not formatted · 7 sendersTry it: a real call of safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes) in the playground
  3. routeMulti((uint8,bytes)[],bytes)3%Not formatted · 26 sendersTry it: a real call of routeMulti((uint8,bytes)[],bytes) in the playground

Arbitrum One

Enso Router V2

Entry point for Enso swaps, zaps and shortcuts sent from EOAs

Uncovered
Address
0xF755…22CfEnsoRouter · v2
Descriptor
None for this deployment
Described elsewhere
calldata-EnsoRouter.jsonFor the same address on Polygon; it does not list this deployment.The functions it formats make up 1% of what recent senders called here.
Functions
0 of 4 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders229 transactions, 4 October – 6 November 2026 · 7.1 a day
Sourcify
Verified, exact match

Most-called functions

  1. routeSingle((uint8,bytes),bytes)87%Not formatted · 87 sendersTry it: a real call of routeSingle((uint8,bytes),bytes) in the playground
  2. routeMulti((uint8,bytes)[],bytes)12%Not formatted · 20 sendersTry it: a real call of routeMulti((uint8,bytes)[],bytes) in the playground
  3. safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes)1%Not formatted · 1 senderTry it: a real call of safeRouteSingle((uint8,bytes),(uint8,bytes),address,bytes) in the playground

OP Mainnet

Enso Router V2

Entry point for Enso swaps, zaps and shortcuts sent from EOAs

Uncovered
Address
0xF755…22CfEnsoRouter · v2
Descriptor
None in the registry
Functions
0 of 4 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 24 August – 6 November 2026 · 7 a day
Sourcify
Verified, exact match

Most-called functions

  1. routeSingle((uint8,bytes),bytes)93%Not formatted · 82 sendersTry it: a real call of routeSingle((uint8,bytes),bytes) in the playground
  2. routeMulti((uint8,bytes)[],bytes)7%Not formatted · 13 sendersTry it: a real call of routeMulti((uint8,bytes)[],bytes) in the playground
Reading it

What these numbers say, and do not

  • Covered means the registry has a descriptor for the deployment and it formats at least 95% of what recent senders called. Partial means a descriptor formats less, or its reach could not be measured. Uncovered means the registry has no descriptor for it.
  • Described elsewhere means the registry has a descriptor for another deployment of Enso, on another chain or at another address, with functions this contract's recent senders call. It does not list this contract, which stays uncovered, and whether it fits is for its owner to check.
  • By transactions, every call counts. By senders, each address counts once for each function, so a relayer bot counts once however many calls it sends.
  • A descriptor is not an audit, and wallets decide which descriptors they trust.

How we measureWhat the tracker does not claimAll protocols

Get covered

Get Enso clear-signed

Of the 4 contracts of Enso here, 4 have no descriptor in the registry. We write, test and submit descriptors.