Author

Topic: a list of transaction inclusion policies of all major pools (Read 740 times)

legendary
Activity: 1078
Merit: 1005
We had a nice list of this, but then the 0.8 hardfork/bug happened and most pools reverted back to default or near-default policies.  After May 15th we should probably revive organofcorti's thread once pools update their policies again.  Until May 15th, we're held back by the 0.8.1 limits.
That would be this thread.
legendary
Activity: 1750
Merit: 1007
We had a nice list of this, but then the 0.8 hardfork/bug happened and most pools reverted back to default or near-default policies.  After May 15th we should probably revive organofcorti's thread once pools update their policies again.  Until May 15th, we're held back by the 0.8.1 limits.
sr. member
Activity: 334
Merit: 250
Is there anywhere a list of current policies of all major pools regarding including transactions in mined blocks?

The current default policy is described here:

https://en.bitcoin.it/wiki/Transaction_fees#Including_in_Blocks

Quote
27.000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee. Transactions are added highest-priority-first to this section of the block. Then transactions that pay a fee of at least 0.0005 BTC/kb are added to the block, highest-fee transactions first, until the block is not more than 250.000 bytes big.

But as I understand it, pools can choose to have a different policy, and that can change over time.

It would be very useful to have a regularly updated wiki page with policies of all the major (e.g. having at least 1/1000 of the current global hashrate) pools and their current transaction inclusion policies.

Also the default policy changes over time, so when a change happens, it would be useful to know which pools have already switched to the new default policy, and which not.

Maybe lets start with listing available information in this thread, and then make a wiki page - preferably updated by pool owners, so we have reliable information aggregated somewhere.
Jump to: