From: Tier Nolan <tier.nolan@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Selector Script
Date: Fri, 25 Apr 2014 21:05:02 +0100 [thread overview]
Message-ID: <CAE-z3OVxf3GCeL21aVm2svSD=Dr=2gvVbEAZ2ve3F9GQGfSMFw@mail.gmail.com> (raw)
In-Reply-To: <20140425195838.GA3965@savin>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Fri, Apr 25, 2014 at 8:58 PM, Peter Todd <pete@petertodd•org> wrote:
> Keep in mind that P2SH redeemScripts are limited to just 520 bytes;
> there's going to be many cases where more complex transactions just
> can't be encoded in P2SH at all.
>
True. Having said that, this is just a change to isStandard(), rather than
a protocol change.
These transactions can already be mined into blocks.
> --
> 'peter'[:-1]@petertodd.org
> 00000000000000006407c80d5d4506a4253b4b426e0c7702963f8bf91e7971aa
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 1965 bytes --]
next prev parent reply other threads:[~2014-04-25 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 Tier Nolan
2014-04-25 19:17 ` Luke-Jr
2014-04-25 19:58 ` Peter Todd
2014-04-25 20:05 ` Tier Nolan [this message]
2014-04-25 20:02 ` Tier Nolan
2014-04-25 20:13 ` Gregory Maxwell
2014-04-25 20:26 ` Luke-Jr
2014-04-25 20:48 ` Tier Nolan
2014-04-26 17:00 ` Mark Friedenbach
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='CAE-z3OVxf3GCeL21aVm2svSD=Dr=2gvVbEAZ2ve3F9GQGfSMFw@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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