Skip to content

Commit 6206b4c

Browse files
committed
updates
1 parent 490aa62 commit 6206b4c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

bip-paytoanchor.mediawiki

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,17 +25,17 @@ The "anchor" output type is a commonly used pattern in Bitcoin layer 2 systems s
2525
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:
2626

2727
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
2929

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].
3131

3232
===Specification===
3333

3434
A P2A output is defined as one with the exact witness output script
3535

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>
3737

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.
3939

4040
P2A inputs are considered standard for spending if no witness data is attached. This avoids meaningless witness padding. Consensus meaning is unchanged.
4141

@@ -47,7 +47,7 @@ P2A inputs are considered standard for spending if no witness data is attached.
4747

4848
There are a number of related but separate historical concepts:
4949

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.
5151

5252
[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.
5353

0 commit comments

Comments
 (0)