SOV Network

PRE-TESTNET DEVELOPMENT

Native infrastructure for open value.

SOV Network is a native, non-EVM Layer 1 in active development—built around verifiable consensus, Ed25519 accounts, and infrastructure that can be operated independently.

Explore the design View development status

Mainnet is not live. No public token sale is offered on this website.

Native addresssov1…
SignaturesEd25519
ExecutionNative / non-EVM
Native assetSOV

01 / ARCHITECTURE

Designed as a chain, not a compatibility layer.

The protocol uses its own transaction format, account model, address space, and wallet verification boundary. Compatibility is defined by open specifications—not by imitating Ethereum JSON-RPC.

04

Wallet verification

Local signing, native addresses, multi-provider RPC comparison, and light-client checkpoints.

03

Public RPC boundary

Non-validator full nodes, bounded native routes, and isolated edge gateways.

02

Consensus network

Independent validator operators, signed evidence, state sync, and fault campaigns.

01

Native protocol

Canonical transactions, deterministic state commitments, Ed25519 authorization, and sov1 addresses.

02 / PRINCIPLES

Decentralization must be measurable.

A

Independent operators

Mainnet readiness requires distinct operators, infrastructure, control paths, and publicly reviewable evidence.

B

Verify at the edge

Wallets should verify network identity, transaction bytes, provider agreement, and consensus checkpoints locally.

C

Fail closed

Unclear state, inconsistent heights, invalid signatures, and unsafe deployment configuration are rejected rather than guessed.

03 / ROADMAP

Launch follows evidence.

Dates are not promised before the security and decentralization gates are satisfied.

  1. 01
    Protocol core

    Native transaction, consensus application, state sync, wallet SDK, and bounded RPC work.

    In development
  2. 02
    Distributed testnet

    Independent hosts, fault testing, public telemetry, and external review.

    Next gate
  3. 03
    Wallet and explorer

    Reference wallet, public explorer, provider registry, and vendor integration.

    Planned
  4. 04
    SOV Network Mainnet

    Genesis ceremony and launch only after the published gates pass.

    Gated

SOV NETWORK

Open infrastructure begins with verifiable boundaries.

This website will publish testnet access, technical documentation, explorer links, and mainnet readiness evidence as they become available.

Back to top