Repository navigation
docs: Platform v5.0.3 SDK pins, v5 explanation gaps, and Rust SDK quick start fixes - #173
Conversation
v5.0.3 fixes wasm gRPC-Web requests going to a double-slash path (which some gateways reject) and compacted address-balance syncing in rs-sdk. Bump @dashevo/evo-sdk for the interactive runners and the Cargo tag pins in the Rust SDK pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- tokens: add the once-per-identity distribution to Claim and the distribution rules table - fees: note that ttl documents are priced by lifetime, prepay their deletion, and get no storage refund - state transitions: an elected moderation team's pot is paid by its charter's reward split, not in equal shares - query syntax: limit 0 means "default" only for SDK query objects and the v0 wire; the v1 wire rejects it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The DAPI client example built an Sdk with no context provider, which SdkBuilder::build() rejects. Send the request through a bare DapiClient instead, which needs no Core node or context provider. - Proof verification no longer requires Dash Core: describe TrustedHttpContextProvider, and drop the claim that the JS SDK does not support proofs (the Evo SDK verifies them by default). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n is created Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Summary
Updates the docs for Platform v5.0.3. The Rust and JS SDK pins move to the new release, several explanation and reference pages get v5 behavior they were missing, and the Rust SDK quick start is fixed: its DAPI client example did not work, and its proof verification claims were out of date.
Highlights
@dashevo/evo-sdk(used by the interactive runners) and the Cargo tag pins on the Rust SDK pages now point to v5.0.3. This release fixes wasm gRPC-Web requests that went to a double-slash path and fixes compacted address-balance syncing in rs-sdk.ttldocuments are priced by lifetime, prepay their deletion, and get no storage refund.limit: 0means "default" only in SDK query objects and on the v0 wire. The v1 wire rejects it.DapiClient. The old example built anSdkwith no context provider, whichSdkBuilder::build()rejects.TrustedHttpContextProviderinstead of saying Dash Core is required.🤖 Generated with Claude Code
Preview build: https://dash-docs-platform--173.org.readthedocs.build/en/173/