Adopt the reviewed GroveDB foundation

Parent: #4626 · Complete tracking register

Proposed target: 4.4-dev. This is a workstream tracking issue, not a claim that the release branch exists or the implementation is done. Owner: QuantumExplorer. Dates and effort remain unset.

Scope

Integrate a reviewed, pinned GroveDB develop revision and versioned codecs, with dependency compatibility, untrusted decode and historical tree/proof behavior verified. Recheck develop when implementing; do not track a moving dependency in production.

Specification

DVM-04 · DVM-10

The current parent acceptance and module/capability appendices remain authoritative; these DIP drafts add proposed engineering detail without silently approving open allocations.

Completion criteria

Preserve existing root layouts, old protocol dispatch and proof/refund behavior. New contract namespaces and new guest adapters are not enabled. The proposed writable execution-branch API under FIX-01 is 5.0 work, not assumed to ship with this upgrade.

Early work-package prerequisites: 43-FEES. These are separate from the 234 task-level links.

Task acceptance

CAP-01

• Integrate the reviewed GroveDB develop revision and versioned codecs

Dependency compatibility, bincode/untrusted decode, PlatformVersion/GroveVersion maps and old behavior remain reproducible.

Prerequisites: None recorded.

Dependents: CAP-03, CAP-05, CAP-06, CAP-07, CAP-08, CAP-17.

Modules: VERSION, BATCH, PROOFS, PROOF_CLIENT. Original task context. Capabilities: A12.

Coordination and dependencies

Task-level prerequisites above govern order. Workstreams contain multiple stages, so a cross-link is not a claim that the entire other issue must close first. These are Markdown relationships, not native GitHub blocked-by edges. The parent dependency register preserves all 234 links, reasons and explicit/inferred labels.

• CAP-01 → CAP-03 (inferred): Implementation dependency between the specified adapters and their integration checks.
• CAP-01 → CAP-05 (inferred): Implementation dependency between the specified adapters and their integration checks.
• CAP-01 → CAP-06 (inferred): Implementation dependency between the specified adapters and their integration checks.
• CAP-01 → CAP-07 (inferred): Implementation dependency between the specified adapters and their integration checks.
• CAP-01 → CAP-08 (inferred): Implementation dependency between the specified adapters and their integration checks.
• CAP-01 → CAP-17 (inferred): Implementation dependency between the specified adapters and their integration checks.

PR and evidence tracking

Create focused PRs against the chosen development branch. Link this issue with Refs #<issue-number> for partial work. Do not use Fixes for the whole workstream until every listed full task and acceptance criterion is complete.

For a PR that completes an entire task, add a standalone line in its actual PR body: Dash-Tasks: <completed task IDs>. Replace the placeholder with only fully completed IDs. Preparation PRs use ordinary references and omit the completion marker for their broader parent tasks. The site reads this marker on PRs in dashpay/platform and dashpay/grovedb: draft = red, ready for review = yellow, merged with no linked open PR = green. Closed-unmerged is not completion. This does not automatically close issue checkboxes and does not prove acceptance tests passed; reviewers must record the evidence.