ContractsFIG. 01
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.
- Functions
- 1 of 18 writable functions formatted
- Recent calls
- Formatted: 100% of recent transactions, 100% of recent senders1 transaction, 23 October 2026 · 0 a day
- Sourcify
- Verified, partial match
Reading itFIG. 02
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 coveredFIG. 03
Keep Bedrock (uniBTC) clear-signed as it changes
Every contract of Bedrock (uniBTC) here is covered. When a proxy is upgraded or an ABI changes, a descriptor can stop matching: we write, test and submit descriptors, and keep them current.