feat(state): skip the transparent address index in pruned checkpoint-sync mode

.config/nextest.toml

@@ -5,6 +5,19 @@
 fail-fast = true
 status-level = "pass"
 
+# --- Test groups ---
+
+# Zakura networking tests dial real iroh/QUIC endpoints and register peers within
+# a bounded deadline. Running many of them at once oversubscribes the CPU and
+# starves those handshakes/upgrades, which surfaced as flaky timeouts and upgrade
+# races in the PR lane (which has no retries). Cap their concurrency so they do
+# not starve each other. This complements the generous `TEST_NET_TIMEOUT` deadline
+# in the zebra-network testkit: the deadline absorbs slow connects, the group keeps
+# the contention that causes them from piling up. It does not exclude any tests, so
+# coverage is unchanged.
+[test-groups]
+zakura-network = { max-threads = 4 }
+
 # --- Platform-specific overrides ---
 
 # Skip Windows-incompatible tests
@@ -13,6 +26,14 @@ platform = 'cfg(target_os = "windows")'
 
 filter = "not test(=trusted_chain_sync_handles_forks_correctly) and not test(=delete_old_databases)"
 
+# Bound the Zakura networking tests (real iroh/QUIC connects) to the serial test
+# group defined above. This override lives on the `default` profile so it applies
+# to every profile (all-tests, full-tests, ...). It only assigns a test group; it
+# does not filter any tests out, so coverage is unchanged.
+[[profile.default.overrides]]
+filter = "package(zebra-network) and (test(~zakura::legacy_gossip::tests) or test(~zakura::testkit::cluster::tests) or test(~zakura::testkit::gossip::tests) or test(~zakura::testkit::mock_blocksync) or test(~mutual_p2p))"
+test-group = "zakura-network"
+
 # --- All Tests profile ---
 # CI-friendly test selection.
 #

.vscode/settings.json

@@ -0,0 +1,17 @@
+{
+  // Rust build artifacts (~140G in target/, ~5G in unity-node/target/) saturate
+  // the file watcher and index, which hangs the extension host (agents + terminal).
+  // These dirs are gitignored, so hiding them from the editor is safe.
+  "files.watcherExclude": {
+    "**/target/**": true,
+    "**/.git/objects/**": true
+  },
+  "search.exclude": {
+    "**/target": true
+  },
+  "files.exclude": {
+    "**/target": true
+  },
+  // Let rust-analyzer manage the workspace without a redundant cargo check storm.
+  "rust-analyzer.files.excludeDirs": ["target"]
+}

AGENTS.md

@@ -199,6 +199,7 @@ cargo nextest run --profile sync-large-checkpoints-empty
 
 - Update `CHANGELOG.md` under `[Unreleased]` for user-visible changes
 - Update crate `CHANGELOG.md` for library-consumer-visible changes
+- When changing a tunable parameter (a constant, `Config` default, timeout, window/limit, or backoff/growth coefficient), add a row to `CHANGELOG_PARAMS.md` in the same PR — record the parameter, location, old → new, PR link, and a one-line why
 - Apply the appropriate PR label (`C-feature`, `C-bug`, `C-security`, etc.)
 - See `CHANGELOG_GUIDELINES.md` for detailed formatting rules
 

CHANGELOG.md

@@ -66,6 +66,14 @@ and this project adheres to [Semantic Versioning](https://semver.org).
   data. This moves ZIP-244 authorizing-data commitment work off the finalized
   committer's critical path when available, while preserving the existing
   recompute fallback.
+- Skip the transparent address index (balances, address→utxo, address→tx) on a
+  pruned, checkpoint-syncing node. The index is RPC-only state, not consensus, so
+  the minimal fast-validator configuration no longer does the per-block
+  address-balance reads or the index writes (like pruned mode already skips
+  raw-transaction storage). Address-lookup RPCs (`getaddressbalance`,
+  `getaddressutxos`, `getaddresstxids`) return an explicit "index disabled"
+  error in this mode instead of wrong (empty) results. Archive nodes, and pruned
+  nodes with checkpoint sync disabled (full semantic verification), are unchanged.
 - Compute the v5 ZIP-244 txid and authorizing-data digest natively. Both
   previously routed through `Transaction::to_librustzcash`, which re-serializes
   and reparses the whole transaction — decompressing every Jubjub and Pallas
@@ -112,13 +120,31 @@ and this project adheres to [Semantic Versioning](https://semver.org).
 - Limit RocksDB write-ahead logs to 4 GiB in the finalized state database. Heavy
   sync could otherwise accumulate tens of GiB of WAL files, making restarts spend
   minutes replaying logs before Zebra could resume syncing.
+- Precompute note-commitment tree hashing ahead of the finalized committer. The
+  per-leaf Merkle hashing for a block (the dominant committer cost on shielded
+  blocks) depends only on the starting note count, not the frontier's hashes, so
+  the finalized write loop now does a one-block look-ahead and runs the next
+  block's Sapling/Orchard hashing on idle cores while the current block commits;
+  the committer then only applies the precomputed subtree roots onto the frontier
+  (`update_trees_parallel_with` in `zebra-chain`). The precompute is applied only
+  if its starting tree size still matches at commit time and otherwise falls back
+  to inline hashing, so it affects only speed, never the resulting tree. This cuts
+  the committer's tree-update cost by ~54% (12.5 → 5.7 ms/block) where the
+  committer is the bottleneck.
 
 ### Changed
 
 - Increased Zakura's default connection, handshake, stream-open, and QUIC
   window limits, and configured default native Zakura bootstrap peers. The
   larger defaults are intended for the production native-P2P sync path rather
   than the earlier conservative test-network envelope.
+- Transparent address-index RPCs (`getaddressbalance`, `getaddressutxos`, and
+  `getaddresstxids`) now require archive storage mode. Pruned nodes return an
+  error for these calls because pruned storage does not guarantee complete
+  address-index data. A pruned database is now durably marked from its first
+  commit (state database format minor version bump), so this holds even during the
+  initial-sync window before raw-transaction pruning starts, and the database can
+  no longer be reopened as an archive in that window.
 - Extended finalized-state value-pool disk serialization with an Ironwood slot
   after the deferred pool, keeping older value-pool records readable.
 - Use V3 chain-history entries from NU6.3 onward, including Ironwood note
@@ -252,6 +278,14 @@ and this project adheres to [Semantic Versioning](https://semver.org).
 - Treat missing transaction inventory responses during mempool download as a
   recoverable download failure, avoiding a panic when public peers no longer
   have a gossiped transaction available.
+- Stop the database format-validity check from panicking with "just checked for
+  genesis block" while a verified-commitment-trees fast sync is in progress. The
+  check runs on a background thread, concurrently with block commits, and could
+  read its `is_vct_synced()` guard as `false` and then read an absent genesis
+  note-commitment tree once a concurrent fast-sync commit set the marker in
+  between. It now treats an absent genesis tree as a (mid-flight) fast-synced
+  database — where the genesis-root-caching invariant does not apply — instead of
+  panicking.
 - Roll back the Zakura header store together with finalized block data, so
   databases produced by `zebra-rollback-state` can resume Zakura body sync from
   the new body tip instead of stalling behind stale headers and falling back to