Merge #6458: chore: bump MIN_MASTERNODE_PROTO_VERSION to latest proto

1ecfb891bc chore: bump MIN_MASTERNODE_PROTO_VERSION to latest proto (pasta)

Pull request description:

  ## Issue being fixed or feature implemented
  Bump minimum master node protocol version to latest protocol.

  ## What was done?

  ## How Has This Been Tested?

  ## Breaking Changes
  Masternodes that don't upgrade will end up getting a PoSe ban

  ## Checklist:
    _Go over all the following points, and put an `x` in all the boxes that apply._
  - [ ] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  UdjinM6:
    utACK 1ecfb891bc
  kwvg:
    utACK 1ecfb891bc

Tree-SHA512: 18e0620370924c4f9b0c72b9f384a7b627b9d395b4a4a942d1eaabd8f4294869fb5831c8d237b825053a0ca5aa143cfbb4726312877670088333faa04ab10ef2
This commit is contained in:
pasta 2024-12-07 12:14:43 -06:00
parent 9d3f22a4b2
commit 2f71f4d7d0
No known key found for this signature in database
GPG Key ID: E2F3D7916E722D38

View File

@ -20,7 +20,7 @@ static const int INIT_PROTO_VERSION = 209;
static const int MIN_PEER_PROTO_VERSION = 70216; static const int MIN_PEER_PROTO_VERSION = 70216;
//! minimum proto version of masternode to accept in DKGs //! minimum proto version of masternode to accept in DKGs
static const int MIN_MASTERNODE_PROTO_VERSION = 70233; static const int MIN_MASTERNODE_PROTO_VERSION = 70235;
//! protocol version is included in MNAUTH starting with this version //! protocol version is included in MNAUTH starting with this version
static const int MNAUTH_NODE_VER_VERSION = 70218; static const int MNAUTH_NODE_VER_VERSION = 70218;