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 15984C7A for ; Sat, 6 Jan 2018 00:44:23 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f41.google.com (mail-vk0-f41.google.com [209.85.213.41]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 60789CE for ; Sat, 6 Jan 2018 00:44:22 +0000 (UTC) Received: by mail-vk0-f41.google.com with SMTP id o16so4457178vke.12 for ; Fri, 05 Jan 2018 16:44:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-transfer-encoding; bh=eb5oroU3qWpmOGv91tXDXmCzLCmx8XdnG+PuJVWSqgI=; b=vWkMSq3QhQCOS2k2xgBt3AiKsTLhibMnTwNRF06ckhNq5c3Hz+hafwZ3iZl7lUnDjL GDSrEfShg41LtndR/CIBFjKlDrxvu+JbpUX0YpIfh2kf1w+Kxt/heBl9HEQot4YN7OsM /poSs+H+jsaNoPcX3HIeDQMtAh5iCUyYvhLY29dQjWlxPF5/mq1TEOy6IGQKLM+IGG3s qYH770A1Ji8c83W2j02Oq0NA4X63Q0U0OcdQfDmVC8zC+N1AqsfnN8dA/vX6Dfr9v+J8 cV3PsO/C/6iGOH2oZasT2ZaCyWlA8yCazKrh6sz05i88WSe07yu3ooZGtliARZo11Gtg uUFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-transfer-encoding; bh=eb5oroU3qWpmOGv91tXDXmCzLCmx8XdnG+PuJVWSqgI=; b=Oa6CQ0L3p729qbnuyAyI5yCF0DuYWXlhjsD80MKivTaHmkM2cSn+0GAAGvnP+NN5n1 UUaJOpwgEWIUpEyMHnBsH0/1s/eTYIGNXX4luQE7I9Tfl7Bbx/dSkmhk+gBymi67VRym ILj0RmO0+2NTf3rodm4OyoJ/INSNlDX0uWCobqsCcrfc7wRQDhHehxhcOjw3944k8U1x BmUxEueB2QNxKi5gNqGyEJaTIFCDoeoWEFfx6ZCxEVZaqhIUaLQGrdEV+BPtlLYilDk9 MKuak2KOrb6dnitvyNKC9RmFgdT56cTaqWtAnKDN1yQStM4Y4g2PBmbTkVF3mDiZWvXj BTuA== X-Gm-Message-State: AKwxyteud2JULlFtaZdh2+IQ5tdnGaUQtHR3Fn49pf97IRiCPdW6FdVH JVM3ybVhgd2QZA22qbYZSGtjPC+R4mt5o9H5Ro4= X-Google-Smtp-Source: ACJfBou3bFy5WDweBum1MRdFoKZMcvhA57ki7gQJsj3ANRqw+2teKqch8o7g42O/jOz2TuMLuud5Omcn6RJuZSVI9JY= X-Received: by 10.31.120.129 with SMTP id t123mr4407840vkc.172.1515199461478; Fri, 05 Jan 2018 16:44:21 -0800 (PST) MIME-Version: 1.0 Sender: gmaxwell@gmail.com Received: by 10.103.85.148 with HTTP; Fri, 5 Jan 2018 16:44:20 -0800 (PST) In-Reply-To: <201801041423.05959.luke@dashjr.org> References: <201801041423.05959.luke@dashjr.org> From: Gregory Maxwell Date: Sat, 6 Jan 2018 00:44:20 +0000 X-Google-Sender-Auth: d7KLZ69jrj3fWQ7b0mLYJkf7WOc Message-ID: To: Luke Dashjr , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE 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] =?utf-8?q?Bech32_and_P2SH=C2=B2?= 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: Sat, 06 Jan 2018 00:44:23 -0000 P2SH^2 wasn't a serious proposal-- I just suggested it as a thought experiment. I don't think it offers much useful in the context of Bitcoin today. Particularly since weight calculations have made output space relatively more expensive and fees are at quite non-negligible rates interest in "storing data" in outputs should at least not be increasing. Moreover, unfortunately, people already rushed bech32 to market in advance of practically any public review-- regrettable but it is what it is... I don't think adding more address diversity at this time wouldn't be good for the ecosystem. What we might want to do is consider working on an address-next proposal that has an explicit timeframe of N years out, and very loud don't deploy this--- layered hashing is just one very minor slightly nice to have... things like coded expiration times, abilities to have amounts under checksum, etc. are probably more worth consideration. On Thu, Jan 4, 2018 at 2:23 PM, Luke Dashjr via bitcoin-dev wrote: > I know I'm super-late to bring this up, but was there a reason Bech32 omi= tted > the previously-discussed P2SH=C2=B2 improvements? Since deployment isn't = too > widespread yet, maybe it'd be worth a quick revision to add this? > > For those unfamiliar with the concept, the idea is to have the address in= clude > the *single* SHA256 hash of the public key or script, rather than > RIPEMD160(SHA256(pubkey)) or SHA256(SHA256(script)). The sender would the= n > perform the second hash to produce the output. Doing this would in the fu= ture > enable relaying the "middle-hash" as a way to prove the final hash is in = fact > a hash itself, thereby proving it is not embedded data spam. > > Bech32 seems like a huge missed opportunity to add this, since everyone w= ill > probably be upgrading to it at some point. > > Luke > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev