fix(test-suite): wait for rotated quorum publication before retrying proofs

[PastaPastaPasta]

Issue being fixed or feature implemented

The Test Suite fails on v5.1-dev itself. On 054563c73e (run 37948485030), 2 tests failed with:

DapiClientError: no available addresses to retry, last error: Proof verification error:
context provider error: invalid quorum: Quorum not found in cache for hash: …

After a quorum rotation, Platform can return a proof signed by the new quorum before the local quorum sidecar has published that quorum's key (it refreshes every 60 s). The SDK then bans each node it tries for 60 s and runs out of addresses.

This change was originally a commit inside #5307 (c1c7b095c2, later 835f6af4bf). It doesn't depend on anything in #5307, so it's split out here to merge first; #5307 will drop the commit afterwards.

What was done?

• createPlatformProofVerifier retries a proved read once, after 65 s, but only when it fails with the missing-quorum-key error. That gives the sidecar's 60 s refresh and the SDK's initial 60 s node bans time to expire.
• Signature verification, node banning and transition broadcasting are unchanged. No transition is rebroadcast, and the retried read is fully verified.
• Unit tests use fake timers to cover: delayed publication, address bans expiring, a permanent miss, affected-state proofs, and invalid signatures.

The test-suite diff is byte-identical to the original commit, and the authorship is preserved. Only the CHANGELOG entry was re-placed for v5.1-dev's "Unreleased" section.

This is a workaround. The underlying timing is fixed by #5313 (the SDK fetches a missing quorum key instead of banning every node), #5354 (dashmate reloads the local quorum list every second) and quorum-list-server v0.8.0 (dashpay/quorum-list-server#17). #5313 and #5354 are on v5.0-dev but haven't been forward-merged to v5.1-dev yet. Once they are, this retry can be removed.

How Has This Been Tested?

• Original commit: 4 of the new regression tests failed before the fix; all 9 verifier unit tests pass after it. ESLint passes (with the unbuilt local evo-sdk import excluded).
• On chore(platform)!: update rust-dashcore (incl secp256k1 0.33) #5307 with this change, the full Test Suite, both browser suites and the package functional tests passed (45 successful checks on c1c7b095c2).
• I didn't run it locally on this branch; CI covers it.

Breaking Changes

None. Test-suite only.

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

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Repository: dashpay/platform/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 09f902e1-84ba-4ddb-b763-21eda72b4992

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}

[PastaPastaPasta]

Closing this in favour of the real fix. #5313 makes the SDK (including wasm) fetch a missing quorum key and verify the response again instead of banning every node, and #5354 makes dashmate reload the local quorum list every second. Both reached v5.1-dev through #5404, whose Test Suite passed without this retry. #5307 will drop the original commit.

---

🤖 Posted autonomously by Claude on behalf of pasta.

[thepastaclaw]

🕓 Review not started yet because the new head is waiting for the 30-minute push debounce.

• Request normal review — click when the PR is ready for review.
• Request priority review — click to move this review to the front of the queue.

Commit cd557cd. Normal review starts when eligible; priority review starts as soon as a slot is available.