Skip to content

Clear Signing coverage tracker DEXs

SushiSwap

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

Status
Partial
Website
sushi.com
TVL
$54.3M on the four chains, from DefiLlama, 7 November 2026

Contracts

1 of 4

contracts here has a descriptor in the registry

  • 0 covered
  • 1 partial
  • 3 uncovered

Recent traffic

6%

of recent transactions a wallet could clear-sign

6% 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 20263,149 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.

OP Mainnet

RedSnwapper

Swap entry point of the Sushi app (snwap); runs RouteProcessor executors

Uncovered
Address
0xAC4c…0b75RedSnwapper
Descriptor
None for this deployment
Described elsewhere
calldata-RedSnwapper.jsonFor the same address on Ethereum; it does not list this deployment.The functions it formats make up 65% of what recent senders called here.
Functions
0 of 2 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 2,177 a day
Sourcify
Verified, exact match

Most-called functions

  1. snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[])63%Not formatted · 147 sendersTry it: a real call of snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[]) in the playground
  2. snwap(address,uint256,address,address,uint256,address,bytes)37%Not formatted · 271 sendersTry it: a real call of snwap(address,uint256,address,address,uint256,address,bytes) in the playground

Base

RedSnwapper

Swap entry point of the Sushi app (snwap); runs RouteProcessor executors

Uncovered
Address
0xAC4c…0b75RedSnwapper
Descriptor
None for this deployment
Described elsewhere
calldata-RedSnwapper.jsonFor the same address on Ethereum; it does not list this deployment.The functions it formats make up 93% of what recent senders called here.
Functions
0 of 2 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders489 transactions, 5 – 6 November 2026 · 499 a day
Sourcify
Verified, exact match

Most-called functions

  1. snwap(address,uint256,address,address,uint256,address,bytes)92%Not formatted · 164 sendersTry it: a real call of snwap(address,uint256,address,address,uint256,address,bytes) in the playground
  2. snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[])8%Not formatted · 12 sendersTry it: a real call of snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[]) in the playground

Ethereum

RedSnwapper

Swap entry point of the Sushi app (snwap); runs RouteProcessor executors

Partial
Address
0xAC4c…0b75RedSnwapper
Descriptor
calldata-RedSnwapper.jsonOwner: SushiNo attestation
Functions
1 of 2 writable functions formatted
Recent calls
Formatted: 77% of recent transactions, 76% of recent senders1,000 transactions, 2 – 6 November 2026 · 245 a day
Sourcify
Verified, exact match

Most-called functions

  1. snwap(address,uint256,address,address,uint256,address,bytes)77%Formatted · 354 sendersTry it: a real call of snwap(address,uint256,address,address,uint256,address,bytes) in the playground
  2. snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[])23%Not formatted · 111 sendersTry it: a real call of snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[]) in the playground

Arbitrum One

RedSnwapper

Swap entry point of the Sushi app (snwap); runs RouteProcessor executors

Uncovered
Address
0xAC4c…0b75RedSnwapper
Descriptor
None for this deployment
Described elsewhere
calldata-RedSnwapper.jsonFor the same address on Ethereum; it does not list this deployment.The functions it formats make up 61% of what recent senders called here.
Functions
0 of 2 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 2 – 6 November 2026 · 227 a day
Sourcify
Verified, exact match

Most-called functions

  1. snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[])53%Not formatted · 164 sendersTry it: a real call of snwapMultiple((address,uint256,address)[],(address,address,uint256)[],(address,uint256,bytes)[]) in the playground
  2. snwap(address,uint256,address,address,uint256,address,bytes)47%Not formatted · 261 sendersTry it: a real call of snwap(address,uint256,address,address,uint256,address,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 SushiSwap, 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 SushiSwap clear-signed

Of the 4 contracts of SushiSwap here, 1 is partly covered and 3 have no descriptor in the registry. We write, test and submit descriptors.