Mainnet Strategy
Mainnet Strategy
Rollout Plan and Sequencer Abstraction
SnarkSide’s deployment strategy is not just a matter of moving from testnet to mainnet. It is the carefully staged introduction of a new cryptographic execution model into DeFi—one that breaks with legacy assumptions about transparency, addressability, and transaction atomicity.
The path to mainnet focuses on a phased rollout of the core systems, combined with an abstraction layer over sequencing logic that gradually moves from centralized coordination to decentralized intent execution. This page outlines the launch stages, sequencer model evolution, and governance hooks for final deployment.
1. Rollout Phases
SnarkSide’s mainnet release is divided into four major phases:
Phase 0 – Encrypted Settlement L1 Contracts
Deploy minimal settlement contracts on Ethereum mainnet
Add verifier contract for Groth16 proofs
Enable batched intent proof submission and vault Merkle root tracking
This phase supports read-only encrypted trade playback and proof submission APIs
Phase 1 – Trusted Relayer Network + Prover Layer
Launch selected relayers for intent batching and matching
Use centralized relay endpoints for throughput and reliability
Prover coordination is federated, using whitelisted prover nodes
CipherVault, Oblivion Pool, and Liquidation systems become active
LPs and Traders can interact via ZK Wallet SDK and demo clients
Phase 2 – Sequencer Abstraction + Intent Mesh
Introduce permissionless relayer registration via SNSD staking
Enable encrypted relayer gossip (non-direct matching, trustless routing)
Rollout of
RelayerVerifiercontract to accept matching proofs only from bonded nodesLaunch of intent gossip mesh across geographic clusters
Third-party bots can submit match bundles via blind handshakes
Phase 3 – Sovereign Rollup Launch
Deploy dedicated rollup using OP Stack + ZK-native runtime
Use SnarkSide sequencer for block production; rotate proposers via $SNSD stake-weight
All intents are published off-chain and resolved via in-rollup intent pool
Cross-rollup compatibility with Ethereum, Base, and Solana
L2 gas fully paid in SNSD
ZK-native bridge deployed for withdrawals and L1 asset interoperability
2. Sequencer Abstraction
The sequencer in SnarkSide plays a vastly different role than in other L2s or DEXes. Rather than sequencing transactions, it sequences intent validity windows and constraint resolutions.
This abstraction means:
Sequencers never see user orders or addresses
Sequencer nodes are relayer/prover hybrids
Block construction is replaced with proof bundles and constraint attestation
Matching is resolved via multi-party computation before inclusion
Abstracted Sequencer Responsibilities
Vault Tree Coordination
Maintain latest Merkle root and nullifier set
Proof Window Rotation
Trigger epoch-based proof verification intervals
Batch Inclusion Proofs
Aggregate matched intents into zk-rollup bundles
Uptime Enforcement
Relayers must prove liveness for continued sequencing rights
Staked Bond Arbitration
Disputes resolved via zk validity challenges (future version)
Sequencer consensus is proof-based, not gossip-based. Inclusion priority is not time-driven, but constraint-satisfaction driven.
3. Deployment Finality
The final architecture will resemble a modular ZK rollup chain with:
Encrypted off-chain matching
ZK-only intent execution
Native support for MEV resistance at protocol level
Shielded LP system with dark pool liquidity mechanics
Integrated oracle and liquidation proofs
Settlement bridging to Ethereum L1
All protocol modules—intent processing, LP liquidity, relayer arbitration, vault lifecycle—are abstracted into verifiable, decentralized systems that require no transparency, only provable constraint compliance.
4. Governance and Upgrade Path
Governance initialized via $SNSD holder quorum
Circuit upgrades via timelocked zkGov proposals
Intent pool parameters (batch time, max size, vault cap) subject to snapshot governance
Multi-sig only used for emergency halts in first 3 epochs
Future additions include:
Community-proposed circuits for custom constraint sets
Third-party relayer clusters incentivized via $SNSD emission
Research DAO for benchmarking and vulnerability testing
Conclusion
SnarkSide does not “launch” like traditional apps. It emerges through constraint satisfaction, cryptographic guarantees, and sequencer detachment.
From encrypted vaults to sovereign rollup governance, the mainnet plan reflects the same thesis as the protocol itself:
Opacity where needed. Verifiability everywhere else.
Last updated