From: Marco Falke <falke.marco@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] IsStandard
Date: Mon, 29 Apr 2019 13:27:29 -0400 [thread overview]
Message-ID: <CAK51vgCaGnS3Ha9OYF48BSVdzN8SBRjzjkhXBKGNeOUMukkg4g@mail.gmail.com> (raw)
In-Reply-To: <21346b3c-dad5-c666-9234-8916aa5a56e4@gmail.com>
There is not a single document that describes what is standard and
what is not. Transaction relay policy (including minimum relay fees)
may change over time, across different implementations or different
versions of the same implementation.
Generally you can assume that commonly used scripts that are standard
today remain standard. To test if a script is standard and accepted by
current relay policy of a Bitcoin Core node, you can create a tx that
spends from it on mainnet or on testnet and see if it is accepted to
the mempool of your local node. Make sure to disable
-acceptnonstdtxn=0 on testnet.
Should the standardness-rules of a script type ever change, it will be
announced and discussed on this mailing list.
And of course, lightning transactions are standard as they otherwise
wouldn't propagate.
Best,
Marco
On Sun, Apr 28, 2019 at 9:06 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
prev parent reply other threads:[~2019-04-29 17:27 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
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 [this message]
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=CAK51vgCaGnS3Ha9OYF48BSVdzN8SBRjzjkhXBKGNeOUMukkg4g@mail.gmail.com \
--to=falke.marco@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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