build(platform)!: adopt GroveDB 6.0.0 and the published grovedb-bincode 2.1.0

[QuantumExplorer]

Issue being fixed or feature implemented

Platform pinned GroveDB at 6fc7e1e8 together with the QuantumExplorer rust-rocksdb fork, and rust-dashcore at a revision from before GroveDB's bincode moved to the published grovedb-bincode crate. This PR advances those dependencies and adapts Drive, the FFI and the wasm SDK to the GroveDB API changes, without changing how Platform decodes anything. The untrusted-decoding adoption in #4625 builds on top of it.

Companion changes are merged: GroveDB #948 (develop 985ece6574f5fc8fe80db7b304a9a701c0f4afa6) and rust-dashcore #1005 (dev 057e79cd3e1eeb29676288e9aab76b867d8e707f).

What was done?

• Advance GroveDB to develop 985ece65 (6.0.0, about fifty commits since 6fc7e1e8, including the V1 proof hardening series) and rust-dashcore to dev 057e79cd. Use rocksdb 0.25.0 from crates.io instead of the rust-rocksdb fork. Make the workspace bincode dependency an alias for the published grovedb-bincode 2.1.0 so GroveDB, rust-dashcore and Platform share one set of bincode traits; no Cargo patch is needed.
• Build RocksDB 11.8.1 for the prebuilt static library in the Docker image and in the librocksdb GitHub action, matching librocksdb-sys 0.19.0+11.8.1. RocksDB 11's C API dropped the in_range slice-transform callback, so bindgen against the 10.x headers no longer compiles the rocksdb crate.
• Adapt to GroveDB API changes: batch options in Drive's grove operations, element verification aligned with the prover's right-to-left traversal (GroveDB now checks it strictly), and the new backward-reference element variants rendered by the FFI and wasm SDK path-element queries.
• Verify a paged document query's cursor document in the page's walk direction. The prover merges the one-key cursor lookup into the page proof in the page's orderBy direction, and GroveDB fix(scripts): update configure_test_network for hpmn #863 now rejects a layer proof read in the other op family, which failed every proved descending page with a cursor. When a $id-ordered page merges its cursor lookup onto the primary-key layer itself (also for history-keeping types, whose cursor sits one level below), the prover now keeps the requested direction and reserves the extra limit slot only when the page's items do not already cover the cursor, since GroveDB 6 also rejects a layer returning more rows than the verifier's limit; round-trip tests page by $id in both directions with inclusive and exclusive cursors. The drive-abci contestant-votes test helper now verifies with the requested order and cursor, as the SDK's proof verifier does, and the proved test pages with cursors and limits in both directions.

How Has This Been Tested?

Local macOS: cargo fmt --all --check, cargo clippy --workspace --all-targets --all-features --locked -- --no-deps -D warnings, and the CI Rust job's nextest package set (--all-features, same test filter): 14,855 tests passed, none failed. The Docker deps-rocksdb stage was built with RocksDB 11.8.1. No device or browser execution and no live network upgrade were exercised.

Breaking Changes

Rust consumers that serialize Platform or Core types must use the published grovedb-bincode 2.1.0 crate, since bincode trait identities now come from it. Existing bincode encodings and the C ABI are unchanged.

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 added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

Summary by CodeRabbit

• New Features
  • Added support for bidirectional and backward-reference element types in SDK and WASM query output.
  • Added cursor pagination support for proved queries across ascending and descending order, including inclusive and exclusive cursors.
• Bug Fixes
  • Improved query path merging and proof verification for cursor-based pagination.
  • Corrected rendering of reference-based elements while preserving their payloads and reference targets.
• Tests
  • Added coverage for proved pagination and document history queries in both sort directions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: d3285773-bd33-4c70-a20f-a11a6b52658c

📥 Commits

Reviewing files that changed from the base of the PR and between caf2b29 and 7b596ff.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (38)

• .github/actions/librocksdb/action.yaml
• Cargo.toml
• Dockerfile
• packages/rs-dpp/Cargo.toml
• packages/rs-drive-abci/Cargo.toml
• packages/rs-drive-abci/src/execution/validation/state_transition/state_transitions/batch/tests/document/deletion.rs
• packages/rs-drive-abci/src/execution/validation/state_transition/state_transitions/masternode_vote/mod.rs
• packages/rs-drive-proof-verifier/Cargo.toml
• packages/rs-drive/Cargo.toml
• packages/rs-drive/src/query/mod.rs
• packages/rs-drive/src/util/grove_operations/batch_delete/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/batch_delete_items_in_path_query/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/batch_move/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/batch_move_items_in_path_query/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/batch_remove_raw/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/grove_apply_batch_with_add_costs/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/grove_apply_partial_batch_with_add_costs/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/grove_batch_operations_costs/v0/mod.rs
• packages/rs-drive/src/util/grove_operations/grove_delete/v0/mod.rs
• packages/rs-drive/src/verify/document/verify_start_at_document_in_proof/v0/mod.rs
• packages/rs-drive/src/verify/system/verify_elements/v0/mod.rs
• packages/rs-drive/tests/query_tests.rs
• packages/rs-drive/tests/query_tests_history.rs
• packages/rs-platform-serialization/Cargo.toml
• packages/rs-platform-value/Cargo.toml
• packages/rs-platform-version/Cargo.toml
• packages/rs-platform-wallet-ffi/Cargo.toml
• packages/rs-platform-wallet-storage/Cargo.toml
• packages/rs-platform-wallet/Cargo.toml
• packages/rs-sdk-ffi/Cargo.toml
• packages/rs-sdk-ffi/src/system/queries/path_elements.rs
• packages/rs-sdk/Cargo.toml
• packages/simple-signer/Cargo.toml
• packages/strategy-tests/Cargo.toml
• packages/wasm-dpp/Cargo.toml
• packages/wasm-dpp2/Cargo.toml
• packages/wasm-drive-verify/Cargo.toml
• packages/wasm-sdk/src/queries/system.rs

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request updates workspace dependencies and RocksDB, fixes cursor pagination and proof-direction handling, disables backward-reference propagation in GroveDB operations, and adds rendering support for new backward-reference element variants.

Changes

Platform alignment and query behavior

Layer / File(s)	Summary
Workspace and build dependency updates .github/actions/librocksdb/action.yaml, Cargo.toml, Dockerfile, packages/*/Cargo.toml	Workspace crates now share grovedb-bincode 2.1.0, use updated DashCore and GroveDB revisions, and build RocksDB 11.8.1.
Cursor pagination and proof direction packages/rs-drive/src/query/mod.rs, packages/rs-drive/src/verify/..., packages/rs-drive/tests/query_tests*.rs	Cursor-page merging now accounts for cursor coverage and traversal direction. Proved pagination tests cover both sort directions and inclusive or exclusive cursors.
Proved vote pagination packages/rs-drive-abci/src/execution/validation/state_transition/state_transitions/masternode_vote/mod.rs	Proved vote queries now use the request limit, cursor, and ordering. Tests cover paged ascending and descending results.
Backward-reference operation settings packages/rs-drive/src/util/grove_operations/...	Delete, move, apply, cost, and grove operations explicitly disable backward-reference propagation.
Backward-reference element rendering packages/rs-sdk-ffi/src/system/queries/path_elements.rs, packages/wasm-sdk/src/queries/system.rs	Rust FFI and WASM rendering now handles bidirectional and backward-reference variants, including payloads, sums, targets, and type names. Tests cover the new variants.

Priority: ➖ Normal

Estimated code review effort: 4 (Complex) | ~45 minutes

Merge Risk: ⚪ Minimal · up to 7b596

The dependency alignment, proof pagination, and element-rendering updates have no established merge-blocking issue in the reviewed changes.

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant QueryBuilder
  participant GroveDB
  participant ProofVerifier
  Client->>QueryBuilder: Send cursor, limit, and ordering
  QueryBuilder->>GroveDB: Build merged page query
  GroveDB->>ProofVerifier: Provide page proof and root hash
  ProofVerifier->>Client: Return verified page results

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary dependency updates: adopting GroveDB 6.0.0 and grovedb-bincode 2.1.0. It is concise and directly related to the changeset.
Docstring Coverage	✅ Passed	Docstring coverage is 81.82% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 33 functions across 18 files. (20 skipped: …
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch build/grovedb-6-0-0-bincode-2-1-0

---

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 in progress — actively reviewing now (commit 7b596ff) · triage: critical · Phase 2 only (queue backlog)

[codecov]

Codecov Report

❌ Patch coverage is 62.14286% with 53 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.38%. Comparing base (caf2b29) to head (7b596ff).
⚠️ Report is 3 commits behind head on v4.2-dev.

Files with missing lines	Patch %	Lines
...ransition/state_transitions/masternode_vote/mod.rs	62.90%	23 Missing ⚠️
packages/rs-drive/src/query/mod.rs	81.13%	10 Missing ⚠️
...cument/verify_start_at_document_in_proof/v0/mod.rs	30.76%	9 Missing ⚠️
...-drive/src/verify/system/verify_elements/v0/mod.rs	33.33%	2 Missing ⚠️
...e/src/util/grove_operations/batch_delete/v0/mod.rs	0.00%	1 Missing ⚠️
...rations/batch_delete_items_in_path_query/v0/mod.rs	0.00%	1 Missing ⚠️
...ive/src/util/grove_operations/batch_move/v0/mod.rs	0.00%	1 Missing ⚠️
...perations/batch_move_items_in_path_query/v0/mod.rs	0.00%	1 Missing ⚠️
...c/util/grove_operations/batch_remove_raw/v0/mod.rs	0.00%	1 Missing ⚠️
...rations/grove_apply_batch_with_add_costs/v0/mod.rs	0.00%	1 Missing ⚠️
... and 3 more

Additional details and impacted files

@@             Coverage Diff              @@
##           v4.2-dev    #4635      +/-   ##
============================================
- Coverage     85.34%   84.38%   -0.97%     
============================================
  Files          2795     2796       +1     
  Lines        373566   375555    +1989     
============================================
- Hits         318827   316909    -1918     
- Misses        54739    58646    +3907     

Components	Coverage Δ
dpp	84.13% <ø> (-0.25%)	⬇️
drive	84.55% <61.53%> (-0.39%)	⬇️
drive-abci	86.07% <62.90%> (-2.88%)	⬇️
sdk	∅ <ø> (∅)
dapi-client	∅ <ø> (∅)
platform-version	∅ <ø> (∅)
platform-value	92.92% <ø> (ø)
platform-wallet	∅ <ø> (∅)
drive-proof-verifier	41.44% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[thepastaclaw]

Final validation — Phase 2 only (queue backlog)

Both supplied findings are confirmed against the exact head. The GroveDB upgrade exposes a direction mismatch that prevents verification of descending primary-key pages with a cursor, and the updated contestant-vote proof helper has no calls exercising its newly forwarded cursor or limit. Verification was source-based; reviewer-reported test results were not independently rerun.

Source: reviewer 1: gpt-6-astra (agent: phase2-reviewer, role: general); reviewer 2: gpt-6-astra (agent: phase2-reviewer, role: ffi-engineer); reviewer 3: gpt-6-astra (agent: phase2-reviewer, role: rust-quality); reviewer 4: gpt-6-astra (agent: phase2-reviewer, role: security-auditor); final verifier: gpt-6-astra (agent: astra-verifier, role: final-verifier)

Review provenance

• Triage: critical by gpt-6-astra (effort low) — This upgrades consensus-critical storage and serialization dependencies and changes cryptographic proof verification and cursor traversal, so regressions could affect state consistency, data compatibility, or acceptance of proofs across Platform and its SDKs.
• Phase 1 reviewers: not run (skipped for throughput: 20 PRs queued, above the 10 limit)
• Fresh verifier: gpt-6-astra — final-verifier; agent astra-verifier
• Phase 2 reviewers: gpt-6-astra — general (completed, effort xhigh); agent phase2-reviewer, gpt-6-astra — ffi-engineer (completed, effort xhigh); agent phase2-reviewer, gpt-6-astra — rust-quality (completed, effort xhigh); agent phase2-reviewer, gpt-6-astra — security-auditor (completed, effort xhigh); agent phase2-reviewer

🔴 1 blocking | 🟡 1 suggestion(s)

🤖 Prompt for all review comments with AI agents

These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `packages/rs-drive/src/verify/document/verify_start_at_document_in_proof/v0/mod.rs`:
- [BLOCKING] packages/rs-drive/src/verify/document/verify_start_at_document_in_proof/v0/mod.rs:59-63: Align primary-key cursor verification with the merged proof direction
  For a non-history document query ordered by `$id desc` with a cursor, the cursor lookup and main query address the same primary-key tree. Their merged query therefore operates directly on that tree, but `construct_path_query_operations` unconditionally sets `merged.query.query.left_to_right = true` at `query/mod.rs:2061`. These new lines instead select descending verification. The newly pinned GroveDB explicitly rejects upright proof operations in a right-to-left V1 walk, so this valid page cannot be verified. The ascending-root override is justified for separate cursor and index branches, but not when both queries land on the same primary-key path. Preserve the requested document-layer direction in the prover for this case and add ascending/descending primary-key cursor round-trip tests. Reverting only the cursor verifier to ascending is insufficient: `verify_proof_keep_serialized_v0` subsequently verifies the main subset in the requested descending direction.

In `packages/rs-drive-abci/src/execution/validation/state_transition/state_transitions/masternode_vote/mod.rs`:
- [SUGGESTION] packages/rs-drive-abci/src/execution/validation/state_transition/state_transitions/masternode_vote/mod.rs:3079-3081: Exercise the forwarded cursor and limit in a proved vote request
  All four calls to `get_proved_contestant_votes` in `test_proved_contestant_votes_query_request` pass `None` for both the count and cursor. Consequently, the new cursor conversion never executes, and reverting the verifier's `limit` and `start_at` fields to their previous hardcoded `None` values would leave this test passing. The neighboring non-proved pagination test does not exercise proof verification. Add proved requests with a nonempty cursor and a limit smaller than the available results, covering inclusive/exclusive cursors in ascending and descending order, and compare the returned identifiers with the corresponding slices of the full voter sequence.