diff options
| author | Tier Nolan <tier.nolan@gmail.com> | 2014-04-25 19:49:37 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-25 18:49:48 +0000 |
| commit | 7a19cd5df691bcde7944bccae111b520b53b6b78 (patch) | |
| tree | abe3fa77b302fc9805afecb613d74dcc05106fd8 | |
| parent | 32fcd67bb455bdb0c722df5fd76c21903b3428fa (diff) | |
| download | pi-bitcoindev-7a19cd5df691bcde7944bccae111b520b53b6b78.tar.gz pi-bitcoindev-7a19cd5df691bcde7944bccae111b520b53b6b78.zip | |
[Bitcoin-development] BIP - Hash Locked Transaction
| -rw-r--r-- | 44/07bbb39af3881165cc4e943a90e6311d43de30 | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/44/07bbb39af3881165cc4e943a90e6311d43de30 b/44/07bbb39af3881165cc4e943a90e6311d43de30 new file mode 100644 index 000000000..8d10504a5 --- /dev/null +++ b/44/07bbb39af3881165cc4e943a90e6311d43de30 @@ -0,0 +1,125 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <tier.nolan@gmail.com>) id 1WdlC0-0002zH-Ir + for bitcoin-development@lists.sourceforge.net; + Fri, 25 Apr 2014 18:49:48 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.216.54 as permitted sender) + client-ip=209.85.216.54; envelope-from=tier.nolan@gmail.com; + helo=mail-qa0-f54.google.com; +Received: from mail-qa0-f54.google.com ([209.85.216.54]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WdlBu-0002j8-Ni + for bitcoin-development@lists.sourceforge.net; + Fri, 25 Apr 2014 18:49:48 +0000 +Received: by mail-qa0-f54.google.com with SMTP id w8so3992931qac.13 + for <bitcoin-development@lists.sourceforge.net>; + Fri, 25 Apr 2014 11:49:37 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.140.48.13 with SMTP id n13mr13304660qga.90.1398451777200; + Fri, 25 Apr 2014 11:49:37 -0700 (PDT) +Received: by 10.140.25.86 with HTTP; Fri, 25 Apr 2014 11:49:37 -0700 (PDT) +Date: Fri, 25 Apr 2014 19:49:37 +0100 +Message-ID: <CAE-z3OVsQAya3RDzMTvKNK4hLGQVjFOp6Bseo=xK4ApOdPCh8g@mail.gmail.com> +From: Tier Nolan <tier.nolan@gmail.com> +To: Bitcoin Development <bitcoin-development@lists.sourceforge.net> +Content-Type: multipart/alternative; boundary=001a11351cce6a65b004f7e26da1 +X-Spam-Score: -0.6 (/) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (tier.nolan[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-Headers-End: 1WdlBu-0002j8-Ni +Subject: [Bitcoin-development] BIP - Hash Locked Transaction +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Fri, 25 Apr 2014 18:49:48 -0000 + +--001a11351cce6a65b004f7e26da1 +Content-Type: text/plain; charset=UTF-8 + +As part of the atomic cross chain system, outputs need to be hash locked. + +https://github.com/TierNolan/bips/blob/bip4x/bip-0045.mediawiki + +https://bitcointalk.org/index.php?topic=193281.msg2224949#msg2224949 + +A user needs to provide x corresponding to hash(x) in order to spend an +output. + +Under the protocol, one of the participants is required to provide the +secret number in order to spend an output. Once they do that, the other +participant can use the secret number to spend an output on the other +chain. This provides a mechanism to link the 2 chains together (in +addition to lock times). Once the first output is spent, that commits the +transfer. + +This is half of the scripting operations required to implement the protocol. + +The proposal is to make this an adder on to the other standard +transactions. It does a check that the hash matches, and then runs the +standard transaction as normal. + +Adding the prefix to a P2SH transactions wouldn't work, since the template +wouldn't match. + +A script of this form could be embedded into a P2SH output. + +I think that is ok, since embedding the "password" in the hashed script +gets all the benefits. + +If there is agreement, I can code up the reference implementation as a PR. + +--001a11351cce6a65b004f7e26da1 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div><div><div><div>As part of the atomic cross chain syst= +em, outputs need to be hash locked.<br><br><a href=3D"https://github.com/Ti= +erNolan/bips/blob/bip4x/bip-0045.mediawiki">https://github.com/TierNolan/bi= +ps/blob/bip4x/bip-0045.mediawiki</a><br> +<br><a href=3D"https://bitcointalk.org/index.php?topic=3D193281.msg2224949#= +msg2224949">https://bitcointalk.org/index.php?topic=3D193281.msg2224949#msg= +2224949</a><br><br></div><div>A user needs to provide x corresponding to ha= +sh(x) in order to spend an output.<br> +</div><div><br></div><div>Under the protocol, one of the participants is re= +quired to provide the secret number in order to spend an output.=C2=A0 Once= + they do that, the other participant can use the secret number to spend an = +output on the other chain.=C2=A0 This provides a mechanism to link the 2 ch= +ains together (in addition to lock times).=C2=A0 Once the first output is s= +pent, that commits the transfer.<br> +<br>This is half of the scripting operations required to implement the prot= +ocol.<br></div></div><br></div>The proposal is to make this an adder on to = +the other standard transactions.=C2=A0 It does a check that the hash matche= +s, and then runs the standard transaction as normal.<br> +<br></div><div>Adding the prefix to a P2SH transactions wouldn't work, = +since the template wouldn't match.=C2=A0 <br><br>A script of this form = +could be embedded into a P2SH output.<br><br></div><div>I think that is ok,= + since embedding the "password" in the hashed script gets all the= + benefits.<br> +</div><br><div><div><div><div><div><div></div><div>If there is agreement, I= + can code up the reference implementation as a PR.<br></div></div></div></d= +iv></div></div></div> + +--001a11351cce6a65b004f7e26da1-- + + |