This updates the 2.0 release branch to use the latest versions of the dcrjson/v4, rpc/jsonrpc/types/v4, and mixing modules which include some minor improvements to the pairing process and the addition of a new RPC method named getmixmessage to obtain mixing messages from the mixpool. It also backports the relevant RPC server code to implement the new method.
In particular, the following updated module version is used:
Note that it also cherry picks all of the commits included in updates to the dcrjson/v4, rpc/jsonrpc/types/v4, and mixing modules to ensure they are also included in the release branch even though it is not strictly necessary since go.mod has been updated to require the new releases and thus will pull in the new code. However, from past experience, not having code backported to modules available in the release branch too leads to headaches for devs building from source in their local workspace with overrides such as those in go.work.
This updates the 2.0 release branch to use the latest versions of the
dcrjson/v4,rpc/jsonrpc/types/v4, andmixingmodules which include some minor improvements to the pairing process and the addition of a new RPC method namedgetmixmessageto obtain mixing messages from the mixpool. It also backports the relevant RPC server code to implement the new method.In particular, the following updated module version is used:
Note that it also cherry picks all of the commits included in updates to the
dcrjson/v4,rpc/jsonrpc/types/v4, andmixingmodules to ensure they are also included in the release branch even though it is not strictly necessary sincego.modhas been updated to require the new releases and thus will pull in the new code. However, from past experience, not having code backported to modules available in the release branch too leads to headaches for devs building from source in their local workspace with overrides such as those ingo.work.