📅 Original date posted:2017-07-13
📝 Original message:The BIP has been updated.
Changes:
- The technical spec has been improved: now the block size increase is
specified in terms of weight and not in terms of bytes.
- The increase in the maximum block sigops after HF has been documented.
- Comments added about the worst case block size.
Happy weekend! And don't forget to start signaling something before block
475776 ! It's just 90 blocks away.
Bit 1 or 4,1 or whatever you wish, but please signal something.
To the moon!
On Wed, Jul 12, 2017 at 2:38 PM, Jorge Timón via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>
> On 12 Jul 2017 2:31 pm, "Tom Zander via bitcoin-dev" <bitcoin-dev at lists.
> linuxfoundation.org> wrote:
>
> On Monday, 10 July 2017 20:38:08 CEST Jorge Timón via bitcoin-dev wrote:
> > I think anything less than 1 year after release of tested code by some
> > implementation would be irresponsible for any hardfork, even a very
> > simple one.
>
> Good news!
>
> Code to support 2x (the hard fork part of the proposal) has been out and
> tested for much longer than that.
>
>
> Not true. It's different code on top of segwit. The first attempt in btc1
> (very recent) didn't even increased the size (because it changed the
> meaningless "base size" without touching the weight limit. As for the
> current code, I don't think it has been properly tested today, let alone
> "for mucj longer than 1 year.
> Anyway, I said, one year from tested release. Segwitx2 hasn't been
> released, has it? If so, too late to discuss a bip imo, the bip may end up
> being different from what has been released due to feedback (unless it is
> ignored again, of course).
>
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170713/03b124d8/attachment.html>;
Sergio Demian Lerner [ARCHIVE] /
npub1fv…3vq7f
2023-06-07 18:04:06
in reply to nevent1q…t65r
Author Public Key
npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7fPublished at
2023-06-07 18:04:06Event JSON
{
"id": "5a3bcca599be86476729c558cde8d2a59e859276afe2bede1209b39a23f0f3aa",
"pubkey": "4b38603408f5be002091210e869a4ca86fc2aa1ffd0871036a0668068ee626ee",
"created_at": 1686161046,
"kind": 1,
"tags": [
[
"e",
"74e46143b6146bfbf41855e76069c36a2cf73fb16bb2644a1bf3b792696fbbf0",
"",
"root"
],
[
"e",
"0825563956681f8e094101c353b1c43d6db22611e2ca6ef5da9fa436c7dfe0d7",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2017-07-13\n📝 Original message:The BIP has been updated.\n\nChanges:\n- The technical spec has been improved: now the block size increase is\nspecified in terms of weight and not in terms of bytes.\n- The increase in the maximum block sigops after HF has been documented.\n- Comments added about the worst case block size.\n\nHappy weekend! And don't forget to start signaling something before block\n475776 ! It's just 90 blocks away.\nBit 1 or 4,1 or whatever you wish, but please signal something.\n\nTo the moon!\n\n\nOn Wed, Jul 12, 2017 at 2:38 PM, Jorge Timón via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e\n\u003e\n\u003e On 12 Jul 2017 2:31 pm, \"Tom Zander via bitcoin-dev\" \u003cbitcoin-dev at lists.\n\u003e linuxfoundation.org\u003e wrote:\n\u003e\n\u003e On Monday, 10 July 2017 20:38:08 CEST Jorge Timón via bitcoin-dev wrote:\n\u003e \u003e I think anything less than 1 year after release of tested code by some\n\u003e \u003e implementation would be irresponsible for any hardfork, even a very\n\u003e \u003e simple one.\n\u003e\n\u003e Good news!\n\u003e\n\u003e Code to support 2x (the hard fork part of the proposal) has been out and\n\u003e tested for much longer than that.\n\u003e\n\u003e\n\u003e Not true. It's different code on top of segwit. The first attempt in btc1\n\u003e (very recent) didn't even increased the size (because it changed the\n\u003e meaningless \"base size\" without touching the weight limit. As for the\n\u003e current code, I don't think it has been properly tested today, let alone\n\u003e \"for mucj longer than 1 year.\n\u003e Anyway, I said, one year from tested release. Segwitx2 hasn't been\n\u003e released, has it? If so, too late to discuss a bip imo, the bip may end up\n\u003e being different from what has been released due to feedback (unless it is\n\u003e ignored again, of course).\n\u003e\n\u003e\n\u003e --\n\u003e Tom Zander\n\u003e Blog: https://zander.github.io\n\u003e Vlog: https://vimeo.com/channels/tomscryptochannel\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170713/03b124d8/attachment.html\u003e",
"sig": "853ff555f0d5107b05f665d1ecba5d995be8a73494737beccd8aab1653e947f0da69ca45a0704074139a211dc9e87ba6c6b4dd96bf3744c7054d0221342aed3e"
}