wiki commit

2020-01-02 11:04:10 -05:00
parent 621be6eb86
commit e4e2e990e1
2 changed files with 4 additions and 2 deletions
@@ -12,8 +12,10 @@ Standard transactions are those that:
 - Have input scripts that only contain push operations
 - Have input scripts with unlocking scripts below the 1650 byte maximum
 - Have at most one [data output](/protocol/blockchain/transaction/locking-script#Data%20Output)
+ - For [multisig](/protocol/blockchain/transaction/locking-script#Multisig) outputs, must have at most 3 parties and at least 1 required party (i.e. 1-of-1 through 3-of-3).
 - Have non-data outputs with amount above the [dust](#dust) threshold

 Be aware, however, that these rules may vary from node-to-node as they are often configurable.  Some nodes may also accept and relay non-standard transactions.  For this reason, among others, it is always wise to send transactions to multiple nodes.

 ### Dust
+
@@ -84,7 +84,7 @@ One drawback of this is that it is not possible to determine whether certain ins
 This makes retirement of opcodes impossible.
 However, it's also possible for people to create transactions and not commit them to the blockchain, so the viability of opcode retirement is questionable anyway.

-### Multisig Script
+### Multisig

 Multiple-signature, or multisig, scripts provide a mechanism to have multiple private keys coordinate with spending funds.
 For example, three people could share funds and require that for some transactions any one of them could spend it while, for others, two of them would need to agree, and for others still, all three people would need to agree to spend the funds.