Solidus Network Roadmap

Unified project roadmap synthesized from all source documents across the Solidus ecosystem. Where individual plans presented conflicting timelines, this document reconciles them into a single coherent sequence. All phases are approximate and subject to adjustment as market conditions, funding, and technical progress evolve.

Status note (2026-06-07): Several items below shipped ahead of this narrative. Live on testnet today: Verify, Identity, Auth, Pod, Explorer, Node (validator + operator dashboard), RPC, the SDKs, and the BFT validator testnet. The phases below describe the original planned sequencing, not current state — see the Ecosystem → Service Map for authoritative per-surface live/planned status.

Phase 1: Foundation (Months 1-6)

The foundation phase establishes the technical core, validates the product thesis, and builds the initial community.

Deliverables

• Verify product MVP (identity verification): Functional decentralized identity verification service capable of performing KYC checks, issuing W3C Verifiable Credentials, and storing results in user-controlled data pods. This is the first revenue product and the primary validation vehicle for the “verify once, present everywhere” protocol value proposition.

• Protocol specification finalization: Complete and published specification for the Solidus identity protocol, including DID method, credential schemas, consensus rules, and validator requirements. Peer review by external cryptographers and identity specialists.

• Testnet deployment: Operational test network with 4-10 validator nodes running the Solidus consensus mechanism. Sufficient to validate block production, credential issuance, and cross-validator coordination.

• Basic DID/VC verifier service: Standalone service that third parties can query to verify the validity of Solidus-issued credentials without running a full node.

• Marketing website (solidus.network): Public-facing site communicating the vision, technical approach, product suite, and calls to action for developers, validators, and early users.

• Security audit of core components: Third-party audit of the consensus mechanism, credential issuance logic, and cryptographic primitives.

• 1,000 beta users for Verify: Closed beta with real users completing the identity verification flow end to end (private beta Months 4-6, public beta Month 6).

Key Decisions Required

• Token supply model: Fixed supply, inflationary, or hybrid. Must be decided before mainnet architecture is locked.
• Blockchain base: Decided 2026-03-22 — original novel chain built from first principles in Rust, not a fork. HotStuff-inspired BFT consensus with Proof-of-Identity validator eligibility. See protocol/apps/consensus/ for implementation.
• Jurisdiction strategy: Which countries to target first for KYC compliance and regulatory engagement.

Success Criteria

• Protocol specification published and externally reviewed
• Testnet producing blocks reliably with 4+ validators
• 1,000 beta users have completed at least one verification
• Security audit completed with no critical findings
• Marketing site live with email capture active

Phase 2: Launch (Months 7-12)

The launch phase transitions from testnet to mainnet, moves Verify to production, and begins generating revenue from identity verification services.

Deliverables

• Verify live with paying customers: Production-grade identity verification service with pricing, SLAs, and customer support. First revenue milestone.

• Identity platform beta (identity.solidus.network): Self-sovereign identity management interface where users can view, manage, and selectively share their verified credentials.

• 100-1,000 validator nodes operational: Distributed validator set providing meaningful decentralization and fault tolerance across the three tiers (Light Node, Subnet Validator, Core Validator).

• Mainnet launch: Production blockchain network with finalized consensus parameters, token economics active, and genesis block produced.

• First production applications: Third-party developers building on the Solidus protocol, using the SDK to integrate identity verification.

• 1M verifications per month: Aggregate verification volume across all consumers of Verify and the broader identity platform.

• SDKs released: Developer libraries for JavaScript, Python, and Go covering credential issuance, verification, and wallet integration.

• Angel/seed funding secured: External capital raised to fund the transition from launch to growth phase.

Targets

Success Criteria

• Mainnet running without downtime for 30 consecutive days
• At least 3 paying enterprise customers
• SDK documentation published with quickstart guides
• Seed round closed or term sheet signed

Phase 3: Growth (Year 2)

The growth phase scales the network, expands the product surface, and establishes Solidus as a credible alternative to centralized identity providers.

Deliverables

• Wallet launch: User-facing wallet application for managing identity credentials, tokens, and transaction history. Mobile-first with desktop support.

• Explorer launch: Public block explorer for the Solidus network, providing transparency into validator activity, credential issuance volume, and network health.

• 1,000-5,000 validator nodes: Network scale sufficient to resist collusion and provide geographic distribution across multiple continents.

• 100 production applications: Third-party integrations spanning fintech, healthcare, education, and government verticals.

• 1M daily active users: Users actively managing credentials or completing verifications through Solidus-powered interfaces.

• 10M+ verifications per day: Volume demonstrating production-grade throughput and reliability.

• Enterprise customers onboarded: Named accounts using Verify or the identity protocol for their compliance and authentication needs.

• Geographic expansion: Operations and regulatory compliance in 5+ countries across at least 2 continents.

• Government pilot programs: At least one government agency piloting Solidus for citizen identity or public service authentication.

Targets

Success Criteria

• Wallet and explorer publicly available and stable
• At least one government pilot in progress
• Revenue supports core team operating costs
• Network has never experienced a consensus failure in production

Phase 4: Scale (Year 3+)

The scale phase transitions Solidus from a growing startup to established infrastructure. The full product vision begins to materialize.

Deliverables

• Full ecosystem rollout: All 19 planned product surfaces in the Solidus suite are either live or in active development. This includes specialized identity services, developer tools, governance interfaces, and enterprise integration products.

• 5,000-11,000+ validator nodes: Network scale comparable to major public blockchains, grounded in the three-tier architecture (100 Core + 1,000 Subnet + 10,000 Light). Validator distribution spans every inhabited continent.

• 1,000+ production applications: Broad adoption across industries, with Solidus identity becoming a recognized standard for decentralized authentication.

• 10M+ daily active users: User base comparable to mid-tier SaaS platforms, with identity management becoming a habitual behavior.

• Force incumbent price cuts: Market pressure from Solidus’s decentralized model compels centralized KYC and authentication providers to reduce pricing. This is a key indicator of market impact.

• Enterprise adoption (Fortune 500): At least one Fortune 500 company using Solidus for production identity verification or authentication.

• Standards body recognition: Active participation in W3C DID Working Group, IETF identity standards, and relevant ISO committees. Solidus protocol elements proposed or adopted as part of formal standards.

• DAO governance transition begins: Progressive transfer of protocol governance from the founding team to the decentralized autonomous organization. Token holders begin voting on protocol upgrades, treasury allocation, and validator policies.

Success Criteria

• Revenue is self-sustaining without dependence on token sales
• At least one W3C or IETF draft references Solidus
• DAO has successfully executed at least one governance vote
• Incumbent competitors have publicly responded to Solidus

Phase 5: Maturity (Year 5+)

The maturity phase represents the long-term vision where decentralized identity is the default, not the alternative.

Vision State

• “Sign in with Solidus” as a default standard: Comparable to “Sign in with Google” but without the centralized data collection. Supported natively by major browsers and operating systems.

• 100M+ users: Global adoption at a scale where Solidus identity is a common part of daily digital life.

• Centralized providers relegated to legacy: Traditional KYC vendors and centralized authentication services are recognized as legacy approaches, used primarily by organizations that have not yet migrated.

• Protocol ossification: Core protocol changes become rare and require broad consensus. The protocol is stable enough to build critical infrastructure on top of without fear of breaking changes.

• Full decentralization: The founding team no longer has privileged access or control. Governance, development, and operations are fully community-driven.

Product Dependencies

Certain products must exist before others can be built. The following dependency chain governs the order of development:

Protocol Specification
  |
  +-- Testnet
  |     |
  |     +-- Mainnet
  |           |
  |           +-- Explorer
  |           +-- Wallet
  |           +-- Staking Interface
  |           +-- DAO Governance Tools
  |
  +-- DID/VC Verifier Service
  |     |
  |     +-- KYC Product
  |     |     |
  |     |     +-- Identity Platform (identity.solidus.network)
  |     |           |
  |     |           +-- "Sign in with Solidus" SDK
  |     |           +-- Enterprise Identity Suite
  |     |
  |     +-- Developer SDKs
  |           |
  |           +-- Third-Party Integrations
  |           +-- Developer Portal
  |
  +-- Data Pod Infrastructure (Solid Protocol)
        |
        +-- Personal Data Management
        +-- Cross-Application Data Portability

Critical Path

The critical path runs through: Protocol Specification —> Testnet —> DID/VC Verifier —> Verify (Identity Verification) —> Revenue

Everything else can proceed in parallel once the critical path milestones are achieved, but revenue generation through Verify is the single most important near-term objective.

Critical Decision Points

Risks and Mitigations