BIP 19 low-SigOp multisignature explained as a closed alternative using CHECKSIG operations, including policy limits, custody risks and replacements.
This guide explains BIP 19 M-of-N Standard Transactions (Low SigOp) in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 19 M-of-N Standard Transactions (Low SigOp): For an N-of-N policy, each public key was followed by CHECKSIGVERIFY, requiring every signature to pass in sequence.
A node operator is checking BIP 19 M-of-N Standard Transactions (Low SigOp). At the time, CHECKMULTISIG could be conservatively charged as twenty sigops, sharply limiting transaction density.
Bitcoin limits signature operations per block to bound validation cost. At the time, CHECKMULTISIG could be conservatively charged as twenty sigops, sharply limiting transaction density. BIP 19 explored equivalent small quorum policies composed from individually counted CHECKSIG operations to make the accounting closer to the actual number of keys.
For an N-of-N policy, each public key was followed by CHECKSIGVERIFY, requiring every signature to pass in sequence. Failure stopped execution immediately. The simple shape reduced sigop overcounting but exposed every public key and produced a non-standard construction that wallets still had to coordinate correctly.
The proposed M-of-N form evaluated signatures against public keys, used SWAP to arrange stack items, added the Boolean results and compared the total with the threshold. Stack order and signature matching were consensus execution details, not explanatory notation. A missing or reordered item could invalidate an otherwise intended quorum.
The templates were limited to small key counts and accompanied by a larger standard scriptSig allowance. Existing nodes could evaluate the opcodes as consensus-valid script, yet old relay and mining policy would not treat the construction as standard. Broadcast reliability therefore depended on adoption beyond raw script validity.
The BIP discussed wallet protection services and buyer-seller-agent escrow. Those examples assume communication, identity, backups and dispute processes outside Script. A two-of-two service can strand funds when the provider disappears unless the user retains a tested recovery route; a two-of-three escrow is only as fair as its key and evidence procedures.
BIP 11 standardised small bare CHECKMULTISIG, P2SH improved sender usability, and later SegWit and Taproot constructions changed weight and privacy options. Descriptors and PSBT now coordinate policies more reliably. BIP 19 remains a useful resource-accounting experiment rather than a maintained wallet target.
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
BIP 19 M-of-N Standard Transactions (Low SigOp): For an N-of-N policy, each public key was followed by CHECKSIGVERIFY, requiring every signature to pass in sequence.
Bitcoin limits signature operations per block to bound validation cost. At the time, CHECKMULTISIG could be conservatively charged as twenty sigops, sharply limiting transaction density.
For an N-of-N policy, each public key was followed by CHECKSIGVERIFY, requiring every signature to pass in sequence.
The proposed M-of-N form evaluated signatures against public keys, used SWAP to arrange stack items, added the Boolean results and compared the total with the threshold.
BIP 19 explored a clever way to reduce multisignature sigop cost with existing opcodes, but it closed without becoming the modern standard. Current custody should use maintained descriptor and PSBT workflows with explicit recovery controls.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
BIP 450 guide to Draft Formosa themed mnemonic stories, entropy and checksum mapping, theme JSON, BIP39 conversion, passphrases and recovery safety.
BIP 393 guide to Draft descriptor annotations for birth height, gap limit and Silent Payment max label, checksum rules, parsing and recovery safety.
BIP 392 guide to Draft sp() descriptors, spscan and spspend encodings, watch-only and full-wallet forms, key origins, recovery and validation.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.