Difference between revisions of "Genesis upgrade"

Line 20: Line 20:
 
                     the block including the block header and all of the  
 
                     the block including the block header and all of the  
 
                     transactions confirmed by the block.
 
                     transactions confirmed by the block.
Number of CheckSig Operations per MB of Block Space
+
 +
        Number of CheckSig Operations per MB of Block Space
  
 
Transaction Consensus Rules
 
Transaction Consensus Rules
Line 29: Line 30:
 
                     bytes). This limitation is expected to be lifted in the  
 
                     bytes). This limitation is expected to be lifted in the  
 
                     future.
 
                     future.
Maximum Number of CheckSig Operations per Transaction
+
nLockTime
+
        Maximum Number of CheckSig Operations per Transaction
nSequence
+
 +
        nLockTime
 +
 +
        nSequence
 
 
 
Script Language Rules
 
Script Language Rules

Revision as of 12:26, 24 January 2020

Genesis is a major update to the BitcoinSV mining client which is used by the majority of miners on the BitcoinSV network.

The upgrade is seen as a return to the original Bitcoin protocol, and includes the removal of all limit based consensus rules, and their replacement with miner configurable settings that give node operators the autonomy needed to set their own limits as they determine are practical.

The full specification is available here.

Genesis is scheduled to go into effect on or around the 4th of February 2019.

See also:

https://bitcoinsv.io/2020/01/15/changes-for-the-genesis-upgrade/

https://www.prnewswire.com/news-releases/bitcoin-svs-genesis-hard-fork-300989579.html

The four following areas of the protocol and specification contain the changes required for the Genesis upgrade

Block Consensus Rules

Block Size - The size of a block in bytes of the serialized form of

                    the block including the block header and all of the 
                    transactions confirmed by the block.
       Number of CheckSig Operations per MB of Block Space

Transaction Consensus Rules

Maximum Transaction Size - The size of a transaction is the size in

                    bytes of the serialized form of the transaction. The 
                    maximum size of a transaction is 1GB (1,000,000,000 
                    bytes). This limitation is expected to be lifted in the 
                    future.
       Maximum Number of CheckSig Operations per Transaction
       nLockTime
       nSequence

Script Language Rules P2SH sunset


Standard Local Policies Maximum Acceptable Transaction Size Policy Transaction Evaluation Timeout