From: Pieter Wuille <pieter.wuille@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Beyond IP transactions: towards a bitcoin payment protocol
Date: Sat, 24 Sep 2011 05:05:08 +0200 [thread overview]
Message-ID: <20110924030505.GA21292@ulyssis.org> (raw)
In-Reply-To: <201109231922.01269.luke@dashjr.org>
On Fri, Sep 23, 2011 at 07:21:58PM -0400, Luke-Jr wrote:
> On Friday, September 23, 2011 7:15:48 PM Pieter Wuille wrote:
> > What I want to do is to standardize part of that out-of-band communication
> > inside a protocol.
>
> Email and XMPP are suitable. Just sign the message with the "from" key.
I don't want to send a mail to you or chat with you when I'm buying something
in your webshop. Or do you mean my client does that automatically? Why not
through an HTTP connection like the one I'm already using anyway to view
the static address on your website?
> > The first observation is that if you want a freshly negotiated key each
> > time, some form of bidirectional communication is necessary anyway, and a
> > static txout template does not suffice anymore.
>
> False. Deterministic keypairs remove the necessity of bidirectional
> communication. A standard for a "public key root" "address" could be
> worthwhile.
They still require you to give me your public key root, and me to give
you the ephemeral private key I generated, optionally together with what
I'm paying you for. That's bidirectional communication to me. Agreed, your
scheme requires a few steps less, but I believe mine is far more flexible
and user-friendly.
--
Pieter
prev parent reply other threads:[~2011-09-24 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 16:21 [Bitcoin-development] Beyond IP transactions: towards a bitcoin payment protocol Pieter Wuille
2011-09-23 17:38 ` kjj
2011-09-23 23:15 ` Pieter Wuille
2011-09-23 23:21 ` Luke-Jr
2011-09-24 3:05 ` Pieter Wuille [this message]
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=20110924030505.GA21292@ulyssis.org \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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