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 3F231412 for ; Wed, 24 Aug 2016 14:42:29 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A3217AA for ; Wed, 24 Aug 2016 14:42:28 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id o80so31598383wme.1 for ; Wed, 24 Aug 2016 07:42:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=WPgZbDeBP9krCqyGgS+k3rCVgsYcAn+EjMY4h44PGJ8=; b=jJb0MExOMGeWpzTdRKn58LCiKKeFPs/TCZjoJEMgaixmPGxrT0HkwJSaW/2N4o3coy W4yMTknoio0USrmspnA71sHWWN08tBtuKRC8CkqSa6MVMXMmgcAJEDM5vxwaqdHoZuEK yEPpXzttGzF3ADNsez7qIF/0vKZEKRUDPGE2LYeR5B+W2XpDKZPzyASr29P01Ip8zHSq 2BXKAZqi9WzMcg/+r+EabPAgOIcIlTjAmrodfpSSqjHqIpogBzCYT43uB1fAupdY0nv6 RlF0w/aQfUsVzdvAkeDxA2hdtWWR+zhD6o0cUL5aAw7lJHeLltv3i7At1oAQrjtpsu9i wj3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=WPgZbDeBP9krCqyGgS+k3rCVgsYcAn+EjMY4h44PGJ8=; b=RwU8M7X30BeDMBMb5VB5lJMQieK0h7ky4igodYbJDm0l2ZpcLfxMt/Wj8egrPR/Vnf WE0eDDfkgLh1fJ7TocnFxJBR73Jc0xnWFP40KnWb3uDUtKxAvyZcr1+4MMcr7YSq9HJG AKLY49KBIrQnu4YeSNTm5CpxjrWj7qI3Sdz3N2FxgL44k7k998tFzbG6W1WJWFaMlBCT C+IuXMLTccdfEYPjn6nd4jaMM+q9wLklxf0Q5kO3/hE98eBMx4lmaXVfbhVkcX5VJRYt 7SQV9VAKmhOYuExwZyADvT6m9E6kLyAOlmQ/e+hCckAOSfGgsM+8seajSzCm/lBO6/uE rjmQ== X-Gm-Message-State: AEkoouujTiRguSsSwITUyGIdrCj1FZnHzXB+asEJHQxBZbv3QUElWD7oDB/7VYfBoKHJ1w== X-Received: by 10.194.80.104 with SMTP id q8mr3410210wjx.151.1472049746977; Wed, 24 Aug 2016 07:42:26 -0700 (PDT) Received: from [10.126.45.199] (ufr-132-230-194-230.eduroam-nat.uni-freiburg.de. [132.230.194.230]) by smtp.googlemail.com with ESMTPSA id 190sm10957853wmk.13.2016.08.24.07.42.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Aug 2016 07:42:25 -0700 (PDT) To: Jonas Schnelli , Bitcoin Protocol Discussion References: <201608232012.12588.luke@dashjr.org> <90bf12f2-e109-28b4-e93e-54bbc8002cb4@electrum.org> <57BDACB2.9040307@jonasschnelli.ch> From: Jochen Hoenicke Message-ID: <278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com> Date: Wed, 24 Aug 2016 16:42:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <57BDACB2.9040307@jonasschnelli.ch> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 Subject: Re: [bitcoin-dev] BIP Status updates (including to Active/Final Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130 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: Wed, 24 Aug 2016 14:42:29 -0000 On 24.08.2016 16:18, Jonas Schnelli via bitcoin-dev wrote: > > Another thing that I think could be a BIP misdesign: > > BIP44 Gap Limits > From the BIP: > > ---------- > "Address gap limit is currently set to 20. If the software hits 20 > unused addresses in a row, it expects there are no used addresses beyond > this point and stops searching the address chain." > ---------- > > * Does that mean, we do a transaction rescan back to the genesis block > for every 20 addresses? As I understand it, you can scan sequentially starting with the genesis block (or with a block at around the time when BIP44 was written). Then if you find a new transaction, which requires to generate new addresses, you generate them and scan further from that point on. This way you can scan in a single pass if the scanning process calls you back when it finds a transaction and allows you to change the set of addresses on the fly. Jochen