Architecture

Proven stack. Novel mechanics.

Construct launches on infrastructure that has already been audited and battle-tested. The novel work is at the application layer. Not in consensus, not in sequencing, not in rollup proofs. That is where the novel work belongs.

Phase 1

OP Stack L2 on Ethereum.

The OP Stack provides a proven, audited rollup framework with full EVM compatibility. Any existing Solidity tooling, wallet, RPC client, or block explorer works on Construct from day one. Sequencing and settlement use components that have already secured billions of dollars across the Superchain ecosystem.

Starting as an L2 is a deliberate choice. It lets us ship the novel mechanics (Red Pools, Forging, CSwap, Degrader Scores) in months rather than years, without rebuilding consensus from scratch. Construct does not need its own base-layer consensus: it inherits ledger security from Ethereum and runs Proof of Degradation as an economic-security layer on top (see below).

Two-layer security

Proof of Degradation secures the economy, not the ledger.

Ledger security — ordering, settlement, data availability — is inherited from Ethereum via the OP Stack. Proof of Degradation secures the layer Ethereum cannot: the economy. Fair, capital-resistant distribution and the solvency of the closed-loop reward model. Because CNST is recyclable gas, using the chain and funding the rewards that pay participants are the same act — earning and protecting the economy are one behavior loop.

A migration to a sovereign chain remains optional and data-driven, evaluated only if real usage warrants it. It is not required for PoDeg to work; state and contract continuity would be preserved if pursued.

Gas & Compatibility

CNST is the only gas token users see.

CNST is the native gas token from genesis. ETH is bridged and abstracted. Users transact in CNST without holding or thinking about the underlying bridge asset. This creates native demand for CNST from the first transaction and avoids the dual-token UX problem that frustrates users on other L2s.

Full EVM compatibility means no porting work for existing Solidity contracts. solc, Foundry, Hardhat, Viem, wagmi, Etherscan forks all work day one.

Protocol-Layer Components

What ships at the chain level.

CSwap
Native AMM
Settlement-layer DEX, not a deployed application. All liquidity routes through it.
Ancilla
On-chain scheduler
Deterministic scheduling with no off-chain dependency. Replaces cron, keepers, automation services.
Forge Module
Contract fuel bonding
Every contract deploys with a CNST fuel reserve. Health is public, real-time, on-chain.
GPU Gate
GPU proof-of-work
Memory-hard GPU proof-of-work. ASIC/FPGA resistant by design.
Coordination Layer
libp2p gossip mesh
Peer-to-peer coordination for Red Pool participants. Pool announcements, participant set discovery, and timing synchronization propagate through a gossip mesh. No central server, no relay operator.

Compared to Existing Approaches

Why not just use what's already shipped.

Flashbots Protect
Private mempool
Centralizes order flow. Doesn't eliminate MEV, just relocates it.
MEV-Share / Blocker
Returns a cut of MEV
Still adversarial. Bots still extract. Users get crumbs back.
SUAVE
Decentralized block builder
Optimizes extraction efficiency. Adversarial frame unchanged.
Encrypted mempools
Threshold encryption
Adds latency, complexity. Post-decryption MEV still exists.
Optimism / Base / Arbitrum
L2 with sequencer ordering
Sequencer holds MEV power. Single point of ordering control.
Construct
MEV redirection
Bots earn more attacking Red Pools than attacking users. Cooperation is the Nash equilibrium.
“Every existing solution accepts the adversarial frame and tries to mitigate damage. Construct changes the frame.” Pitch Deck, slide 13

Economics →