Elysium Security: The Trust Model at Launch, Explained
Elysium launches with a single sequencer, permissioned validators, an AnyTrust data committee and upgradeable bridges, and no published audits yet. What each means for users and builders, and what's planned.
3 min readUpdated First published By Titan Locker
At launch, Elysium trusts a small set of operators: one sequencer (run with Conduit), permissioned validators, and an AnyTrust committee for data availability. There's no security council and no published audit of Elysium-specific contracts yet. Users keep an escape hatch — transactions can be forced through HyperEVM's delayed inbox — and permissionless fraud proofs (Arbitrum BoLD) are planned without a date.
| Component | At launch | Planned |
|---|---|---|
| Sequencer | Single sequencer, priority-fee ordering, no privileged lanes | Timeboost, MEV telemetry |
| Censorship resistance | Force-include via HyperEVM's delayed inbox (24 h delay on testnet) | — |
| Validation | Permissioned validators | Permissionless BoLD fraud proofs (no date) |
| Data availability | AnyTrust k-of-n committee (size unpublished; 1-of-1 on testnet), full-data fallback to HyperEVM | Larger committee |
| Bridges | Upgradeable proxies and beacon clones | — |
| Audits | None published for Elysium-specific contracts | Part of post-launch hardening |
| HyperCore data (after upgrade) | Attested by the sequencer, not proven | — |
Is Elysium a rollup?
Kinetiq calls Elysium an optimistic rollup that settles to HyperEVM. Its transaction data, though, is held by an AnyTrust committee that posts certificates to HyperEVM, so frameworks such as L2BEAT's would class it as an AnyTrust chain (an “optimium”) rather than a rollup. AnyTrust needs only one honest committee member; if the committee is unavailable, Elysium posts full data to HyperEVM, which costs more but doesn't halt the chain. A dishonest committee threatens liveness, not the safety of funds.
What users should take from this
- The sequencer can reorder or delay your transactions, but can't steal them; the delayed inbox is the backstop.
- Bridge contracts are upgradeable: Kinetiq notes the beacon owner can replace all bridge-wallet logic at once — the same trust class as the chain's upgrade keys.
- Keep amounts you bridge proportionate while the chain hardens.
- Elysium isn't listed on L2BEAT, which tracks Ethereum-settling chains.
What builders should take from this
- Elysium and HyperCore actions aren't atomic: make callbacks idempotent.
- HyperCore market data (after the upgrade) is sequencer-attested — treat it like an oracle with that trust model.
- The 300 Mgas/s throughput target is still to be validated under load.
How Titan Locker fits
Locks on Titan Locker are immutable contracts: nobody, including Titan, can unlock early, and every lock's owner, amount and unlock date are readable on-chain. Titan Locker's Elysium manager is 0x713E56CeE7060F01F710bF26Aff988264dcfb311; its source and deployment record are public at https://github.com/titan-ecosystem/Titan-Locker-Contracts. The chain-level trust assumptions above still apply to everything on Elysium.
Frequently asked questions
Is Elysium safe?
Elysium launches with a single sequencer, permissioned validators, an AnyTrust data committee, upgradeable bridges and no published audits; permissionless BoLD proofs and audits are planned. Users can force transactions through HyperEVM's delayed inbox.
Is Elysium decentralized?
Not yet: sequencing and validation are permissioned at launch, with permissionless fraud proofs planned.
Is Elysium a rollup or an optimium?
Kinetiq calls it an optimistic rollup; with AnyTrust data availability it's what many frameworks call an optimium/AnyTrust chain.
Has Elysium been audited?
No audit of Elysium-specific contracts had been published as of early November 2026; audits are part of Kinetiq's post-launch hardening plan.
Can the Elysium sequencer censor me?
It can delay you, but transactions can be forced through the delayed inbox on HyperEVM (a 24-hour delay on testnet).
Something unclear or out of date? Tell us in Telegram support