From: Tier Nolan <tier.nolan@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] About hardware accelerators advantages for full-node (not mining)
Date: Mon, 13 Jul 2015 14:47:57 +0100 [thread overview]
Message-ID: <CAE-z3OXezLpr+v3zgx3GeNqii3z06uC0u6GkGk9P8Adg_8d1NA@mail.gmail.com> (raw)
In-Reply-To: <c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1056 bytes --]
prev parent reply other threads:[~2015-07-13 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 12:55 Alex Barcelo
2015-07-13 13:47 ` Tier Nolan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE-z3OXezLpr+v3zgx3GeNqii3z06uC0u6GkGk9P8Adg_8d1NA@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox