Message-ID: <56086.134.106.52.172.1319724739.squirrel@webmail.uni-osnabrueck.de>
In-Reply-To: <20111024110955.GC8115@ulyssis.org>
References: <44861.134.106.52.172.1319444997.squirrel@webmail.uni-osnabrueck.de>
	<20111024110955.GC8115@ulyssis.org>
Date: Thu, 27 Oct 2011 16:12:19 +0200 (CEST)
From: "Jan Vornberger" <jan@uos.de>
To: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
User-Agent: SquirrelMail/1.4.8-5.el5_4.10
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [Bitcoin-development] Determine input addresses of a transaction
Precedence: list

Am Mo, 24.10.2011, 13:09, schrieb Pieter Wuille:
> As far as your green transactions idea is concerned, maybe we could
> provide an interface
> to mark certain addresses as 'trusted', and have an RPC call to request
> all incoming
> transaction that originate from trusted sources?

That would be fine as well. Although I would prefer if one could
query for a specific transaction id, whether it comes from a trusted
source and also from which trusted source, as you might want to
keep track of the amount of unconfirmed funds you are currently
accepting from a specific source (or the Bitcoin daemon could
keep track of that as well, either way is fine).

This sounds a little too involved though, for my level of familiarity
with the Bitcoin source code and C++, to implement myself.

Regards,
Jan