summaryrefslogtreecommitdiff
path: root/93/6d0ea49ab0386ca390eb1fd9e148e572d5aa6c
blob: 54340cd3fbd640f4185d04e41bd6cb9989a4bca5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
Return-Path: <satoshin@mybitcoincenter.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 25F5647B6
	for <bitcoin-dev@lists.linuxfoundation.org>;
	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 <bitcoin-dev@lists.linuxfoundation.org>;
	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 <bitcoin-dev@lists.linuxfoundation.org>;
	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 <satoshin@mybitcoincenter.com>)
	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 <satoshin@mybitcoincenter.com>
In-Reply-To: <wTXHV7W_AXHz5xdhXJVJr2OdSpEOaFh0PBQubFdZv4JyF6SlImszj2QyF9G-_Dem06A3iBWLF3vdgiHC_NlsVqy7DFX5XTphajNnMqiU6r0=@protonmail.com>
Date: Tue, 22 Jan 2019 09:58:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D2883DC-360C-401A-B518-B8205A3AAA53@mybitcoincenter.com>
References: <CACV3+OU1ynRuR2SioW+O+CAp5M7ZQA6af_hEY5JZCVrXpqjtKQ@mail.gmail.com>
	<BTyUDt_7oOQmFj_V61w2eUJ7rfi-eOuNphy5nN0xNAhY4sUHnR2-0U9m-ZEKip4YjFi2-hGBtucvFv7nCTVo3aBxZ94VQCa1Kx2pP_zgdxU=@protonmail.com>
	<CACV3+OWjszx6istHo7yaNxiS22kyhHQhcPxGT3QLDx3KPUMU6g@mail.gmail.com>
	<nq9NDv6z-EJuJ9jGMWdlIZbpVM6Rm8QyuWL3nRYtXWF90I-cErA_WS1ib28kt950bZYyfF1_eP153aDjhUy523wYSM9TVaeHqeZdp3xJpsk=@protonmail.com>
	<CACV3+OXQsUsgquJWZ9o8tTtak=axnbsdiNgLzF-j6yz1dDv4bA@mail.gmail.com>
	<wTXHV7W_AXHz5xdhXJVJr2OdSpEOaFh0PBQubFdZv4JyF6SlImszj2QyF9G-_Dem06A3iBWLF3vdgiHC_NlsVqy7DFX5XTphajNnMqiU6r0=@protonmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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 =
<bitcoin-dev@lists.linuxfoundation.org> 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