Skip to content

Clear Signing coverage tracker Aggregators

KyberSwap Aggregator

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

Status
Covered

Contracts

4 of 4

contracts here have a descriptor in the registry

  • 4 covered
  • 0 partial
  • 0 uncovered

Recent traffic

100%

of recent transactions a wallet could clear-sign

100% 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 202618,398 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

KyberSwap Meta Aggregation Router v2

Swap router for the KyberSwap app and Aggregator API

Covered
Address
0x6131…37b5MetaAggregationRouterV2
Descriptor
calldata-MetaAggregationRouterV2.jsonOwner: KyberSwapNo attestation
Functions
1 of 7 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 6 November 2026 · 13,209 a day
Sourcify
Verified, partial match
Address from
docs.kyberswap.com

Most-called functions

  1. swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes))100%Formatted · 219 sendersTry it: a real call of swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes)) in the playground

Ethereum

KyberSwap Meta Aggregation Router v2

Swap router for the KyberSwap app and Aggregator API

Covered
Address
0x6131…37b5MetaAggregationRouterV2
Descriptor
calldata-MetaAggregationRouterV2.jsonOwner: KyberSwapNo attestation
Functions
1 of 7 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 6 November 2026 · 2,125 a day
Sourcify
Verified, partial match
Address from
docs.kyberswap.com

Most-called functions

  1. swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes))100%Formatted · 363 sendersTry it: a real call of swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes)) in the playground

Arbitrum One

KyberSwap Meta Aggregation Router v2

Swap router for the KyberSwap app and Aggregator API

Covered
Address
0x6131…37b5MetaAggregationRouterV2
Descriptor
calldata-MetaAggregationRouterV2.jsonOwner: KyberSwapNo attestation
Functions
1 of 7 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 6 November 2026 · 1,910 a day
Sourcify
Verified, partial match
Address from
docs.kyberswap.com

Most-called functions

  1. swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes))100%Formatted · 159 sendersTry it: a real call of swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes)) in the playground

OP Mainnet

KyberSwap Meta Aggregation Router v2

Swap router for the KyberSwap app and Aggregator API

Covered
Address
0x6131…37b5MetaAggregationRouterV2
Descriptor
calldata-MetaAggregationRouterV2.jsonOwner: KyberSwapNo attestation
Functions
1 of 7 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 5 – 6 November 2026 · 1,154 a day
Sourcify
Verified, partial match
Address from
docs.kyberswap.com

Most-called functions

  1. swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,bytes),bytes))100%Formatted · 80 sendersTry it: a real call of swap((address,address,bytes,(address,address,address[],uint256[],address[],uint256[],address,uint256,uint256,uint256,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.
  • 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

Keep KyberSwap Aggregator clear-signed as it changes

Every contract of KyberSwap Aggregator here is covered. When a proxy is upgraded or an ABI changes, a descriptor can stop matching: we write, test and submit descriptors, and keep them current.