ChainMind
Module · 1

Five archetypes of a chain.

Each archetype is the same five layers — consensus, execution, data availability, settlement, proof — assigned to different actors. Where the boundary falls determines who you trust.

ArchetypeSolana, Aptos, Sui, BSC

Monolithic L1

One chain handles consensus, execution, data availability, and settlement together.

Proof / ValidityRe-execution by full nodes
SettlementValidator set
Data AvailabilityValidator set
ExecutionValidator set
ConsensusValidator set

Performance comes from putting everything in one place. Trust is reduced to: enough validators are honest. Re-execution is the only proof — there is no proof artifact.

ArchetypeCelestia + Rollup + EVM L1

Modular stack

Layers are sold separately. Each rented from a different provider.

Proof / ValidityFraud or validity proof
SettlementSettlement L1 (Ethereum)
Data AvailabilityDA chain (Celestia / EigenDA)
ExecutionRollup operator
ConsensusDA chain (e.g. Celestia)

Specialization. Each layer can be replaced. The cost is more interfaces and more attack surface — bridges between the layers themselves become a trust point.

ArchetypeArbitrum, Optimism, Base

Optimistic rollup

Execute optimistically. Trust 1-of-N watchers to spot a fraud and submit proof.

Proof / ValidityFraud proof, after challenge window
SettlementSettlement L1
Data AvailabilitySettlement L1 (Ethereum)
ExecutionSequencer (often singleton)
ConsensusSettlement L1 (inherited)

Cheaper than ZK rollups. The 7-day challenge window is the price. Liveness depends on at least one honest watcher being online with a working bridge to the L1.

ArchetypezkSync Era, StarkNet, Scroll, Polygon zkEVM

ZK rollup

Every batch is accompanied by a validity proof verified on the settlement chain.

Proof / ValidityValidity proof (ZK)
SettlementSettlement L1 verifier contract
Data AvailabilitySettlement L1
ExecutionProver network
ConsensusSettlement L1 (inherited)

No challenge window. Withdrawal is final the moment a proof is verified on L1. Cost: heavy proving, often a trusted setup, sometimes a centralized sequencer for the moment of submission.

PsyPsy Protocol

Psy (sovereign ZK L1)

Sovereign L1 with native ZK. Cross-chain anchored to EVM/TRON via on-L1 verifiers.

Proof / ValidityPlonky2 → Groth16 → on-L1 verifier
SettlementNative L1, plus EVM/TRON anchor for bridges
Data AvailabilityNative (ScyllaDB + checkpoints)
ExecutionRealm prover network (Plonky2)
ConsensusCoordinator + 128 realms (PARTH)

Not a rollup — Psy is its own L1. But its bridges are settled by ZK proofs on EVM and TRON, so withdrawal trust reduces to circuit soundness, not validator honesty. M-of-N relayers exist for liveness only — any user can self-generate a withdrawal proof if relayers go silent.

trustless

The layer's safety property is enforced by math. No human can override it.

trust minimized

Distributed trust. Many actors must collude to violate it.

trust required

A small set of actors can violate the layer's safety. This is where attacks land.