Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id F1421110D for ; Thu, 15 Mar 2018 07:37:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5ABED576 for ; Thu, 15 Mar 2018 07:37:17 +0000 (UTC) Received: from ip-10-217-1-36.ap-northeast-1.compute.internal (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id 22EB414C0D4 for ; Thu, 15 Mar 2018 16:37:16 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1) by 0 with SMTP; 15 Mar 2018 16:37:14 +0900 X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id A50534C072 for ; Thu, 15 Mar 2018 16:37:14 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw23.oz.hdemail.jp (ip-10-216-196-34.ap-northeast-1.compute.internal [10.216.196.34]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id 42DB214C0D4 for ; Thu, 15 Mar 2018 16:37:11 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qt0-f198.google.com (lb05.oz.hdemail.jp [54.238.57.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw23.oz.hdemail.jp (Postfix) with ESMTP id E483B148C115 for ; Thu, 15 Mar 2018 16:37:10 +0900 (JST) X-Received: by mail-qt0-f198.google.com with SMTP id v89so3862423qte.21 for ; Thu, 15 Mar 2018 00:37:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oNvlSEA0Ikq8wlxddwgfRcbBqkWfHJHDJgQXUpScLU8=; b=neDHkBoS0Li2WAofZiylNBP5hEbjz7SYrioisquMtn2o8P6dbXsysf8IN25dBGGPvC TIm89yAgbTWMjB8ddihPeCQmWAlo01um28SvjLzio8ryjfTR8F8GEYt/OM7hPz+LgI0o ZaBn6wMvq1ryw2QECflv2ppjaP/adZosgGTfh2sCBlRhxmkTEIhUvsmxDC0qHoc7ZD23 tT8dWgLli/X13uUT7Ldrz4tUDxmPyEeOweNv1Mj4kg3ApuuB3teiTzNXaeJ4Fe9dIAYd HaJuKiJ96FSxzC7oCyXPQhvdPuHHdP2wUuE0vto7jCk3usRWLKkWqhV3b1rv/EdGtrK0 kHog== X-Gm-Message-State: AElRT7HbElw6sKr/eVUF5cYcHN1kOdQCsOvxznTYf3JvB1GhLk9genTq PDzosiLOCpDvAWTHaJZaAy4aWJrdVdUig1zDZ9/5rTTyKpisHSPzvQkQrtWQgFg/6PYTLMqa4Yg C11ni4jpng0GKCkORBuyRUtbOSQCyRM1AYsvBkMiuas8aOLeji2oluW39fgrSmCBASFzDSphnel WJzWWLdICNPCmGAVW+ZVqVLXtvsNABiFJq54C5gwkgBQ7/Hnx0AXXCmXfIntlFmsL318PkyGcIv a6FYfk2YBqumgPxHb1VACW/XtzBR3UdrXfAA1WQhH84sroFh0t1PhSz06JB1XrqilEfmbqQluhP LNZYdLshfIyTiegcsxe5EZsHR00= X-Received: by 10.200.6.6 with SMTP id d6mr7416085qth.112.1521099429248; Thu, 15 Mar 2018 00:37:09 -0700 (PDT) X-Google-Smtp-Source: AG47ELsN4RaBFUjONNqv9tB3A74vYG0zIhRQb9Y7OjmB6jodib4O3yroY0kZsU+CwY/dgBWy36+GZUV8ZR9FJpkLqfg= X-Received: by 10.200.6.6 with SMTP id d6mr7416066qth.112.1521099428954; Thu, 15 Mar 2018 00:37:08 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.12.176.3 with HTTP; Thu, 15 Mar 2018 00:36:48 -0700 (PDT) In-Reply-To: <201803141236.48869.luke@dashjr.org> References: <201803141236.48869.luke@dashjr.org> From: Karl Johan Alm Date: Thu, 15 Mar 2018 07:36:48 +0000 Message-ID: To: Luke Dashjr Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] {sign|verify}message replacement 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: Thu, 15 Mar 2018 07:37:18 -0000 On Wed, Mar 14, 2018 at 12:36 PM, Luke Dashjr wrote: > Ideally, it should support not only just "proof I receive at this address", > but also "proof of funds" (as a separate feature) since this is a popular > misuse of the current message signing (which doesn't actually prove funds at > all). To do this, it needs to be capable of signing for multiple inputs. Re-reading this, I think what you mean is it should be possible to create a proof for (a) specific UTXO(s), hence "inputs". That sounds pretty useful, yeah! So you could provide a mix of addresses and inputs (as txid:vout) and it would generate a proof that signs the message for each input (taking scriptPubKey from address or from the UTXO data directly on the blockchain). -Kalle.