From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A2531941 for ; Sun, 15 Nov 2015 03:04:47 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 4465911C for ; Sun, 15 Nov 2015 03:04:47 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id D665038A6FC8; Sun, 15 Nov 2015 03:04:41 +0000 (UTC) X-Hashcash: 1:25:151115:bitcoin-dev@lists.linuxfoundation.org::ie8bK=lfPwUgUokG:cwTH X-Hashcash: 1:25:151115:peter_r@gmx.com::PzFege2V=1Y/kMyl:ber7 X-Hashcash: 1:25:151115:gmaxwell@gmail.com::D24FUIIYLHNvMiEM:DSbx X-Hashcash: 1:25:151115:telemaco@neomailbox.net::6pqpKRZYIsQkk3EP:d52T From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Peter R Date: Sun, 15 Nov 2015 03:04:33 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.9-gentoo-r1; KDE/4.14.8; x86_64; ; ) References: <5631C363.5060705@neomailbox.net> <571D9B7F-077D-4B80-B577-1C18FF2ECF31@gmx.com> In-Reply-To: <571D9B7F-077D-4B80-B577-1C18FF2ECF31@gmx.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201511150304.41003.luke@dashjr.org> X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: telemaco Subject: Re: [bitcoin-dev] [patch] Switching Bitcoin Core to sqlite db X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 03:04:47 -0000 On Sunday, November 15, 2015 1:02:33 AM Peter R via bitcoin-dev wrote: > A group of us have been exploring this =E2=80=9Cmeta-cognition=E2=80=9D i= dea with Bitcoin > Unlimited. For example, Bitcoin Unlimited can be (optionally) made to > automatically fork to the longest chain if it =E2=80=9Cgets stuck=E2=80= =9D and can neither > prove that a block is valid nor that the block is invalid. This situation isn't something that can be ignored and simply moved past. I= f=20 you can't determine the validity of a block, you also cannot process its=20 results correctly. Taking for example the BDB/LevelDB issue, the result was= =20 that BDB failed to accept further changes to the UTXO set. Unless the UTXO = set=20 could be updated correctly, there is no way to even attempt to validate the= =20 next block or any new transactions. Luke