Add secp256k1_ec_grind to grind keypairs #507
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nym-zone
added a commit
to nym-zone/secp256k1
that referenced
this pull request
Feb 13, 2018
sipa's pull request upstream: bitcoin-core#507 Thanks to gmaxwell for the tip: https://bitcointalk.org/index.php?topic=2934774.msg30174356#msg30174356
nym-zone
added a commit
to nym-zone/segvan
that referenced
this pull request
Feb 13, 2018
This is an early, experimental implementation of vanity search using the secp256k1_ec_grind() patch by Pieter Wuille (sipa). Initial tests find that for appropriate (not-too-short) patterns, vanity generation by this means runs 5x faster than the code currently on master. (This means a total of about a 25x speedup over the OpenSSL-based version I made in December.) Thanks to Greg Maxwell for the tip. References: - bitcoin-core/secp256k1#507 - https://bitcointalk.org/index.php?topic=2934774.msg30174356#msg30174356 My own code here code is unoptimized, and UNTESTED for correctness of outputs. I usually do not check code into a public repo unless I have at least verified that it produces correct privkey/pubkey/addr tuples. In this case, I am committing this while exhausted after many hours wrestling with a GNU autoconf problem (worked around by a one-line Makefile change in this commit), and then fixing a subtle stupid mistake I made. I may have made other dumb mistakes. Do not rely on this yet. THIS CODE MAY EAT YOUR COINS. I will test and clean it up later. Apologies for the non-atomic commit. There are a few reasons it had to be that way.
|
Tested ACK 885ea63 This PR is used as is in https://github.com/kallewoof/btcdeb/tree/vanitygen -- I verified that the keypair is valid. I grinded bc1qkallealmkdwwyuc2tmf5c6hzmlaujq6jl38hpe using this, and sent myself 10k goodly satoshi, which a wallet with the imported private key saw in its balance, and could sign transactions for. |
sipa
force-pushed
the
201802_grind
branch
3 times, most recently
from
37a2bdd
to
8c4df23
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unsure if this should be in upstream, but it may be useful for things like shaving off a few bytes from signatures.