public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Aymeric Vitte <vitteaymeric@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] IsStandard
Date: Thu, 2 May 2019 16:35:06 -0700	[thread overview]
Message-ID: <CAPg+sBgDEMfeh_17q++EANOu9T4fcf49kJdi4rT8vRqQQkmdHA@mail.gmail.com> (raw)
In-Reply-To: <6b8f2a91-af73-4d66-1b90-51acd4ce217c@gmail.com>

On Thu, 2 May 2019 at 16:28, Aymeric Vitte via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Thanks for the answer, indeed for the redeem script and someone
> attempting a 0/1 of 3, good example
>
> So to summarize everything is standard as long as it matches P2PKH,
> P2SH, P2WPKH or P2WSH , the redeem scripts for the sha bounties are in
> op_return

Generally, all spends of P2SH/P2WSH is standard, with the following exceptions:
* Non-push operations in the scriptSig
* Resource limitations (too large scripts or items on the stack)
* Protections against known attack vectors (low s rule, cleanstack
rule, minimally encoded numbers rule, codesep usage, ...)
* Usage of unconditionally spendable constructions intended for future
extensions, such as spending future segwit versions.

Cheers,

-- 
Pieter


  parent reply	other threads:[~2019-05-02 23:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27 10:37 [bitcoin-dev] IsStandard 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 [this message]
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=CAPg+sBgDEMfeh_17q++EANOu9T4fcf49kJdi4rT8vRqQQkmdHA@mail.gmail.com \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=vitteaymeric@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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