Mr. Spread, here is the Darkcoin dev's explanation for the fork. Hopefully SPR will be able to avoid like issues:
[noparse]https://darkcointalk.org/threads/0-11-0-darkcoin-core-release.3601/page-23[/noparse]
Post 453 and 458
You need to copy and paste otherwise you get rickrolled.
This will not happen with SpreadCoin.
In DarkCoin the messages which select masternodes are separate from the blockchain and are distributed independently. This way it is possible that nodes will have different opinion on what masternode should receive next payment.
In SpreadCoin all votes for masternodes will be stored in blocks and the payee will be uniquely determined from previous blocks. Just like you can check that any transaction included in the block is correct by comparing its inputs with outputs in previous blocks you will be able to check that masternode payment is correct by checking previous blocks.
Why bitcoin is so reliable? Because all nodes have exactly the same rules how to determine which blockchains are correct and which one is better (required more work) than others, these rules are only depended on blocks themselves, not on the order in which they were received them nor on any other messages which you may or may not receive in time. The network can be unstable in the case of some major event which will break connectivity between nodes such as damage of submarine cables, world war, alien invasion, zombie apocalypse, etc. but once connectivity between nodes is reestablished all nodes will stick to the same blockchain. The same will apply to SpreadCoin.
Where exactly will the Ddosing happen? Constantly asking the network to send the list of the top 1000 allowed masternodes? Is this transmitted data going to be what bloats/attacks the system?
Isn't this data communicated thru the blockchain? If not, maybe it should, so that miners can secure this data.