From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP - Selector Script
Date: Fri, 25 Apr 2014 20:26:55 +0000 [thread overview]
Message-ID: <201404252026.56765.luke@dashjr.org> (raw)
In-Reply-To: <CAE-z3OX5_POg9kFoz-LsGhuLRA6qFPcNXoECLhewe+o-+Pw2gA@mail.gmail.com>
On Friday, April 25, 2014 8:02:41 PM Tier Nolan wrote:
> I don't think the cross chain system needs a BIP (except to justify this
> one).
>
> If cross chain transfer become popular, then it would be useful to ensure
> that clients are interoperable, but first things first. If the
> transactions aren't accepted in any chains, then everything stalls.
I think you may be misunderstanding what BIPs are. They do not force nodes to
take on any given relay/mining policy (thus, BIPs should never talk about
IsStandard at all). They define standard for interoperability between
software. So, if you want nodes to relay these transactions, you need to
convince them, not merely write a BIP for the transaction format. Defining a
BIP for cross-chain trading would be one way to do that.
> Secure transfers require that the malleability issue is fixed, but that is
> a separate issue. I am assuming that will be fixed at some point in the
> future, since micro-payment channels also requires that it is fixed.
The malleability "issue" has been known for years.
I wouldn't expect any special effort made to fix it...
> A soft fork that expands P2SH functionality would be even better, but I
> would rather not let the best be the enemy of the good.
There is some ongoing discussion of a softfork to basically redo the Script
language entirely, but it will take quite a bit of time and development before
we'll see it in the wild.
Luke
P.S. Did the BIP editor assign these numbers? If not, best to keep them
numberless until assigned, to avoid confusion when people Google the real BIP
44 and 45...
next prev parent reply other threads:[~2014-04-25 20:27 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
2014-04-25 20:02 ` Tier Nolan
2014-04-25 20:13 ` Gregory Maxwell
2014-04-25 20:26 ` Luke-Jr [this message]
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=201404252026.56765.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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