From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net,
Amir Taaki <zgenjix@yahoo•com>
Subject: Re: [Bitcoin-development] BIP 16 changes (list inside)
Date: Sun, 18 Mar 2012 14:11:48 -0400 [thread overview]
Message-ID: <201203181411.49361.luke@dashjr.org> (raw)
In-Reply-To: <1332079467.53650.YahooMailNeo@web121003.mail.ne1.yahoo.com>
On Sunday, March 18, 2012 10:04:27 AM Amir Taaki wrote:
> Is this an accurate and precise summary of the changes needed for P2SH and
> BIP 16?
You might find my 0.4.x backport helpful:
https://github.com/luke-jr/bitcoin/commit/bip16_0.4.x
Be aware, this still needs auditing (nobody else has looked it over), but I
believe should cover only the minimal changes required to get P2SH validation
(though not the "standard" rule changes to accept them into blocks).
prev parent reply other threads:[~2012-03-18 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 14:04 Amir Taaki
2012-03-18 18:11 ` Luke-Jr [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=201203181411.49361.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(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