From: Gavin Andresen <gavinandresen@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
Date: Tue, 7 Feb 2012 11:14:14 -0500 [thread overview]
Message-ID: <CABsx9T0jXxwc8N2i4kVOqNP5B8AgiPUJuxMcgB7=WU2cCeq-iQ@mail.gmail.com> (raw)
In-Reply-To: <201202071004.37615.luke@dashjr.org>
> Do you have an alternative solution to the
> problem of green addresses spamming the blockchain?
Sure, here's one:
Green address provider give a REST-ful API, that provides the
following functionality:
+ Give transaction ID and credentials, request that the transaction be
declared "green"
(sender's wallet site/software would do this)
+ Give transaction ID, return boolean "has this transaction been
deeclared green?"
As I said, I think any design that relies on clients recognizing two
variations of a transaction is a very bad idea.
--
--
Gavin Andresen
prev parent reply other threads:[~2012-02-07 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 15:44 Gavin Andresen
2012-02-06 15:54 ` Luke-Jr
2012-02-07 15:04 ` Luke-Jr
2012-02-07 16:14 ` Luke-Jr
2012-02-07 16:14 ` Gavin Andresen [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='CABsx9T0jXxwc8N2i4kVOqNP5B8AgiPUJuxMcgB7=WU2cCeq-iQ@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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