Quote from: edmundedgar on May 08, 2014, 11:32:08 AM

What do we reckon is the next move to get this stuff accepted? The cross-chain stuff is really important, and it seems a shame to be kludging around the oracle branching use-cases with multiple transactions or by torturing ECDSA keys in all kinds of unmentionable ways.

I have managed to get it down to 1 non-standard tx. This means that you can trade between 2 coins if at least one of them accepts non-standard transactions.

In theory, testnet coins could have value, just as an intermediary. More likely, an altcoin would see it as a marketing opportunity.

Even accepting

OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG

would be enough.

That seems pretty low risk to me.

I think the 2 drafts have spurred some discussions. Parhaps isStandard() could have a whitelist of opcodes added.

On the other hand, I think adding the hash-locking template immediately and then looking into changes to isStandard() strategy would be best. Optimistically, the change would be in the release after the next one. Disccusions about isStandard() strategy would take longer than checking one new template.