Skip to content

Clear Signing coverage tracker Yield

Beefy

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

Status
Uncovered
Website
beefy.com
TVL
$71.1M on the four chains, from DefiLlama, 7 November 2026

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 2026266 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

Zap Router

Zap any token into or out of a Beefy vault in one transaction

Uncovered
Address
0x6F19…6a63BeefyZapRouter
Descriptor
None in the registry
Functions
0 of 6 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders180 transactions, 5 – 6 November 2026 · 184 a day
Sourcify
Verified, exact match

Most-called functions

  1. executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[])100%Not formatted · 74 sendersTry it: a real call of executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[]) in the playground

OP Mainnet

Zap Router

Zap any token into or out of a Beefy vault in one transaction

Uncovered
Address
0xE823…C01cBeefyZapRouter
Descriptor
None in the registry
Functions
0 of 6 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders221 transactions, 30 October – 6 November 2026 · 29 a day
Sourcify
Verified, exact match

Most-called functions

  1. executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[])100%Not formatted · 105 sendersTry it: a real call of executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[]) in the playground

Ethereum

Zap Router

Zap any token into or out of a Beefy vault in one transaction

Uncovered
Address
0x5Cc9…0d1FBeefyZapRouter
Descriptor
None in the registry
Functions
0 of 6 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders823 transactions, 7 October – 6 November 2026 · 27 a day
Sourcify
Verified, exact match

Most-called functions

  1. executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[])100%Not formatted · 415 sendersTry it: a real call of executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[]) in the playground

Arbitrum One

Zap Router

Zap any token into or out of a Beefy vault in one transaction

Uncovered
Address
0xf49F…6E5ABeefyZapRouter
Descriptor
None in the registry
Functions
0 of 6 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders884 transactions, 4 October – 6 November 2026 · 26 a day
Sourcify
Verified, exact match

Most-called functions

  1. executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[])100%Not formatted · 389 sendersTry it: a real call of executeOrder(((address,uint256)[],(address,uint256)[],(address,uint256,bytes),address,address),(address,uint256,bytes,(address,int32)[])[]) 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 Beefy clear-signed

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