feat(dashmate): state sync configuration for tenderdash and drive snapshots

[PastaPastaPasta]

Supersedes #4521, recreated from a dashpay/platform branch so the full CI (Rust, wallet, Kotlin, Swift, e2e) runs; fork PRs skip those jobs. The commits are unchanged (head 01004943ba). Review history is on #4521.

Issue being fixed or feature implemented

Dashmate plumbing for Tenderdash state sync + Drive snapshot serving. Companion to the drive-abci state sync PR #4648 (which superseded #4520; config surface and env names are its contract) and finishes what #2558 started. Targets the Tenderdash 1.8 line that v5.1-dev pins, which supports every [statesync] option used here (enable, use-p2p, rpc-servers, discovery-time, retries, temp-dir, chunk-request-timeout, fetchers; dashpay/tenderdash#1425 is in 1.8). Merge after #4648: snapshot serving defaults on, and its disk bound (serving-pin lifetime and count cap) lives in Drive.

What was done?

• New config schema:
  • platform.drive.tenderdash.stateSync = { enabled (base default true — safe: tenderdash self-disables when local state exists, so only fresh nodes consume; local preset false), retries (3), chunkRequestTimeout ('15s', min 5s), fetchersCount (4) }
  • platform.drive.abci.stateSync.snapshots = { enabled (base true, local false), frequencySeconds (600, min 60), maxCount (6, min 2) }
• Tenderdash config template: [statesync] templated; use-p2p = true hardcoded — tenderdash RPC is loopback-bound, not gateway-proxied, and has no TLS/auth, so the RPC state-provider mode (≥2 rpc-servers) is not viable between evonodes; deleted the stale trust-height/trust-hash/trust-period keys (removed in tenderdash 1.7, absent in 1.8); added retries.
• ABCI routing: ListSnapshots/LoadSnapshotChunk route to drive-abci's gRPC endpoint (26670) so snapshot serving never blocks the consensus socket; grpc-concurrency entries added.
• docker-compose: passes SNAPSHOTS_ENABLED / SNAPSHOTS_FREQUENCY_SECONDS / MAX_NUM_SNAPSHOTS to drive-abci. Checkpoints stay inside the existing drive_abci_data volume (DB_PATH/checkpoints) — no new volume.
• Config migration keyed 5.1.0, the release this ships in (configs stamped by 4.2.x/5.0.x builds all pass through it; configs without a Drive section are left alone); doctor accounts for snapshot disk headroom (+10 GB when enabled, without downgrading existing severities); docs for both new sections.

Dropped from the old reference branch: maxConcurrentListSnapshots/maxConcurrentSnapshotChunk (don't exist in tenderdash 1.7/1.8), the feat-statesync-improvements image pin (1.7+ ships everything needed), GROVEDB_LATEST_FILE, and the separate checkpoints volume.

How Has This Been Tested?

Full dashmate unit suite (at the original 4.2-based head): 829 passing, 0 failing, including new schema-bounds specs, the migration test (deep-equal against new defaults), doctor severity tests, and template render-sanity (base and local configs rendered and parsed with a real TOML parser — valid, no undefined, correct statesync/routing values). docker-compose.yml YAML-parsed; eslint clean.

After the rebase onto v5.1-dev and the re-key (2026-10-05): stateSyncOptions 9, analyseSystemResourcesFactory 3, verifySystemRequirementsFactory 13, tenderdashConfigTemplate 3 and tenderdashImageMigration 3 specs pass. The migration was checked against all four default configs stamped at the current package version. migrateConfigFileFactory.spec.js needs a built wasm-dpp (through the DI container), so it was left to CI. eslint is clean on the touched files.

Breaking Changes

None. New config keys are added by migration; tenderdash consuming is enabled by default but self-disables on nodes with existing state.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation if needed

---

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

🕓 Review not started yet because this PR is a draft.

• Request normal review — click when the PR is ready for review.
• Request priority review — click to move this review to the front of the queue.

Commit d002668. Normal review starts when eligible; priority review starts as soon as a slot is available.