Hop Protocol — ETH address 0xb8901a…19727f

0xb8901acB165ed027E32754E0FFe830802919727f

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 (0xed6e0a…bad921).OFAC SDN list4inbound
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
unknown48.7%
Socket5.9%
Hop Protocol5.1%
LiFi3.7%
HopImpl1.8%
Chun Wang (F2Pool)0.9%

Who it transacts with

CounterpartyKnown asTransactions
0x710bda329b2a6224e4b44833de30f38e7f81d564Hop Protocol1322965
0x3a23f943181408eac424116af7b7790c94cb97a5Socket85399
0x4c9fad010d8be90aba505c85eacc483dff9b8fa9HopImpl47239
0x6ef81a18e1e432c289dc0d1a670b78e8bbf9aa35LiFi33631
0x1231deb6f5749ef6ce6943a275a1d3e7486f4eaeLiFi28156
0xd286595d2e3d879596fab51f83a702d10a6db27bSocket18858
0x9137a628546e2b1bc26f60a5d1262fb6d58ea44anot attributed16413
0x5d3675d698a3dd53e3457951e1debef717a29a72not attributed12628

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.