From: "Jorge Timón" <jtimon@jtimon•cc>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Fwd: Re: [RFC] Canonical input and output ordering in transactions
Date: Sun, 21 Jun 2015 09:27:33 +0200 [thread overview]
Message-ID: <CABm2gDoq-nxqGYkYVh0YJQ8p5noLMKrEGuvJmRXU9FYs42ma2g@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDpkwHvrsB8Dh-hsO6H9trcweEX9XGB5Jh5KLPsPY5Z1Sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
---------- Forwarded message ----------
From: "Jorge Timón" <jtimon@jtimon•cc>
Date: Jun 17, 2015 6:59 PM
Subject: Re: [Bitcoin-development] [RFC] Canonical input and output
ordering in transactions
To: "Rusty Russell" <rusty@rustcorp•com.au>
Cc:
On Tue, Jun 16, 2015 at 10:06 AM, Rusty Russell <rusty@rustcorp•com.au>
wrote:
> Jorge Timón <jtimon@jtimon•cc> writes:
>> On Jun 15, 2015 11:43 PM, "Rusty Russell" <rusty@rustcorp•com.au> wrote:
>>
>>> Though Peter Todd's more general best-effort language might make more
>>> sense. It's not like you can hide an OP_RETURN transaction to make it
>>> look like something else, so that transaction not going to be
>>> distinguished by non-canonical ordering.
>>
>> What about commitments that don't use op_return (ie pay2contract
>> commitments)?
>
> I have no idea what they are? :)
Here's a short explanation and the code:
https://github.com/Blockstream/contracthashtool
Here's a longer explanation with a concrete use case (the contract is
the invoice):
https://www.youtube.com/watch?v=qwyALGlG33Q
> Yes, my plan B would be an informational bip with simple code,
> suggesting a way to permute a transaction based on some secret. No
> point everyone reinventing the wheel, badly.
Great. Well, then all I'm saying is that I like this as plan A.
[-- Attachment #2: Type: text/html, Size: 2002 bytes --]
next prev parent reply other threads:[~2015-06-21 7:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 4:42 [Bitcoin-development] " Rusty Russell
2015-06-06 4:46 ` Mark Friedenbach
2015-06-06 6:44 ` Rusty Russell
2015-06-06 8:24 ` Wladimir J. van der Laan
2015-06-06 9:45 ` Mark Friedenbach
2015-06-08 21:25 ` Danny Thorpe
2015-06-08 21:36 ` Peter Todd
2015-06-14 23:04 ` Gregory Maxwell
2015-06-14 23:02 ` Gregory Maxwell
2015-06-15 2:29 ` Rusty Russell
2015-06-15 2:33 ` Gregory Maxwell
2015-06-15 2:47 ` Mark Friedenbach
2015-06-15 21:01 ` Rusty Russell
2015-06-16 7:10 ` Jorge Timón
2015-06-16 8:06 ` Rusty Russell
[not found] ` <CABm2gDpkwHvrsB8Dh-hsO6H9trcweEX9XGB5Jh5KLPsPY5Z1Sw@mail.gmail.com>
2015-06-21 7:27 ` Jorge Timón [this message]
2015-06-15 4:01 ` Kristov Atlas
2015-06-24 22:09 ` [bitcoin-dev] " Kristov Atlas
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=CABm2gDoq-nxqGYkYVh0YJQ8p5noLMKrEGuvJmRXU9FYs42ma2g@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--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