From: Tier Nolan <tier.nolan@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] BIP - Hash Locked Transaction
Date: Fri, 25 Apr 2014 19:49:37 +0100 [thread overview]
Message-ID: <CAE-z3OVsQAya3RDzMTvKNK4hLGQVjFOp6Bseo=xK4ApOdPCh8g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
next reply other threads:[~2014-04-25 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 Tier Nolan [this message]
2014-04-25 19:18 ` Luke-Jr
2014-04-25 19:37 ` Tier Nolan
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-z3OVsQAya3RDzMTvKNK4hLGQVjFOp6Bseo=xK4ApOdPCh8g@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