Development Update · September 25, 2026

Changes in this update were merged to master through August 16, 2026. Wider public access remains a future step.

Sakviti's launch rules now have a single protocol identity: consensus version 7.0. Since the August 5 update, the code merged to master has also changed how nodes schedule work, how a browser wallet starts and recovers, and how storage and asset operations manage records. These are implementation steps toward a public testnet, with important verification work still open.

One Set of Launch Rules

Version 7.0 brings several consensus decisions under one activation point. Nodes use the V2 union-block comparison when choosing between competing histories. Replay now checks the exact set of generated slips, so a union block cannot quietly add or omit an economic output. Empty epochs can advance through the ordinary signed, bonded, proof-of-work union-block path when no eligible candidate wins. The older deterministic fallback is confined to historical handling and pre-activation catch-up.

The fee and collateral checks moved with that version. Producer bonds are checked against a replay-parent floor, while even zero-value slips must cover their processing cost. The work also removed old stake constants whose raw units did not match the launch denomination. Economic simulations examined fee-only rewards and ways a producer might regain its own routed fees. That analysis matters because an incentive rule must hold up under hostile use, not only under a friendly traffic model.

This is a code-level activation, not a claim that consensus has passed every network drill. A multi-producer convergence scenario was disabled after a per-peer union-session slot collision exposed a livelock; that case remains an open verification gap.

A Node That Can Say Which Work Goes First

The native node, browser runtime, and test node now use the same bounded priority, normal, and control lanes. The browser feeds network input through a single cooperative mutator and scheduler. The native runtime wakes on ready work instead of polling while idle, and compute admission can return a typed overload result when its bounded capacity is full. These changes make the ordering and limits explicit where messages, timers, and service work compete for a turn.

The accompanying tests check phase order and native/browser behavior. They give a useful baseline for diagnosing stalls, but they do not establish throughput or recovery under a large public network. A live Agni route throughput benchmark client was also added so routed messaging can be measured against a real node path.

Recoverable Wallets and Bounded Asset Records

Nexus gained a first-run wallet flow with creation, recovery, backup status, and import of encrypted backup or raw key files. Browser node identity keys are encrypted at rest, and cryptographic randomness paths now fail closed when the operating system cannot provide secure randomness. Recovery is a safety feature only if it refuses a mismatched identity, so the import path checks the canonical wallet identity before replacing an existing wallet.

Asset work moved full metadata out of hot indexes. Compact summaries and bounded pages now serve listings, while the node resolves full records from canonical storage when needed. Renewal and cancellation of time-limited assets also gained executable, replay-safe slips and retained audit evidence. The asset readiness plan still calls for production query and browser paths, so these changes should not be read as unrestricted asset launch approval.

Storage Work With a Clear Operator Boundary

Filament release retrieval gained a background worker that can fetch a configured release object through paid grant pages, resume staging after a restart, and verify the complete bytes against both a content address and a manifest-declared SHA-256. It requires an operator-configured pointer, payment slip, and bounded budget; it does not authorize autonomous spending or install the binary. The payment design still has a documented single-slip, multi-page settlement risk. Filament also needs more browser, host-churn, repair, and operations evidence before public storage activation.

The next meaningful milestone is proof across those live paths. Version 7.0, wallet recovery, and storage retrieval are now concrete code, but open convergence and production-readiness checks still decide when wider access is safe.