From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] [PULLs] 6 *more* branches
Date: Tue, 4 Oct 2011 01:06:17 -0400 [thread overview]
Message-ID: <201110040106.20441.luke@dashjr.org> (raw)
These branches are ready for merging to mainline. Note that these are not the
same ones I sent earlier today, but part of a larger batch I have just
finished rebasing.
Branches can be viewed at:
http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/heads
git pull git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin.git <branchname>
=
coinbaser: allow customizing what addresses are paid by generation, with
failover to the standard "50 BTC to me" behaviour; also adds the
"setworkaux" JSON-RPC call to add arbitrary data to the coinbase,
which can be used to implement merged-mining (has safeguards
against creating invalid coinbases)
Eligius has tested this quite a bit under the 0.3.23 codebase.
=
txinfo: adds "pooledtx" (number of transactions in memory pool),
"currentblocktx" (number of txns in the last block created), and
"currentblocksize" to the output of the JSON-RPC 'getinfo' method;
adds "block_hash" and "block_index" to transactions shown by
'listtransactions' and similar JSON-RPC methods
Been using this since 0.3.21 without issues.
=
force_send: disables automatically adding "minimum" fees for JSON-RPC
methods-- instead, it returns an error or, iff the user sets the
new second parameter "force" to the 'settxfee' JSON-RPC call,
sends the transaction with the user-specified fee
This only affects JSON-RPC users, who should be assumed to understand the
risk of sending with insufficient fees.
=
eligius_relay: relay transactions that satisfy Eligius's minimum fee when it's
lower than the default rules
eligius_sendfee: allow sending the lower fee between default and Eligius, and
adds relay.eligius.st to the DNS seed list
Merge or not, up to you guys... I don't really care.
=
bugfix_CreateThread_ThreadSocketHandler_errReporting: report an error in
debug.log
reply other threads:[~2011-10-04 5:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110040106.20441.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox