Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <wtogami@gmail.com>) id 1Ywzi1-00006Y-JJ
	for bitcoin-development@lists.sourceforge.net;
	Mon, 25 May 2015 21:14:53 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.178 as permitted sender)
	client-ip=209.85.192.178; envelope-from=wtogami@gmail.com;
	helo=mail-pd0-f178.google.com; 
Received: from mail-pd0-f178.google.com ([209.85.192.178])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Ywzi0-0000L1-JG
	for bitcoin-development@lists.sourceforge.net;
	Mon, 25 May 2015 21:14:53 +0000
Received: by pdbqa5 with SMTP id qa5so75695514pdb.0
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 25 May 2015 14:14:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.69.17.130 with SMTP id ge2mr42116112pbd.75.1432588486976;
	Mon, 25 May 2015 14:14:46 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Mon, 25 May 2015 14:14:46 -0700 (PDT)
In-Reply-To: <mk00n6$719$1@ger.gmane.org>
References: <CANe1mWzBy8-C+CWfwaOLxJ2wokjy8ytQUh2TkRY_Ummn1BpPzw@mail.gmail.com>
	<2114827.D6GUhXtGkV@crushinator>
	<CANEZrP2KnL9NO-DgUuaT5-VHE0oT5MTsok2YuAO1nJiznLfpMA@mail.gmail.com>
	<1515563.NQHYuaqTfB@crushinator> <mk00n6$719$1@ger.gmane.org>
Date: Mon, 25 May 2015 14:14:46 -0700
Message-ID: <CAEz79PrfWpkNKNDpsh6q3KNpdceTpH++w4j_BusADSB2OqBtXA@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 2.3 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(wtogami[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.2 MISSING_HEADERS        Missing To: header
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	2.7 MALFORMED_FREEMAIL Bad headers on message from free email service
X-Headers-End: 1Ywzi0-0000L1-JG
Subject: Re: [Bitcoin-development] A suggestion for reducing the size of the
 UTXO database
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 25 May 2015 21:14:53 -0000

On Mon, May 25, 2015 at 1:29 PM, Andreas Schildbach
<andreas@schildbach.de> wrote:
> Yes, that's the issue. Because you're connecting only to one node, you
> don't get any instant confirmations -- due to a Bitcoin protocol
> limitation you can only get them from nodes you don't post the tx to.

Is it really wise to call this a "confirmation"?  All this is really
telling you is one seemingly random peer has relayed the transaction
back to you that you sent to a presumably different seemingly random
peer.

Warren