D
Having the same problem.
Unfortunately not.
As discussed in chat, I think we are better off bundling this with the changes coming in #2786 since this isn't priority and would require similar amounts of work to...
Would like to be assigned to this, should start researching on the the design soon.
This details the possible design approaches outlined for versioning dcrd's RPC endpoints. #### Option One: A single versioned endpoint for the entire API. Providing a single version endpoint for the...
After further discussions in chat with davec, versioning JSON-RPC endpoints individually was the best of the two approaches suggested. #2901 when done will outline the endpoint versioning process.
@JoeGruffins please provide the database, thanks.
Opting to go with re-indexing if this issue occurs instead of spending any more time fixing it since the underlying structures have been removed and will not be in the...
```sh 2021-12-13 23:47:05.194 [DBG] PEER: Received getinitstate (types [headblocks headblockvotes tspends]) from 127.0.0.1:50414 (inbound) 2021-12-13 23:47:05.194 [DBG] PEER: Sending headers (num 1, final hash 0e2cda36e9ffcce74456d173ce7c7bdcd43f3e3cd4289288b175cdd666157cb4, height 2) to 127.0.0.1:50414 (inbound)...
After discussing the two approaches in chat with davec, versioning each RPC individually was the better approach and that is what this versioning process recommends. "Per-RPC Versioning" and "versioned per-RPC...