Hop Protocol — ETH address 0x3d4Cc8…48EDd1

0x3d4Cc8A61c7528Fd86C55cfe061a78dCBA48EDd1

PublicAML knows this Ethereum address as Hop 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 4 hops from OFAC SDN list (0xdcbeff…643193).

What we know about this address

ChainEthereum (ETH)
EntityHop Protocol
Categorybridge
AML score0 / 100 (floored from 55, 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 4 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list4inbound
Funds reaching this address are 4 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list4inbound
Funds reaching this address are 4 hops from OFAC SDN list (0xed6e0a…bad921).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
unknown44.9%
Socket2.6%
LiFi1.8%
HopImpl1.3%
mixer1.0%

Who it transacts with

CounterpartyKnown asTransactions
0x305933e09871d4043b5036e09af794facb3f6170not attributed3752
0x10b6cbdfe187c04d63f179b87067c49e7a1e91afnot attributed2770
0x9298dfd8a0384da62643c2e98f437e820029e75enot attributed2090
0x4c9fad010d8be90aba505c85eacc483dff9b8fa9HopImpl849
0x3a23f943181408eac424116af7b7790c94cb97a5Socket833
0x1231deb6f5749ef6ce6943a275a1d3e7486f4eaeLiFi553
0xa6a688f107851131f0e1dce493ebbebfaf99203enot attributed495
0x10720f58cf4a22fa540ff10430fd967d2ef102denot attributed392

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.