bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2026-09-21 19:04:28 +00:00
Code Issues Releases Wiki Activity

bip-433: fix heading levels, stray '<', typos, add Copyright section

Browse Source 
- Specification was a level-3 heading and therefore rendered as a
  subsection of Motivation; Backward Compatibility, Implementation and
  Related Work were one level too deep as well.
- Drop the stray '<' in front of the testnet address tb1pfees9rn5nz.
- 'typea' -> 'type', 'ineherent' -> 'inherent'.
- Add the Copyright section required by BIP 3, matching the
  BSD-3-Clause License header.
This commit is contained in:
Kanan
2026-09-13 20:17:47 +04:00
parent bfc142f2b5
commit e2e7a03d69
1 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
bip-0433.mediawiki
View File

@@ -15,7 +15,7 @@
This document describes a new standard output script called Pay to Anchor (P2A) and prescribes making spending of this output type standard.
This output is "keyless" meaning no signature or witness data at all are required to spend this output typea.
This output is "keyless" meaning no signature or witness data at all are required to spend this output type.
==Motivation==
@@ -28,21 +28,21 @@ When the wallet user is unconcerned by *who* is able to bump the transaction fee
with the drawback that selection of this output type could result in griefing if anti-pinning measures are not taken. If unsure, use in conjunction with [https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki TRUC transactions].
===Specification===
==Specification==
A P2A output is defined as one with the scriptPubKey
<code>OP_1 <0x4e73></code><ref>Native segwit outputs are composed of a witness version and a witness program. A witness program must be at least two bytes long and the specific bytes cannot be zeros. The two bytes for the P2A witness program are chosen to spell "fees" in bech32m encoding.</ref>
corresponding to the addresses <code>bc1pfeessrawgf</code> on Bitcoin mainnet, <code><tb1pfees9rn5nz</code> on public testnets, and <code>bcrt1pfeesnyr2tx</code> on regtest.
corresponding to the addresses <code>bc1pfeessrawgf</code> on Bitcoin mainnet, <code>tb1pfees9rn5nz</code> on public testnets, and <code>bcrt1pfeesnyr2tx</code> on regtest.
P2A inputs are considered standard by Bitcoin Core for spending if no witness data is attached. This avoids meaningless witness padding. Consensus meaning is unchanged.
====Implementation====
===Implementation===
* https://github.com/bitcoin/bitcoin/pull/30352
====Related Work====
===Related Work===
There are a number of related but separate historical concepts:
@@ -50,9 +50,9 @@ There are a number of related but separate historical concepts:
[https://bitcoinops.org/en/topics/ephemeral-anchors/ Ephemeral Anchors]: Historically the union of P2A output type and ephemeral dust. Keyed anchors along with ephemeral dust are also an accepted pattern and as such they remain separate concepts.
[https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki TRUC transactions]: TRUC transactions bound the topology including child transaction size, which aids in anti-pinning for the P2A output, as anyone can attach a child transaction including an oversized, low feerate one. There is no ineherent dependency on this concept and P2A.
[https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki TRUC transactions]: TRUC transactions bound the topology including child transaction size, which aids in anti-pinning for the P2A output, as anyone can attach a child transaction including an oversized, low feerate one. There is no inherent dependency on this concept and P2A.
====Backward Compatibility====
==Backward Compatibility==
Creation of P2A outputs has been considered standard since the deployment of Segwit softfork on the network.
@@ -73,3 +73,7 @@ and Bastien Teinturier.
<references/>
==Copyright==
This document is licensed under the 3-clause BSD license.