Skip to content

Clear Signing coverage tracker Lending

Aave v4

2 contracts of Aave v4 on Ethereum, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered Draft ready
Website
aave.com

Contracts

0 of 2

contracts here have a descriptor in the registry

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

2 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. Where B3Pay has a draft, one real transaction shows how a call reads with it.

Ethereum

Aave v4 Main Spoke

Supply, borrow, repay and withdraw in the v4 Main Spoke

Uncovered
Address
0x94e7…c485Spoke · v4
Descriptor
None in the registry
Functions
0 of 23 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 4 – 6 November 2026 · 364 a day
Sourcify
Verified, partial match

Most-called functions

  1. multicall(bytes[])40%Not formatted · 258 sendersTry it: a real call of multicall(bytes[]) in the playground
  2. borrow(uint256,uint256,address)29%Not formatted · 180 sendersTry it: a real call of borrow(uint256,uint256,address) in the playground
  3. withdraw(uint256,uint256,address)19%Not formatted · 143 sendersTry it: a real call of withdraw(uint256,uint256,address) in the playground
  4. supply(uint256,uint256,address)4%Not formatted · 30 sendersTry it: a real call of supply(uint256,uint256,address) in the playground
  5. repay(uint256,uint256,address)3%Not formatted · 27 sendersTry it: a real call of repay(uint256,uint256,address) in the playground
Signature requestDraft ready

Ethereum · Aave v4 Main Spoke

Borrow

Amount
2300000000
Reserve ID
7
On behalf of
0xeeb9afb4ED985AdDd7615d59E4AA1F3377C6A56A
from transaction 0x25ce…34da

A B3Pay draft, not in the registry. Every function it formats has a test built from a real transaction. The full draft is on request.

Formats
7 functions
Would cover
99% of recent senders' calls
Tested on
7 transactions
Linter
Warnings
Get this descriptor

Ethereum

Aave v4 NativeTokenGateway

Supply, withdraw, borrow and repay native ETH on v4 spokes

Uncovered
Address
0xe68a…42BeNativeTokenGateway · v4
Descriptor
None in the registry
Functions
0 of 15 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 27 October – 6 November 2026 · 95 a day
Sourcify
Verified, partial match

Most-called functions

  1. supplyAsCollateralNative(address,uint256,uint256)47%Not formatted · 218 sendersTry it: a real call of supplyAsCollateralNative(address,uint256,uint256) in the playground
  2. withdrawNative(address,uint256,uint256)33%Not formatted · 158 sendersTry it: a real call of withdrawNative(address,uint256,uint256) in the playground
  3. supplyNative(address,uint256,uint256)7%Not formatted · 60 sendersTry it: a real call of supplyNative(address,uint256,uint256) in the playground
  4. repayNative(address,uint256,uint256)7%Not formatted · 24 sendersTry it: a real call of repayNative(address,uint256,uint256) in the playground
  5. borrowNative(address,uint256,uint256)6%Not formatted · 22 sendersTry it: a real call of borrowNative(address,uint256,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.
  • 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 draft is B3Pay's, not the registry's. No wallet reads it yet, and its preview shows how one call would read, not how any wallet shows it today.
  • 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 Aave v4 clear-signed

Of the 2 contracts of Aave v4 here, 2 have no descriptor in the registry. B3Pay has a tested draft for 1 of the 2, and the full draft is on request. We write, test and submit descriptors.