Skip to content

Conversation

@instagibbs
Copy link
Member

For interoperability with other schemes, it behooves me to write a BIP for this output type. It's already standard to spend in well over half the network.

h/t roasbeef for bothering me about this repeatedly

Copy link
Member

@jonatack jonatack left a comment

Choose a reason for hiding this comment

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

Quick first pass.


====Backward Compatibility====

Creation of P2A outputs has been considered standard since the deployment of Segwit softfork on the network.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe link here to the SegWit BIP section making them standard.

Copy link
Member Author

Choose a reason for hiding this comment

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

the BIPs aren't standardness BIPs, so I'm not sure that helps.

Copy link
Contributor

Choose a reason for hiding this comment

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

I’m not sure if the segwit BIPs (141–144) mentioned it, but BIP 173 (Bech32) states that “implementations MUST allow the use of any version”. And that recommendation is repeated in BIP 350 (bech32m), which mentions it in the Implementation advice for test vectors.

Copy link
Contributor

@Roasbeef Roasbeef 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 making this. Nearly done with an implementation for btcsuite.

Copy link
Contributor

@murchandamus murchandamus left a comment

Choose a reason for hiding this comment

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

Looks pretty good already. I got a bag of nits for you.


====Backward Compatibility====

Creation of P2A outputs has been considered standard since the deployment of Segwit softfork on the network.
Copy link
Contributor

Choose a reason for hiding this comment

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

I’m not sure if the segwit BIPs (141–144) mentioned it, but BIP 173 (Bech32) states that “implementations MUST allow the use of any version”. And that recommendation is repeated in BIP 350 (bech32m), which mentions it in the Implementation advice for test vectors.

@Roasbeef
Copy link
Contributor

Roasbeef commented Dec 9, 2025

This BIP has been assigned number 433!

(can update the readme in the PR to reflect assignment)

@Roasbeef Roasbeef changed the title Add P2A BIP BIP 433: Add P2A BIP Dec 9, 2025
@murchandamus
Copy link
Contributor

Please add an entry to the table in the README.md for your BIP, add the number to the preamble, and update the “Created” header to 2025-12-08.

@instagibbs instagibbs force-pushed the 2025-09-p2a branch 2 times, most recently from 7ab1a16 to 3afec38 Compare December 9, 2025 16:05
@instagibbs
Copy link
Member Author

Thanks for the review and number!

Copy link
Contributor

@murchandamus murchandamus left a comment

Choose a reason for hiding this comment

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

Changes look good to me. ACK ab9bc69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants