📅 Original date posted:2013-05-25
📝 Original message:On 25 May 2013 07:46, 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?
>
> 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.
>
It might be an idea to have 'rule change' fixes and 'bug fix' releases go
out separately
>
> Regards,
>
> Zooko Wilcox-O'Hearn
>
> Founder, CEO, and Customer Support Rep
>
> https://LeastAuthority.com
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130525/84a6f9ae/attachment.html>;
Melvin Carvalho [ARCHIVE] /
npub1uv…saxrt
2023-06-07 15:02:26
in reply to nevent1q…frge
Author Public Key
npub1uvtfvcegcn9kds68r8he57emc480vqtx8t22kpsctxgjxae44gvsksaxrtPublished at
2023-06-07 15:02:26Event JSON
{
"id": "cb679cbff3ff7ba2e606dfec84419a03f61245f0766a15552c682effad79e582",
"pubkey": "e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19",
"created_at": 1686150146,
"kind": 1,
"tags": [
[
"e",
"2e4ed8621239305d3661a7f5128ae289da4cef55f854def90b39bf0c1366d978",
"",
"root"
],
[
"e",
"84820b92dd1f47a6cf1db6191783befce1364c92f5ebd00c5fe79bb7b8aafbfc",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2013-05-25\n📝 Original message:On 25 May 2013 07:46, Zooko Wilcox-OHearn \u003czooko at leastauthority.com\u003e wrote:\n\n\u003e jgarzik wrote:\n\u003e \u003e 1) Rule changes. We don't want these.\n\u003e\n\u003e In general? What constitutes a rule change?\n\u003e\n\u003e For example, if I understand correctly (from what Gavin said at\n\u003e Bitcoin 2013), there is a move afoot to lift the block size limit.\n\u003e Although, when I went to confirm my understanding by reading the\n\u003e bitcoin-development list archives, I don't see mention of this. Is\n\u003e there another forum I should be reading if I want to follow Bitcoin\n\u003e development?\n\u003e\n\u003e Anyway, I hope that there are some rule changes that you would\n\u003e consider for Bitcoin, although I recognize there are vast classes of\n\u003e such changes that you wouldn't.\n\u003e\n\u003e I'm trying to figure out what's the most productive way to show you,\n\u003e and everyone, candidates for such changes. Things that are definitely\n\u003e not suitable for merging to trunk tomorrow, but might be suitable in a\n\u003e year or two, or \"Next Time We Have A Hardfork\".\n\u003e\n\u003e I don't think alternative bitcoin-clones are the best venue for those.\n\u003e Although they are certainly good venues for changes which can never\n\u003e make it into Bitcoin.\n\u003e\n\u003e Perhaps the best venue for such a thing is just to fork bitcoin.git on\n\u003e github.\n\u003e\n\nIt might be an idea to have 'rule change' fixes and 'bug fix' releases go\nout separately\n\n\n\u003e\n\u003e Regards,\n\u003e\n\u003e Zooko Wilcox-O'Hearn\n\u003e\n\u003e Founder, CEO, and Customer Support Rep\n\u003e\n\u003e https://LeastAuthority.com\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Try New Relic Now \u0026 We'll Send You this Cool Shirt\n\u003e New Relic is the only SaaS-based application performance monitoring service\n\u003e that delivers powerful full stack analytics. Optimize and monitor your\n\u003e browser, app, \u0026 servers with just a few lines of code. Try New Relic\n\u003e and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130525/84a6f9ae/attachment.html\u003e",
"sig": "115e79547b4a209072066cc5d7fb4206ccb2d77f60e039f8543a198d0c709107fbdd6a021c62c53ca53d2f4c0b245668209ac019c662967cfef13dcaf1985622"
}