Skip to content

Cross-chain traceability

cross_chainTakes at most 12 points off the score

Example 0x7a3f...9c0d: transactions sent per chain

On EVM chains one key gives the same address on every chain. A wallet that sends transactions on several chains is one visible identity across all of them, and a bridge transfer that arrives at the same address ties the two sides together.

Spreading activity over chains can feel like splitting it up. With one address it does the opposite: what is known about the wallet on one chain, such as an ENS name on Ethereum or an exchange withdrawal on Base, applies to its activity everywhere else.

RuleFires whenSeverityConfidence
multichain_presenceThe address sent transactions on 2 or more chains: the chain’s own count from its RPC, or a transaction it signed. Coins and tokens that others sent to it do not count.medium from 4 chains, else low1.0
received_onlyOthers sent to the address on a chain where it never sent a transaction.info, no points1.0
bridge_matchAt least 0.001 leaves one chain, and 0% to 3% less of the same asset arrives at this same address on another chain within 45 minutes. The asset is the native coin when it is ETH or xDAI, or the same stablecoin.medium0.55 + 0.1 × (matches - 1), at most 0.85

The 3% leaves room for bridge fees. Each outgoing transfer is matched to at most one incoming transfer: the one with the smallest difference.

  • bridge_match only sees a bridge transfer that arrives at the same address. A transfer to a different address on the other side is not matched in V1.
  • A chain counts as used only where the address sent a transaction. Anyone can send coins or tokens to any address, so what only arrived there shows as received_only and costs no points. A chain where the address never sent a transaction and holds no native coin gets one quick check and is not read further.
  • Native coins other than ETH and xDAI, and tokens other than stablecoins, are not matched across chains.
  • Use a different address for each chain where you want activity kept apart.
  • A bridge keeps its own record of both ends. Receiving on a new address defeats a simple amount match, not the bridge’s own data.