The development team has done a blitz Hard Fork on the 06th of January 2023 to stop crackers from being able to continue with the hacking of accounts with no public key and also to freeze the stolen Signa on those cracker's accounts. You can read the details here : https://medium.com/signum-network/improving-the-security-of-the-signum-chain-69f4daac8545

The upgrade was driven by good intentions for the Signum network, but mainly initiated by the development team and information was not widely distributed as the team did not want the cracker to gain advanced notice of the hard fork.

Now, after all information about the code change and its reasons are revealed, to be completely open and to conform to our high standards of decentralization, the community as a whole has to decide if the applied constraints should be kept or lifted. If the community chooses to lift all the constraints added in Signum Node v3.6.0, then we will organize an upgrade removing them.

As every hard fork aka protocol change is only valid if the majority of nodes follow it, we should also open the vote again for the current change by giving a vote via the current nodes of the Signum network.

Node operators that oppose the v3.6.0 upgrade, should run v3.5.3 with the following in their config file:

P2P.BootstrapPeers = canada.signum.network:8123

P2P.rebroadcastTo = canada.signum.network:8123

P2P.NumBootstrapConnections = 1

With the above configuration, these versions have compatible databases and will join the current majority of nodes, plus they can be freely switched without having to sync from empty.

We will monitor the number of nodes running either v3.6.0 or v3.5.3 within the next 30 days (deadline 22.02.2023).

The poll will only count currently known nodes, to avoid people trying to spin multiple nodes to manipulate the results. The nodes which are valid to vote will be assigned to a vote icon on the explorer https://explorer.notallmine.net/.

The nodes should have been found before 21.01.2023, are not a duplicate node, and must be online to be valid. These votes will be counted on the deadline date.

If the majority of nodes choose to run v3.5.3 we will prepare all that is necessary to lift all the recently imposed constraints. If the majority chooses to keep running v3.6.0, then we continue discussing the best solution for the unprotected accounts and stolen funds, currently frozen.

We suggest pool operators to keep using v3.6.0 until this voting section ends to avoid unnecessary forks while the voting.If a pool-owner likes to vote for 3.5.3 he/she can do that by announcing it on the Signum discord channel #under-attack in a special thread.

The SNR will be paid for nodes with 3.5.3 or 3.6.0.

Download Signum-Node 3.5.3: https://github.com/signum-network/signum-node/releases/tag/v3.5.3

Download Signum-Node 3.6.0: https://github.com/signum-network/signum-node/releases/tag/v3.6.0

Your Signum-Network