summaryrefslogtreecommitdiff
path: root/bip-0325.mediawiki
diff options
context:
space:
mode:
authorLuke Dashjr <luke_github1@dashjr.org>2020-10-05 16:18:24 +0000
committerGitHub <noreply@github.com>2020-10-05 16:18:24 +0000
commitc4c407710591a49d4113237eea622b0aa21cc304 (patch)
tree83049cb2fab34b06e244747dede6be352889525e /bip-0325.mediawiki
parent80d4cb82bb900f548cfe402a7843b590c36c5db9 (diff)
parentff2833e6d6768a3423007b532b671e911b4b608d (diff)
downloadbips-c4c407710591a49d4113237eea622b0aa21cc304.tar.xz
Merge pull request #978 from MarcoFalke/patch-1
BIP 325: Clarify that scriptWitness is a stack, not a byte string
Diffstat (limited to 'bip-0325.mediawiki')
-rw-r--r--bip-0325.mediawiki3
1 files changed, 1 insertions, 2 deletions
diff --git a/bip-0325.mediawiki b/bip-0325.mediawiki
index 4b45030..e1e2773 100644
--- a/bip-0325.mediawiki
+++ b/bip-0325.mediawiki
@@ -21,7 +21,6 @@ Testnet is a great place to try out new things without risking real money, but i
A new type of test network would be more suitable for integration testing by organizations such as exchanges, or testing of next generation Layer-2 protocols like Eltoo or sidechain pegs. The goal is not to be perfectly reliable but rather to have a predictable amount of unreliability. You want a test network to behave like mainnet (i.e. no thousands of block reorgs) while also making it easier to trigger expected but rare events like a 6-block reorg. Regtest is not suitable for longer-term scenarios involving multiple independent parties because creating blocks costs nothing, so any party can completely control the test network.
-
== Specification ==
A new type of network ("signet"), which takes an additional consensus parameter called the challenge (scriptPubKey). The challenge can be a simple pubkey (P2PKH style), or a k-of-n multisig, or any other script you would want.
@@ -33,7 +32,7 @@ The witness commitment of the coinbase transaction is extended to include a seco
x bytes - scriptSig
y bytes - scriptWitness
-The scriptSig is serialized by first encoding its length as CompactSize. If the scriptWitness is empty, it is encoded as 0 bytes, otherwise it is encoded in the usual way (see BIP 141 "witness" encoding).
+The scriptSig is serialized by first encoding its length as CompactSize. The scriptWitness stack is serialized as described in BIP 141.
Any push operations that do not start with the 4 byte Signet header are ignored. Multiple push operations with the 4 byte Signet header are ignored except for the first instance of the header.