When merged, this will merge #9292 as well.
I created a new pull, so 0.13.2 isn't blocked by this.
When merged, this will merge #9292 as well.
I created a new pull, so 0.13.2 isn't blocked by this.
It looks intentional and desirable to allow setting future serialisation versions. Especially something like 9999 to mean "use the very latest even if not the default".
ACK
987 | @@ -988,6 +988,9 @@ bool AppInitParameterInteraction() 988 | if (GetArg("-rpcserialversion", DEFAULT_RPC_SERIALIZE_VERSION) < 0) 989 | return InitError("rpcserialversion must be non-negative."); 990 | 991 | + if (GetArg("-rpcserialversion", DEFAULT_RPC_SERIALIZE_VERSION) > 1)
Maybe define a constant for the max valid RPC serialize version?
Which would imply the default is not always the max. It is not clear from the comments if this is desired.
Edit: Anyway, fixing this nit is irrelevant for backport. Either we merge/backport this and bikeshed later or we close the pull based on luke-jr's rationale.
Milestone
0.13.2