From: Zooko Wilcox-OHearn <zooko@leastauthority•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] (no subject)
Date: Sat, 25 May 2013 05:46:11 +0000 [thread overview]
Message-ID: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com> (raw)
jgarzik wrote:
> 1) Rule changes. We don't want these.
In general? What constitutes a rule change?
For example, if I understand correctly (from what Gavin said at
Bitcoin 2013), there is a move afoot to lift the block size limit.
Although, when I went to confirm my understanding by reading the
bitcoin-development list archives, I don't see mention of this. Is
there another forum I should be reading if I want to follow Bitcoin
development?
Anyway, I hope that there are some rule changes that you would
consider for Bitcoin, although I recognize there are vast classes of
such changes that you wouldn't.
I'm trying to figure out what's the most productive way to show you,
and everyone, candidates for such changes. Things that are definitely
not suitable for merging to trunk tomorrow, but might be suitable in a
year or two, or "Next Time We Have A Hardfork".
I don't think alternative bitcoin-clones are the best venue for those.
Although they are certainly good venues for changes which can never
make it into Bitcoin.
Perhaps the best venue for such a thing is just to fork bitcoin.git on github.
Regards,
Zooko Wilcox-O'Hearn
Founder, CEO, and Customer Support Rep
https://LeastAuthority.com
next reply other threads:[~2013-05-25 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 5:46 Zooko Wilcox-OHearn [this message]
2013-05-25 8:09 ` Wladimir
2013-05-27 2:43 ` [Bitcoin-development] Handling alerts & communication on bitcoin.org Saïvann
2013-05-25 8:25 ` [Bitcoin-development] (no subject) Melvin Carvalho
2013-05-25 8:53 ` Luke-Jr
2013-05-25 9:23 ` Melvin Carvalho
2014-05-04 1:47 losewife
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='CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com' \
--to=zooko@leastauthority$(echo .)com \
--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