From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Aymeric Vitte <vitteaymeric@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] IsStandard
Date: Mon, 29 Apr 2019 01:46:35 +0000 [thread overview]
Message-ID: <NvaqlAYJTXaCBdFqlgaJdky81FfhEG5Q8r6gWnkoYGpp4_dWfYzU3OsZkAOWbFQ947n8ahnMQz_ZM1u7fL6j2GnuJmJ4i9alsJVjCzw7jqY=@protonmail.com> (raw)
In-Reply-To: <21346b3c-dad5-c666-9234-8916aa5a56e4@gmail.com>
Good morning Aymeric,
Different versions may consider different output scripts standard.
Your rule of thumb, post-SegWit, should be:
* If not P2PKH or P2WPKH, then wrap it in a P2SH or P2WSH.
There are more standard outputs accepted, but you can be reasonably sure that P2PKH, P2WPKH, P2SH, and P2WSH are the only standard output scripts that are likely to remain supported in the mid-future (5->10 years from 2019).
Lightning uses P2WSH for its scripts.
Any m-of-n signing scheme in Bitcoin is P2SH (usually) or P2WSH (if you are cool).
Regards,
ZmnSCPxj
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, April 27, 2019 6:37 PM, Aymeric Vitte via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Maybe trivial question but asking here because I can't find anything
> clear (or updated) about it: is somewhere explained in details what txs
> are considered standard and non standard today without having to read
> the core code?
>
> For example, modification of multisig 2 of 3:
>
> scriptSig:
> OP_0
> OP_PUSHDATA sign1
> OP_PUSHDATA sign2
> OP_2
> OP_PUSHDATA <pubkey1><pubkey2><pubkey3> OP_3 OP_CHECKMULTISIG
>
> scriptPubKey:
> OP_HASH160 hash160(<pubkey1><pubkey2><pubkey3> OP_3
> OP_CHECKMULTISIG) OP_EQUAL
>
> Is this standard? Are lightning txs standards ? etc
>
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2019-04-29 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 10:37 Aymeric Vitte
2019-04-29 1:46 ` ZmnSCPxj [this message]
2019-04-29 3:01 ` Luke Dashjr
2019-04-29 9:30 ` Aymeric Vitte
2019-04-30 4:29 ` ZmnSCPxj
2019-04-30 9:43 ` Aymeric Vitte
2019-05-02 0:10 ` ZmnSCPxj
2019-05-02 10:01 ` Aymeric Vitte
2019-05-02 23:33 ` James Prestwich
2019-05-03 9:51 ` Aymeric Vitte
2019-05-02 23:35 ` Pieter Wuille
2019-04-29 17:27 ` Marco Falke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='NvaqlAYJTXaCBdFqlgaJdky81FfhEG5Q8r6gWnkoYGpp4_dWfYzU3OsZkAOWbFQ947n8ahnMQz_ZM1u7fL6j2GnuJmJ4i9alsJVjCzw7jqY=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vitteaymeric@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox