Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MAX] MaxCoin - Alive and Kickin'
by
miningpoolhub
on 06/09/2014, 17:34:01 UTC
Actually checkpoint is not needed for hardfork. Hardfork don't need to be holding 51% major hash.

Not even major hashrate is needed for successful hardfork - what new nodes must do is ignore any node which does not comply to the new ruleset, it is as easy as that. Even
some coins laughed at by most people did it right (see Flappycoin, if node is not at least v3.1 it will end up ignored immidiately, you will never ever see it connect even for a split
second) but instead of just using what worked - which is what they did in the first place by cloning Bitcoin - so called developers opted for some untested techniques and stuff
that realy make no sense.

Unfortunately the wallet version was not updated with the client so we cannot do this until the majority of users has updated to the most recent fix. Once this happens we will ban previous versions.

Instructions for updating to the most recent version can be found at http://maxcoinnews.net/maxcoin-0-9-2-1-release/


Well coins don't determine to disconnect by the version information since it will behave abnormally when connected to malicious peer.
Validating block's reward amount and block hash is already implemented to check peer to peer and it disconnects automatically from the hardfork.

Client version doesn't do anything. You can implement to force disconnect from reading the version info but don't need to do that. It's implemented already on all altcoins.

If node reports old version ignore it else connect to it (or accept connection) and proceed with additional checks (block hash and so on). That is the way only few altcoins work.

With current hardfork, block reward amount changed and block reward is checked by all altcoins.
If block reward from the other peer does not matches local wallet's block reward calculation, then it disconnects.

All altcoins have this implemented.