Token Dashboard
tokens
2818
contracts
8328
confirmed
5710 of 8328
chains seen
14
unmeasured
181
queued
0

MAIV

MAIV
status
fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged
2 d ago
arrived via
portal_bridge
contracts
3 on 2 chains
confirmed by a transfer
2 of 3
liquidity
2 of 2 chains checked · 2 liquid
checking
hot
already alerted on
base, ethereum
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:06:40 UTC · 2 d ago #7440 via portal_bridge
  2. token discovered 2026-09-03 02:17:17 UTC · 2 d ago 3 contracts today
  3. first liquid 2026-09-03 02:54:53 UTC · 2 d ago a chain quoted liquid
  4. first alert 2026-09-03 02:54:53 UTC · 2 d ago multi_chain_liquid, sent 2 d ago
  5. reported chains base, ethereum — 2 of 2

Where this token lives

More than one contract on base (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

base canonical via portal_bridge potential · no transfer seen 2
0xa96a84774d5eb308b8bd05ed2b6d5ce40a7e7b4b open
liquidlast verified an unknown time

Every source here is an inference. A contract on this chain has not confirmed the link itself.

discord+2{"notes":["Wormhole NTT"],"proven":true,"ticker":"MAIV","source_tx":"0xab2138838abe2ef02d49fb289e0d072dbddb5ba27845e7d50008b1426b82ea6e","message_id":"1478424123003633836","message_ts":"2026-03-03T16:09:38","source_url":"https://wormholescan.io/#/tx/0xab2138838abe2ef02d49fb289e0d072dbddb5ba27845e7d50008b1426b82ea6e","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1478424123003633836","source_kind":"wormhole_tx","curator_liquidity":false}
base canonical via portal_bridge shadowed · not checked 8
0x4b82ac0d1531290e3edb3abe9a985623bf7edaee open
liquidlast verified 2 d ago

2 of 2 sources are protocol-attested — a contract confirmed this link.

registry+3{"tx":"0x174cb3de2bd5ad929ad3fb704e7024983ed8987b4583d15c1604124a31186745","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":30}
ethereum mint burn via portal_bridge 7
0x39903a1a6f289a67e0de94096915c4ccd506ab2a open
liquidlast verified 2 d ago

1 of 2 sources are protocol-attested — a contract confirmed this link.

derivation+5{"via":"ntt_peer","adapter":"portal_bridge","manager":"0x373821335a7ff64d9768aeda7c47a25db7ac0221","wormholeId":2,"peerManager":"0x373821335a7ff64d9768aeda7c47a25db7ac0221"}
discord+2{"notes":["Wormhole NTT"],"proven":true,"ticker":"MAIV","source_tx":"0xab2138838abe2ef02d49fb289e0d072dbddb5ba27845e7d50008b1426b82ea6e","message_id":"1478424123003633836","message_ts":"2026-03-03T16:09:38","source_url":"https://wormholescan.io/#/tx/0xab2138838abe2ef02d49fb289e0d072dbddb5ba27845e7d50008b1426b82ea6e","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1478424123003633836","source_kind":"wormhole_tx","curator_liquidity":true}

How it moves between chains

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 1 of 1 reachable
ethereum portal_bridge 0x174cb3de… 2 d ago
from ethereum 1 of 1 reachable
base portal_bridge 0xd87874a5… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#7440 2 d ago portal_bridgebase → ethereum 0x9debe5cb…c084aa SKIPPED_DUPLICATE 9 h

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid2 d ago SENT 2 d ago96

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.