Skip to content

feat(dapi): wasm-dpp integration - #801

Closed
markin-io wants to merge 26 commits into
v0.24-devfrom
feat/dapi/wasm-dpp-integration
Closed

feat(dapi): wasm-dpp integration#801
markin-io wants to merge 26 commits into
v0.24-devfrom
feat/dapi/wasm-dpp-integration

Conversation

@markin-io

Copy link
Copy Markdown
Contributor

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

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

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@markin-iomarkin-io changed the title wip(dapi): test dapi build with wasm-dppfeat(dapi): wasm-dpp integrationFeb 22, 2023
Comment threadpackages/dapi/Dockerfile Outdated
alpine-sdk \
zeromq-dev
zeromq-dev \
bash

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need bash?

@markin-io
markin-ioforce-pushed the feat/dapi/wasm-dpp-integration branch 2 times, most recently from 8638bba to cea713cCompareMarch 15, 2023 18:56
@markin-io
markin-ioforce-pushed the feat/dapi/wasm-dpp-integration branch from 0f4ebee to 14334a9CompareMarch 22, 2023 11:39
@shumkovshumkov closed this Apr 7, 2023
@shumkov
shumkov deleted the feat/dapi/wasm-dpp-integration branch April 7, 2023 15:39
shumkov added a commit that referenced this pull request Aug 19, 2026
The counted-skip feature merged to grovedb develop as 879cdbc2
(dashpay/grovedb#792) and its branch was deleted, so the previous pin
(63df14c2) survived only on dangling-commit retention — and was two
revisions behind the branch's final reviewed state besides. All 14
workspace entries now pin the merge commit itself.
Crossing grovedb #795-#813 costs three mechanical adaptations, none of
which touch the ranked read paths' behavior:
- The verify_indexed_* family gained a &GroveVersion parameter
(grovedb #801). verify_ranked_top_k_proof_v0 and
verify_having_range_proof_v0 now take platform_version — their doc
claim that nothing in the body needs a version is no longer true —
and pass platform_version.drive.grove_version through.
- grovedb's Query gained an optional read_mode field; the three literal
initializers in the shielded-notes verifiers set it to None. Query's
Display prints the field only when Some, so the pinned to_string
assertion is unaffected.
The unproved counted read (indexed_*_top_k_paginated ->
IndexedTopKPage { entries, skipped }) is byte-identical between the old
pin and the merge commit; the executors compile unchanged. Ranked (71),
shielded (149 drive + 153 drive-abci), and having (38) suites pass.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@markin-io@shumkov