[Bitcoin-development] BIP - Selector Script

Luke-Jr luke at dashjr.org
Fri Apr 25 20:26:55 UTC 2014

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.


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...

More information about the bitcoin-dev mailing list