reUSDe

Re Protocol reUSDe

status: liquid2/2 checked · 1 liquid · hot
first bridged: 21 h ago
arrived via: ccip
contracts: 2 on 2 chains
confirmed by a transfer: 2 of 2
liquidity: 2 of 2 chains checked · 1 liquid
checking: hot
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-03 06:07:55 UTC · 2 d ago #8949 via ccip
token discovered 2026-09-03 21:49:50 UTC · 21 h ago 2 contracts today
first liquid 2026-09-04 19:07:11 UTC · 2 min ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

bera mint burn via ccip 5

0x5e5c810b3338b4b9215983db7aee0d592fd9f5a2 open

illiquidpools hold $0, under the floor

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

registry

{"via":"TokenAdminRegistry","pool":"0x37cAD86F09741D17A4124eb0c8dca7e2272f33e1","adapter":"ccip","selector":"1294465214383781161"}

ethereum canonical via ccip 3

0xddc0f880ff6e4e22e4b74632fbb43ce4df6ccc5a open

liquid74 bps · 0.74% via kyberswap

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

registry

{"tx":"0xb5ef00777bea1d3f8c34ac9cf071d25d4efcf1f634bc517c3f82420943056036","from":"bridge_pin"}

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 bera 0 of 1 reachable

No transfer has been seen leaving bera.

show 1 unreachable hide unreachable

ethereum no transfer seen

from ethereum 1 of 1 reachable

bera ccip 0xb5ef0077… 21 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8949	2 d ago	ccipethereum → bera	0xb5ef0077…056036	DISCOVERED	15 h

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