Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd2VD-0002VS-Av for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 19:06:39 +0000 X-ACL-Warn: Received: from mail-ve0-f176.google.com ([209.85.128.176]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd2VB-0001He-Tj for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 19:06:39 +0000 Received: by mail-ve0-f176.google.com with SMTP id db11so1644243veb.7 for ; Wed, 23 Apr 2014 12:06:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=+r/LpDwBweY4b2sETK42sKc0IcxM5O/8Lw9Q4713tSk=; b=I2MjIFsTg3aW0fdVdI2e9a1HnMTIL0ZfykU5N3Wy6hEs/u3KfqEKkpubyKFemmZrIK 34Io7sWXU7cv7izcJKTTWXyNKvYWP9vXIGpeCMAcTZBWB5VO6lI/w6XuM3xulBV4iX/W fNRWu47ZsArYXRYAm/NY6Q08R0G6nX0cpMdnKzxcxWVC/GU8aHOBI0qIxNR9S668wu6J 0QOwc+diiF/MLLc1PbYjcaH5s2hP1eb+2XAzlIdY54IGXDADmSYWEa24mBYLI/Scbw9k aZl8r/TKJA5xylltiYbJO75MJv9NsUBUt1TA4h6i8VC5dfMkKj+MHoCXVF2GBd0LsivE PWkA== X-Gm-Message-State: ALoCoQkt2sVfgwvOxewFpzHbW6v3ZQQ3NmIJ7VGtnRY3Es/Y3bNHs1tgKDd+0piOKAEWa/So0Q+V X-Received: by 10.220.2.142 with SMTP id 14mr1012762vcj.48.1398279992347; Wed, 23 Apr 2014 12:06:32 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.234.68 with HTTP; Wed, 23 Apr 2014 12:06:02 -0700 (PDT) In-Reply-To: References: <53344FF8.7030204@gk2.sk> <53580A73.9070208@gk2.sk> From: slush Date: Wed, 23 Apr 2014 21:06:02 +0200 X-Google-Sender-Auth: MAdOrTd7UoCJi1fQ3HtG3Oc7uT0 Message-ID: To: Tier Nolan Content-Type: multipart/alternative; boundary=001a11c3dd183da67c04f7ba6ebb X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1Wd2VB-0001He-Tj Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] New BIP32 structure 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: Wed, 23 Apr 2014 19:06:39 -0000 --001a11c3dd183da67c04f7ba6ebb Content-Type: text/plain; charset=ISO-8859-1 Using higher gap limit in the software is not prohibited, but then it breaks the standard "as is", in mean that importing such wallet to another BIP64 wallet won't recover the funds properly, without proper settings of gap limit... Gap limit 20 is the most sane defaults for majority of users (actually I think it is a bit higher than is really necessary for 99% users) and majority of users won't need to change it at any time. Marek On Wed, Apr 23, 2014 at 9:00 PM, Tier Nolan wrote: > On Wed, Apr 23, 2014 at 7:46 PM, Pavol Rusnak wrote: > >> >> > Setting the gap limit to high is just a small extra cost in that case. >> >> Not if you have 100 accounts on 10 different devices. >> > > I meant for a merchant with a server that is handing out hundreds of > addresses. > > The point is to have a single system that is compatible over a large > number of systems. > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a11c3dd183da67c04f7ba6ebb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Using higher gap limit in the software is not prohibited, = but then it breaks the standard "as is", in mean that importing s= uch wallet to another BIP64 wallet won't recover the funds properly, wi= thout proper settings of gap limit...

Gap limit 20 is the most sane defaults for majority of users= (actually I think it is a bit higher than is really necessary for 99% user= s) and majority of users won't need to change it at any time.

Marek


On Wed, Apr 23, 2014 at 9:00 PM, Tier Nolan <ti= er.nolan@gmail.com> wrote:
=
On Wed, Apr 23, 2014 at 7:46 PM,= Pavol Rusnak <stick@gk2.sk> wrote:

> Setting the gap limit to high is just a small extra cost in that case.=

Not if you have 100 accounts on 10 different devices.

I meant for a merchant with a server that is han= ding out hundreds of addresses.
=A0
The point i= s to have a single system that is compatible over a large number of systems= .

-----------------------------------------------------------------------= -------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.n= et/sfu/ExoPlatform
_______________________________________________ Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a11c3dd183da67c04f7ba6ebb--