UNSUBSCRIBE
On Wed, Feb 11, 2015 at 2:25 AM,
bitcoin-development-requ...@lists.sourceforge.net wrote:
Send Bitcoin-development mailing list submissions to
bitcoin-development@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
My replace-by-fee patch is now available for the v0.10.0rc4 release:
https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.10.0rc4
Along with demo scripts of the functionality:
https://github.com/petertodd/replace-by-fee-tools
New to this version is a comprehensive set of
Peter,
An important use of the core is being border router to proprietary software,
that is usually indexing the block chain and mempool. That software is also
assuming that double spends are not relayed by the core.
To remain useful as border router, the replace-by-fee patched core should
A proposal for stemming the tide of mining centralisation -- Requiring a
miner's signature in the block header (the whole of which is hashed), and
paying out coinbase to the miner's public key.
Please comment on whether this idea is feasible, has been thought of before,
etc., etc. Thank you.
Den 11 feb 2015 09:55 skrev Hector Chu hector...@gmail.com:
A proposal for stemming the tide of mining centralisation -- Requiring a
miner's signature in the block header (the whole of which is hashed), and
paying out coinbase to the miner's public key.
Please comment on whether this idea is
If you're interested in working on mining decentralisation, chipping away
at getblocktemplate support would be a better path forward. It's possible
to have decentralised pooled mining - I know it sounds like a contradiction
but it's not.
I wrote about some of the things that can be done in this
On Thu, Feb 12, 2015 at 08:23:29AM +0100, Tamas Blummer wrote:
Peter,
An important use of the core is being border router to proprietary software,
that is usually indexing the block chain and mempool. That software is also
assuming that double spends are not relayed by the core.
To
7 matches
Mail list logo
