Development Update · August 5, 2026
An August 5 update on the repositioned landing page with plain-language copy, node-core simplification, and consensus/economics hardening toward the freeze.
Snapshot from August 5, 2026.
The past few weeks moved Sakviti forward on two fronts at once: hardening the core network for the upcoming consensus-and-economics freeze, and sharpening how the project presents itself publicly. This update covers both, plus a cleanup of the documentation trail that ties them together.
Landing Page Now Says What Sakviti Is
The public homepage has been reworked to lead with the actual product thesis instead of a feature list. The site now opens by describing Sakviti as a general-purpose peer-to-peer application network: a network where your apps and data belong to you, not a company. It walks through the story in order: the platform idea, the first application (Coo Lite), the multi-app proof shown in Nexus, and then the technical evidence underneath.
Two things about that rework are worth calling out. First, Coo Lite now has its own section explaining what it is in plain terms: a simple public-message app where anyone can read, but posting is limited to a small invited group during the test phase so it stays safe and spam-free. Second, all the visible copy was rewritten for a general audience. The previous version assumed a reader already knew terms like "cohort-gated", "DAG settlement", or "Hydra execution paths". Those details haven't been removed; they've moved to the technical deep-dive, where a curious reader can still find the exact mechanism. The testnet disclaimer is now visible up front too: experimental network, and test tokens have no monetary value.
Node-Core Simplification
A sustained effort to reduce the size and duplication of the node-core codebase is well underway. The work has proceeded in mechanical phases: removing dead code and facade shims, extracting duplicated logic into shared helpers, and unifying the test harnesses that had drifted into near-identical copies. The payoff isn't cosmetic. A smaller, less redundant core is faster to review, easier to reason about under consensus changes, and cheaper to keep correct as the freeze approaches. Phase 4 work (parameterizing repeated test families and seam analysis) is the current focus, with documented analysis of what remains.
Consensus And Economics Hardening
Work on the consensus layer continues toward the freeze. Recent slices landed a bounded producer-bond penalty mechanism (V7), froze the SPR denomination at 100M, and closed out the union-block V7 foundation. Alongside this, the launch documentation was reconciled and consolidated. Duplicate review records were merged and the canonical reading path for the freeze was established, so the engineering and the documentation now describe the same plan.
What This Means
The direction is consistent: the core network is being made smaller, stricter, and easier to verify, while the public face of the project now matches the product it actually is. Nothing here claims the freeze is done or that public access is ready. Those have their own evidence gates, and we'll keep reporting against them as they land.