Skip to content

Clear Signing coverage tracker Liquid staking

Lombard

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

Status
Partial

Contracts

1 of 2

contracts here has a descriptor in the registry

  • 1 covered
  • 0 partial
  • 1 uncovered

Recent traffic

67%

of recent transactions a wallet could clear-sign

67% 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 202658 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.

Ethereum

LBTC

Mint LBTC from a notarized BTC deposit and redeem LBTC to BTC

Covered
Address
0x8236…4494StakedLBTC
Descriptor
calldata-lbtc-mainnet.jsonOwner: Lombard FinanceNo attestation
Functions
8 of 36 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 11 October – 6 November 2026 · 39 a day
Sourcify
Verified, exact match

Most-called functions

  1. approve(address,uint256)61%Formatted · 403 sendersTry it: a real call of approve(address,uint256) in the playground
  2. redeemForBtc(bytes,uint256)18%Formatted · 109 sendersTry it: a real call of redeemForBtc(bytes,uint256) in the playground
  3. transfer(address,uint256)14%Formatted · 87 sendersTry it: a real call of transfer(address,uint256) in the playground
  4. redeem(uint256)6%Formatted · 44 sendersTry it: a real call of redeem(uint256) in the playground
  5. mint(bytes,bytes)1%Formatted · 7 sendersTry it: a real call of mint(bytes,bytes) in the playground

Base

LBTC on Base

Mint LBTC on Base from a notarized BTC deposit and redeem LBTC to BTC

Uncovered
Address
0xecAc…11c1StakedLBTC
Descriptor
None for this deployment
Described elsewhere
calldata-lbtc-mainnet.jsonFor LBTC at 0x8236…4494 on Ethereum; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 36 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders19 transactions, 5 – 6 November 2026 · 19 a day
Sourcify
Verified, exact match

Most-called functions

  1. approve(address,uint256)95%Not formatted · 17 sendersTry it: a real call of approve(address,uint256) in the playground
  2. transfer(address,uint256)5%Not formatted · 1 senderTry it: a real call of transfer(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 Lombard, 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 Lombard clear-signed

Of the 2 contracts of Lombard here, 1 has no descriptor in the registry. We write, test and submit descriptors.