Research previewMainnet not launchedView launch criteria

BUILD IN THE OPEN

Every connection,
a step forward.

From a reproducible experiment toward an independently verifiable network.

PROJECT ROADMAP
STATUS — 2026.09

Progress is measured by completion criteria. Running features, planned engineering and open research are kept distinct.

01
✓ Completed

FOUNDATION

Bring real data into computation.

Pin the official source and establish a reproducible input.

  • Official MaleCNS v1.0 download and verification
  • Canonical encoding and Merkle root for 311,833,243 rows
  • Compressed fingerprints for every body ID
  • Deterministic FlyHash and serial synapse accesses
Read the data note ↗
02
● Current stage

WEB WORKBENCH

Turn the experiment into a working tool.

Connect computation, verification and record inspection in one local workflow.

  • Native web mining and field-by-field verification
  • Persistent candidates and complete proofs
  • Signed wallets, bonded validators and 80% / 20% settlement
  • Supply-triggered halvings, launch grants and weekly rankings
  • English / Chinese and interactive 3D brain views
  • Cross-implementation and input-boundary tests
Open workstation ↗
03
Planned

NETWORK & BENCHMARKS

Test the network and its utility.

Test the rules on independent nodes and real hardware, and measure retrieval quality.

  • P2P communication, block sync and persistent state
  • Full targets, difficulty adjustment and cumulative work
  • CPU / GPU / SSD time-memory comparisons
  • Recall@K and mAP retrieval benchmarks
04
Research

PROVABLE COMPUTATION

Make verification lighter.

Explore proofs of full-index computation to reduce repeated verifier work.

  • Merkle multiproofs for accessed records
  • Chunked computation proofs and recursive aggregation
  • Index publication, data availability and independent audits
  • Choose the next network design based on evidence
Explore verification paths ↗

BEFORE A PUBLIC NETWORK

Launch gates, not promises.

  • 01 / REQUIREDReproducible miner and validator clients with independently checked builds
  • 02 / REQUIREDPublic testnet, peer synchronization, fork handling and difficulty adjustment
  • 03 / REQUIREDMeasured resource costs, security review and an explicit threat model
  • 04 / REQUIREDPublished launch rules, transparent community allocations and Sybil review

These are open engineering requirements, not completed milestones. No mainnet date is announced, and the proposed one-week first halving starts only after a network launches and accepts the required blocks.

NEXT CHECKPOINT

Evidence for every step.

Follow the field notes ↗