The first warning came from a status line that just said pending. I was moving some $NIL over to Ethereum and nothing happened for a while.

I blamed the bridge. Congestion, probably, or a stuck transaction. On paper, that seemed obvious.

Then I went back to the @Nillion roadmap and that was the first mismatch. The migration isn't one click, it's a window. Operators unstake from the L2, bridge over, and rewards keep getting paid while it happens. The wait is built in. Confirmation ≠ Completion.

What I hadn't looked at is the order. Unstake → bridge (around nine days, apparently) → arrive on L1 → stake again → node running. Dusk goes live on mainnet and the node network has to bootstrap from people who were mid-transit a week earlier.

So the capital sits in neither place for a while. Covenants need nodes to decrypt on time, and nodes are partly a function of who finished the trip.

I'm still unsure how many operators see that gap as a cost worth paying #NIL

What I can't resolve is the end of the window. When the bridge closes and the L2 retires, and everyone who waited moves at once, does the Ethereum node set hold?#nil $NIL @Nillion