📅 Original date posted:2015-07-04
📝 Original message:On Sat, Jul 4, 2015 at 3:11 AM, Raystonn <raystonn at hotmail.com> wrote:
> We need some analysis on why this has happened. It appears the larger hashrate is violating BIP66. Thus it appears the network is rejecting this BIP, though potentially accidentally. If this is an accident, how is such a large portion of hashrate forking, and what can we do to avoid this in the future?
A near majority of the hashrate on the network appears to be SPV mining.
Btcnuggets was a non-upgraded miner that produced an invalid block
after the lock in and f2pool and antpool have been extending it.
Fortunately their extension contains no transactions (an artifact of
SPV mining). Obviously a complete understanding is going to take some
time; though I would note that this general failure mode was one we
were aware of and is part of the reason the treshold is so high.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 15:41:37
in reply to nevent1q…tl5v
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 15:41:37Event JSON
{
"id": "71fca1261aa809b62cab954e61bc6fbb5e2dd5f37b4381015a4b5e3be16c397a",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686152497,
"kind": 1,
"tags": [
[
"e",
"b4b48e548f28c73730b217f080be671f078fe0ae13a4f41bdbadad9ec30c2e41",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-07-04\n📝 Original message:On Sat, Jul 4, 2015 at 3:11 AM, Raystonn \u003craystonn at hotmail.com\u003e wrote:\n\u003e We need some analysis on why this has happened. It appears the larger hashrate is violating BIP66. Thus it appears the network is rejecting this BIP, though potentially accidentally. If this is an accident, how is such a large portion of hashrate forking, and what can we do to avoid this in the future?\n\nA near majority of the hashrate on the network appears to be SPV mining.\n\nBtcnuggets was a non-upgraded miner that produced an invalid block\nafter the lock in and f2pool and antpool have been extending it.\nFortunately their extension contains no transactions (an artifact of\nSPV mining). Obviously a complete understanding is going to take some\ntime; though I would note that this general failure mode was one we\nwere aware of and is part of the reason the treshold is so high.",
"sig": "4a5782c8723e7808f5b5f761e837aa661c3c07bcb66f5a196743ecc1e80d29dbe305aac3748359c4c5c1e11900071f3c26bcb1e6d0354b49e1e8cf7cbc0ad570"
}