hwUSD
name unknown
status illiquid 3/3 checked · 0 liquid · warm
first bridged 2 d ago
arrived via layerzero
contracts 3 on 3 chains
confirmed by a transfer 3 of 3
liquidity 3 of 3 chains checked · 0 liquid
checking warm
already alerted on nothing yet
Lifecycle
first pin received
2026-09-06 14:00:10 UTC · 21 h ago
#9371 via layerzero
token discovered
2026-09-05 12:33:06 UTC · 2 d ago
3 contracts today
first liquid
pending
not yet
first alert
pending
not yet
reported chains
pending
none yet
Where this token lives
ethereum
canonical
via layerzero
4
0xa2f8da4a55898b6c947fa392ef8d6bfd87a4ff77same
copy
open
illiquid pools hold $0, under the floor
1 of 2 sources are protocol-attested — a contract confirmed this link.
discord +1 {"notes":[],"proven":false,"ticker":"hwUSD","source_tx":null,"message_id":"1420906191755935865","message_ts":"2025-09-25T22:53:55","source_url":"https://layerzeroscan.com/address/0xffd5FFF7F184fa63e7B9eEdF7EEc2dA7bf03f170","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420906191755935865","source_kind":"oft_address","curator_liquidity":false} registry +3 {"tx":"0xf00d57514794d0165dcfe9cf426b3badbaaf835ab1bf9dfc0bbd2fc6825ddc74","from":"bridge_pin"}
base
mint burn
via layerzero
4
0xa2f8da4a55898b6c947fa392ef8d6bfd87a4ff77same
copy
open
illiquid pools hold $0, under the floor
Every source here is an inference. A contract on this chain has not confirmed the link itself.
discord +1 {"notes":[],"proven":false,"ticker":"hwUSD","source_tx":null,"message_id":"1420906191755935865","message_ts":"2025-09-25T22:53:55","source_url":"https://layerzeroscan.com/address/0xffd5FFF7F184fa63e7B9eEdF7EEc2dA7bf03f170","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420906191755935865","source_kind":"oft_address","curator_liquidity":false} same_address +3 {"chain":"base"}
hyperevm
mint burn
via layerzero
4
0xa2f8da4a55898b6c947fa392ef8d6bfd87a4ff77same
copy
open
illiquid pools hold $0, under the floor
Every source here is an inference. A contract on this chain has not confirmed the link itself.
discord +1 {"notes":[],"proven":false,"ticker":"hwUSD","source_tx":null,"message_id":"1420906191755935865","message_ts":"2025-09-25T22:53:55","source_url":"https://layerzeroscan.com/address/0xffd5FFF7F184fa63e7B9eEdF7EEc2dA7bf03f170","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420906191755935865","source_kind":"oft_address","curator_liquidity":false} same_address +3 {"chain":"hyperevm"}
How it moves between chains
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.
from base
2 of 2 reachable
from ethereum
2 of 2 reachable
from hyperevm
2 of 2 reachable
Pins behind this token
Pin Received Bridge Bridge tx Outcome Discovery took
#9371 21 h ago
layerzeroethereum → hyperevm
0xf00d5751…5ddc74 DISCOVERED
18 min
Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.