From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] [RFCs] 13 new branches
Date: Tue, 4 Oct 2011 01:15:09 -0400 [thread overview]
Message-ID: <201110040115.11613.luke@dashjr.org> (raw)
These branches are NOT ready for merging to mainline, but need peer review.
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>
=
my_free_txn: accept the user's own transactions regardless of fees or
standardness; put credits-to-user toward covering fees required
Common-sense, really.
=
accept_nonstdtxn: adds a -acceptnonstdtxn option to allow miners to easily
accept "non-standard" transactions
We probably want to amend this with a block for OP_NOP*?
=
free_relay: relay transactions regardless of fees
=
optimize_cache_rpcauth: cache RPC username and password
Part of JoelKatz's diffN patches for a while, seems fairly well-tested on
(other) pools
=
optimize_conn_adjtime: cache AdjustedTime around a for loop
Another part of JoelKatz's diff4 patch.
=
optimize_ToHex: faster binary-to-hexadecimal-string function
=
optimize_DecodeBase64: faster base64 decoding
=
optimize_remove_CheckWork_delay: remove 2 second delay from CheckWork
I don't know why this is here, but apparently most pools work fine without
it? (from JoelKatz)
=
optimize_FastGetWork: optimizations for the common case of getwork
Yet another JoelKatz patch. His patch has it bundled tightly with the
ToHex branch, so once one is merged, the other will need rebasing.
=
optimize_http_status: use C instead of C++ for HTTP status reply strings
=
rpcclient_conn_close: "Connection: close" header in client mode
=
threaded_rpc: use a new thread for each JSON-RPC connection, with mutexes
preventing actual methods from being executed concurrently
(except for parts of getwork)
Tested on Eligius from day 1, under older versions. A few months ago, the
code was merged with some of JoelKatz's patch, making it stable with SSL
support.
=
rpc_keepalive: support for HTTP 1.1 keep-alive
Depends on threaded_rpc.
reply other threads:[~2011-10-04 5:15 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=201110040115.11613.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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