Control profile
- Transaction ordering
- A centralized upstream sequencer orders transactions; the validity system has one whitelisted proposer and one whitelisted challenger.
- Escape hatch
- Users can force transactions through Ethereum after the sequencer window, but permissioned proof roles and effectively indefinite inactivity recovery prevent an independent exit guarantee.
- Upgrade authority
- An X Layer multisig can execute immediate upgrades with no user exit window; one critical implementation address was not source-verified at review.
- Liveness record
- OKX announced a 2025 mainnet upgrade that temporarily suspended block production and all X Layer services. The later migration to an OP Stack and OP Succinct design improved the architecture without removing the single sequencer, permissioned proof roles, or instant upgrade control.
Ketju assessment
REJECTED. X Layer combines three control dependencies that should not be blurred together: a single operator orders transactions, whitelisted actors control proof proposal and challenge, and an operator multisig can change the system immediately. The historical planned suspension demonstrates that block production is operationally within the platform's control. Ethereum data availability and a forced-transaction path are positives, but they do not provide a credible self-service exit when proof recovery and upgrade authority remain permissioned.
Observable review triggers
- Revisit after proposer and challenger roles become permissionless
- Revisit after regular upgrades carry an enforceable on-chain delay of at least 7 days
- Revisit after every critical implementation is source-verified and inactivity recovery is practical
These triggers make the judgment monitorable. They are not predictions; each identifies a fact that would revoke or force review of the current assessment.
Advisor implementation questions
- Does the client’s thesis require censorship resistance, or primarily low-cost settlement?
- Can the client exit without cooperation from the normal transaction-ordering party?
- Who can upgrade bridges or contracts, and what delay applies?
- Does the asset introduce an issuer weaker than the chain grade?
- What evidence will show a halt, censorship event, or governance change?
Research sources
- OKX — X Layer migration from Geth to Reth — OP Stack migration, centralized sequencer, execution client
- OKX — X Layer mainnet upgrade commenced — operator halt, upgrade control
- L2BEAT — X Layer — permissioned proof roles, upgrade delay, source verification, forced transactions
Sources were accessed 2026-08-19. Primary documents and measured control conditions can change; the review triggers above govern off-cycle reassessment.