feat(sdk): transport-free verification and query core for embedders

[PastaPastaPasta]

Issue being fixed or feature implemented

Embedders that bring their own transport and trust context cannot currently consume Platform's query and proof-verification layer without depending on the networked SDK or reconstructing Drive query shapes themselves.

Dash Core is the concrete consumer: it already owns endpoint selection, transport, locally synchronized LLMQ keys, and wallet key custody. It needs Platform's canonical request construction, response decoding, and proof verification without adopting rs-dapi-client or tonic's native channel/TLS stack.

What was done?

This branch is rebased onto current v4.2-dev, which includes the proof-vector corpus from #4345. It contains corrected #4344 as its prerequisite followed by six focused commits:

1. feat(sdk): add transport feature to dapi-grpc for types-only consumers #4344: opt-in native transport for dapi-grpc

   • generated types and transport-generic client stubs remain in the default feature set;
   • native channel/TLS support is behind transport;
   • native rs-dapi-client and server builds opt in at their target-specific boundaries;
   • default dash-sdk and wasm-sdk wasm32 graphs remain transport-free.

2. Extract dash-platform-queries

   • moves query types, wire encoding, aggregate proof helpers, DPNS helpers, and transition validation into a reusable crate;
   • dash-sdk consumes it and preserves historical re-export paths.

3. Share document request decoding

   • moves v1 proto-to-query decoding into one shared implementation used by both drive-abci and clients;
   • adds DocumentQuery::try_from_request;
   • adds request-driven verify_documents_response entry points for embedders.

4. Extract pure DPNS and DashPay builders

   • adds transport-free preorder/domain and contact-request document assembly;
   • callers supply entropy, salt, and encrypted material, so key custody remains outside this crate.

5. Cover transport-free cuts in CI

   • checks standalone dapi-grpc, drive-proof-verifier, and dash-platform-queries graphs;
   • rejects hyper/rustls/tower leakage in native proof verification;
   • rejects hyper/rustls/tower/mio leakage in default wasm SDK graphs;
   • adds both verification crates to nightly per-feature checks.

6. Document the embedder path

   • documents the precise boundary: no rs-dapi-client or tonic native channel/TLS stack;
   • shared generated types and context-provider utilities remain dependencies.

7. Harden validation seams

   • matches DPNS builder validation to the contract's consensus schema while preserving the stricter existing client policy separately;
   • rejects aggregate projections at the plain-documents verifier entry point;
   • documents client/server validation scope.

Once #4344 lands, this branch can be rebased to drop that prerequisite commit without changing the remaining series.

How Has This Been Tested?

Local validation on the final rebased revision e8e1961fe54fcdcb8eae55b7c2d84bcdf44004a8:

• cargo fmt --check --all
• workspace-wide clippy with all targets/features and warnings denied
• cargo machete
• wallet dependency-closure check
• dash-platform-queries: 36 unit tests + 9 wire-roundtrip integration tests
• drive-proof-verifier --features mocks: 261 unit tests + all 19 test(sdk): add proof-vector regression corpus for drive-proof-verifier #4345 fixture tests
• native dapi-grpc, rs-dapi-client, dash-sdk, verifier, and query-core checks
• transport feature-tree and dependency-leak assertions for native and wasm32 graphs

The exact published revision was then pinned from a clean Dash Core #67 checkout:

• all 31 dash-platform-ffi tests passed (6 decoder, 14 proof, 11 signing/transition)
• dashrust built successfully with the platform feature

Breaking Changes

Existing dash-sdk paths remain re-exported.

Two narrow Rust source changes remain:

• the unused QuerySettings.request_settings field is removed;
• DocumentQuery::new_with_data_contract_id is provided by the DocumentQuerySdk extension trait and requires that trait in scope.

External native consumers depending directly on dapi-grpc and calling generated connect() methods must explicitly enable features = ["transport"]. Native SDK/server consumers retain transport through their normal dependencies, and wasm consumers can use the default feature set safely.

Checklist:

• I have performed a self-review of my own code
• I have commented code where non-obvious invariants require explanation
• I have added or updated relevant tests
• I have updated the documentation
• I have assigned this pull request to a milestone

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: eda9aade-6b05-49b2-9183-b99ae72ba068

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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