Closed theStack closed 7 months ago
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process. | Type | Reviewers |
---|---|---|
ACK | maflcko, pablomartin4btc | |
Concept ACK | MarnixCroes, kristapsk |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
@MarnixCroes
Using the default address type (bech32) for this makes the most sense I think, instead of the latest, no?
P2TR addresses look similar enough to P2WPKH ones (with the only difference that they are longer and start with "bc1p..." rather than "bc1q..."), so I thought it's fine if use the most recent one already. No hard feelings though, I'm happy to change this if requested, it doesn't take too much effort to adapt the Python script used.
lgtm ACK c6d1b8de89d87fe4fd171dc85557299e429e6564
Concept ACK
rfm or is anything left to be done here?
Legacy addresses are less and less common these days and not recommended to use, so it seems senseful to also reflect that in the example addresses and update to the most recent address / output type (bech32m / P2TR). Also, as I couldn't see any value in computing these at runtime, they are pre-generated. This was done with the following Python script, executed in
./test/functional
(it's also included in the commit body, though without the she-bang):Note that the last bech32 character is modified in order to make the checksum fail.
master (mainnet):
PR (mainnet):