Please describe the feature you’d like to see added.
OpenRPC is a (human and) machine-readable, programming language-agnostic JSON-RPC API interface description standard.
Is your feature related to a problem, if so please describe it.
Having such a document could facilitate e.g. specification driven development, interactive documentation, code generation (documentation / clients), and automation of test cases.
Describe the solution you’d like
Generate the specification file automatically from src/rpc documentation.
Describe any alternatives you’ve considered
Write the specification “by hand” and update it manually.
Please leave any additional context
Ideally, Bitcoin core should switch to JSON-RPC version 2.0 (OpenRPC builds on top of JSON-RPC 2.0). In practice, we can still use OpenRPC generated clients as long as the missing "jsonrpc": "2.0"
is ignored. JSON-RPC 2.0 was implemented in implemented in #27101 and #30238.