Free transaction relay policy: Difference between revisions
code samples |
|||
| Line 15: | Line 15: | ||
| [[Eligius]] || 0.2 TBC (0.00008192 BTC) || 0.2 TBC || {{Table Value Yes}} || 2 TBC/KB at larger sizes | | [[Eligius]] || 0.2 TBC (0.00008192 BTC) || 0.2 TBC || {{Table Value Yes}} || 2 TBC/KB at larger sizes | ||
|} | |} | ||
== Code example for pool ownners == | |||
see : | |||
http://luke.dashjr.org/programs/bitcoin/files/0.3.24-eligius_sendfee.patch | |||
and : | |||
https://gitorious.org/bitcoin/gentoo/trees/master/net-p2p/bitcoind/files | |||
==See Also== | ==See Also== | ||
Revision as of 05:40, 25 October 2011
The original client currently refuses to relay transactions it considers "unacceptable". However, there may be miners that are willing to put these in a block. This group is for people who want to send such transactions, and those who want to put them in blocks.
Simply have your node maintain a connection to Lightfoot Hosting's node, which relays indiscriminately. This means that you can broadcast your transaction to it, and it will relay it to any miner who also has a connection to it. If your transaction meets the policies of at least one miner connected, it should eventually get into a block.
How to use or participate
Bitcoind/wxBitcoin
Add the command-line parameter: -addnode=173.242.112.53
Participating miners
| Miner | Minimum Fee (BTC) | Cost per KB | Non-standard Tx | Other Policy Notes |
|---|---|---|---|---|
| Eligius | 0.2 TBC (0.00008192 BTC) | 0.2 TBC | Yes | 2 TBC/KB at larger sizes |
Code example for pool ownners
see :
http://luke.dashjr.org/programs/bitcoin/files/0.3.24-eligius_sendfee.patch
and :
https://gitorious.org/bitcoin/gentoo/trees/master/net-p2p/bitcoind/files