jorbs/stellar-keypair-tool

A tool to generate vanity Stellar public address

Stellar Keypair Tool

A tool to generate vanity Stellar public address. It was implemented in C++ in order to use the NaCl EdDSA25519 implementation (https://nacl.cr.yp.to/sign.html), available throught libsodium.

Installation

1. Install libsodium (http://libsodium.org)
2. make

Usage

./keypair [-p|-m|-s] <term> [-j <jobs>]

It searches term for prefix, middle or suffix positions. term can have down case chars.

Concurrency

By default, this tool creates a number of threads based on the available CPUs. This number can be overrided using the -j parameter.

Address validation

In order to validate the generated public and secret keys, use the Stellar Javascript SDK (https://www.stellar.org/developers/js-stellar-sdk/reference/):

var keypair = StellarBase.Keypair.fromSecret('<your secret>');
console.log(keypair.publicKey());
console.log(keypair.secret());

stellar-keypair-tool's Issues

Replace strong random source with pseudo random?

We are trying millions of keys. Wouldn't picking a strong random seed, then doing deterministic randomness after that be a lot faster than reading new crypto-strength randomness each loop?

This might be a bad idea, but could be worth potentially large speed increases.

Implement elapsed time

The tool must feedback the user about the elapsed time.

Implement concurrency

• A parameter -j will define the number of jobs (threads) to search the public key;
• If that value isn't provided buy the user, then it needs to be automatically determined.

Use SUPERCOP implementation

Its randombytes function doesn't use /dev/urandom as source for PRNG. Using arc4random functions we will have a performance gain.

Concurrent usage?

I'm getting at least 20% faster generation per-core using this library than I am using the official Go library (which this other key-generation lib is using). However, it's trivial to use go routines to create more workers per CPU.

Do you have any plans for multiple CPUs, or is the source of random fine to simply spawn multiple instances?

Change function pointers to lambda

Use C++11 lambda instead of using function pointers.