Post
📅 Original date posted:2013-05-25 📝 Original message: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 LeastAuthority.com
0
📅 Original date posted:2013-05-25 📝 Original message:On Sat, May 25, 2013 at 7:46 AM, Zooko Wilcox-OHearn < zooko at leastauthority.com> wrote: > jgarzik wrote: > > 1) Rule changes. We don't want these. > > In general? What constitutes a rule change? > I'm sure he means rule changes with economical impact, such as miner block reward, total number of bitcoins, block speed. Mostly non-interesting from a technical view point, but the only changes most altcoins seem to be making... In any case, these are set in stone and cannot ever be changed for bitcoin or all hell will break loose. See also en.bitcoin.it/wiki/Hardfork_Wishlist. Wladimir -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130525/cbc46b25/attachment.html>
0