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 EB33B721 for ; Fri, 30 Oct 2015 03:35:34 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E4D4F128 for ; Fri, 30 Oct 2015 03:35:33 +0000 (UTC) Received: by igbdj2 with SMTP id dj2so2989085igb.1 for ; Thu, 29 Oct 2015 20:35:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iNL04aM5c2HDk65vKgm/f6p6ajqszT9keLJqHG4T6ho=; b=1Jx2N+7WaHFDvNnHrVcBsI4LRusscfckpMYVtkEGua2y/XZ9IAlZBfHMHwv+SWkmmw bGif54nZn+LxZdZNK/bXNaLREicTkeiP7iI9+kfrGleGxWHeBcXXECa59b6mv6bXT/pl JRUTJ9aXsVn2x78Obw/jhSwWlDtj6dxpa/haec4x9PQWkmKCdxvbuWaABOCJr0GF4V31 +lAU06iMnHyO9qN8JnDVCMbtlcDeBgqcym2wbH8KhIu9xQ4bF/rjQQWbMGf557gRAKW/ mqnAuCtZULvzFGHsq2nphmtIxK3NKGiwKuVKKFElKKLFJ5Eiv0TZCow1wa9S4Qmqzqn1 bRxA== MIME-Version: 1.0 X-Received: by 10.50.27.10 with SMTP id p10mr715575igg.66.1446176133409; Thu, 29 Oct 2015 20:35:33 -0700 (PDT) Received: by 10.107.192.199 with HTTP; Thu, 29 Oct 2015 20:35:33 -0700 (PDT) In-Reply-To: <5632DE33.7030600@bitcartel.com> References: <5631C363.5060705@neomailbox.net> <201510290803.52734.luke@dashjr.org> <5632DE33.7030600@bitcartel.com> Date: Fri, 30 Oct 2015 03:35:33 +0000 Message-ID: From: Gregory Maxwell To: Simon Liu Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev , 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: Fri, 30 Oct 2015 03:35:35 -0000 On Fri, Oct 30, 2015 at 3:04 AM, Simon Liu via bitcoin-dev wrote: > Given that UTXO storage is considered critical, it seems reasonable to This sounds like a misunderstanding of what consensus criticial means. It does not mean that it must be right (though obviously that is preferable) but that it must be _consistent_, between all nodes. > full node and keep up with the network, why not let those users with the > resources to operate big iron databases do so? It would be a good > feature to have. Because it provides no value, the data is opaque and propritarily encoded with a compression function which we may change from version to version, and because many of these alternatives are enormously slow; enough that they present problems with falling behind the network even on high performance hardware. Moreover, additional functional which will not be sufficiently used will not adequately maintained and result in increased maintains costs and more bugs.