From: Peter Todd <pete@petertodd•org>
To: Gregory Maxwell <gmaxwell@gmail•com>,
Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
Nicolas Dorier <nicolas.dorier@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Fri, 21 Aug 2015 09:29:25 +0000 [thread overview]
Message-ID: <BE291934-F40A-4163-834C-6B3FFBD7C4E0@petertodd.org> (raw)
In-Reply-To: <CAAS2fgR4bsJtC99-fK1L+FsQT7vOfOpz9FOVqvAnqbpkaRJHLQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 20 August 2015 21:45:23 GMT-07:00, Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>I think this is a bit well, sad, at the moment-- a basic principle in
>sound decision making is that one should try to withhold judgement
>until after the analysis and options are laid out to avoid prematurely
>laying down "battle lines" which then they're socially and politically
>committed to a particular answer.
>
>
>There are several other BIPs in the works right now that aren't out
>there yet, as well (as presumably) new insight from the workshop. It
>would be a shame if these things would be for naught because of being
>decided prematurely.
I'll second that, which is why I've mostly not commented on whether or not particular proposals are good ideas, except in the case where they're obviously broken due to reasons other than the blocksize itself. For instance both of Garzik's proposals and Andresen's BIP101 have serious flaws regardless of your thoughts on the blocksize, which is why I've commented on them. Wuille's OTOH is implemented well, which is why I have not commented about it.
What might be valuable is to ask devs to explain what their threat models are, what should be at the root of their thinking about the blocksize.
-----BEGIN PGP SIGNATURE-----
iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV1u9o
AAoJEMCF8hzn9Lncz4MH/0ZvaS+XK4+kVsgvdO0Mx8Axi8lesQoOSNafY1O8F4Tx
QQcIWYk+QgST0wBOooqIkivlWUhXUUc0A22VvYJ2gOt+KCWCscXkOnPrHWMA2f80
4KBEbLyFd+eaKQnCXoWX6SlDiYrNhyIySwAAvZyJ6IxTliUljuuk4Cc+K7pnVKu2
tfaRXtoal3IzyVb/rxUafgRoCaR2QdkYfr+xwkeF9AjqYFUKL+p5zENV97cbLsiF
/Rxtpe0A9RSClc+VX0yyjFAIIUfmFDWdC7+wNv8YBvHssE0lndPByxWTNVHnHmCk
44XfrsSL0LAqPIqcxyK0hnUSUgKPo0c2chd9mlXHpYE=
=eHHo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-08-21 9:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 4:57 Nicolas Dorier
2015-08-21 3:10 ` Btc Drak
2015-08-21 4:45 ` Gregory Maxwell
2015-08-21 5:10 ` Nicolas Dorier
2015-08-21 9:09 ` Btc Drak
2015-08-21 9:32 ` Peter Todd
2015-08-21 9:29 ` Peter Todd [this message]
2015-08-21 9:31 ` Btc Drak
2015-08-21 9:35 ` Peter Todd
2015-08-21 10:55 ` Yifu Guo
2015-08-21 11:28 ` Btc Drak
2015-08-21 12:28 ` Yifu Guo
2015-08-21 13:18 ` Oliver Egginger
2015-08-21 13:34 ` Will Madden
2015-08-21 17:31 ` Oliver Egginger
2015-08-21 18:07 ` Will Madden
2015-08-22 3:02 ` odinn
2015-08-21 16:58 ` Nicolas Dorier
2015-08-21 3:38 Nicolas Dorier
2015-08-21 3:45 ` Eric Lombrozo
2015-08-21 3:54 ` Nicolas Dorier
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=BE291934-F40A-4163-834C-6B3FFBD7C4E0@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmaxwell@gmail$(echo .)com \
--cc=nicolas.dorier@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