From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP Draft: Atomic Cross Chain Transfer Protocol
Date: Wed, 30 Apr 2014 18:59:07 +0000 [thread overview]
Message-ID: <201404301859.07833.luke@dashjr.org> (raw)
In-Reply-To: <CAE-z3OUE5AQAC2G4MtF=RVHwYEP1TKXTOopO14rmPiGkxC5MQw@mail.gmail.com>
On Wednesday, April 30, 2014 6:03:59 PM Tier Nolan wrote:
> Due to "popular" demand, I have created a BIP for cross chain atomic
> transfers.
>
> https://github.com/TierNolan/bips/blob/bip4x/bip-atom.mediawiki
Instead of TX0, TX1, etc, can you put some kind of meaningful identifier for
these transactions?
TX1 and TX2 *cannot* be signed until after TX0 is completely signed by both
parties. After TX0 is signed, but before TX2 is signed, either party could
walk away or otherwise hold the funds hostage. The sequence of signing
proposed in this BIP is *not possible to perform*. How did you implement and
test this? :/
What is the purpose of the OP_EQUAL_VERIFY in TX4? I don't see a use...
IMO, there should be separate BIPs for the exchange itself, and the protocol
to negotiate the exchange. I would recommend changing the latter from JSON-RPC
to some extension of the Payment Protocol, if possible.
Perhaps it would be good to only support compressed keys, to discourage use of
uncompressed ones..
Luke
next prev parent reply other threads:[~2014-04-30 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 18:03 Tier Nolan
2014-04-30 18:59 ` Luke Dashjr [this message]
2014-04-30 20:48 ` Tier Nolan
2014-04-30 23:02 ` 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=201404301859.07833.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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