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
|
Return-Path: <tier.nolan@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D9D769F2
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 13:47:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f42.google.com (mail-qg0-f42.google.com
[209.85.192.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7DEBD7C
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 13:47:58 +0000 (UTC)
Received: by qgep37 with SMTP id p37so64202531qge.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 06:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:cc
:content-type; bh=tx6QEpj39jZyo43ltyBNtXS+WBee0UQQER1xLECSm38=;
b=p4/6twU9dH9ozq9e1paNq9Sb9A0tarLLs8bXV9cGxGeHUNi3TZWOwmqpuhhEp2/Fvj
T5KtQ1B0l7Sm1n3afJFIfgKCtuBokgn7u/cDh9W9oD+ju2JNPvBUfbghBroAtwd5cOvP
0rUg6gpwAr+pErJetxAAx2981RqOFDTy38tUfOHWHRlNrreHd+NlCW0GwhTsKjXUWtVV
5Seloqwn6Zy3sybulgOrUwwAtbqhc4xcK60QemN/mOOkoFn4kdQzTaDNF7oVGa9WmitG
UdmeBqCZeFw8ir+pGZz2Lqq6mBHQbOYaGpHwKGLg8cTTn166AKpLz80nMilLNta6ugJG
QXKg==
MIME-Version: 1.0
X-Received: by 10.140.217.149 with SMTP id n143mr57149155qhb.9.1436795277704;
Mon, 13 Jul 2015 06:47:57 -0700 (PDT)
Received: by 10.140.93.162 with HTTP; Mon, 13 Jul 2015 06:47:57 -0700 (PDT)
In-Reply-To: <c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net>
References: <c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net>
Date: Mon, 13 Jul 2015 14:47:57 +0100
Message-ID: <CAE-z3OXezLpr+v3zgx3GeNqii3z06uC0u6GkGk9P8Adg_8d1NA@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1137351824857f051ac1f8ac
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MISSING_HEADERS,
RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] About hardware accelerators advantages for
full-node (not mining)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 13 Jul 2015 13:47:59 -0000
--001a1137351824857f051ac1f8ac
Content-Type: text/plain; charset=UTF-8
The main processor load is for signature verification.
This requires a hash function call, some large number maths and an elliptic
curve operation. The elliptic curve stuff is the longest step.
This takes around 1ms per signature on normal hardware, but optimized code
is faster.
The main task is to prove that
R = u1 * G + u2 * Q
G is a constant, and the rest are different per signature.
Some of the core team have created a fast CPU implementation.
https://github.com/bitcoin/secp256k1.git
There was talk of batch verification of signatures. The process might take
16 signatures and compute them together.
I think a lot of the benefit of the GPU would be lost due to communication
bandwidth. GPU miners benefit from needing very little information to be
sent to the GPU routine.
--001a1137351824857f051ac1f8ac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>The main processor load is for signature ve=
rification. <br><br></div><div>This
requires a hash function call, some large number maths and an elliptic=20
curve operation.=C2=A0 The elliptic curve stuff is the longest step.<br></d=
iv><div><br></div>This takes around 1ms per signature on normal hardware, b=
ut optimized code is faster.<br><br></div><div>The main task is to prove th=
at <br><br></div><div>R =3D u1 * G + u2 * Q<br><br></div><div>G is a consta=
nt, and the rest are different per signature.<br></div><div><br></div><div>=
Some of the core team have created a fast CPU implementation.<br><br>=C2=A0=
<a href=3D"https://github.com/bitcoin/secp256k1.git">https://github.com/bit=
coin/secp256k1.git</a><br><br></div>There was talk of batch verification of=
signatures.=C2=A0 The process might take 16 signatures and compute them to=
gether.<br><br></div>I
think a lot of the benefit of the GPU would be lost due to=20
communication bandwidth.=C2=A0 GPU miners benefit from needing very little=
=20
information to be sent to the GPU routine.<br></div>
--001a1137351824857f051ac1f8ac--
|
