VELVET

Velvet

status: liquid2/2 checked · 1 liquid · warm
first bridged: 2 d ago
arrived via: debridge
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 1 liquid · 1 unmeasured
checking: warm
already alerted on: nothing yet
pins: 17

Lifecycle

first pin received 2026-09-02 21:49:29 UTC · 2 d ago #3075 via portal_bridge
token discovered 2026-09-02 23:34:49 UTC · 2 d ago 3 contracts today
first liquid 2026-09-05 08:50:26 UTC · 5 min ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

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.

binance canonical via portal_bridge 11

0x8b194370825e37b33373e74a41009161808c1488 open

liquid25 bps · 0.25% via kyberswap

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

registry	+3	{"tx":"0x65e22f880bf6dff7c6773c5cd1a2309ba60fad5668fa08147898660c606bc888","from":"bridge_pin"}
registry	+3	{"tx":"0xc54ea10ca16b5bffe690c5b0fe91315bf6298da012a7e676c36f2e92104929f8","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":4}

base mint burn via debridge 5

0xb06adb0cc62208aa738ec89122933f93a40ba090 open

illiquidpools hold $0, under the floor

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

registry

{"via":"submission_claim","adapter":"debridge","claimTx":"0xcc30a86edcba5bca9e8c96a72d2875db9fcb7f6445df87e610004d583dc53574"}

base lock mint wrapper via portal_bridge shadowed · not checked 7

0xbf927b841994731c573bdf09ceb0c6b0aa887cdd open

unknownBALANCE_READ_FAILED — not a negative result

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

offchain_list	+2	{"via":"token-list","symbol":"VELVET","adapter":"debridge","decimals":18,"debridgeChainId":8453,"decimalsDiffersFromSource":false}
derivation	+5	{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x8d2de8d2f73F1F4cAB472AC9A881C9b123C79627","originChainId":4}

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

binance portal_bridge 0x6cfc6533… 2 d ago

from binance 1 of 1 reachable

base debridge, portal_bridge 0xc54ea10c… 36 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8769	2 d ago	portal_bridgebinance → base	0xf133f6de…bd9855	SKIPPED_DUPLICATE	15 h
#8384	2 d ago	portal_bridgebase → binance	0xf87443d8…b61c54	SKIPPED_DUPLICATE	13 h
#5857	2 d ago	portal_bridgebase → binance	0xd3db5b8e…fc36d7	SKIPPED_DUPLICATE	1 h 35 min
#5849	2 d ago	portal_bridgebase → binance	0x80cedba7…6adf86	SKIPPED_DUPLICATE	1 h 37 min
#5842	2 d ago	portal_bridgebase → binance	0x0c2e47a0…e2fe70	SKIPPED_DUPLICATE	1 h 38 min
#5558	2 d ago	portal_bridgebase → binance	0x88e61ca1…8adc34	SKIPPED_DUPLICATE	2 h 4 min
#5557	2 d ago	portal_bridgebase → binance	0x954f81f8…3a83c8	SKIPPED_DUPLICATE	2 h 4 min
#5447	2 d ago	portal_bridgebase → binance	0x6c6a0224…ae9845	SKIPPED_DUPLICATE	2 h 26 min
#5182	2 d ago	portal_bridgebase → binance	0x6400ccff…3efc4f	SKIPPED_DUPLICATE	2 h 48 min
#4107	2 d ago	portal_bridgebase → binance	0x6cfc6533…b7450e	SKIPPED_DUPLICATE	4 h 26 min
#3308	2 d ago	portal_bridgebase → binance	0xf74bbd34…551ccb	SKIPPED_DUPLICATE	5 h 50 min
#3080	2 d ago	portal_bridgebase → binance	0xe77f21f0…9c0c29	SKIPPED_DUPLICATE	6 h

all 17 pins

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