public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christian Decker <decker.christian@gmail.com>
To: "Jorge Timón" <timon.elviejo@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
Date: Thu, 15 Dec 2011 12:22:29 +0100	[thread overview]
Message-ID: <CALxbBHXHi=AR+AWWutbHX4XXr3vh18-Pi=V-1kvC7TKdr3ECNA@mail.gmail.com> (raw)
In-Reply-To: <CAGQP0AEep1RtaPm6chQh-fLB63tx7Eb9tGq_Obpp003PREt6zw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

> But we don't have to
> define how the server will get that address.
> Some possibilities:
>
> -A static address: less anonymity, but some people may not care. Say a
> donation address.
> -The servers stores the recipient private keys and generates a new one
> for each payment.
> -The server stores a set of addresses provided by the recipient and it
> manages what address it gives in each request (like in the web service
> I told you I can't find).
>

Exactly, I think we should starting separating the minimal protocol that is
to be supported by everybody, and the rest can be summed up in a few best
practices, no need to standardize the part that to the user is transparent.
I was on the same lines as Andy, which is that in order to have require a
payment I probably have an order/transaction pending with my vendor or have
an account to be filled, so there's a 1-to-1 mapping between the details
page and the bitcoin address I have to send to.

As a further possibility we could use <meta> tags like the OpenID server
delegation mechanism. It would allow customers to open the transaction
details page, see that everything is ok, then paste the same URL into the
bitcoin client, the bitcoin client retrieves the URL, parses the meta tag
and knows what to send where. Alternatively the Bitcoin Client sends an
Accept header which tells the server to return just the address.

As for the format I'd say either a Bitcoin address or a Bitcoin URI [1]
which ought to be flexible enough as it includes amount and messages, for
the customer to be able to track transactions.

Regards,
Chris

[1] https://en.bitcoin.it/wiki/URI_Scheme

[-- Attachment #2: Type: text/html, Size: 1952 bytes --]

  reply	other threads:[~2011-12-15 11:24 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 23:16 [Bitcoin-development] [BIP 15] Aliases Zell Faze
2011-12-12 23:37 ` Jorge Timón
2011-12-12 23:41   ` Luke-Jr
     [not found]     ` <CAGQP0AGBKKEqhaJZj-Rw400AjrVHE9_EMve=RWdqoaOaDsTgtw@mail.gmail.com>
2011-12-13  0:00       ` [Bitcoin-development] Fwd: " Jorge Timón
2011-12-13  0:42         ` Amir Taaki
2011-12-13  2:32           ` Daniel F
2011-12-13  2:37             ` Amir Taaki
2011-12-13  2:43               ` Luke-Jr
2011-12-13  2:52               ` Daniel F
2011-12-13 10:55           ` Mike Hearn
2011-12-13 11:42             ` Christian Decker
2011-12-13 12:32               ` Jorge Timón
2011-12-13 13:06                 ` Gavin Andresen
2011-12-13 15:46                   ` Amir Taaki
2011-12-13 16:22                     ` Andy Parkins
2011-12-14 19:22                       ` D.H.
2011-12-14 20:07                         ` Luke-Jr
2011-12-14 20:17                           ` D.H.
2011-12-14 20:21                           ` Joel Joonatan Kaartinen
2011-12-14 22:51                             ` Jorge Timón
2011-12-14 23:02                               ` Rick Wesson
2011-12-14 23:27                                 ` Luke-Jr
2011-12-15  1:22                                   ` Rick Wesson
2011-12-15  3:57                                     ` Zell Faze
2011-12-15  4:56                                       ` Kyle Henderson
2011-12-15  6:04                                         ` Zell Faze
2011-12-15  6:41                                           ` Walter Stanish
2011-12-15  7:45                                             ` Jordan Mack
2011-12-15  7:52                                               ` Jorge Timón
2011-12-15  7:48                                             ` Jorge Timón
2011-12-15  8:26                                               ` Walter Stanish
2011-12-15 10:01                                                 ` Andy Parkins
2011-12-15 11:08                                                 ` Jorge Timón
2011-12-15 11:22                                                   ` Christian Decker [this message]
2011-12-16  5:42                                                   ` Walter Stanish
2011-12-16  8:46                                                 ` Pieter Wuille
2011-12-15 15:44                                               ` Rick Wesson
2011-12-15 15:42                                           ` Rick Wesson
2011-12-16  0:07                       ` slush
2011-12-16 15:52                         ` Rick Wesson
2011-12-16 16:36                           ` slush
2011-12-16 17:10                           ` Andy Parkins
2011-12-16 17:41                             ` Rick Wesson
2011-12-16 18:29                               ` Amir Taaki
2011-12-16 19:06                                 ` Gavin Andresen
2011-12-16 19:22                                   ` Rick Wesson
2011-12-16 20:58                                   ` Andy Parkins
2011-12-16 20:54                               ` Andy Parkins
2011-12-16 21:50                                 ` Rick Wesson
2011-12-13 15:47                   ` Luke-Jr
2011-12-16 17:36                   ` Khalahan
2011-12-16 17:48                     ` Gregory Maxwell
2011-12-13 15:55               ` Walter Stanish
2011-12-13 16:15                 ` Jorge Timón
2011-12-13 16:48                 ` Gavin Andresen
2011-12-14  2:30                   ` Walter Stanish
2011-12-13  2:39     ` [Bitcoin-development] " Stefan Thomas
2011-12-12 23:52   ` Matt Corallo
2011-12-12 23:37 ` Will
     [not found] <9109000381434268897@unknownmsgid>
2011-12-13  8:55 ` [Bitcoin-development] Fwd: " Cameron Garnham

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='CALxbBHXHi=AR+AWWutbHX4XXr3vh18-Pi=V-1kvC7TKdr3ECNA@mail.gmail.com' \
    --to=decker.christian@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=timon.elviejo@gmail.com \
    /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