Repository navigation
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Basic explanation
We ran a first test pass of 5.1 (protocol version 15) on the palmatum devnet on 2026-11-15. The token marketplace was left out on purpose: it moves to protocol version 16 with #5910. Of 40 protocol version 15 cases, 26 pass, 1 fails, 12 are Blocked (mostly because they need masternode voting or owner keys) and 1 was not run. The devnet never halted.
This issue lists everything the pass found. Most of it is in the clients. Each item should get its own PR; tick it off here when it lands.
Setup
- Devnet
dash-devnet-palmatum: Drive and DAPI 5.1.0-dev.1 (5b73d83b50), Tenderdash 2.0.0-dev.2, protocol version 15 since genesis, GroveDB pinfa92511c. - Clients:
@dashevo/evo-sdk5.1.0-dev.1 (needsversion: 15, see item 6), and SwiftExampleApp and KotlinExampleApp built fromv5.1-devatadfa029b3c. - Quorum service
https://quorums.palmatum.networks.dash.org, faucethttps://faucet.palmatum.networks.dash.org.
Findings
Node
- 1. Wrong error kind for a byte array holding integers that are not bytes (rs-dpp). A document whose
byteArrayproperty (for example an identifier field) holds a list of integers that are notu8passes schema validation, because validation runs on the JSON view, then fails serialization in Drive at check_tx. The client gets an internal error instead of a consensus error naming the field. Such transitions are kept out of blocks, so this is an error classification problem. Fix: refuse it as a consensus error in document validation (rs-dpp/src/data_contract/methods/validate_document/v1) at protocol version 15. This is the one failing case (CD-02). evo-sdk produces such documents from aUint8Array(item 2).
evo-sdk / wasm-sdk (5.1.0-dev.1)
- 2. Byte values are encoded wrongly. A
Uint8ArrayorBufferproperty is sent as a list of 64-bit integers, and anIdentifierobject as text. Neither validates against abyteArrayfield (the text form is refused with 10101is not of type "array"); only base58 strings work. Byte values should be sent as bytes. - 3. Refusals are lost. When the node refuses a transition,
documents.createwaits until its deadline (about 30 s) and reportsstate transition result is unconfirmedwith code -1, so the consensus code and message never reach the caller. - 4. Integers round-trip as strings. Fetched documents return integer properties as
BigInt. Writing them back intodoc.propertiesserializes them as strings, so fetch, edit, replace is refused locally: 10101"1" is not of type "integer", path: /encryptionKeyIndex. Converting toNumberworks around it. Related: WASM JSON serialization rejects valid u64 values above Number.MAX_SAFE_INTEGER #3786. - 5.
settings.waitTimeoutMspanics in Node 22.documents.create({..., settings: {waitTimeoutMs: 60000}})aborts the wasm module:time not implemented on this platform, thenRuntimeError: unreachable.retriesandtimeoutMswork. Related: bug(wasm-sdk): usingwaitTimeoutMsin the browser crashes wasm state-transition waits #3499 (same panic in the browser). - 6. Smaller SDK problems.
- On a devnet the SDK assumes protocol version 14 unless it is given
version: 15. history({ documentId })refuses anIdentifierobject ("Invalid identifier. Expected Identifier, ...") but takes its base58 string.new DataContract({ tokens })throws.contractNoncereturns the raw stored bits.- No API for a single document at a block time, or a maybe-contested single document fetch (fix(drive): verify a single document that may be contested (PV15) #5835, fix(drive): look up a single document at a block time (PV15) #5838), and no helper for multiple choice proposals in dev.1 (feat(sdk): multiple choice decision proposals in rs-sdk, wasm-sdk and js-evo-sdk #5903 adds it).
- On a devnet the SDK assumes protocol version 14 unless it is given
- 7. A retry can send a duplicate DPNS preorder.
dpns.registerNamegot a proof error (quorum key unavailable) after the first attempt had already executed. The retry sent a second preorder, then failed withalready a contestant. Under DPNS chooseFirst ordering, that stray preorder blocked the other contender's registration until it was deleted (or its 1 h TTL ran out). A retry should check whether the first attempt landed before sending again.
rs-sdk / rs-dapi-client
- 8. One burst of client-side proof failures bans every node for about 20 minutes. At app launch the first proof-verified queries named a quorum the client's quorum source did not know yet (before SPV processed QRInfo). Each node was banned for
quorum key unavailable ... Quorum not found in cache: 56 bans in 1 ms, all 13 addresses banned, ban count 4 from one burst, and Platform unusable in the app for 20 minutes. The nodes were healthy. A provider-side miss should not count as a node fault, and one burst should not escalate the ban count. Related: rs-dapi-client: per-error-class ban policy — don't ban on rate-limit or client-side decode errors #3695, rs-dapi-client: burst of ordinary TCP timeouts can ban the whole address pool, surfacing a raw transport error instead of a structured exhaustion error #4141, fix(sdk): context-provider failures still attributed to nodes or reported as transient #5777. - 9. Launch race checks DashPay proofs against the protocol version 14 contract. The SDK starts at protocol version 14 and ratchets to 15 about 2 s later. Requests built before the ratchet ask the trusted context provider (
LocalContextResolver::data_contract) for the version 14 DashPay contract, which can't decode v3contactRequestdocuments (serialized document has trailing bytes ... contract version 3). 4 healthy nodes were banned. Intermittent: seen on 1 launch of 4.
SwiftExampleApp
- 10. A same-device recipient's balance never updates. After a credit transfer from identity A to identity B in another wallet on the same device, B's balance stays at the old value, even after "Refresh Identity Data": the refresh writes the right value, then about 1 s later the persistence handler overwrites it with the stale balance Rust still holds. Fails ID-14.
- 11. An undecryptable contact request is offered and accepted. A request whose sender key is an authentication key and whose
encryptedPublicKeyis junk (valid on chain: consensus checks only the ciphertext shape) shows as a normal incoming request. Accepting it broadcasts a paid reciprocal request, lists the sender as a contact with "Send Dash" enabled, and leaves a "contacts waiting to finish setup" banner that never clears. Fails the app half of DS-01. - 12. Contested vote state query can't show a contest. Settings, Queries, Get Contested DPNS Name Vote State: the display name returns
[ ]because it isn't normalized, and the normalized name fails withFailed to parse JSON array. The FFI (contested_resource/queries/vote_state.rs) returns a JSON object, but Swift parses it withprocessJSONArrayResult. Fails VOTE-03. - 13. A private contact rewinds SPV to height 0. Sending or accepting a private contact request lowers SPV's synced height to genesis to backfill contact payments, because a private request carries no core height. On mainnet that is a full-chain filter rescan per private contact. Public contacts use
$coreHeightCreatedAt. - 14. Identities found by Re-scan can't sign document updates. Replace, delete and transfer fail with "No AUTHENTICATION key with security High or higher (and an available private key)".
DocumentsView.swiftpicks the signing key in Swift throughKeyManager.findSigningKey, which needs a Keychain row that discovery never writes. Create, DashPay and transfers sign through the wallet signer and work. The key choice belongs in the SDK. - 15. Re-scan reports "+0" when every lookup failed. During a ban outage (item 8), Re-scan for Identities said no identities were registered while every lookup had failed with
no available addresses to use. The error should be shown. - 16. Rediscovered identity shows 0 keys. After deleting and re-importing a wallet, a rediscovered identity shows "Identity Keys, 0 public" (it has 6 on chain); its old key rows survive the delete unlinked, as 18 orphan rows.
- 17. Automatic Platform address sync stops after Clear. After Platform Sync, Clear, Sync Now, the recurring address sync never restarts (
reset_platform_address_sync_statedoesn't restart the loop and Sync Now is one-shot), so Platform balances go stale until relaunch. - 18. Received shielded transfer row has no height, date or memo. The recipient's activity row has block height 0, time 0 (shown as 1 Jan 2513 on the Buddhist calendar) and no memo, while the sender's row has all three.
- 19. Progress steps tick when they never ran. Top Up Platform Address shows Building, Broadcasting, InstantSend and ChainLock all green when signing the asset lock failed before anything was broadcast. Create Identity shows the same pattern.
KotlinExampleApp
- 20. Choosing Devnet crashes the app. Settings, Network, Devnet throws
DashSdkError$InvalidParameter: DAPI addresses not available for network: Devnetfrom an uncaught coroutine (SettingsScreen.ktcallsswitchNetworkwith no try/catch, and the quorum URL is empty). - 21. The app has no devnet settings. The Quorum URL field only renders once the network is already Devnet, which needs the URL first. The URL isn't persisted. No devnet name is passed to SPV (
platform_wallet_manager_spv_startrefuses devnet without one), and there is no peer discovery from{quorumUrl}/masternodes. SwiftExampleApp has all of these. This has been missing since the initial port. All Kotlin devnet cases are Blocked by items 20 and 21.
platform-test-suite
- 22. The JS SPV can't sync a devnet with custom block spacing. The legacy
dash-spvused by the suite rejects palmatum's headers, so functional and e2e runs fail on sync (functional: 5 pass, 5 pending, 6 fail; e2e: 12 fail, all on that error). rust-dashcore'sdash-spvsyncs palmatum to the tip. Fix: pass the spacing through, or move the suite to rust-dashcore's SPV.
Devnet operations (palmatum)
- 23. Quorum service lag and InstantSend refusals. The quorum service lags validator-set rotation ("quorum not found in cache"), which triggers item 8. Fresh InstantSend asset locks are refused with 10513 while Platform's chain-locked height lags; a retry a minute later works. Worth a look by whoever runs the devnet.
Not covered
- Marketplace (protocol version 16, fix(platform)!: the token marketplace starts with protocol version 16, not 15 #5910).
- Cases that need masternode voting or owner keys: yes/no and multiple choice resolution, contest votes and award, vote counting (VO-02, VO-04, VO-05, VO-08), masternode key and payout changes (DS-09), and stopping a masternode during a DKG (DS-10).
- Other Blocked cases: the encrypted shielded address on a contact request (no client attaches one) and fresh shielded addresses (no app surface).
- QF-05 (rs-sdk behind a SOCKS5 proxy), Yappr smoke and part of the Swift catalog were not run.
- Not testable on palmatum: the protocol version 14 to 15 upgrade (genesis was already 15), fix(platform)!: refuse high-S signatures on key-recovery paths from protocol version 15 #5899 and the 2026-11-11 GroveDB fixes (not in dev.1). Moving palmatum to a build with fix(platform)!: the token marketplace starts with protocol version 16, not 15 #5910 needs a re-cut, since such a node can't replay this chain.
🤖 Generated with Claude Code
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Activity