From b180ee5872d0ae42ea5776794c09f8e78b9fe1f5 Mon Sep 17 00:00:00 2001 From: cryptapus Date: Wed, 22 Jun 2016 12:46:31 -0500 Subject: [PATCH] Proposed change to default BLOCK_MAX_SIZE This is a proposed change to prevent a spam attack. An attacker would need to be a miner to needlessly fill blocks. Individual miners should be able to change this if desired. Alternatively, we could look at adjusting fees, but seems to be not as straight forward? --- src/main.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main.h b/src/main.h index f5603992..06dbbc50 100644 --- a/src/main.h +++ b/src/main.h @@ -48,7 +48,7 @@ class CValidationState; struct CNodeStateStats; /** Default for -blockmaxsize and -blockminsize, which control the range of sizes the mining code will create **/ -static const unsigned int DEFAULT_BLOCK_MAX_SIZE = 750000; +static const unsigned int DEFAULT_BLOCK_MAX_SIZE = 200000; static const unsigned int DEFAULT_BLOCK_MIN_SIZE = 0; /** Default for -blockprioritysize, maximum space for zero/low-fee transactions **/ static const unsigned int DEFAULT_BLOCK_PRIORITY_SIZE = 50000;