Bitcoin Forum
February 27, 2024, 03:59:49 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
   Home   Help Search Login Register More  
Pages: [1]
Author Topic: Transaction options for bitcoind  (Read 807 times)
cabin (OP)
Sr. Member
Offline Offline

Activity: 604
Merit: 250

View Profile
November 02, 2012, 03:52:34 PM

Are there ways to configure bitcoin.conf so that it only accepts at most say 500 transactions into the next block, or only those transactions with a fee > 0? I thought I remember seeing development on this but not sure where it went and I can't find any recent docs on it.
No Gods or Kings. Only Bitcoin
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Gavin Andresen
Offline Offline

Activity: 1652
Merit: 2163

Chief Scientist

View Profile WWW
November 02, 2012, 06:10:52 PM

The relevant settings and their default values for recent versions of bitcoind are:

Maximum size, in bytes, of blocks you create:

How many bytes of the block should be dedicated to high-priority transactions,                                                                                                 
included regardless of the fees they pay                                                                                                                                 

Minimum block size you want to create; block will be filled with free transactions                                                                                       
until there are no more or the block reaches this size:                                                                                                                 

Fee-per-kilobyte amount (in BTC) considered the same as "free"                                                                                                                   
Be careful setting this: if you set it to zero then                                                                                                                     
a transaction spammer can cheaply fill blocks using                                                                                                                     
1-satoshi-fee transactions. It should be set above the real                                                                                                             
cost to you of processing a transaction.                                                                                                                                 

So if you set blockprioritysize=0, you will only accept fee-paying transactions.

If you only want to accept 500 or so transactions, set the blocksize to 500 * average transaction size (400 bytes or so) = 200000

The rules for filling up the block are:

First, take the highest priority transactions (regardless of fee) and fill up the block to blockprioritysize.  (if blockprioritysize is zero, then this step does not apply)

Then, take the highest fee-per-kilobyte transactions and continue filling the block until either you run out of transactions with a fee-per-kilobyte greater than mintxfee or the block would be larger than blockmaxsize.

Finally: the rules are likely to change again fairly soon so that groups of related transactions are considered together ("child pays for parent", so customers can send zero-fee transactions to merchants, who can create a child transaction with a fee when they need the transaction to be confirmed).

How often do you get the chance to work on a potentially world-changing project?
cabin (OP)
Sr. Member
Offline Offline

Activity: 604
Merit: 250

View Profile
November 03, 2012, 12:17:03 PM

Thanks, those settings are working perfectly for me.
Pages: [1]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!