Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C4AEE86 for ; Sun, 9 Aug 2015 14:12:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from homiemail-a6.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 51029183 for ; Sun, 9 Aug 2015 14:12:25 +0000 (UTC) Received: from homiemail-a6.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a6.g.dreamhost.com (Postfix) with ESMTP id D3DDB598077 for ; Sun, 9 Aug 2015 07:12:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jrn.me.uk; h=to:from :subject:message-id:date:mime-version:content-type: content-transfer-encoding; s=jrn.me.uk; bh=jIJAUZo8BJiAZrUFDEJg5 4J+SfY=; b=L1H/utH6fP5TTagqzYCdn8udwSV42UmbUlAurqWSqhlijaxtAbJFg CYNxq/npDeI79Ok6H4AyuWISFlS78d+4/ZkpQDhXRKvfX8/91DbgBmmjZu/G2ddr 6SuBEFU8iVxMHEJMK4WUX5u8YRug4Vc24uXSEi1jSBmVHdynHh6pBs= Received: from [10.9.1.130] (unknown [89.238.129.18]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jrn@jrn.me.uk) by homiemail-a6.g.dreamhost.com (Postfix) with ESMTPSA id 7503259806B for ; Sun, 9 Aug 2015 07:12:24 -0700 (PDT) To: bitcoin-dev@lists.linuxfoundation.org From: Ross Nicoll Message-ID: <55C75FC8.6070807@jrn.me.uk> Date: Sun, 9 Aug 2015 15:12:24 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, 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: [bitcoin-dev] Alternative chain support for payment protocol 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: Sun, 09 Aug 2015 14:12:25 -0000 BIP 70 currently lists two networks, main and test (inferred as testnet3) for payment protocol requests. This means that different testnets cannot be supported trivially, and the protocol cannot be used for alternative coins (or, lacks context to indicate which coin the request applies to, which is particularly dangerous in cases where coins share address prefixes). I propose adding a new optional "genesis" field as a 16 byte sequence containing the SHA-256 hash of the genesis block of the network the request belongs to, uniquely identifying chains without any requirement for a central registry. For backwards compatibility, the "network" field would contain "main" for Bitcoin main net, "test" for Bitcoin testnet3, and "other" for other networks apart from those two. I'd appreciate initial feedback on the idea, and if there's no major objections I'll raise this as a BIP. Ross