Skip to content

Clear Signing coverage tracker DEXs

Maverick

3 contracts of Maverick on Ethereum, Base and Arbitrum One, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered

Contracts

0 of 3

contracts here have a descriptor in the registry

  • 0 covered
  • 0 partial
  • 3 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 202621 transactions a day across 3 contractsThe data, as JSON
Contracts

3 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

Maverick V2 Router

Maverick v2 swaps and liquidity

Uncovered
Address
0x5eDE…f527MaverickV2Router · v2
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders20 transactions, 6 November 2026 · 20 a day
Sourcify
Verified, exact match
Address from
docs.mav.xyz

Most-called functions

  1. inputSingleWithTickLimit(address,address,bool,uint256,int32,uint256)100%Not formatted · 12 sendersTry it: a real call of inputSingleWithTickLimit(address,address,bool,uint256,int32,uint256) in the playground

Ethereum

Maverick V2 Router

Maverick v2 swaps and liquidity

Uncovered
Address
0x62e3…22fAMaverickV2Router · v2
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders24 transactions, 9 October – 5 November 2026 · 0.8 a day
Sourcify
Verified, exact match
Address from
docs.mav.xyz

Most-called functions

  1. exactInputSingle(address,address,bool,uint256,uint256)100%Not formatted · 2 sendersTry it: a real call of exactInputSingle(address,address,bool,uint256,uint256) in the playground

Arbitrum One

Maverick V2 Router

Maverick v2 swaps and liquidity

Uncovered
Address
0x5c3b…fc76MaverickV2Router · v2
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders5 transactions, 6 – 21 October 2026 · 0.1 a day
Sourcify
Verified, exact match
Address from
docs.mav.xyz

Most-called functions

  1. inputSingleWithTickLimit(address,address,bool,uint256,int32,uint256)80%Not formatted · 3 sendersTry it: a real call of inputSingleWithTickLimit(address,address,bool,uint256,int32,uint256) in the playground
  2. multicall(bytes[])20%Not formatted · 1 senderTry it: a real call of multicall(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.
  • 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 Maverick clear-signed

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