⛔ One-way. Burning MOLI destroys it. There is no instruction that brings it back,
so bMOLI cannot be redeemed for MOLI. ⛔ Backing is the bonded anchor, not proof-of-work
— and the bond only covers a publisher signing two attestations for one height. A single
false anchor is not slashable, and this contract has no owner and no pause, so during the
challenge window there is no on-chain remedy. The window buys time to stop accepting the token.
1 · Wallet
account
—
chain
—
balance
—
base fee
—
⛔ Your wallet reserves gasLimit × maxFeePerGas — the
worst case, not the likely cost. A red alert on a valid transaction usually means that
reserve exceeds your balance, not that the transaction is wrong.
2 · Deploy BridgedMoli
Deployed once. Both constructor arguments are immutable afterwards.
—
3 · Burn MOLI on Molibra
This is the destruction the mint is backed by. It cannot be undone.
—
⛔ Addressed to a contract, never to yourself. MetaMask refuses calldata sent to an
account it manages — "External transactions to internal accounts cannot include data" —
and a self-addressed Molibra payload looks exactly like that. Consensus is unaffected: every
decoder runs before the EVM branch, so the destination is never called.
4 · Anchor the block, then claim
The block holding the burn must be anchored on Ethereum, and the challenge
window must pass, before the mint is possible. Anchoring is done on the
settlement page.
no proof loaded
5 · Conservation
What was destroyed on Molibra, against what exists on Ethereum.