public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Hash Locked Transaction
Date: Fri, 25 Apr 2014 22:52:01 +0100	[thread overview]
Message-ID: <CAE-z3OUM6_+qtxzcLg1FkUe8jxCLnJDya=eH9O5+LY_KRrhZpg@mail.gmail.com> (raw)
In-Reply-To: <20140425211426.GD8994@savin>

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

On Fri, Apr 25, 2014 at 10:14 PM, Peter Todd <pete@petertodd•org> wrote:

> Along those lines, rather than doing up yet another format specific type
> as Tier Nolan is doing with his BIP, why not write a BIP looking at how
> the IsStandard() rules could be removed?


Removal of isStandard() would be even better/more flexible.

A whitelist of low risk opcodes seems like a reasonable compromise.

My thoughts behind these two BIPs are that they are a smaller change that
adds functionality required for a particular use-case (and some others).

Changing the entire philosophy behind isStandard() is a much bigger change
than just adding one new type.

[-- Attachment #2: Type: text/html, Size: 1025 bytes --]

  reply	other threads:[~2014-04-25 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 18:49 Tier Nolan
2014-04-25 19:18 ` Luke-Jr
2014-04-25 19:37   ` Tier Nolan
2014-04-25 20:06 ` Alex Mizrahi
2014-04-25 20:14   ` Peter Todd
2014-04-25 20:19     ` Gregory Maxwell
2014-04-25 21:14       ` Peter Todd
2014-04-25 21:52         ` Tier Nolan [this message]
2014-04-26 11:11           ` Jorge Timón
2014-04-26 11:31             ` Tier Nolan

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-z3OUM6_+qtxzcLg1FkUe8jxCLnJDya=eH9O5+LY_KRrhZpg@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