Honest bypercentage.

Evidence: Cross-platform releases cover peer, mine, host, node, wallet, benchmark, registry, and Engine commands.

Next: Broaden production soak testing and simplify operator recovery.

Evidence: Local vaults, recovery phrases, signing, balances, and a read-only node wallet API are implemented.

Next: Complete independent security review and production recovery drills.

Evidence: Genesis produces canonical signed blocks and peers can replicate and verify them.

Next: Remove the single-leader trust boundary and harden long-running recovery.

Evidence: Noise-encrypted discovery, block replication, signed-chain verification, and inbound/outbound peer modes exist.

Next: Increase public peer diversity, adversarial testing, and partition recovery coverage.

Evidence: Pilot work, receipts, scoring inputs, settlement polling, and capped devnet rewards operate.

Next: Add stronger Sybil resistance, broader useful workloads, and audited verification.

Evidence: A stateful coordinator assigns deterministic pilot work and persists verified settlement receipts.

Next: Authenticate operators and decentralize verification and issuance authority.

Evidence: Peers independently verify signed history, but Genesis remains the sole canonical finalizer.

Next: Specify, implement, test, and audit an enforced independent validator quorum.

Evidence: Containerd, Lima/WSL paths, encrypted volumes, manifests, capability access, logs, and lifecycle commands exist.

Next: Complete cross-platform reliability testing and third-party sandbox review.

Evidence: A narrow Git-backed Caddy workload profile and encrypted private service path are staged.

Next: Run multi-host pilots and add carefully allowlisted compute workload families.

Evidence: Nodes expose capacity and the coordinator assigns pilot work, but a general buyer marketplace is not live.

Next: Add quotes, reservations, job escrow, retries, SLAs, and buyer-facing APIs.

Evidence: Deterministic pilot verification and signed receipts exist for narrow work.

Next: Add redundant execution, challenges, fraud handling, and workload-specific verifiers.

Evidence: The design blocks broad mounts, keys, sockets, capabilities, and public exposure by default.

Next: Complete adversarial review, escape testing, resource metering, and incident drills.

Evidence: The production site includes product, education, downloads, registry, identity, news, and operational APIs.

Next: Keep claims synchronized with engineering reality and expand accessibility testing.

Evidence: Signed heartbeats, replay controls, coarse locations, compute records, registration, and public APIs exist.

Next: Improve decentralized trust, moderation operations, and long-term availability.

Evidence: Public views expose blocks, peers, capacity estimates, coordinator state, and Genesis health.

Next: Add independent data sources, historical reliability, and alerting transparency.

Evidence: Operator guides, API references, concepts, security boundaries, examples, lessons, and quizzes are published.

Next: Version documentation against releases and close remaining implementation/spec gaps.

Evidence: Tauri desktop clients resolve grid:// names, built-in realms, registry computes, local mappings, and deep links.

Next: Complete signed releases, broader OS testing, gateway hardening, and production navigation.

Evidence: A native SwiftUI wallet integrates the GRID CLI contract and supports Genesis, local, and custom node views.

Next: Complete end-to-end transaction UX, signing review, packaging, and sustained beta testing.

Evidence: The Tauri desktop source and shared wallet contract exist.

Next: Reach feature parity, sign installers, and run platform-specific release testing.

Evidence: Native and React Native source surfaces exist, with wallet architecture documented.

Next: Finish secure signing, recovery, synchronization, platform QA, and store distribution.

Evidence: Registration, verification, TOTP, approvals, sessions, mailbox UI, and AWS mail architecture are implemented.

Next: Complete production infrastructure, deliverability, recovery, abuse controls, and audits.

Evidence: Supply, allocation, epoch limits, Proof of Resource rewards, inclusion, escrow, and staged growth are documented.

Next: Resolve remaining governance choices and validate assumptions with pilot data and counsel.

Evidence: Devnet minting, metadata, guarded issuance, duplicate rejection, epoch caps, wallets, and issuer bridge exist.

Next: Replace operator policy with audited on-chain controls before any mainnet use.

Evidence: Requirements and safety boundaries are documented; an audited production controller is not deployed.

Next: Implement the program, multisig governance, audits, public testing, and reconciliation.

Evidence: Blockchain settlement is the security boundary; supported rails remain subject to audited integration.

Next: Implement audited execution, reserve policies, Lightning decisions, and operational settlement.

Evidence: Allocation totals, GEX reserve, treasury uses, and public diagrams are documented.

Next: Bind disclosures to controlled addresses, vesting, governance, and independently verifiable reporting.

Evidence: The UI, reference feed, fixed-point order contract, schema, and per-market serialized order books exist.

Next: Connect committed balances, complete market controls, and pass every launch gate.

Evidence: State, transition, hold, fill, fee, deposit, withdrawal, and replay invariants are specified with partial implementation.

Next: Finish Genesis state transitions, double-entry reconciliation, recovery, and independent tests.

Evidence: The exchange-scoped Chip, backing, swap, redemption, and non-transfer rules are now conceptually defined.

Next: Freeze the protocol schema and implement issuance, burns, reserves, and user disclosures.

Evidence: Exchange → GRID Exchange → exchange clearing semantics and core invariants are defined conceptually.

Next: Specify participants, quotes, holds, burns, backing reassignment, destination issuance, failures, and dispute handling.

Evidence: The required BTC, ETH, SOL, and USDC custody plane is architected but not production-ready.

Next: Deploy MPC/HSM custody, chain indexers, reserve tiers, withdrawals, reconciliation, and drills.

Evidence: Launch gates comprehensively identify legal, identity, AML, custody, market, audit, and operational obligations.

Next: Assign accountable owners, implement controls, obtain legal approval, and record evidence.

Evidence: The market is designed and displayed, while real order submission and withdrawals remain deliberately disabled.

Next: Complete custody, liquidity, surveillance, disclosures, approval, and controlled launch.

Evidence: Signed CLI downloads and install paths exist for macOS, Linux, and Windows.

Next: Automate reproducible releases, provenance, rollback, and broader installation telemetry.

Evidence: Core Rust and TypeScript projects include targeted protocol, policy, ledger, and interface tests.

Next: Add full-system, chaos, adversarial, custody, and upgrade-path coverage.

Evidence: Genesis, coordinator, explorer, registry, node, service, and exchange status surfaces exist.

Next: Unify SLOs, alerts, incident timelines, historical uptime, and independent probes.

Evidence: Threat boundaries and launch gates are documented, but required external audits and rehearsals remain outstanding.

Next: Commission audits, operate a bug bounty, rehearse recovery, and publish remediation evidence.