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
|
Return-Path: <nickodell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4BF85B93
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Dec 2016 17:35:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com
[209.85.218.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B389423E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Dec 2016 17:35:50 +0000 (UTC)
Received: by mail-oi0-f42.google.com with SMTP id v84so275945218oie.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Dec 2016 09:35:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=7tcuIGc2HqPKi21nwG1Pgaozi3GeC37c0f0EW1soVNU=;
b=TIl/Kx9n0joG3Z7qk9c5hxKvlgZpirP0Xe+/x1r3ZnTVXio5Wfds4BlS4LZPtfoMok
GpJqGo65J2gT0HnKHAYbmJnUsi9V/v4qfKQl+LOU62GxgJHDm6chh/0gPrnc6vqQq+fq
xL+gCfZIn3tTOirGgmkl2ulZJp4+Wj0iT1AFZ+jj3mF40YVJiYuJjN39cGwjcos6inJd
73NHQgXOH3Na7bp1FZAlqDpCqWGS7FAKLNQzHDavxnbjeOFLWjs55BPGiIkDR/lHrXBg
ltWeT6lqw5s4YjEtYyDfJxsA5eHlr2MLy3JmrVPs6zNcDTRFPe6nVYE32Nh+s33834Pd
nOTg==
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;
bh=7tcuIGc2HqPKi21nwG1Pgaozi3GeC37c0f0EW1soVNU=;
b=EMxEq1HpLNb4Rts/IbwRkJECFHddK3nRZzYnheLtkXk8ot4kPYKYnNnJeIoQrKTxmX
/0E7bothGrxCpn538P2ddzT3OvrclXRLDTyvJGQQ3v7zI6ena8PCCbiPIRW4TGAsJmul
BbUhR0vhcUAx6zTxTNFSgNrWVRYMy/cGTba/3ZU3An2YOgc56eNXUHElkfCrTFhzr38b
Zugsyb3yNB2UOuahvDGwgeyQ4nseRSA1yyVG4N4uLjt32Y/2RFLm+IutPcOCZOXouvAP
ToO2/iGdYqg3DzS0usF/+NgqLGPrxlqti0lhNmlVsfV7mMAP30ZLv2tTKy9zwgjqNlOv
jGOQ==
X-Gm-Message-State: AIkVDXIbYeSihS99rBkn1XR97D823DwjgpMjqXHH/3uOWmoLA50p96K/OdlKxc8sxj3wFpwuHiM4AmVWgiQzxg==
X-Received: by 10.157.20.35 with SMTP id h32mr8814650oth.37.1482514550029;
Fri, 23 Dec 2016 09:35:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.194.74 with HTTP; Fri, 23 Dec 2016 09:35:49 -0800 (PST)
In-Reply-To: <CAL8tG=n6NnTaeV71-sWi3Bvk_8E8F20_69f90k-Shrc4XXUQog@mail.gmail.com>
References: <CAL8tG=n6NnTaeV71-sWi3Bvk_8E8F20_69f90k-Shrc4XXUQog@mail.gmail.com>
From: Nick ODell <nickodell@gmail.com>
Date: Fri, 23 Dec 2016 10:35:49 -0700
Message-ID: <CANN4kmcQGehMAVWdvakOam6n=crVnv5Gc6WGMg6WCstkD3XRPw@mail.gmail.com>
To: Andrew <onelineproof@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, 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] Multisig with hashes instead of pubkeys
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: Fri, 23 Dec 2016 17:35:51 -0000
The first issue is that doing two OP_SWAP's in a row will just return
you to the original state. The second issue is that all of them end up
hashing the same key, so anyone on the network can spend this output.
(See https://en.bitcoin.it/wiki/Script for a good resource on opcodes
and what each of them do. There are also a few simulators floating
around, but I can't recommend any in particular.)
Third, if you're concerned about exposing public keys, why not use a
P2SH script? That won't expose your public keys until you spend from
it.
On Thu, Dec 22, 2016 at 11:29 AM, Andrew via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi
>
> Is there a worked out scriptPubKey for doing multisig with just hashes
> of the participants? I think it is doable and it is more secure to a
> compromised ECDSA. I'm thinking something like this for the
> scriptPubKey:
> 2 OP_SWAP OP_SWAP OP_SWAP OP_DUP OP_HASH160 <pubKeyHash1>
> OP_EQUALVERIFY OP_DUP OP_HASH160 <pubKeyHash2> OP_EQUALVERIFY OP_DUP
> OP_HASH160 <pubKeyHash3> OP_EQUALVERIFY 3 OP_CHECKMULTISIG
>
> and <sigs><pubkeys> for the scriptSig
>
> Can anyone confirm or send me a link to the worked out script?
>
> Thanks
>
> --
> PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
