View source for SIP2-Increase-Work-Weighting-For-Higher-Fields

<div align="center">
    <h1>Snowblossom Improvement Proposal 2</h1>
    <h2>SIP2: Increase Work Weighting For Higher Fields</h3>
</div>
= Background =

Without this change, a miner with decent hash power but not a majority can do the following:

* Wait until the network goes to a new field and the hash rate drops due to some miners slowing down or dropping out.
* Miner forks the chain as a private fork just before the new snow field activates.<br />

* They control their block times to keep field from activating.
* Since the main network is dropping in difficulty and the miner is keeping the difficulty high (but not quite high enough to trigger new field) their private change ends up having more work on it than the main chain.
* Miner broadcasts their chain and causes a major reorg

= Fix =

The fix is fairly simple, it is to add a weighting to the work sum such that higher fields are prefered. In this fix, each increase of the snow field 4x the effective work added per block. This doesn't make the attack above impossible, it just makes it harder. The attacker would have to keep the hash rate of their chain at four times that of the main chain to have a higher work sum.

= Code =

Working branch for this is [https://github.com/snowblossomcoin/snowblossom/tree/sip2 sip2]

= Questions =

Should it be 4x or higher? The higher it is, the harder this attack is. However, if it is very high then someone can go back to when the network got near but did not enter a new field and make a few blocks into the new field and reorg into that. If we do 4x for example, they could do that with 1/4 the hash power of the full network, but would have to maintain 1/4 the hash power on the higher field, which will probably be a challenge.

= Deployment =

Since nodes don't have to actually agree on what the worksum is, nodes can update whenever. They will just start using the new worksum math and it is fine. No need to even nuke database and restart.

= Voting =

* Passes when 1000 blocks pass containing 25% voting and &gt;50% agreement
* Pools will represent their miners.
* Set in your miner or pool configuration file either
** <code>vote_yes=2</code>
** <code>vote_no=2</code>

= Sponsors =

* Joseph Gleason - Fireduck (slack) - fireduck64 (github)
* Zachary Coon - Clueless (slack) - cluelessperson (github)