04 Июня я сделал депозит BTC.
Положил в lending 05 Июня.
Ну далее вы в курсе.
Выиграл в лотерею, только наоборот.
В тикетах стандартно посылают.
Заполнил форму в SEC. Полагаю, бесполезно, но хотя бы попытался..
В общем отжали битки по-черному. К Гопстопу больше солидарности.

Thank you. I would be very happy to do this. But I'm not able do more than few edits =D

I did an exception for char "1" in a code

I think it's impossible on regular GPU for next years

Well I just added more symbols to wildcard match function in Wildcard.cpp/GPUWildcard.h for finding exact patterns I want.
It's very easy to do. I shared my one https://github.com/skipper70/VanitySearch
I guess it's not a good way to go for production because we should write own regex on next steps =D

Finally I've found the perfect vanity for me!
https://www.blockchain.com/btc/address/1EKKKKLVMLHUUTSXMWGSBQGPATSBDCEEVH

It took ~one full day with 15MK/s
Huge thank you senior Jean_Luc
Also now I have a lot of pleasant addresses with only one number inside

I think I've found something.
Suddenly yesterday wildcard started to work well.
Speed 15MK/s is 5-6x slower than normal search which is perfect anyway.
During the time later the program behavior was going by random way. And I've closed firefox. Started to work well again.

In general I guess you could try debug the program in difficult memory conditions.

Just any command for wildcard search (* or ? symbols) with -gpu flag. I'm not even sure if the GPU works comparing to 100MK/s in normal mode. The OS is very lagging/hanging at the same time. GTX 750, Win10 and CUDA 10.1.

Thank you.
Hope to find solution for issue with my GPU. Feel free to contact. I will do everything what I can.
However I'm happy already. I can generate quickly a lot of suchlike addresses by VanitySearch (on CPU).
Pub Addr: 1333Q4HANHJM6G6XRGB4HV15LCGSUU93YM
Pub Addr: 1C27MV3VUKHR4FB9V3TXZ3PRRAJR3PCACM
Pub Addr: 1KWF2ZH7D3X7MMWWR56XV347TA9CKRD4CW

There are new commits on github.
It is huge work has done there.
Thank you a lot.

I am testing wildcard search now.
It is 10x slower on my CPU.
And 100x slower on GPU with hanging system.
Guess something wrong there.

Thank you very very much! I am really looking forward to a new commit.

GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128)
104.960 MK/s (GPU 94.405 MK/s) (2^32.12)

Oh my take my money I want buy that now

I can. But I guess it is possible by slow CPU regexp in slow Vanitygen only.
Please if you know something lmk about that

Awesome!
Hope to see all upper-case or all lower-case search. Also hope to see regexp search for finding whatever want.

I am not an expert but I guess there are some algos for base64 encoding/decoding on GPU:
https://www.codeproject.com/Articles/276993/Base64-Encoding-on-a-GPU
https://lemire.me/blog/2018/01/17/ridiculously-fast-base64-encoding-and-decoding/

Also there are several fast GPU regexp:
https://madhumithasridhara.github.io/QuickMatch/

Hello, @Jean_Luc!

First of all I want to say a big thank you for the amazing project you are developing. Just a huge pleasure to use it.
Had you been thinking about expanding pattern abilities? Search for a word at the end of an address or inside an address? What do you think about the implementation of regular expressions?
I know regex in vanitygen working with CPU only. I don't know if this is possible but I think it would be just awesome to see something like a hybrid algo for finding regex patterns faster.
Thank you!

Hey guys!
Thank you for every advice here.
At start I invested less then 0.1btc to MIN
I was just selling on lows and buying on tops.
Before falling I sold everything. It was predictible here.
Now I bought 12k+ MIN

Thank you.