Cross-chain traceability
On EVM chains one key gives the same address on every chain, so a wallet that sends transactions on several chains is one visible identity across all of them.
| Rule | Fires when | Severity | Confidence |
|---|---|---|---|
multichain_presence | The 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 low | 1.0 |
received_only | Others sent to the address on a chain where it never sent a transaction. | info, no points | 1.0 |
bridge_match | At 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. | medium | 0.55 + 0.1 × (matches - 1), at most 0.85 |
The 3% leaves room for bridge fees. A bridge transfer to a different address on the other side is not matched in V1.
How to reduce it
Section titled “How to reduce it”- Keep a separate address on each chain where you want the activity kept apart.
- A bridge keeps its own record of both ends, so receiving on a new address defeats a simple amount match but not the bridge’s own data.