Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 25F5647B6 for ; Tue, 22 Jan 2019 14:58:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gateway22.websitewelcome.com (gateway22.websitewelcome.com [192.185.47.228]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F234E6 for ; Tue, 22 Jan 2019 14:58:27 +0000 (UTC) Received: from cm12.websitewelcome.com (cm12.websitewelcome.com [100.42.49.8]) by gateway22.websitewelcome.com (Postfix) with ESMTP id E8AA58140 for ; Tue, 22 Jan 2019 08:58:26 -0600 (CST) Received: from gator4219.hostgator.com ([108.167.189.45]) by cmsmtp with SMTP id lxVSgxUaUiQerlxVSgH5RP; Tue, 22 Jan 2019 08:58:26 -0600 X-Authority-Reason: nr=8 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mybitcoincenter.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Cc:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=arx8NEYhumXnjZKKAQcFmmnWzvkww/qTXSZVlVIF7UI=; b=EkQcGHo0p4HsSH/MFWsgf9srB pq4H11gQwNfEYKFM+rBBD5j5mPaT0sCzvwhWS7kGDyEezhnlXpomjy07rfbUSNO47aACj0xYVFR9G 66eeVIGA1R47oC/mTUINcUhGFfTXpg8Bq6KsopsoKFrUUBrHMz4sj5skeB4y5YONDrfBrj/t+lRV/ rb8kaRw7eF0iRAy20fC2itBbexBpp0h4i3+imxOjUi1r0C0Quv2KLeribDWs2TVoeTr7v7mNPZTAC YuJJ2ZnOVvwyDt6rRWLNjMmQEOmup6upWTba9C/aqY02t5hqZa4+q5qDBQvIqA2fo1qJZUfIsRu+5 97YDrmU4g==; Received: from [77.234.46.214] (port=12134 helo=[100.98.22.24]) by gator4219.hostgator.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.91) (envelope-from ) id 1glxVS-002TNq-LQ; Tue, 22 Jan 2019 08:58:26 -0600 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Satoshin In-Reply-To: Date: Tue, 22 Jan 2019 09:58:25 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <9D2883DC-360C-401A-B518-B8205A3AAA53@mybitcoincenter.com> References: To: ZmnSCPxj , Bitcoin Protocol Discussion X-Mailer: Apple Mail (2.2104) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator4219.hostgator.com X-AntiAbuse: Original Domain - lists.linuxfoundation.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - mybitcoincenter.com X-BWhitelist: no X-Source-IP: 77.234.46.214 X-Source-L: No X-Exim-ID: 1glxVS-002TNq-LQ X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([100.98.22.24]) [77.234.46.214]:12134 X-Source-Auth: satoshin@mybitcoincenter.com X-Email-Count: 2 X-Source-Cap: bXlvZmZpY2VzO215b2ZmaWNlcztnYXRvcjQyMTkuaG9zdGdhdG9yLmNvbQ== X-Local-Domain: yes X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, 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 X-Mailman-Approved-At: Tue, 22 Jan 2019 19:53:57 +0000 Subject: Re: [bitcoin-dev] Proof-of-Stake Bitcoin Sidechains 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: Tue, 22 Jan 2019 14:58:28 -0000 This could could be a viable option. I think this is the right approach. Any downside to this and how much does this add to the blockweight if = anything at all. Anonymouse > On Jan 22, 2019, at 4:19 AM, ZmnSCPxj via bitcoin-dev = wrote: >=20 > Good Morning Matt, >=20 >> ### ZmnSCPxj, >>=20 >> I'm intrigued by this mechanism of using fixed R values to prevent = multiple signatures, but how do we derive the R values in a way where = they are > unique for each blockheight but still can be used to create signatures = or verify? >=20 > One possibility is to derive `R` using standard hierarchical = derivation. > Then require that the staking pubkey be revealed to the sidechain = network as actually being `staking_pubkey =3D P + hash(P || parent_R) * = G` (possibly with some trivial protection against Taproot). > To sign for a blockheight `h`, you must use your public key `P` and = the specific `R` we get from hierarchical derivation from `parent_R` and = the blockheight as index. >=20 >=20 >=20 > Regards, > ZmnSCPxj > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev