Synapse Protocol — ETH address 0x7E7A0e…18C96a

0x7E7A0e201FD38d3ADAA9523Da6C109a07118C96a

PublicAML knows this Ethereum address as Synapse Protocol, a bridge. Its AML score is 0 of 100 because we treat this address as infrastructure (known bridge — infrastructure, AML floored). Exposure that reaches it is not scored against it, and the findings below describe what we traced rather than an accusation. Funds reaching this address are 3 hops from OFAC SDN list (0xdcbeff…643193).

What we know about this address

ChainEthereum (ETH)
EntitySynapse Protocol
Categorybridge
AML score0 / 100 (floored from 70, treated as infrastructure)

Risk findings

Each row is a path our propagation engine traced from a flagged address to this one, with the number of hops and the source that flagged it. A finding is an observation about the flow of funds, not a statement about the owner of this address.

FindingSourceHopsDirection
Funds reaching this address are 3 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list3inbound
Funds reaching this address are 3 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list3inbound
Funds reaching this address are 4 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list4inbound

7 further internal signals are held back from this page. They come from heuristics with known false positives, and we do not publish an accusation we would not defend. They are visible in the live check.

Where the funds came from

SourceShare of received value
unknown99.5%

Who it transacts with

CounterpartyKnown asTransactions
0x2796317b0ff8538f253012862c06787adfb8ceb6Synapse Protocol71349
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2WETH39289
0x1116898dda4015ed8ddefb84b6e8bc24528af2d8Synapse Protocol32316
0x3a23f943181408eac424116af7b7790c94cb97a5Socket24315
0xc9b89acfb36c9f7d8d2befe38ac3fb766204cbd9not attributed1747
0xe6a20a2eade672bcfeb19529137c5f79b406c596not attributed825
0xca74f404e0c7bfa35b13b511097df966d5a65597"WinnersWin" on Polymarket581
0xffb9faf89165585ad4b25f81332ead96986a2681XY Finance422

If this page is wrong

Attribution and risk propagation both make mistakes, and a page like this one is visible for a long time. If you own this address or can show that a finding here is incorrect, tell us and we will re-check it. Corrections are applied to the underlying data, so they carry over to the API and to every other view of this address.

Contact us about this address

PublicAML reports what it can observe on-chain and what public and vendor sources say about an address. Nothing on this page is a legal finding, an allegation against a person, or advice. Risk scores describe exposure through transaction paths, and an address can carry exposure without its owner having done anything wrong.

Data is read live from the PublicAML API at the time this page was served.