From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YwzZJ-00008P-MI for bitcoin-development@lists.sourceforge.net; Mon, 25 May 2015 21:05:53 +0000 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; Received: from outmail148113.authsmtp.com ([62.13.148.113]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YwzZI-0002bb-Cs for bitcoin-development@lists.sourceforge.net; Mon, 25 May 2015 21:05:53 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4PL5kqf002457; Mon, 25 May 2015 22:05:46 +0100 (BST) Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com [75.119.251.161]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4PL5g6r096238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 25 May 2015 22:05:45 +0100 (BST) Date: Mon, 25 May 2015 17:05:41 -0400 From: Peter Todd To: Andreas Schildbach Message-ID: <20150525210541.GA12430@savin.petertodd.org> References: <2114827.D6GUhXtGkV@crushinator> <1515563.NQHYuaqTfB@crushinator> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: cf979b92-0321-11e5-b396-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdAcUFVQNAgsB AmMbWVZeUFh7XWY7 bA9PbARUfEhLXhtr VklWR1pVCwQmRRhh ehtJVFtyfgNEe3Y+ bEVnWj4ICk19fBR0 QFNUFm8HeGZhPWUC AkNRcR5UcAFPdx8U a1UrBXRDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4iViUh SB8PBikuGktNSSIp ZwYrJkMXHUAeelky PBM6WEAVexgcQhFe EiMFPRNpABENTjYi BwpBUCYA X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 75.119.251.161/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1YwzZI-0002bb-Cs Cc: bitcoin-development@lists.sourceforge.net 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2015 21:05:53 -0000 --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--