CNFI

Connect Financial

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

Lifecycle

first pin received pending no pin linked (added by hand, or before pins were tracked)
token discovered 2026-09-02 22:54:51 UTC · 4 d ago 3 contracts today
first liquid 2026-09-07 10:36:51 UTC · 8 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 ethereum (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.

arbitrum canonical via portal_bridge 8

0x6f5401c53e2769c858665621d22ddbf53d8d27c5same open

liquid263 bps · 2.63% via kyberswap

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

registry	+3	{"tx":"0xcb5956f667d26a7dc3fbd0e27bc3f193ef2da345386429f1ecd8cf246e1a566c","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":23}

ethereum lock mint wrapper via portal_bridge 5

0xfc1b550a53fc5765942234b8e4ae88c4693182e7 open

illiquidpools hold $0, under the floor

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

derivation

{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":23}

ethereum mint burn potential · no transfer seen 3

0x6f5401c53e2769c858665621d22ddbf53d8d27c5same open

illiquidpools hold $0, under the floor

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

same_address

{"chain":"ethereum"}

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 arbitrum 1 of 1 reachable

ethereum portal_bridge 0xcb5956f6… 4 d ago

from ethereum 0 of 1 reachable

No transfer has been seen leaving ethereum.

show 1 unreachable hide unreachable

arbitrum no transfer seen

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.

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