docs(rpc): update core rpcs to 23.1.7#582
Conversation
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe RPC documentation is updated for wallet external-signer functionality, structured masternode addresses, governance validity fields, expanded Evolution schemas, and additional transaction and blockchain response fields. ChangesRPC documentation
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/core/api/remote-procedure-calls-dash.md`:
- Around line 583-592: Update the governance-object field tables in both the
`gobject diff` and `gobject list` sections so `fBlockchainValidity`,
`IsValidReason`, `fCachedValid`, `fCachedFunding`, `fCachedDelete`, and
`fCachedEndorsed` use `→ →` nesting, matching `DataHex`, `Hash`, and the
vote-count fields rather than appearing as direct `Result` members.
- Around line 604-620: Synchronize each documented RPC example with its version
caption: in docs/core/api/remote-procedure-calls-dash.md lines 604-620, update
the gobject diff caption or restore the historical payload; in lines 821-855,
update the gobject list caption or restore its historical payload; and in lines
1753-1809, change the masternodelist caption to Dash Core 23.0.0 or later, or
remove the addresses field. Preserve accurate field availability for every
example.
In `@docs/core/api/remote-procedure-calls-wallet.md`:
- Around line 709-711: Update the response table’s lastprocessedblock, hash, and
height rows so each has the appropriate nesting marker placing them inside the
result object, matching the documented JSON example.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 6312a28a-d582-42c6-9da5-dc8f052d9ffe
📒 Files selected for processing (6)
docs/core/api/remote-procedure-call-quick-reference.mddocs/core/api/remote-procedure-calls-blockchain.mddocs/core/api/remote-procedure-calls-dash.mddocs/core/api/remote-procedure-calls-evo.mddocs/core/api/remote-procedure-calls-raw-transactions.mddocs/core/api/remote-procedure-calls-wallet.md
Voting for delete via RPC is no longer supported
1 participant
Updates the Core RPC API reference to Dash Core 23.1.7, capturing new RPCs, result-field additions, and deprecations introduced across the 23.1.x series.
Highlights
enumeratesignersandwalletdisplayaddress(external signer support, new in Dash Core 23.1.0), added to both the wallet reference and the RPC quick reference.addressesobject (core_p2p,platform_p2p,platform_https) acrossmasternode,masternodelist, andprotxresults, with the flatservice,platformP2PPort, andplatformHTTPPortfields marked deprecated in 23.0.0.Preview build: https://dash-docs--582.org.readthedocs.build/en/582/
Summary by CodeRabbit
protx listdiff,fundrawtransaction, and transaction response schemas.