From: Tier Nolan <tier.nolan@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Hash Locked Transaction
Date: Fri, 25 Apr 2014 20:37:53 +0100 [thread overview]
Message-ID: <CAE-z3OVo9wPbSwfHrpf8bSGWYBR510Q0np6VFfQUZdX3hWoQtA@mail.gmail.com> (raw)
In-Reply-To: <201404251918.44282.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Fri, Apr 25, 2014 at 8:18 PM, Luke-Jr <luke@dashjr•org> wrote:
> This one looks entirely useless (it cannot be made secure)
The hash locking isn't to prevent someone else stealing your coin. Once a
user broadcasts a transaction with x in it, then everyone has access to x.
It is to release the coin on the other chain. If you spend the output, you
automatically give the other participant the password to take your coin on
the other chain (completing the trade).
The BIP allows the hash to protect any of other standard transactions
(except P2SH, since that is a template match).
For example, it would allow a script of the form
OP_HASH160 [20-byte-password-hash] OP_EQUAL_VERIFY OP_DUP OP_HASH160
<pubKeyHash> OP_EQUALVERIFY OP_CHECKSIG
To spend it, you would need to provide the password and also sign the
transaction using the private key.
> and the assertion
> that it is necessary for atomic cross-chain transfers seems unfounded and
> probably wrong...
>
>
I meant that it is required for the particular protocol.
> Luke
>
[-- Attachment #2: Type: text/html, Size: 1946 bytes --]
next prev parent reply other threads:[~2014-04-25 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 Tier Nolan
2014-04-25 19:18 ` Luke-Jr
2014-04-25 19:37 ` Tier Nolan [this message]
2014-04-25 20:06 ` Alex Mizrahi
2014-04-25 20:14 ` Peter Todd
2014-04-25 20:19 ` Gregory Maxwell
2014-04-25 21:14 ` Peter Todd
2014-04-25 21:52 ` Tier Nolan
2014-04-26 11:11 ` Jorge Timón
2014-04-26 11:31 ` Tier Nolan
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=CAE-z3OVo9wPbSwfHrpf8bSGWYBR510Q0np6VFfQUZdX3hWoQtA@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--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