Notice: As a pseudonymous developer who can only pay in BTC, I am currently seeking a legitimate means of Amazon EC2 access. The most immediate (but not only) motivation therefor is for work on a segvan client/server trustless tweak generator. Trustworthy persons with their own EC2 accounts are invited to work with me. This is for long-term legitimate development: I am NOT trying to buy an account; offers of such will be treated as spam.

(Translation: Plan A embraced BCH, and lacked EC2s flexibility anyway.)

Quote from: mattcode on March 10, 2018, 02:29:02 PM

Quote from: nullius on February 13, 2018, 01:54:39 PM

Ive also been seriously mulling ideas for an online service which finds vanity tweaks for a private key held by a useressentially, convenient results from rented time on powerful CPUs in the cloud (much though I loathe that word). Im curious as to how popular such a service could be. Anybody interested?

I'd be interested in a service like that. Please could you PM me if you ever get round to doing it? Thanks :)

Please see above. Im currently trying to do a 2⁴⁵ (9 characters of Bech32) search on a very slow laptop; I estimate that after both cores spin sipas keygrinder 24/7 for two months, I will then have about a 1% chance of having found a match. Getting access to some fast cloud computing would give me both the impetus and the opportunity to develop a production-quality client/server implementation.

Quote from: mattcode on March 19, 2018, 09:46:50 PM

I just used segvan to find 3Jjjjj8466bZXCFJQGDk1reaAXwrri39Vz, 3AAaAAMy2auJ1c5wCRj7Qbzx8qshh9cVrx and 3FffFFLntXU14ePkYK3pyASx2Smaw5TfF1 :)

Unfortunately I had to build from master instead of the sipa_grind branch so I think I'm missing out on the huge performance improvements. Is the sipa_grind meant to be working right now?

I also noticed the 333333mR6i1xHnDQAy1xUwvbGXFqjGgzUU address in your signature and profile!

Apples to apples, rounding liberally, the same patterns with the same codepath give me about 7000 keys/sec generating keys one by one, and 35000 keys/sec with sipas keygrinder. Thus, about a 5x speedup. (For comparison, with OpenSSL on the same hardware, I maxed out at about 1400 keys/sec. Cores secp256k1 really blows OpenSSL away; it is something to be most thankful for when synching the blockchain.)

Quote from: Velkro on March 16, 2018, 02:28:20 AM

If you want this to become more popular like vanitygen original version, you need to make windows version of it.
Most users using Windows while generating their private keys. You need above average knowledge to compile it yourself and use linux.

Please see the discussion of Windows porting in a Segwit vanity address generator request thread which pushed me to make an initial release of segvan.

My current priorities are approximately:

0.0. Stable, feature-complete, well-tested implementation on FreeBSD and Linux. This is much more popular than Id expected when I whipped up v0.0.0 on an idle afternoon in December. I want to do it right.

0.1. Packaging on FreeBSD ports and at least one or two popular Linux distributions such as Debian (depending on acceptance by those with commit bits). This would cut down on the above average knowledge to compile it part. As of this writing, there are 31593 FreeBSD ports available; and the Debian homepage currently claims >51000 packages. I understand that lack of application compatibility is one of the major problems faced by Microsoft Windows users; and if I have a popular application, I will try to see how I can help with that.

1. Online services, possibly including a stripped-down trustless tweak generation client usable in some way with Microsoft Windows, among others. This is a high priority to me, since I myself am poor in hardware; and the v1 network protocol I have in mind would make it almost trivial to support securely ordering up vanity addresses from your Windows PC, your iPhone, or whatever.

2. If that does not resolve demand, then maybe a Windows port, potentially with fewer features. The modularization I am now doing should help with portability. For example, one of the first roadblocks I hit with a mingw build was POSIX regex support. The ultra-fast prefix checker Im currently playing with is portable C code; a Windows build might include that and omit regex support, at least initially.

Quote from: Sellingaccs on March 19, 2018, 10:03:49 PM

Code:

pc@pc:~/segvan$ ./segvan -r accs

Anchored regexes will usually be significantly faster (or less slow, depending on your perspective). Thus, try ^bc1qaccs unless you truly desire every match appearing anywhere in the string. Giving the HRP/separator prefix is necessary, since segvan currently matches against a whole address; and no warning will be given if you provide an impossible pattern.