Skip to content

Clear Signing coverage tracker DEXs

Camelot

4 contracts of Camelot on Arbitrum One, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered
TVL
$6.79M on the four chains, from DefiLlama, 7 November 2026

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 202647 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.

Arbitrum One

AMMv3 position manager

Create and manage concentrated-liquidity (Algebra) positions

Uncovered
Address
0x00c7…CD15NonfungiblePositionManager · v3
Descriptor
None in the registry
Functions
0 of 21 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders770 transactions, 4 October – 6 November 2026 · 22 a day
Sourcify
Verified, partial match

Most-called functions

  1. multicall(bytes[])82%Not formatted · 160 sendersTry it: a real call of multicall(bytes[]) in the playground
  2. collect((uint256,address,uint128,uint128))10%Not formatted · 21 sendersTry it: a real call of collect((uint256,address,uint128,uint128)) in the playground
  3. increaseLiquidity((uint256,uint256,uint256,uint256,uint256,uint256))5%Not formatted · 1 senderTry it: a real call of increaseLiquidity((uint256,uint256,uint256,uint256,uint256,uint256)) in the playground
  4. decreaseLiquidity((uint256,uint128,uint256,uint256,uint256))1%Not formatted · 2 sendersTry it: a real call of decreaseLiquidity((uint256,uint128,uint256,uint256,uint256)) in the playground
  5. mint((address,address,int24,int24,uint256,uint256,uint256,uint256,address,uint256))1%Not formatted · 2 sendersTry it: a real call of mint((address,address,int24,int24,uint256,uint256,uint256,uint256,address,uint256)) in the playground

Arbitrum One

AMMv2 Router

v2 pool swaps and v2 liquidity add/remove

Uncovered
Address
0xc873…448dRouter · v2
Descriptor
None in the registry
Functions
0 of 11 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders710 transactions, 4 October – 6 November 2026 · 21 a day
Sourcify
Verified, partial match

Most-called functions

  1. swapExactTokensForTokensSupportingFeeOnTransferTokens(uint256,uint256,address[],address,address,uint256)48%Not formatted · 24 sendersTry it: a real call of swapExactTokensForTokensSupportingFeeOnTransferTokens(uint256,uint256,address[],address,address,uint256) in the playground
  2. removeLiquidity(address,address,uint256,uint256,uint256,address,uint256)27%Not formatted · 176 sendersTry it: a real call of removeLiquidity(address,address,uint256,uint256,uint256,address,uint256) in the playground
  3. swapExactTokensForETHSupportingFeeOnTransferTokens(uint256,uint256,address[],address,address,uint256)6%Not formatted · 11 sendersTry it: a real call of swapExactTokensForETHSupportingFeeOnTransferTokens(uint256,uint256,address[],address,address,uint256) in the playground
  4. swapExactETHForTokensSupportingFeeOnTransferTokens(uint256,address[],address,address,uint256)5%Not formatted · 8 sendersTry it: a real call of swapExactETHForTokensSupportingFeeOnTransferTokens(uint256,address[],address,address,uint256) in the playground
  5. addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256)4%Not formatted · 12 sendersTry it: a real call of addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256) in the playground

Arbitrum One

AMMv4 position manager

Create and manage AMMv4 (Algebra Integral) positions

Uncovered
Address
0xA602…E9d8NonfungiblePositionManager · v4
Descriptor
None in the registry
Functions
0 of 24 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders120 transactions, 4 October – 5 November 2026 · 3.6 a day
Sourcify
Verified, partial match

Most-called functions

  1. multicall(bytes[])99%Not formatted · 27 sendersTry it: a real call of multicall(bytes[]) in the playground
  2. safeTransferFrom(address,address,uint256)1%Not formatted · 1 senderTry it: a real call of safeTransferFrom(address,address,uint256) in the playground

Arbitrum One

Camelot aggregator router

Swaps from the Camelot app (aggregator)

Uncovered
Address
0x99D4…eC5ECamelotYakRouter
Descriptor
None in the registry
Functions
0 of 19 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders12 transactions, 5 October – 1 November 2026 · 0.4 a day
Sourcify
Verified, exact match

Most-called functions

  1. swapNoSplit((uint256,uint256,address[],address[],address[]),uint256,address)100%Not formatted · 9 sendersTry it: a real call of swapNoSplit((uint256,uint256,address[],address[],address[]),uint256,address) 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.
  • 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 Camelot clear-signed

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