Skip to content

Commit

Permalink
docs: Correct blockmaxsize and blockprioritysize.
Browse files Browse the repository at this point in the history
  • Loading branch information
hypernoob authored and davecgh committed Jul 7, 2018
1 parent dc64afc commit 029fc17
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions doc.go
Expand Up @@ -108,9 +108,9 @@ Application Options:
--blockminsize= Mininum block size in bytes to be used when creating
a block
--blockmaxsize= Maximum block size in bytes to be used when creating
a block (750000)
a block (375000)
--blockprioritysize= Size in bytes for high-priority/low-fee transactions
when creating a block (50000)
when creating a block (20000)
--getworkkey= DEPRECATED -- Use the --miningaddr option instead
--nonaggressive Disable mining off of the parent block of the blockchain
if there aren't enough voters
Expand Down
4 changes: 2 additions & 2 deletions sampleconfig/sampleconfig.go
Expand Up @@ -311,15 +311,15 @@ const FileContents = `[Application Options]
; Specify the maximum block size in bytes to create. This value will be limited
; to the consensus limit if it is larger than this value.
; blockmaxsize=750000
; blockmaxsize=375000
; Specify the size in bytes of the high-priority/low-fee area when creating a
; block. Transactions which consist of large amounts, old inputs, and small
; sizes have the highest priority. One consequence of this is that as low-fee
; or free transactions age, they raise in priority thereby making them more
; likely to be included in this section of a new block. This value is limited
; by the blockmaxsize option and will be limited as needed.
; blockprioritysize=50000
; blockprioritysize=20000
; ------------------------------------------------------------------------------
Expand Down

0 comments on commit 029fc17

Please sign in to comment.