Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing fork with activation date example #31

Open
Giszmo opened this issue Nov 7, 2024 · 0 comments
Open

Confusing fork with activation date example #31

Giszmo opened this issue Nov 7, 2024 · 0 comments

Comments

@Giszmo
Copy link
Contributor

Giszmo commented Nov 7, 2024

Early proposals such as BIP16 Pay to Script Hash (P2SH) used a predetermined Flag Day to activate on the network. P2SH was activated on April 1, 2012 at block 173,805. Following the activation there were reports that some Miners who failed to update from 0.6.0 rc1 were stuck at block 170,060.

How were Miners stuck on an earlier block for lack of updating? Did the updated miners fork on the earlier block? Also it should read "nodes" and not "Miners" as problems syncing the blockchain isn't exclusive to miners.

I did not read all the linked information but it doesn't look like a normal thing that would happen with this kind of fork activation. Especially Gavin's closing remark "If there are any Berkeley DB database experts reading this we could use your help figuring out what the heck is going on..." looks like this is not the most informative link for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant