TXL

Tixl Token

status: liquid2/2 checked · 1 liquid · warm
first bridged: 3 d ago
arrived via: polygon_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 04:51:25 UTC · 3 d ago 3 contracts today
first liquid 2026-09-04 18:45:50 UTC · 6 h ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

More than one contract on polygon (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.

ethereum canonical via polygon_bridge 8

0x8eef5a82e6aa222a60f009ac18c24ee12dbf4b41same open

illiquidtradeable but costly — 529 bps · 5.29%

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

registry	+3	{"tx":"0xc2edb317674cae8dd0ece7d01f57b13dc68c8102b19c904dc9f0bcfedb3399ce","from":"bridge_pin"}
derivation	+5	{"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}

polygon mint burn via polygon_bridge 5

0x6ee244034336f0135dcef9a5755d03a9f51dd114 open

illiquidpools hold $0, under the floor

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

derivation

{"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}

polygon mint burn shadowed · not checked potential · no transfer seen 3

0x8eef5a82e6aa222a60f009ac18c24ee12dbf4b41same open

liquid212 bps · 2.12% via kyberswap

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

same_address

{"chain":"polygon"}

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

polygon polygon_bridge 0xc2edb317… 3 d ago

from polygon 0 of 1 reachable

No transfer has been seen leaving polygon.

show 1 unreachable hide unreachable

ethereum no transfer seen

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