Skip to content

Clear Signing coverage tracker Yield

Solv Protocol

3 contracts of Solv Protocol on Ethereum, Base and Arbitrum One, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered

Contracts

0 of 3

contracts here have a descriptor in the registry

  • 0 covered
  • 0 partial
  • 3 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 20261 transactions a day across 3 contractsThe data, as JSON
Contracts

3 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.

Ethereum

SolvBTC Router V2

Deposit BTC assets to mint SolvBTC or its yield tokens; request and cancel withdrawals

Uncovered
Address
0x3d93…6334SolvBTCRouterV2
Descriptor
None in the registry
Functions
0 of 13 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders24 transactions, 9 October – 1 November 2026 · 0.8 a day
Sourcify
Verified, exact match

Most-called functions

  1. withdrawRequest(address,address,uint256)58%Not formatted · 11 sendersTry it: a real call of withdrawRequest(address,address,uint256) in the playground
  2. deposit(address,address,uint256,uint256,uint64)33%Not formatted · 7 sendersTry it: a real call of deposit(address,address,uint256,uint256,uint64) in the playground
  3. cancelWithdrawRequest(address,address,uint256)8%Not formatted · 2 sendersTry it: a real call of cancelWithdrawRequest(address,address,uint256) in the playground

Arbitrum One

SolvBTC Router V2

Deposit BTC assets to mint SolvBTC or its yield tokens; request and cancel withdrawals

Uncovered
Address
0x92E8…080ASolvBTCRouterV2
Descriptor
None in the registry
Functions
0 of 13 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders3 transactions, 9 – 14 October 2026 · 0.1 a day
Sourcify
Verified, exact match

Most-called functions

  1. withdrawRequest(address,address,uint256)100%Not formatted · 3 sendersTry it: a real call of withdrawRequest(address,address,uint256) in the playground

Base

SolvBTC Router V2

Deposit BTC assets to mint SolvBTC or its yield tokens; request and cancel withdrawals

Uncovered
Address
0xcf87…8aA1SolvBTCRouterV2
Descriptor
None in the registry
Functions
0 of 13 writable functions formatted
Recent calls
No transactions, 5 – 6 November 2026
Sourcify
Verified, exact match
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 Solv Protocol clear-signed

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