Skip to content

Clear Signing coverage tracker Bridges

USDT0

3 contracts of USDT0 on Ethereum, Arbitrum One and OP Mainnet, checked against the Clear Signing registry and their recent transactions.

Status
Uncovered
Website
usdt0.to

Contracts

0 of 3

contracts here have a descriptor in the registry

  • 0 covered
  • 0 partial
  • 3 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 2026201 transactions a day across 3 contractsThe data, as JSON
Contracts

3 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

USDT0 OFT Adapter

Bridge USDT out of Ethereum as USDT0 (send, after approving USDT to the adapter)

Uncovered
Address
0x6C96…1deeOAdapterUpgradeable
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 29 October – 6 November 2026 · 119 a day
Sourcify
Verified, exact match
Address from
docs.usdt0.to

Most-called functions

  1. send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,uint256),address)>99%Not formatted · 291 sendersTry it: a real call of send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,uint256),address) in the playground
  2. 0x779b432d<1%Not formatted · name not known · 1 sender

Arbitrum One

USDT0 OFT

Bridge USDT0 from Arbitrum One to another chain (send)

Uncovered
Address
0x14E4…8D92OUpgradeable
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 23 October – 6 November 2026 · 71 a day
Sourcify
Verified, exact match
Address from
docs.usdt0.to

Most-called functions

  1. send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,uint256),address)100%Not formatted · 340 sendersTry it: a real call of send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,uint256),address) in the playground

OP Mainnet

USDT0 OFT

Bridge USDT0 from OP Mainnet to another chain (send)

Uncovered
Address
0xF03b…A0aDOUpgradeable
Descriptor
None in the registry
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders75 transactions, 30 October – 6 November 2026 · 9.9 a day
Sourcify
Not verified
Address from
docs.usdt0.to

Most-called functions

  1. send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,uint256),address)100%Not formatted · 30 sendersTry it: a real call of send((uint32,bytes32,uint256,uint256,bytes,bytes,bytes),(uint256,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 USDT0 clear-signed

Of the 3 contracts of USDT0 here, 3 have no descriptor in the registry. We write, test and submit descriptors.