Skip to content

Clear Signing coverage tracker Aggregators

0x (Matcha)

4 contracts of 0x (Matcha) on Ethereum, Base, Arbitrum One and OP Mainnet, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered
Website
0x.org

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 202636,305 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

0x AllowanceHolder

Swap entry point for 0x Swap API AllowanceHolder-flow swaps: users approve it and call exec(), which forwards to the current Settler

Uncovered
Address
0x0000…2734AllowanceHolder
Descriptor
None in the registry
Functions
0 of 0 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 32,047 a day
Sourcify
Verified, partial match

Most-called functions

  1. 0x2213bc0b100%Not formatted · name not known · 77 sendersTry it: a real call of 0x2213bc0b in the playground

Ethereum

0x AllowanceHolder

Swap entry point for 0x Swap API AllowanceHolder-flow swaps: users approve it and call exec(), which forwards to the current Settler

Uncovered
Address
0x0000…2734AllowanceHolder
Descriptor
None in the registry
Functions
0 of 0 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 3,245 a day
Sourcify
Verified, partial match

Most-called functions

  1. 0x2213bc0b100%Not formatted · name not known · 722 sendersTry it: a real call of 0x2213bc0b in the playground

Arbitrum One

0x AllowanceHolder

Swap entry point for 0x Swap API AllowanceHolder-flow swaps: users approve it and call exec(), which forwards to the current Settler

Uncovered
Address
0x0000…2734AllowanceHolder
Descriptor
None in the registry
Functions
0 of 0 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 5 – 6 November 2026 · 848 a day
Sourcify
Verified, partial match

Most-called functions

  1. 0x2213bc0b100%Not formatted · name not known · 539 sendersTry it: a real call of 0x2213bc0b in the playground

OP Mainnet

0x AllowanceHolder

Swap entry point for 0x Swap API AllowanceHolder-flow swaps: users approve it and call exec(), which forwards to the current Settler

Uncovered
Address
0x0000…2734AllowanceHolder
Descriptor
None in the registry
Functions
0 of 0 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 31 October – 6 November 2026 · 164 a day
Sourcify
Verified, partial match

Most-called functions

  1. 0x2213bc0b100%Not formatted · name not known · 474 sendersTry it: a real call of 0x2213bc0b 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 0x (Matcha) clear-signed

Of the 4 contracts of 0x (Matcha) here, 4 have no descriptor in the registry. We write, test and submit descriptors.