The RPC API compatibility is going to be absolutely destroyed with the RingCT RPC default update and adding in all the new fields to support more RingCT field information. This must require a major version update to reflect this.
v2 doesn't specifically indicate a hard fork of the protocol.
List view
0 issues of 6 selected
- Status: Open.#695 In Veil-Project/veil;
- Status: Open (in progress).Veil-Project/veilnumber 688#688 In Veil-Project/veil;
- Status: Open.#674 In Veil-Project/veil;
- Status: Open.#725 In Veil-Project/veil;
- Status: Open.#768 In Veil-Project/veil;
- Status: Open (in progress).Veil-Project/veilnumber 1019#1019 In Veil-Project/veil;