Gavin Andresen [ARCHIVE] on Nostr: 📅 Original date posted:2011-11-23 🗒️ Summary of this message: A hard block ...
📅 Original date posted:2011-11-23
🗒️ Summary of this message: A hard block found in a short time frame could incentivize miners to keep it secret and build more blocks on top of it, causing a potential network split.
📝 Original message:On Wed, Nov 23, 2011 at 9:38 AM, Christian Decker
<decker.christian at gmail.com> wrote:
> At some point you might find an incredibly hard block that makes your forked
> chain the hardest one in the network
Seems to me that's the real problem with any "hardest block found in X
minutes" scheme.
If I get lucky and find a really extremely hard block then I have an
incentive to keep it secret and build a couple more blocks on top of
it, then announce them all at the same time.
If the rest of the network rejects my longer chain because I didn't
announce the extremely hard block in a timely fashion... then how
could the network ever recover from a real network split? A network
split/rejoin will look exactly the same.
Bitcoin as-is doesn't have the "I got lucky and found an extremely
hard block" problem because the difficulty TARGET is used to compute
chain difficulty, not the actual hashes found.
---
PS: I proposed a different method for dealing with large hash power
drops for the testnet on the Forums yesterday, and am testing it
today.
--
--
Gavin Andresen
🗒️ Summary of this message: A hard block found in a short time frame could incentivize miners to keep it secret and build more blocks on top of it, causing a potential network split.
📝 Original message:On Wed, Nov 23, 2011 at 9:38 AM, Christian Decker
<decker.christian at gmail.com> wrote:
> At some point you might find an incredibly hard block that makes your forked
> chain the hardest one in the network
Seems to me that's the real problem with any "hardest block found in X
minutes" scheme.
If I get lucky and find a really extremely hard block then I have an
incentive to keep it secret and build a couple more blocks on top of
it, then announce them all at the same time.
If the rest of the network rejects my longer chain because I didn't
announce the extremely hard block in a timely fashion... then how
could the network ever recover from a real network split? A network
split/rejoin will look exactly the same.
Bitcoin as-is doesn't have the "I got lucky and found an extremely
hard block" problem because the difficulty TARGET is used to compute
chain difficulty, not the actual hashes found.
---
PS: I proposed a different method for dealing with large hash power
drops for the testnet on the Forums yesterday, and am testing it
today.
--
--
Gavin Andresen