<unnamed>

Public Key

npub1z4nwmaam6z2a4mszqjl2fh0g402xfsnsehcctnxrr62mqa9agc9sv684vc

Profile Code

nprofile1qqsp2ehd77aap9w6acpqf04ymh52h4rycfcvmuv9enp3a9dswj75vzcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsujkhs6

Publishing to

nostr.wine

relay.damus.io

nos.lol

Last Notes

2023-06-07 15:02:26 UTC

- reply

📅 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
https://LeastAuthority.com