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 A4A5389F for ; Fri, 7 Apr 2017 00:48:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2CFE7169 for ; Fri, 7 Apr 2017 00:48:53 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 6F1712079D; Thu, 6 Apr 2017 20:48:52 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Thu, 06 Apr 2017 20:48:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rH6/j8 bwcaLhybumdxvQnUIxagdUaEDTVj6YYvNtff0=; b=cnJCW2A8SF1UUjhrHQNueS wmEgqZNUeJB2gPmfNhMj8+XPou052ZOC3/Xtf/MPK1tFceuahG9nPj3St5faJEPz ykZbwrt8GaihgU6citFA/45batXT70icqGHRqCQffx8h60u7yBVWLFwxzb8Hdsxv bNdP2tWBMD8eWQDsWSm506MUdSPcNLw0vRHsqKaKHirAjmvYGh7glOgoZgt6hZzR 1jQ8H1d/ZOaDWKAPc2we52f6yjwy1mR09WdtVIqsnTgTZkzY6BUbxzHLb7Fro/2X yM+h4pjF9i6LQ/Uut/oNzy5+akryTbzWPImifdoy2Hr5qssUrC7IQvMh4ek3Dp0g == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4BF009EC32; Thu, 6 Apr 2017 20:48:52 -0400 (EDT) Message-Id: <1491526132.723002.936945760.06A943C6@webmail.messagingengine.com> From: Tomas To: Gregory Maxwell , Bitcoin Protocol Discussion MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-8e6aa83c In-Reply-To: Date: Fri, 07 Apr 2017 02:48:52 +0200 References: <1491516747.3791700.936828232.69F82904@webmail.messagingengine.com> X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 X-Mailman-Approved-At: Fri, 07 Apr 2017 01:13:16 +0000 Subject: Re: [bitcoin-dev] Using a storage engine without UTXO-index X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 00:48:53 -0000 On Fri, Apr 7, 2017, at 02:32, Gregory Maxwell wrote: > Perhaps a simple question would help: > > What is the minimal amount of space your system requires to take a new > block received from the P2P network and verifying that all its spends > were valid spends of existing coins unspent coins today? > > For Bitcoin Core the answer is ~2GB (plus the configuration handling > currently forces you to keep another 550MB of blocks for reorgs). Bitcrust separates script validation (base load, when transaction come in) from order validation (peak load, when blocks come in). For script validation it would obviously need the ~2GB (or I think ~1.5GB) of outputs needed to validate these. For order validation it needs ~200mb or the spent-index (for bit-lookups) and I would guess roughly ~500mb of the spent-tree (for scanning), though I don't think the 5.7GB full spend tree isn't worth pruning anytime soon. Then it is currently using a ~1.5GB index for transaction hash to fileptr lookups, though this could be made more space efficient.