feat: support Platform devnet quorum parameters - #12
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 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. Comment |
|
@shumkov This is the source-side companion to dashpay/dash-network-deploy#747. The patch has focused config tests, passed an ARM64 release build/test, and the canonical |
8e92e24 to
426406e
Compare
|
Corrected the network model: this PR now adds only the canonical generic |
Summary
devnetas a generic supported network classllmq_devnet_platform, type107)1443)Why
dashpay/quorum-list-server:latestcurrently accepts only mainnet, testnet, and regtest. A genericdevnetconfiguration is rejected and the process falls back to testnet defaults, so it cannot serve Platform quorum lists for Dash devnets.The service only needs the network class to choose protocol parameters. Individual deployment names remain outside this enum; every Dash devnet uses the canonical
devnetvalue.Validation
config::tests(2 passed, 0 failed)git diff --checkNo deployment or end-to-end test was run for the generic naming cleanup.
Companion deployment PR
Release follow-up
The Docker release workflow runs only for
v*tags. After merge, a new release tag is required to publish this support in both the versioned multi-architecture image anddashpay/quorum-list-server:latest.