Skip to content

Clear Signing coverage tracker Infrastructure

Disperse

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

Status
Partial

Contracts

1 of 4

contracts here has a descriptor in the registry

  • 1 covered
  • 0 partial
  • 3 uncovered

Recent traffic

12%

of recent transactions a wallet could clear-sign

12% 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 20264,134 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

Disperse

send ETH or a token to many addresses in one transaction (disperseEther, disperseToken)

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

Most-called functions

  1. disperseToken(address,address[],uint256[])99%Not formatted · 3 sendersTry it: a real call of disperseToken(address,address[],uint256[]) in the playground
  2. disperseEther(address[],uint256[])1%Not formatted · 2 sendersTry it: a real call of disperseEther(address[],uint256[]) in the playground

Ethereum

Disperse

send ETH or a token to many addresses in one transaction (disperseEther, disperseToken)

Covered
Address
0xD152…2150Disperse
Descriptor
calldata-Disperse.jsonOwner: DisperseNo attestation
Functions
3 of 3 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 4 – 6 November 2026 · 486 a day
Sourcify
Verified, partial match

Most-called functions

  1. disperseEther(address[],uint256[])88%Formatted · 246 sendersTry it: a real call of disperseEther(address[],uint256[]) in the playground
  2. disperseTokenSimple(address,address[],uint256[])10%Formatted · 4 sendersTry it: a real call of disperseTokenSimple(address,address[],uint256[]) in the playground
  3. disperseToken(address,address[],uint256[])2%Formatted · 5 sendersTry it: a real call of disperseToken(address,address[],uint256[]) in the playground

Arbitrum One

Disperse

send ETH or a token to many addresses in one transaction (disperseEther, disperseToken)

Uncovered
Address
0xD152…2150Disperse
Descriptor
None for this deployment
Described elsewhere
calldata-Disperse.jsonFor the same address on Ethereum; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 3 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders514 transactions, 4 October – 6 November 2026 · 16 a day
Sourcify
Verified, partial match

Most-called functions

  1. disperseEther(address[],uint256[])94%Not formatted · 170 sendersTry it: a real call of disperseEther(address[],uint256[]) in the playground
  2. disperseTokenSimple(address,address[],uint256[])3%Not formatted · 7 sendersTry it: a real call of disperseTokenSimple(address,address[],uint256[]) in the playground
  3. disperseToken(address,address[],uint256[])3%Not formatted · 6 sendersTry it: a real call of disperseToken(address,address[],uint256[]) in the playground

OP Mainnet

Disperse

send ETH or a token to many addresses in one transaction (disperseEther, disperseToken)

Uncovered
Address
0xD152…2150Disperse
Descriptor
None for this deployment
Described elsewhere
calldata-Disperse.jsonFor the same address on Ethereum; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 3 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders17 transactions, 30 October – 6 November 2026 · 2.2 a day
Sourcify
Verified, partial match

Most-called functions

  1. disperseEther(address[],uint256[])94%Not formatted · 3 sendersTry it: a real call of disperseEther(address[],uint256[]) in the playground
  2. disperseTokenSimple(address,address[],uint256[])6%Not formatted · 1 senderTry it: a real call of disperseTokenSimple(address,address[],uint256[]) 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 Disperse, 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 Disperse clear-signed

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