Skip to content

Clear Signing coverage tracker Bridges

Scroll Bridge

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

Status
Uncovered
Website
scroll.io

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

Scroll L1 Messenger

Claim withdrawals on Ethereum (relayMessageWithProof)

Uncovered
Address
0x6774…b367L1ScrollMessenger
Descriptor
None in the registry
Functions
0 of 9 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 24 October – 6 November 2026 · 73 a day
Sourcify
Verified, partial match

Most-called functions

  1. relayMessageWithProof(address,address,uint256,uint256,bytes,(uint256,bytes))98%Not formatted · 181 sendersTry it: a real call of relayMessageWithProof(address,address,uint256,uint256,bytes,(uint256,bytes)) in the playground
  2. sendMessage(address,uint256,bytes,uint256)3%Not formatted · 18 sendersTry it: a real call of sendMessage(address,uint256,bytes,uint256) in the playground

Ethereum

Scroll L1 Gateway Router

Deposit ETH and ERC-20 tokens to Scroll (depositETH, depositERC20)

Uncovered
Address
0xF8B1…1Fd6L1GatewayRouter
Descriptor
None in the registry
Functions
0 of 15 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders55 transactions, 8 October – 6 November 2026 · 1.8 a day
Sourcify
Verified, partial match

Most-called functions

  1. depositERC20(address,uint256,uint256)76%Not formatted · 9 sendersTry it: a real call of depositERC20(address,uint256,uint256) in the playground
  2. depositETH(address,uint256,uint256)13%Not formatted · 7 sendersTry it: a real call of depositETH(address,uint256,uint256) in the playground
  3. depositETH(uint256,uint256)5%Not formatted · 2 sendersTry it: a real call of depositETH(uint256,uint256) in the playground
  4. depositERC20(address,address,uint256,uint256)5%Not formatted · 2 sendersTry it: a real call of depositERC20(address,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 descriptor is not an audit, and wallets decide which descriptors they trust.

How we measureWhat the tracker does not claimAll protocols

Get covered

Get Scroll Bridge clear-signed

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