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 633F2AAB for ; Mon, 28 Aug 2017 17:06:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com [209.85.213.44]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DCEEE42C for ; Mon, 28 Aug 2017 17:06:05 +0000 (UTC) Received: by mail-vk0-f44.google.com with SMTP id l132so3054456vke.5 for ; Mon, 28 Aug 2017 10:06:05 -0700 (PDT) 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; bh=PZji/FG0lshDZYlwAZy6aK83es4JyOYhnwO4xxspwGM=; b=Bb2bbVZOMWGFdW296YKKd4LgJt/7m1veo9uKJBrlCIOUwdxaSTZ6UiqOY/FhZ4bUKt SDEDZ76V9kMpqz1JFGvEK3ZxqDzGdWH9WW1fvsmo4q5s3gN+8P5fwbznkIZw2v98BdoK NDF6lyseVopx5qGyXDDPcf0RzQr2bMOeRcr8O+LIXdhqkhNhpDwj5v689f4hO21ghL0u Oolw3DTc2GkpKdpkw029Um6hUE3EFDxoA51iBwHdF1t1boEvAJMm1avvKtB0EJz8M+a7 uVzEaJjLWqf7NYJcR2ZJYW8eaNqibsWV5oW7sOoNkGEwHznIhT3q5ivTubcCyH95MX8G R5mw== 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; bh=PZji/FG0lshDZYlwAZy6aK83es4JyOYhnwO4xxspwGM=; b=PXDZDmJC9J/b2XBe1EzSueQWJVga2W5EwfJ6eZUeZrGIC0yRIyhOpwACUanxfnzp0Q 5afJsuBptcpXOontr4wZg2Qug/raXvehf+nCYtPb2eVaapWw4lMvDIOcjDikbYkJb5a3 HbK2IqdJkJv6L7Xv1nfKrke65x6EYQAQ2NvseGYZ4jJQV6YFNCP21prA/ceVeQNmaXBq 1oGNMI85eEHjq5xfvyOHEEcW75rD2MZPc61EcJMpKAGqhkx6E6n5SisNWdV4aj8RkZCp Q5oowsafNBdbtqawuycYThk5gWiha7Ch/DeIb6Szq7zo+Jtz3SwZc601olvvomyd3wv4 biaw== X-Gm-Message-State: AHYfb5igOgF1uXRtk8dG+0jvrNMaGn4lgN1QYgHY0SC271utrcAL9J7W kfZpDozfh8dRWq7BUZnhEejwrtqQZA== X-Received: by 10.31.179.130 with SMTP id c124mr754110vkf.154.1503939964781; Mon, 28 Aug 2017 10:06:04 -0700 (PDT) MIME-Version: 1.0 Sender: gmaxwell@gmail.com Received: by 10.103.176.71 with HTTP; Mon, 28 Aug 2017 10:06:04 -0700 (PDT) In-Reply-To: References: From: Gregory Maxwell Date: Mon, 28 Aug 2017 17:06:04 +0000 X-Google-Sender-Auth: L_xlcOueZixTNp02GmLhw-X_oq0 Message-ID: To: Bitcoin Dev Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: [bitcoin-dev] Fwd: P2WPKH Scripts, P2PKH Addresses, and Uncompressed Public Keys 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: Mon, 28 Aug 2017 17:06:06 -0000 On Mon, Aug 28, 2017 at 3:29 PM, Alex Nagy via bitcoin-dev wrote: > If Alice gives Bob 1MsHWS1BnwMc3tLE8G35UXsS58fKipzB7a, is there any way Bob > can safely issue Native P2WPKH outputs to Alice? Absolutely not. You can only pay people to a script pubkey that they have specified. Trying to construct some alternative one that they didn't specify but in theory could spend would be like "paying someone" by putting a cheque in a locked safe labeled "danger radioactive" that you quietly bury in their back yard. Or taking the payment envelope they gave you stuffing it with cash after changing the destination name to pig latin and hiding it in the nook of a tree they once climbed as a child. There have been technical reasons why some wallets would sometimes display some outputs they didn't generate but could spend, but these cases are flaws-- they're not generic for all cases they could in theory spend, and mostly exist because durability to backup recovery makes it impossible for it to tell what it did or didn't issue. So regardless of your query about uncompressed keys, you cannot do what you described: Wallets will not see the payment and may have no mechanism to recover it even if you tell the recipient what you've done. And yes, the use of an uncompressed yet could later render it unspendable.