BLUEAGENTThe pledge window is closed. Do NOT send tokens — transfers after the deadline are not counted toward the allocation table. If your transfer is not in the ledger below, it is not in the allocation. There is still no claim contract: allocations are published before distribution, not guaranteed. If you sent something by mistake, use the contact route at the bottom of this page rather than sending anything further.
Token migration pledge
The window for pledging old $BLUEAGENT toward the relaunch has closed. This page does not hold, sign, or move anything — it reads the chain and publishes every transfer it found, with the transaction hash for each one.
0xA4660F6b1d939358042Abd8111735a1D6F149845The same address on both chains. It stays published so pledgers can audit the ledger against the explorer — not as somewhere to send to. Anyone telling you this window is still open, or offering a “late pledge”, is not us.
How it works
The window for transferring old $BLUEAGENT has passed. Nothing sent to the address below is counted now — the address stays published so that people who did pledge can verify where their tokens went.
This page reads Transfer events into the receiving wallet directly from the chain. Every transfer that landed before the deadline is listed below with its transaction hash linked to the block explorer, so you can check it yourself.
The final allocation table is published from this same ledger. The claim contract is built separately and does not exist yet — see the notice above.
Sent the wrong token, or sent by mistake? Reach out on X @blueagent_. Anything that is not old $BLUEAGENT is returned on request. A pledged $BLUEAGENT transfer is not reversible — that is what the warning above means.
The full record is downloadable as CSV and readable as JSON. Neither requires an account. Every row can be checked against the block explorer without trusting this page.