Skip to content

Clear Signing coverage tracker Bridges

Linea Bridge

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

Status
Uncovered

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

Linea L1 Message Service (LineaRollup)

Deposit ETH to Linea (sendMessage) and claim withdrawals on Ethereum (claimMessageWithProof)

Uncovered
Address
0xd19d…876FLineaRollup
Descriptor
None in the registry
Functions
0 of 29 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 15 October – 6 November 2026 · 44 a day
Sourcify
Verified, exact match

Most-called functions

  1. claimMessageWithProof((bytes32[],uint256,uint32,address,address,uint256,uint256,address,bytes32,bytes))42%Not formatted · 120 sendersTry it: a real call of claimMessageWithProof((bytes32[],uint256,uint32,address,address,uint256,uint256,address,bytes32,bytes)) in the playground
  2. finalizeBlocks(bytes,uint256,(bytes32,uint256,(bytes32,bytes32,bytes32,bytes32,bytes32),uint256,uint256,bytes32,bytes32,uint256,uint256,uint256,uint256,uint256,bytes32,bytes32[],address[],bytes))17%Not formatted · 1 senderTry it: a real call of finalizeBlocks(bytes,uint256,(bytes32,uint256,(bytes32,bytes32,bytes32,bytes32,bytes32),uint256,uint256,bytes32,bytes32,uint256,uint256,uint256,uint256,uint256,bytes32,bytes32[],address[],bytes)) in the playground
  3. submitBlobs((uint256,bytes,bytes,bytes32,bytes32)[],bytes32,bytes32)17%Not formatted · 1 senderTry it: a real call of submitBlobs((uint256,bytes,bytes,bytes32,bytes32)[],bytes32,bytes32) in the playground
  4. claimMessage(address,address,uint256,uint256,address,bytes,uint256)15%Not formatted · 96 sendersTry it: a real call of claimMessage(address,address,uint256,uint256,address,bytes,uint256) in the playground
  5. sendMessage(address,uint256,bytes)9%Not formatted · 58 sendersTry it: a real call of sendMessage(address,uint256,bytes) in the playground

Ethereum

Linea L1 Token Bridge

Deposit ERC-20 tokens to Linea (bridgeToken, bridgeTokenWithPermit)

Uncovered
Address
0x051F…3319TokenBridge
Descriptor
None in the registry
Functions
0 of 20 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders24 transactions, 8 October – 6 November 2026 · 0.8 a day
Sourcify
Verified, exact match

Most-called functions

  1. bridgeToken(address,uint256,address)100%Not formatted · 15 sendersTry it: a real call of bridgeToken(address,uint256,address) 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 Linea Bridge clear-signed

Of the 2 contracts of Linea Bridge here, 2 have no descriptor in the registry. We write, test and submit descriptors.