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

bip-0011/12 - fixed broken implementation url #1351

Merged
merged 2 commits into from
Sep 30, 2022

Conversation

russeree
Copy link
Contributor

Replaced the current implementation URL which gives an error 404. The new link is to the equivalent branch since the original named branch has been removed.

@russeree russeree changed the title bip-0012 - fixed broken implementation url bip-0011/12 - fixed broken implementation url Aug 13, 2022
fixed bip-0012 broken url - implementation

fixed bip-0011 broken url - implementation
@russeree russeree force-pushed the bip12-Implementation-url-fix branch from 4d9500d to df9c3fa Compare August 13, 2022 00:39
@@ -54,7 +54,7 @@ A weaker argument is OP_CHECKMULTISIG should not be used because it pops one too

OP_CHECKMULTISIG is already supported by old clients and miners as a non-standard transaction type.

https://github.com/gavinandresen/bitcoin-git/tree/op_eval
https://github.com/gavinandresen/bitcoin-git/tree/e679ec969c8b22c676ebb10bea1038f6c8f13b33
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an old commit. Why not the most recent 77f21f1583deb89bf3fffe80fe9b181fedb1dd60?

Or perhaps link https://github.com/bitcoin/bitcoin/pull/669/files ?

Copy link
Contributor Author

@russeree russeree Sep 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated Commit

Ack'd to fixing with the more modern commit.

The reason I chose the commit was it was referenced as the OP_EVAL implementation by Gavin Andresen in bip11/12 and would match the branch at the time the BIP was submitted. Though yours is newer and would represent the final state of the branch before the branch was removed.

My method to determine the location of the deleted branch was to run
git log --all --full-history -- "**op_eval*"

The result provided this as well as your commit linked.

image

In regards to the "Or perhaps".

I feel this would be the most appropriate solution for the brokens links as it was the entire merged implementation of the code changes, but isn't Gavin Andresen original 'implementation'.

Advantages to this method

  • Actual implementation into BitcoinQt is clear.
  • Preserved as a part of the bitcoin/bitcoin repo.

Disadvantages to this method

  • Doesn't wholly represent the BIP authors implementation.

Closing statement.

I would like to implement it as a link to Gavins implementation as to preserve the original BIP as much as possible.

If you would like to use the link to the OP_EVAL and merge into bitcoin/bitcoin I can do that as well. Please let me know which fix you would like and I will implement immediately.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure there was a distinction between the "original" and the final version in this sense - BIPs typically get updated as the proposal changes.

But ultimately, it's a question of what @gavinandresen will ACK here.

@gavinandresen
Copy link
Contributor

ACK.

(but I'm retired, so please stop mentioning me and just use common sense from now on)

@luke-jr luke-jr merged commit 6545b81 into bitcoin:master Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants