From: Joel Joonatan Kaartinen <joel.kaartinen@gmail•com>
To: Jan Vornberger <jan@uos•de>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Determine input addresses of a transaction
Date: Tue, 25 Oct 2011 13:03:04 +0300 [thread overview]
Message-ID: <1319536985.27400.34.camel@mei> (raw)
In-Reply-To: <44190.134.106.52.172.1319535941.squirrel@webmail.uni-osnabrueck.de>
On Tue, 2011-10-25 at 11:45 +0200, Jan Vornberger wrote:
> 1) Get something working reasonable fast to detect current green address
> style transactions. It's fine if it is a little bit of a hack, as long as
> it's safe, since I don't expect it to be merged with mainline anyway at
> this point.
>
> 2) Rethink how green transactions are created and verified and try to put
> something 'proper' together which has a chance of being merged at some
> point.
>
> For the moment I was going more with 1) because I got the impression, that
> green transactions are too controversial at this point to get them
> included in mainline. Criticism ranging from 'unnecessary, as
> 0-confirmation transactions are fairly safe today' to 'encourages too much
> centralization and therefore evil'. So how to people on this list feel
> about green transactions? Would people be interested in helping me with
> 2)?
One possibility would be to create a peer sourced green address
implementation. That is, each user could, individually decide to trust
certain addresses as "green" and optionally, publish this trust. Basing
things on the published trust, you could dynamically, as opposed to
static hierarchies, evaluate the trustworthiness of each green address
you haven't personally decided to trust.
This would be somewhat involved implementation, though, as it would
require heavy statistical calculations.
- Joel
next prev parent reply other threads:[~2011-10-25 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 9:45 Jan Vornberger
2011-10-25 10:03 ` Joel Joonatan Kaartinen [this message]
2011-10-25 10:42 ` Mike Hearn
-- strict thread matches above, loose matches on Subject: below --
2011-10-24 8:29 Jan Vornberger
2011-10-24 11:09 ` Pieter Wuille
2011-10-27 14:12 ` Jan Vornberger
2011-10-24 14:55 ` Gavin Andresen
2011-10-24 16:25 ` Mike Hearn
2011-10-24 18:52 ` Simon Barber
2011-10-24 17:14 ` Michael Hendricks
2011-10-27 13:37 ` Jan Vornberger
2011-10-27 14:50 ` Jan Vornberger
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=1319536985.27400.34.camel@mei \
--to=joel.kaartinen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jan@uos$(echo .)de \
/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