VanitySearch (Yet another address prefix finder) - page 26.

BASE16

member

Activity: 180

Merit: 38

If such undesired results occur i would not call that method reliable or could term it even as being risky.
So its not a good idea to take that same route again once more.
In stead you can try other methods, or even roll your own script to mine for the correct vanity key's and address in a way that you understand what is going on and so as to prevent yourself from making these mistakes again.

TheArchaeologist

sr. member

Activity: 310

Merit: 727

---------> 1231006505

Quote from: GazetaBitcoin on July 14, 2020, 08:05:21 AM

I'll give this program another try and I'll let you know how it works.

Ok, nice. And if you do run into problems can you make some screendumps from the steps you took? That would make it a lot easier to reproduce. Although I don't expect you to run into trouble this time since the -u parameter is no longer supported.

GazetaBitcoin

legendary

Activity: 1680

Merit: 6524

Fully-fledged Merit Cycler|Spambuster'23|Pie Baker

I'll try again and see how it goes. I didn't use the -u parameter (I performed just the steps mentioned by 1miau in his topic) and I saw that my address was watch-only.

The users from the quoted topic seem to have user that parameter though. I can't offer the topic link, as those quotes were given by 1miau to me in that specific form... But I think they quotes are somewhere in this topic.

I'll give this program another try and I'll let you know how it works.

TheArchaeologist

sr. member

Activity: 310

Merit: 727

---------> 1231006505

Quote from: GazetaBitcoin on July 14, 2020, 04:56:11 AM

However, why don't you try to create a vanity address and then import it in Electrum? You'll see by yourself. And to be sure, create two addresses: ine starting with 1 and the second one starting with 3. I remember I created one starting with 3.

That works flawless.

So based on the info you gave this specific situation happened:

An old version of vanitygen was used
In this old version the -u parameter was used (no longer available) which generates an uncompressed pubkey
This uncompressed pubkey was then used to wrap into a P2SH script (by vanitygen) to generate an address starting with 3
The WIF for the 3-address was then imported to Electrum
Electrum now threats the addres as an P2SH wrapped P2WPKH
But since P2WPKH public keys are not meant to be uncompressed Electrum throws an error when you try spending. So in order to unlock the locking script Electrum doesn't know how to handle this.

So all in all it seems like a combination of events. Can you link to the topic you quoted from as I wonder how many people got their funds locked up in this way.

BASE16

member

Activity: 180

Merit: 38

This happened because you used (hash of) a uncompressed pubkey.
Uncompressed public key starts with prefix '04' and can not (yet) be used in this process.
Compressed public key starts with prefix '02' or '03' depending on odd or even on the curve point and these can be used in this process.
That wallet software clearly tells you that these can only work with compressed public keys so any funds you send will most likely become undependable.

GazetaBitcoin

legendary

Activity: 1680

Merit: 6524

Fully-fledged Merit Cycler|Spambuster'23|Pie Baker

This is not my screenshot...if you would look at the quoted text, you could see that the screenshot belongs to someone else. I just wanted to show another example (excepting mine and 1miau's) when someone couldn't spend the funds sent to a vanity address. In my case, I did not lose any money. I saw the address was shown as watch-only in Electrum, and I didn't send any funds to it. Thus, my problem was that I had a vanity address which I could use only for signing messages and for my own vanity... But 1miau and that user lost the funds they previously sent to the vanity addressand this is a severe issue.

I did not mention my steps as I din't remember them precisely - it was a few months ago. But I made all the steps needed and I also had available 1miau's tutorial.

However, why don't you try to create a vanity address and then import it in Electrum? You'll see by yourself. And to be sure, create two addresses: ine starting with 1 and the second one starting with 3. I remember I created one starting with 3.

TheArchaeologist

sr. member

Activity: 310

Merit: 727

---------> 1231006505

Quote from: GazetaBitcoin on July 14, 2020, 04:07:27 AM

I did all the necessary steps

Except for listing them here.

The problem sure isn't the address itself. Based on the screenshot is seems you imported the private keys as P2WPKH or P2WPKH-P2SH,while your WIF starts with a 5. Did you prefix the wif with p2pkh: when importing?

GazetaBitcoin

legendary

Activity: 1680

Merit: 6524

Fully-fledged Merit Cycler|Spambuster'23|Pie Baker

I did all the necessary steps

Furthermore, I also had avaliable a tutorial written by 1miau: How to add a Bitcoin address to Electrum / difference sweep and import priv. key. Of course I imported the private key - I was also able to sign a message.

And yes, I know that these addresses are supposed to be used as normal ones...

However, excepting the problem encountered by me (to see the address as being a "watch-only" one), 1miau told me he received an error when he tried to spend funds from the vanity address. Furthermore, others encountered also this problem:

Quote from: feryjhie on May 23, 2019, 05:56:25 PM

Quote from: 1miau on May 23, 2019, 05:48:31 PM

Quote from: feryjhie on May 18, 2019, 11:09:03 PM

done

btw a few days ago i made a vanitysegwitaddress from an older version which is 1.11 but when i try to spend the balance in that address it turns out an error like this

so there is no way to spend the balance again? because of uncompressed addresses?

Hi, may I ask if you get your problem solved?

i ask the creator and he answers that i can't spend my bitcoin from that address
because i create using -u command which generates an uncompressed addresses

Quote from: feryjhie on May 23, 2019, 08:03:46 PM

Quote from: 1miau on May 23, 2019, 06:59:32 PM

Quote from: feryjhie on May 23, 2019, 05:56:25 PM

i ask the creator and he answers that i can't spend my bitcoin from that address
because i create using -u command which generates an uncompressed addresses

So sad. Are you sure that there is no way to spend the bitcoins? I thought it's just Electrum why it doesn't work. If it's not possible to spend bitcoins from such an uncompressed addresses why he has added -u as option Huh

It's not only an useless option, it's a dangerous option. Cheesy

Maybe add a warning to your guide that people shouldn't use -u and if they use it, the bitcoins are lost. (if that's the case)

Are you really sure that the BTC are lost forever? I think it's still possible to use bitaddress, to get the compressed/uncompressed privkey and import it. The address wil be another one but the bitcoins are on both addresses (theoretically).

jean_Luc already disable a feature to generates an address from -u commands
i think we can still spend from compressed/uncompressed addresses but as long it's not a segwit address

TheArchaeologist

sr. member

Activity: 310

Merit: 727

---------> 1231006505

Quote from: GazetaBitcoin on July 14, 2020, 03:17:44 AM

Due to the above mentioned problems, I am asking the following: are the vanity addresses useful just for own vanity of the owner? Can't them be used for spending funds?

As far as I see it, such an address can only be used for vanity purposes or for signing messages using Electrum. Is this a bug or am I missing something here?

The whole idea of a vanity address is you can use it just as a normal random generated address. So you should be able to spent from the address once it is funded.

I'm not sure what you did to import to Electrum as I don't use Electrum myself. But since Electrum says "watch-only" address it seems you did not use the Private Key or WIF to import. So my question is: what steps did you take after generating to import in Electrum?

GazetaBitcoin

legendary

Activity: 1680

Merit: 6524

Fully-fledged Merit Cycler|Spambuster'23|Pie Baker

I don't know if this question was posted here before, as I didn't go through all the 37 pages of the thread. I tried a while ago to generate a vanity address and then to import it in Electrum. When I imported it, Electrum said it is a "watch-only" address.

Furthermore, after some talking to 1miau, the author of the topic [Guide] How to create your customized Bitcoin-Address (vanitygen) – step by step, he told me that he once sent some funds to the generated address, but when he tried to spend them (from the vanity address which was also imported in Electrum), he received an error and he was unable to send the funds.

Due to the above mentioned problems, I am asking the following: are the vanity addresses useful just for own vanity of the owner? Can't them be used for spending funds?

As far as I see it, such an address can only be used for vanity purposes or for signing messages using Electrum. Is this a bug or am I missing something here?

jollygreenmidget

newbie

Activity: 8

Merit: 0

Quote from: Jean_Luc on June 24, 2020, 09:51:27 AM

@student
If you are looking for full addresses, do not enter in the list a part of them (for instance the 15 first char)
It will be faster to enter full addresses.
That's true that there is 2^96 priv key for an address and if you perform 2^96 key you will find a collision but that would also imply that you search for the whole address range, on the blockchain there is no 2^160 address with fund and it is not possible to have a file of 2^160 address.
So if you want to find a collision between 2 priv key that give the same address, consider using BTCCollider which would require "only" 2^80 operations to reach the collision.
https://github.com/JeanLucPons/BTCCollider

Is it possible to specify prefix and seed?

bangbumbang

jr. member

Activity: 41

Merit: 1

Quote from: philipma1957 on July 05, 2020, 01:22:10 PM

Anyone know what the following 4 cpus will do

amd 9 3900x
amd 9 3950x

amd 9 3960x thread ripper
amd 9 3970x thread ripper

no but i just tried my ryzen 5 3600 6 core so 12 threads
with -t 11 it gets 13,5 mk/s

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

Quote from: DaveF on April 29, 2019, 09:27:50 AM

Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them.
I know it's a newer project and Jean_Luc is working VERY VERY hard on it so getting accurate numbers is going to be a moving target. But for now all we can do is look through the thread and see who is running what to get a general idea.
So far I have pulled from this thread:

GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128)
914.418 MK/s (GPU 896.216 MK/s)

GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
220.180 MK/s (GPU 220.180 MK/s)

GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128)
10.233 MK/s (GPU 7.026 MK/s)

GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1535.880 MK/s (GPU 1470.257 MK/s)

Added 30-April-2019

GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)
321.929 MK/s (GPU 321.929 MK/s)

GPU: GPU #0 GeForce GTX 1080 (20x128 cores) Grid(160x128)
672.062 MK/s (GPU 672.062 MK/s)

Added 1-May-2019

GPU: GPU #0 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #3 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #2 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
GPU: GPU #1 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128)
7260.449 MK/s (GPU 7212.931 MK/s)
So 7260 / 4 = 1815 MK/s

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

Added 3-May-2019
i7-7700K CPU Number of CPU thread: 8
22.092 MK/s (GPU 0.000 MK/s)

With -t 7
Number of CPU thread: 7
21.609 MK/s

Added 8-May-2019

EVGA RTX 2080 XC ULTRA
1427.967 MK/s (GPU 1424.946 MK/s)

Added 23-May-2019

GPU: GPU #0 GeForce GTX 1660 Ti
961.319 MK/s (GPU 961.319 MK/s)

GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
GPU: GPU #1 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
5128.213 MK/s (GPU 5128.213 MK/s)
So 5128 / 2 = 2564 MK/s

Added 8-June-2019

GPU: GPU #0 GeForce GTX 960M (5x128 cores) Grid(40x128)
117.802 MK/s (GPU 117.802 MK/s)

Added 23-July-2019

GPU: GPU #0 GeForce GTX 1660 (22x64 cores) Grid(176x128)
839.061 MK/s (GPU 839.061 MK/s)

Added 25-July-2019

GPU: GPU #0 GeForce GTX 1650 (14x64 cores) Grid(112x128)
511.906 MK/s (GPU 511.906 MK/s) (2^36.97)

Added 21-Nov-2019

GPU: GPU #0 GeForce GTX 970 (13x128 cores) Grid(104x128)
360.322 MK/s (GPU 331.442 MK/s) (2^32.77)

Added 25-Nov-2019

GPU: GPU #0 GeForce GTX 980 (16x128 cores) Grid(128x128)
375.384 MK/s (GPU 375.384 MK/s)

GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[1361.71 Mkey/s][GPU 1361.71 Mkey/s]

GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256)
[2001.52 Mkey/s][GPU 2001.52 Mkey/s]

Anything else?

-Dave

Last updated 25-Nov-2019.

Anyone know what the following 4 cpus will do

amd 9 3900x
amd 9 3950x

amd 9 3960x thread ripper
amd 9 3970x thread ripper

zedderzed

newbie

Activity: 2

Merit: 0

It produces such an error "GPUEngine: CudaGetDeviceCount CUDA driver version is insufficient for CUDA runti
me version 35" I have a video card gt550ti cuda 7.5

WanderingPhilospher

full member

Activity: 1162

Merit: 237

Shooters Shoot...

Quote from: zedderzed on July 01, 2020, 10:47:15 PM

please tell me where and how to register the path to the version of the CUDA I have an old version CUDA

If you are trying to update the code to go from 11.0 to one lesser like 10.0:
Located in the

Code:

VanitySearch.vcxproj

file:
https://github.com/JeanLucPons/VanitySearch/blob/master/VanitySearch.vcxproj

Line 100:

Code:

and line 171:

Code:

Bring up VanitySearch.vcxproj and do search for Cuda 11...just in case there may be more than those two above.

zedderzed

newbie

Activity: 2

Merit: 0

please tell me where and how to register the path to the version of the CUDA I have an old version CUDA

bangbumbang

jr. member

Activity: 41

Merit: 1

Quote from: student4ever on June 25, 2020, 10:03:50 AM

Quote from: TheArchaeologist on June 25, 2020, 06:20:37 AM

I don't know what you mean by "published" their pubK

PubK are only published if the adress has been used for an outgoing transaction. Of course ~ 80% of the adresses had an outgoing transaction, but for example the big wallets like 1Feex... has never had an outgoing transaction - therefore the pubK is not "published" on the blockchain.
Once again: my goal is not to find wallets with balance. My goal is to find lyrical prefixes.

Now I started something for such an "AI". Yes, it is nonlinear, but with a big dataset and epoches the AI may could crack the whole process, because it is still static, since A -> B. I took 50k pairs of random uncompressed adresses and splitted them into 2 cvs with input and output. I started 100k epoches. If it does not work it is ok, but it is worth a try.

ok, cool, post your finding here :-)

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: math09183 on June 26, 2020, 01:29:37 AM

So probably a few seconds of planned LHC successor... Is yours as sensitive as LHC and also detects TGVs?

No, I'm not working in a collisioner but in a light source. We accelerate electron (6Gev) to produce hard Xrays.

Quote from: math09183 on June 25, 2020, 01:21:03 PM

Coal-running GPUs ;-) It would be interesting to calculate how much CO2 was produced for it.

Something like ~15/20tons of CO2 if considering that all coming from coal.

math09183

member

Activity: 170

Merit: 58

Quote from: Jean_Luc on June 25, 2020, 04:28:00 PM

Quote from: math09183 on June 25, 2020, 01:21:03 PM

Wow... 1000 years of of 1000W coffee machine running 5minutes per day ;-)

And few hours of operation of the accelerator where I'm working and few minutes of operation of the LHC Cheesy

So probably a few seconds of planned LHC successor... Is yours as sensitive as LHC and also detects TGVs?

Quote from: math09183 on June 25, 2020, 01:21:03 PM

GPUs are in Poland?

Yes

Coal-running GPUs ;-) It would be interesting to calculate how much CO2 was produced for it.

Topic: VanitySearch (Yet another address prefix finder) - page 26. (Read 32072 times)