Node Relisiency

[peytonlundquist]

Description

1. Make field for min_vote_acceptance in config
2. Edit Config.java to take in the field to be used later
3. Edit in consensus (Node.java tallyQuorumSig?) so that they just need min_vote_acceptance * quorum amount of votes to proceed
4. Edit in Node.java recieveBlockSkeleton(?) - blocksignature. The nodes will check for quorum votes of signatures in the block before they add it so make it (min_vote_acceptance * quorum)

===========================================

5. The nodes who rejected the block need to also continue on to still add the block if it was voted majority
6. Nodes who for some reason still don't add the block '

Maybe nodes who voted for different block need to ask for a blockskeleton after the quorum to be up to date

How to handle a node which was left behind (failed vote, didn't hear about block, thinks the quorum is something its not)

At waht point do the nodes decide to move on?
Greedy? Do they just move on immediately after receiving enough? Do they give all quorum nodes a chance to sign?
How do they know to move on?

In this case, when the nodes server connection receives a "recieveQuorumSignature" or whatever quorum-related message, it will probably have to ignore that and not get hung-up "trusting"

Acceptance Criteria

Network doesn't fail when nodes don't vote / vote different / go offline (crash)