Could we have some details on the decided changes?
This may sound like tech Jargon but I'll do my best to explain:
As far as I know, the only thing being changed that requires the hard fork is the time allowed for the search interval (hashdrift) and also the timedrift. This is basically a security update related to the possible vulnerability of a time-warp attack. Basically, all that is happening is that the time allowed for the hashdrift and the timedrift are being reduced. The hashdrift is being reduced to 15 seconds and the timedrift is being reduced to 30 seconds which is in line with mintcoin's 30 second block target. A timedrift that is further out in time than the block target presents a vulnerability. The vulnerability is a potential to trick the Mintcoin network into ever decreasing difficulty. This hard fork will make this impossible. The hashdrift (timestamp search interval) is being lowered to help prevent a surge in orphan blocks, as it is better to have the time of the hashdrift below the time of the timedrift. The hashdrift (timestamp search interval) helps the network know what time it is so that it can basically keep the ledger going on a continual time that everyone agrees on.
Specifically:
The hashdrift (timestamp search interval) is being reduced to 15 seconds.
The timedrift is being reduced to 30 seconds.
As far as Supasonic's changes, these are just some wallet GUI optimizations that don't require the hard fork, but are going to be included in it anyway, just to make the wallet more user-friendly.
I hope that helps explain. If anyone knows better, or wants to add to this, please do.
Thanks that makes sense I think
, I got a couple of things wrong on how I thought my p2p protocol worked (it actually uses the average time calculated between connected clients and removed outliers above a certain limit but not looked at it for like 14 months. it also had a different purpose than a coin and was designed more like bittorrent as a distributed database. Building 50 nodes in an L(1) configuration
Vid on 1 computer using TCP average of 14 connections per client, 320 nodes in a least redundancy configuration=
vid I'm sure there are some major flaws in security but I'm learning)
(in case anyone is interested)