Skip to content

Clear Signing coverage tracker Liquid staking

mETH Protocol (Mantle)

1 contract of mETH Protocol (Mantle) on Ethereum, checked against the Clear Signing registry and its recent transactions.

Status
Uncovered

Contracts

0 of 1

contract here has a descriptor in the registry

  • 0 covered
  • 0 partial
  • 1 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 202620 transactions a day across 1 contractThe data, as JSON
Contracts

1 contract, 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

mETH Staking

Stake ETH for mETH; request and claim unstakes

Uncovered
Address
0xe3cB…9E8fStaking
Descriptor
None in the registry
Functions
0 of 24 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders605 transactions, 7 October – 6 November 2026 · 20 a day
Sourcify
Verified, partial match

Most-called functions

  1. stake(uint256)54%Not formatted · 5 sendersTry it: a real call of stake(uint256) in the playground
  2. claimUnstakeRequest(uint256)18%Not formatted · 73 sendersTry it: a real call of claimUnstakeRequest(uint256) in the playground
  3. unstakeRequestWithPermit(uint128,uint128,uint256,uint8,bytes32,bytes32)14%Not formatted · 50 sendersTry it: a real call of unstakeRequestWithPermit(uint128,uint128,uint256,uint8,bytes32,bytes32) in the playground
  4. allocateETH(uint256,uint256,uint256)10%Not formatted · 1 senderTry it: a real call of allocateETH(uint256,uint256,uint256) in the playground
  5. unstakeRequest(uint128,uint128)3%Not formatted · 18 sendersTry it: a real call of unstakeRequest(uint128,uint128) 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 mETH Protocol (Mantle) clear-signed

The one contract of mETH Protocol (Mantle) here has no descriptor in the registry. We write, test and submit descriptors.