Chain security

Who this is for: developers and node operators who want to know what "security" means on Lumia beyond "it's a blockchain": what enforces correct transaction ordering, what enforces correct execution, what backs claims made about off-chain assets, and what has been independently reviewed.

Chain security on Lumia spans four distinct concerns. They fail independently: a valid proof doesn't make an oracle feed honest, and an audit engagement doesn't retroactively cover architecture built after it ran.

These four fail independently. A valid proof does not make an oracle feed honest, and an audit does not cover architecture built after it ran.

Sequencer

Orders and batches transactions before they are proven and settled. Ordering correctness and liveness live here.

zkProvers

Generates the proofs that make a sequencer's batches verifiable, so a state transition can't be accepted without a valid proof behind it.

Oracles & Attestation

How external price data and off-chain claims (reserves, custody) get represented on-chain, and why those are two different trust problems with different failure modes.

Audits

The independent security engagements around Lumia, and the scope each one covered.