From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Jeremy Spilman <jeremy.spilman@gmail.com>
Subject: Re: [Bitcoin-development] Eliminating double-spends with two-party self-escrow for high value transactions
Date: Sat, 26 Apr 2014 20:51:19 +0200 [thread overview]
Message-ID: <CANEZrP2O74111_PxG-yPYFj0x7wfXTUhCYpre_3=93iYk14fEw@mail.gmail.com> (raw)
In-Reply-To: <20140426183119.GB16440@savin>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
>
> Note how the mechanism I'm proposing is basically just a Jeremy
> Spilman-style micropayment channel(1) used for a single payment; I
> should have made that clear in my original post.
Right, that does make more sense. Yes, it's a good idea. The question is
whether wallet UI's can support it without being overly complex. We'd be
asking users to take extra steps to work around unintuitive limitations of
the protocol. Products that do that too much tend to get left for something
that "just works". But there may be a slick way to present it.
[-- Attachment #2: Type: text/html, Size: 806 bytes --]
next prev parent reply other threads:[~2014-04-26 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 11:23 [Bitcoin-development] Eliminating double-spends with two-party self-escrow for high value transactions Peter Todd
2014-04-26 18:07 ` Mike Hearn
2014-04-26 18:31 ` Peter Todd
2014-04-26 18:51 ` Mike Hearn [this message]
2014-04-26 19:37 ` Peter Todd
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='CANEZrP2O74111_PxG-yPYFj0x7wfXTUhCYpre_3=93iYk14fEw@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jeremy.spilman@gmail.com \
--cc=pete@petertodd.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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