Skip to content

Conversation

@gpatkinson
Copy link
Contributor

Great website. I thought that some people would benefit from more introductory words on bitcoin script so added a few more pages to that section. I also made a few minor organizational changes that just made sense to me. Thanks for considering.

@netlify
Copy link

netlify bot commented Nov 24, 2023

Deploy Preview for timely-chimera-eba3bb ready!

Name Link
🔨 Latest commit 3a77a90
🔍 Latest deploy log https://app.netlify.com/sites/timely-chimera-eba3bb/deploys/656e0b1ab3bf4d00085e9a66
😎 Deploy Preview https://deploy-preview-9--timely-chimera-eba3bb.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.


These script types are used together in transaction validation:

>Every bitcoin validating node will validate transactions by executing the locking and unlocking scripts together. Each input contains an unlocking script and refers to a previously existing UTXO. The validation software will copy the unlocking script, retrieve the UTXO referenced by the input, and copy the locking script from that UTXO. The unlocking and locking script are then executed in sequence. The input is valid if the unlocking script satisfies the locking script conditions ... All the inputs are validated independently, as part of the overall validation of the transaction.
Copy link
Contributor

Choose a reason for hiding this comment

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

The terminology "locking script" and "unlocking script" is not recommended anymore, according to Murch's proposed terminology BIP (see "Locking Script and Unlocking Script").

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, good point. I'll update it.

@thunderbiscuit
Copy link
Owner

Hey thanks for the kind words! This PR will now need a rebase, and I left some comments below. Thanks for contributing!

Copy link
Owner

@thunderbiscuit thunderbiscuit left a comment

Choose a reason for hiding this comment

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

Hey thanks for the hard work! I left some comments. Happy to see people interested in the project enough to spend time contributing to it. Cheers!

Copy link
Contributor Author

@gpatkinson gpatkinson left a comment

Choose a reason for hiding this comment

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

I've made all the requested changes, thanks for your feedback.

Copy link
Contributor Author

@gpatkinson gpatkinson left a comment

Choose a reason for hiding this comment

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

All suggestions implemented.

Copy link
Contributor Author

@gpatkinson gpatkinson left a comment

Choose a reason for hiding this comment

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

All set. Ended up removing tx_validation.md for now per @vostrnad recs, will try again in a future PR

Copy link
Contributor Author

@gpatkinson gpatkinson left a comment

Choose a reason for hiding this comment

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

completed.

Copy link
Contributor Author

@gpatkinson gpatkinson left a comment

Choose a reason for hiding this comment

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

removed.

Copy link
Owner

@thunderbiscuit thunderbiscuit left a comment

Choose a reason for hiding this comment

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

Thanks for the hard work! This is getting ready to merge, but I'd need a squash of all these commits into one (maybe two if you really wanted to separate the small syntax fixes from the new page addition).

Would you like to do this yourself? Otherwise I'm happy to do it and merge today.

@gpatkinson
Copy link
Contributor Author

Thank you! Honored to be a part of this. As I'm sure you've noticed, I'm pretty new to GitHub collaboration (though I've used Git for a while). I'm happy to try this commit compression but I feel like I'm usually just stumbling around this GUI--if it's not too much trouble, I'd appreciate your help to make sure I don't botch something and further slow the merge. :)

@thunderbiscuit
Copy link
Owner

Hey no problem! Always happy to help. In this case what I'll be using is

  1. an interactive rebase to squash all your commits into one. If you're using git from the command line this is the article I like to refer people to: https://thoughtbot.com/blog/git-interactive-rebase-squash-amend-rewriting-history
  2. a rebase of that commit onto master

Just a tip: one thing that might give you trouble now is that you have made these commits on your master branch, but I'm rewriting history and merging that to mine. So now your master is off. An easy way to avoid that is to develop your PRs on new branches that don't affect your master.

Cheers!

@thunderbiscuit thunderbiscuit merged commit 3a77a90 into thunderbiscuit:master Dec 4, 2023
@gpatkinson
Copy link
Contributor Author

Thanks, I really appreciate it

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

Successfully merging this pull request may close these issues.

3 participants