Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.113 as permitted sender)
	client-ip=62.13.148.113; envelope-from=pete@petertodd.org;
	helo=outmail148113.authsmtp.com; 
Date: Mon, 25 May 2015 17:05:41 -0400
From: Peter Todd <pete@petertodd.org>
To: Andreas Schildbach <andreas@schildbach.de>
Message-ID: <20150525210541.GA12430@savin.petertodd.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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL"
Content-Disposition: inline
In-Reply-To: <mk00n6$719$1@ger.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] A suggestion for reducing the size of the
 UTXO database
Precedence: list


--vtzGhvizbBRQ85DL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 25, 2015 at 10:29:26PM +0200, Andreas Schildbach wrote:
> > I see this behavior all the time. I am using the latest release, as far=
 as I know. Version 4.30.
> >=20
> > The same behavior occurs in the Testnet3 variant of the app. Go in ther=
e with an empty wallet and receive one payment and wait for it to confirm. =
Then send a payment and, before it confirms, try to send another one. The w=
allet won't let you send the second payment. It'll say something like, "You=
 need x.xxxxxx more bitcoins to make this payment." But if you wait for you=
r first payment to confirm, then you'll be able to make the second payment.
> >=20
> > If it matters, I configure the app to connect only to my own trusted Bi=
tcoin node, so I only ever have one active connection at most. I notice tha=
t outgoing payments never show as "Sent" until they appear in a block, pres=
umably because the app never sees the transaction come in over any connecti=
on.
>=20
> 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.

Odd, I just tried the above as well - with multiple peers connected -
and had the exact same problem.

--=20
'peter'[:-1]@petertodd.org
00000000000000000e83c311f4244e4eefb54aa845abb181e46f16d126ab21e1

--vtzGhvizbBRQ85DL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJVY46gXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwYzc0NjIxZDlhZTIxNGIxMDU5OWI2ZDI5N2VmNTdhNmJl
ZWY3YzM0Nzc1MTE5YzYvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvbqQf+L7qCFwyHJNWAJI7J/20bkZA9
EKNmJpGoSuPd5UhRiHG0hNNu56tfHMtyGtuJRYu7PiTD89+tDp8y/XnllJikKzbd
wyXfg/WiU+jLTw6G0bIi9Im3b3Zk43PBcg38xqPKMR7bXstgYILpAKmL6cwtLIA5
kspeaJONyWz3LV6Q/IxznkYxzGsssW7RmSpKWUUhLzbYxdy1mdY6dam5Io1f8j8q
6m8PfbJJOUkVTcDOvn7hZPUUWZqpFVUS09KxEuu22P9vbXneo6JfeSJtlD3oyLbz
t1zYrruDY7Mkk1HVmbr1eWOfyAhBASyLnqaeQvI3yPUBpxHiAsadnbDsFYgnVQ==
=/sNx
-----END PGP SIGNATURE-----

--vtzGhvizbBRQ85DL--