Security: sequencer, validator, withdrawals and exit times

What runs a layer

One operator runs one sequencer, one batch poster and one validator per layer. On day one there are no permissionless fraud proofs. In principle the operator could post a false state claim, and until the validator set opens nobody can challenge it within the confirm window.

Three things bound that:

• The rollup contracts on Elysium have their owner set to the burn address: there is no upgrade path, no key that can change the bridge, the Outbox or the validator set.
• If no assertion is confirmed for 201,600 HyperEVM blocks, about 2.3 days, anyone may call removeWhitelistAfterValidatorAfk on the rollup and take over validation. This is a function of the BoLD rollup contracts, checked in nitro-contracts v3.2.0 before deployment.
• Forced inclusion stays open: a user can put a transaction through the delayed inbox on Elysium even if the sequencer ignores them, including a withdrawal.

If a plan ends and the sequencer stops

The state remains on Elysium and paying the plan again restarts it. Until then, nothing new is sequenced. Users who want out should withdraw during the grace period. After the sequencer has stopped, leaving requires someone to replay the batches on Elysium and run a validator, or the operator restarting the layer.

Withdrawal timing

A withdrawal from a layer is claimable on Elysium after the confirm window of the layer it left, one hour by default (3,600 HyperEVM blocks, about an hour), plus the time until the next assertion is posted (one every 15 minutes while the layer is active). From Elysium to HyperEVM, the normal exit takes about 6 days.

Apps

One-click templates are short, tested contracts with no owner path to user funds beyond what each template's page states. Contracts written by the AI builder are as safe as the sentence and the tests that produced them: read them before trusting them with anything you cannot lose.