Skip to content

Clear Signing coverage tracker Bridges

Hyperliquid Bridge

2 contracts of Hyperliquid Bridge on Arbitrum One, checked against the Clear Signing registry and their recent transactions.

Status
Partial
TVL
$195M on the four chains, from DefiLlama, 7 November 2026

Contracts

1 of 2

contracts here has a descriptor in the registry

  • 1 covered
  • 0 partial
  • 1 uncovered

Recent traffic

52%

of recent transactions a wallet could clear-sign

52% 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 20266,070 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.

Arbitrum One

Circle CctpExtension (Arbitrum to HyperCore)

Deposit USDC from Arbitrum to Hyperliquid (HyperCore) via CCTP in one transaction (batchDepositForBurnWithAuth)

Covered
Address
0xA95d…4fcECctpExtension
Descriptor
calldata-CctpExtension.jsonOwner: Circle Internet FinancialNo attestation
Functions
1 of 6 writable functions formatted
Recent calls
Formatted: 100% of recent transactions, 100% of recent senders1,000 transactions, 6 November 2026 · 3,152 a day
Sourcify
Verified, exact match

Most-called functions

  1. batchDepositForBurnWithAuth((uint256,uint256,uint256,bytes32,uint8,bytes32,bytes32),(uint256,uint32,bytes32,bytes32,uint256,uint32,bytes))100%Formatted · 847 sendersTry it: a real call of batchDepositForBurnWithAuth((uint256,uint256,uint256,bytes32,uint8,bytes32,bytes32),(uint256,uint32,bytes32,bytes32,uint256,uint32,bytes)) in the playground

Arbitrum One

Hyperliquid Bridge2 (legacy USDC bridge)

Legacy USDC deposits: the user transfers native USDC to this address (the transaction goes to the USDC contract); withdrawals are signed on Hyperliquid, not Arbitrum. Docs mark it deprecated in favour of CCTP

Uncovered
Address
0x2Df1…3dF7Bridge2
Descriptor
None in the registry
Functions
0 of 14 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 2,918 a day
Sourcify
Verified, partial match

Most-called functions

  1. batchedRequestWithdrawals((address,address,uint64,uint64,(uint256,uint256,uint8)[])[],(uint64,address[],uint64[]))42%Not formatted · 4 sendersTry it: a real call of batchedRequestWithdrawals((address,address,uint64,uint64,(uint256,uint256,uint8)[])[],(uint64,address[],uint64[])) in the playground
  2. batchedFinalizeWithdrawals(bytes32[])41%Not formatted · 4 sendersTry it: a real call of batchedFinalizeWithdrawals(bytes32[]) in the playground
  3. batchedDepositWithPermit((address,uint64,uint64,(uint256,uint256,uint8))[])18%Not formatted · 39 sendersTry it: a real call of batchedDepositWithPermit((address,uint64,uint64,(uint256,uint256,uint8))[]) 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 Hyperliquid Bridge clear-signed

Of the 2 contracts of Hyperliquid Bridge here, 1 has no descriptor in the registry. We write, test and submit descriptors.