From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YIIQU-0003ZK-EH for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 14:56:34 +0000 X-ACL-Warn: Received: from mail-wg0-f51.google.com ([74.125.82.51]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YIIQS-0000lZ-At for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 14:56:34 +0000 Received: by mail-wg0-f51.google.com with SMTP id k14so39137897wgh.10 for ; Mon, 02 Feb 2015 06:56:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QUnUflQ2/QPdrbhoC/PEwh7XA+/u90gZlF5DMvNmo3U=; b=j4DErOLNT544LF7qAb6VrXTSskFI0zooNFluIXquzicjDjZkMGZnKOgi5L6mcOwN8g 5QfjvdHA1Dmk/ic7mBjD12UO4SZ5okjFkaKldWWX0T0rv74IY9lxe8giA0TWH9z6IXDn hnUhJU9F2AZvaGkjugrErKPwTaVZ4fl/l9ZC6fK7cKeMUZs855JRJxoJH8Hb4P2U4Kez R2elRP6txC4Q2OJOZY/ScnjMHd+ZR5EePezTl0r16qJmCjIhEOcs0wf9NCaI6aos7bJi bu9jBlqTxgsBSyhvaKNHXILvhqVGgLX0F7XftwckGN9k8njl+ykZhV5yPoBoEohMmgsA PpmQ== X-Gm-Message-State: ALoCoQnBQuXgw0lDLeAHCw+gUXk52AGk+Nw/6f3cnJRPuHBpa4T/BhfPEXqZGxd43/fVa+iv0QF4 X-Received: by 10.194.205.228 with SMTP id lj4mr42824846wjc.77.1422888985978; Mon, 02 Feb 2015 06:56:25 -0800 (PST) Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254]) by mx.google.com with ESMTPSA id u7sm20214698wiy.18.2015.02.02.06.56.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 06:56:24 -0800 (PST) Message-ID: <54CF9016.5070206@gk2.sk> Date: Mon, 02 Feb 2015 15:56:22 +0100 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Andreas Schildbach , bitcoin-development@lists.sourceforge.net References: <54CF74A5.3050304@gk2.sk> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1YIIQS-0000lZ-At Subject: Re: [Bitcoin-development] Export format for xpub 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: Mon, 02 Feb 2015 14:56:34 -0000 On 02/02/15 15:17, Andreas Schildbach wrote: > Yes, except that BIP32-hierarchy and BIP44 differ in some requirements > (e.g. gap limit). Right. To me it seems more important to describe how addresses should be discovered (i.e. to scan xpub/0/i and xpub/1/j chains using gap limit G) instead of how the xpub was created/obtained (bip32 vs bip44). What do you thing about changing ?h=bip32 to something like ?t=01&g=20 - t=01 meaning that chains 0 and 1 should be scanned (feel free to change "01" into any other descriptive string) - g=20 meaning that gap 20 should be used > Those strings are not meant to be read by humans. YYYYMMDD is more > complicated than necessary, given that Bitcoin deals with seconds since > epoch everywhere. OK :-) -- Best Regards / S pozdravom, Pavol Rusnak