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.

Sign up for GitHub

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

Add discussion question for bech32 mutability #24

Closed
wants to merge 1 commit into from
Closed

Add discussion question for bech32 mutability #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions segwit/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,3 +33,4 @@
1. How did users know whether miners support SegWit prior to activation?
1. How does a (virtual block increase) affect IBD cost over time?
1. Where are the locking script operations in P2WPKH/P2WSH?
1. What are some address format design goals and requirements discussed in the bech32 talk? How problematic is the [bech32 mutability](https://bitcoinops.org/en/newsletters/2019/12/28/#bech32-mutability) issue for v0 segwit addresses versus for taproot?
Copy link
Member

Choose a reason for hiding this comment

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

  1. This refers to an optional resource, so not sure how to indicate this question is only for those that watched the video.

  2. I think the optech link should go in the answers file otherwise it just becomes another thing to read beforehand.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Could put [optional] on it? and move the optech link to answers.md, yeah