š
Original date posted:2011-09-14
šļø Summary of this message: Delay forwarding of blocks and their extensions until extended one more time to get the incentives right. Forking change is high risk for little benefit.
š Original message:> Perhaps better thing to do is to also delay the _forwarding_ of these
> blocks _and_ blocks that extend them, until extended one more time.
Excellent idea, that gets the incentives right.
RE: fixing the root cause with a forking change:
What do other people think? I think it is too high risk for too
little benefit and shouldn't be done until we have a really compelling
reason to introduce a forking change.
The first really compelling reason I can think of is removing the
MAX_BLOCK_SIZE limit (but does something clever to prevent the
rogue-miner-sends-you-a-valid-10Terabyte-block attack).
--
--
Gavin Andresen
Gavin Andresen [ARCHIVE] /
npub1s4ā¦d44kw
2023-06-07 02:25:43
in reply to nevent1qā¦0eq0
Author Public Key
npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kwSeen on
wss://relay.noswhere.comPublished at
2023-06-07 02:25:43Event JSON
{
"id": "c98468de11c9a717c8252eb83936625ab16e96b552682ee80a7a81e4d6122174",
"pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4",
"created_at": 1686104743,
"kind": 1,
"tags": [
[
"e",
"c5d8eb0720120c08594c588b2c728c7a4f1ca34d1ae4dfac6ef6225ba2d5a835",
"",
"root"
],
[
"e",
"9c23544701b467728b9a36bc92b9672124a2f6ff00411932446a9b94e8f5da94",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "š
Original date posted:2011-09-14\nšļø Summary of this message: Delay forwarding of blocks and their extensions until extended one more time to get the incentives right. Forking change is high risk for little benefit.\nš Original message:\u003e Perhaps better thing to do is to also delay the _forwarding_ of these\n\u003e blocks _and_ blocks that extend them, until extended one more time.\n\nExcellent idea, that gets the incentives right.\n\nRE: fixing the root cause with a forking change:\n\nWhat do other people think? I think it is too high risk for too\nlittle benefit and shouldn't be done until we have a really compelling\nreason to introduce a forking change.\n\nThe first really compelling reason I can think of is removing the\nMAX_BLOCK_SIZE limit (but does something clever to prevent the\nrogue-miner-sends-you-a-valid-10Terabyte-block attack).\n\n-- \n--\nGavin Andresen",
"sig": "b0764fadab2a157826a97c33c22e6ff6942f81a50cdd1600760cd37d00a8212d443feb997a23d940169cc88c47208513b944bc0356fdf02867f9a1b8cf262424"
}