You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bip-paytoanchor.mediawiki
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,17 +25,17 @@ The "anchor" output type is a commonly used pattern in Bitcoin layer 2 systems s
25
25
When the wallet user is unconcerned by *who* is able to bump the transaction fees as long as someone does, this output type may confer a couple of advantages:
26
26
27
27
1. Using an output type with minimal output and spending input footprint saves fees on average
28
-
2. Keyless operation aids in interoperability of services like watchtowers as there is no privelaged key material for bumping
28
+
2. Keyless operation aids in interoperability of services like watchtowers as there is no privileged key material for bumping
29
29
30
-
with the drawback that selection of this output type could result in griefing if anti-pinning measures are not taken.
30
+
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 [bip-0431.mediawiki TRUC transactions].
31
31
32
32
===Specification===
33
33
34
34
A P2A output is defined as one with the exact witness output script
35
35
36
-
<code>OP_1 <0x4e73></code>
36
+
<code>OP_1 <0x4e73></code><ref>To be segwit it needs to be a witness version + witness program. This conforms to the smallest witness program size of two. The specific bytes cannot be zeros so they are chosen to spell "fees" in bech32m format.</ref>
37
37
38
-
corresponding to the address <code>bc1pfeessrawgf</code> on Bitcoin mainnet.
38
+
corresponding to the addresses <code>bc1pfeessrawgf</code> on Bitcoin mainnet, <code><tb1pfees9rn5nz</code> on public testnets, and <code>bcrt1pfeesnyr2tx</code> on regtest.
39
39
40
40
P2A inputs are considered standard for spending if no witness data is attached. This avoids meaningless witness padding. Consensus meaning is unchanged.
41
41
@@ -47,7 +47,7 @@ P2A inputs are considered standard for spending if no witness data is attached.
47
47
48
48
There are a number of related but separate historical concepts:
49
49
50
-
[https://github.com/bitcoin/bitcoin/pull/30239 Ephemeral Dust]: Relay policies allowing a single dust output as long as it is spent in a transaction package. As an implementation detail, dust for P2A is set at 240 satoshis by default, others dust levels remain unchanged, and the dust-having transaction must be zero fee.
50
+
[https://github.com/bitcoin/bitcoin/pull/30239 Ephemeral Dust]: Relay policies allowing a single dust output as long as it is spent in a transaction package. As an implementation detail, dust threshold for P2A is set at 240 satoshis by default, other dust levels remain unchanged, and the dust-having transaction must be zero fee. Any output script type may have down to 0-value outputs.
51
51
52
52
[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.
0 commit comments