Luke Dashjr [ARCHIVE] on Nostr: 📅 Original date posted:2017-07-05 📝 Original message:I've already opened a PR ...
📅 Original date posted:2017-07-05
📝 Original message:I've already opened a PR almost 2 weeks ago to do this and fix the other
issues BIP 9 has.
https://github.com/bitcoin/bips/pull/550It just needs your ACK to merge.
On Wednesday 05 July 2017 1:30:26 AM shaolinfry via bitcoin-dev wrote:
> Some people have criticized BIP9's blocktime based thresholds arguing they
> are confusing (the first retarget after threshold). It is also vulnerable
> to miners fiddling with timestamps in a way that could prevent or delay
> activation - for example by only advancing the block timestamp by 1 second
> you would never meet the threshold (although this would come a the penalty
> of hiking the difficulty dramatically). On the other hand, the exact date
> of a height based thresholds is hard to predict a long time in advance due
> to difficulty fluctuations. However, there is certainty at a given block
> height and it's easy to monitor. If there is sufficient interest, I would
> be happy to amend BIP8 to be height based. I originally omitted height
> based thresholds in the interests of simplicity of review - but now that
> the proposal has been widely reviewed it would be a trivial amendment.
Published at
2023-06-07 18:03:56Event JSON
{
"id": "abb5776acfa382ae132c96d7f8badfb5be8664044de139309da25a19ad818f31",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686161036,
"kind": 1,
"tags": [
[
"e",
"6dca4ce5a4efa74cb7ed37e5b09a18be6e9c403d445123c985869b2153e645a9",
"",
"root"
],
[
"e",
"5fbbdf6431b7dc5e89f4a3b407be0879f84b7b395548f1e3d19cf84061236215",
"",
"reply"
],
[
"p",
"fb7007c42a06687e3cd3fbbb1a3b17972e2a949ae679445f6b96579114d05cd9"
]
],
"content": "📅 Original date posted:2017-07-05\n📝 Original message:I've already opened a PR almost 2 weeks ago to do this and fix the other \nissues BIP 9 has. https://github.com/bitcoin/bips/pull/550\n\nIt just needs your ACK to merge.\n\n\nOn Wednesday 05 July 2017 1:30:26 AM shaolinfry via bitcoin-dev wrote:\n\u003e Some people have criticized BIP9's blocktime based thresholds arguing they\n\u003e are confusing (the first retarget after threshold). It is also vulnerable\n\u003e to miners fiddling with timestamps in a way that could prevent or delay\n\u003e activation - for example by only advancing the block timestamp by 1 second\n\u003e you would never meet the threshold (although this would come a the penalty\n\u003e of hiking the difficulty dramatically). On the other hand, the exact date\n\u003e of a height based thresholds is hard to predict a long time in advance due\n\u003e to difficulty fluctuations. However, there is certainty at a given block\n\u003e height and it's easy to monitor. If there is sufficient interest, I would\n\u003e be happy to amend BIP8 to be height based. I originally omitted height\n\u003e based thresholds in the interests of simplicity of review - but now that\n\u003e the proposal has been widely reviewed it would be a trivial amendment.",
"sig": "37c47ca8301a569e3e2cb7b577b465371a9834590f2f9a84683bd537ba7b2aaa4aa9859b87c0570ef51df716496b6446b3aec8882782cea0c0d15d719d00d5a4"
}