From: Michael Gronager <gronager@ceptacle•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Blocksize and off-chain transactions
Date: Wed, 13 Mar 2013 19:01:02 +0100 [thread overview]
Message-ID: <2FCCE0F7-66B0-4EBE-8448-C5F0F92A75FF@ceptacle.com> (raw)
In-Reply-To: <20130313174838.GA22621@savin>
Please note that it was not 0.8 that had issues, but 0.7(and downwards).
I really think changing features in 0.8 aiming for a fluffy limit to avoid lock object errors on 0.7 is the wrong way to go, and it will never cover for a similar situations in the future.
Instead I would like to propose a setup for "considerate mining":
* Run pools either on newest or second newest version (up to you depending on which features you like as a pool admin) - say e.g. 0.8
* Connect to the rest of the bitcoin network _only_ through a node of the other version - say e.g. 0.7
This guarantees that no blocks will get into the network that will not be accepted by both 0.8 and 0.7. Those two versions together should add up to say >90%.
Once everyone else (90%) have upgraded to the newest, (0.8), drop the 0.7 and start to introduce 0.9 instead.
/M
next prev parent reply other threads:[~2013-03-13 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:01 Gavin Andresen
2013-03-13 17:48 ` Peter Todd
2013-03-13 18:01 ` Michael Gronager [this message]
2013-03-13 18:08 ` Luke-Jr
2013-03-13 18:28 ` Pieter Wuille
2013-03-13 19:29 ` Roy Badami
2013-03-13 19:43 ` Stephen Pair
2013-03-13 20:14 ` Michael Gronager
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=2FCCE0F7-66B0-4EBE-8448-C5F0F92A75FF@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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