I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290) yeah, of course it's fast... I generated my xchat adress this way, but when I imported this adres in my wallet and I asked my public key it gave me a public key witch was very long it was even you cryptogretzky who said it didn't work I would like to test something...
I made myself a vanity adress for xchat would someone please try to contact me over xchat?
adress: XCHATsLztdvJxb2BkrgVuoq7uoC73u6ghj pubkey: Ro4rYufnJy7RYFnuJBaD1iz5Rrr8o77fyKbcnkAbqC57JCS148WVMabshBjHd1JsZGoJ2JZtj6LYtfP e8bavoY51
(I've noticed that my pub key is really long, that's why I want to test this)
If it works I'll explain it in a tutorial
Said Invalid destination public key I do remember that test. Didn't know you use vanitygen before. The public key is extremely long too for me when I import the uncompressed private key. When I import the compressed private key though, the public key I get back is normal.... of course that defeat the purpose of the vanity address since the search is based on uncompressed address. So... ultimately, will need to modify the vanitygen to make it search based on compressed address instead of uncompressed address. eg. make the following changes in pattern.c len = EC_POINT_point2oct(pgroup, pubkey, POINT_CONVERSION_UNCOMPRESSED, eckey_buf, sizeof(eckey_buf), vxcp->vxc_bnctx); to make it use POINT_CONVERSION_COMPRESSED instead. Now... if only I can compile it....
|
|
|
I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290) Ok thanks, I need to try this. You should look for one that say XCTeka.... I am looking for one that is XCGretz... now Also... use -t to increase the # of workers to make it go faster. I've used the software before (with -t 16 ) but never for altcoins. I tried -t 24 seems to work for me, then I tried 1024 and it kinda locked up for some reason when it gets to 50%.... I thought it was one per thread? Ya, the speed up only lasted for like a few seconds, then it slowed back down to normal speed... although my 3 VM is still running smoothly in the background. So, I am sure I can push it if I want. 36 billions addresses so far... no XCGretz address yet... grrrr Inb4 all addresses have been generated and no new addresses can be made anymore. The amount of addresses that is possible is so large... so so large... 2 to the 160 power.... that's like ... 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 There are only 2^63 grains of sand on earth....
|
|
|
I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290) Ok thanks, I need to try this. You should look for one that say XCTeka.... I am looking for one that is XCGretz... now Also... use -t to increase the # of workers to make it go faster. I've used the software before (with -t 16 ) but never for altcoins. I tried -t 24 seems to work for me, then I tried 1024 and it kinda locked up for some reason when it gets to 50%.... I thought it was one per thread? Ya, the speed up only lasted for like a few seconds, then it slowed back down to normal speed... although my 3 VM is still running smoothly in the background. So, I am sure I can push it if I want. 48 billions addresses so far... no XCGretz address yet... grrrr
|
|
|
I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290) Ok thanks, I need to try this. You should look for one that say XCTeka.... I am looking for one that is XCGretz... now Also... use -t to increase the # of workers to make it go faster. I've used the software before (with -t 16 ) but never for altcoins. I tried -t 24 seems to work for me, then I tried 1024 and it kinda locked up for some reason when it gets to 50%....
|
|
|
I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290) Ok thanks, I need to try this. You should look for one that say XCTeka.... I am looking for one that is XCGretz... now Also... use -t to increase the # of workers to make it go faster.
|
|
|
I've used the vanitygen many times with other coins... but this time it conflicts with the public key...
I guess we could use cryptogretsky's way with the paper wallet gen.
Actually.... This works... vanitygen -X 75 XChat and it's blazing fast even without using the opencl version since it doesn't work for me (R9 290)
|
|
|
precompiled I tried to use -P (with a base pub key.. wich I used from my adres) and than -X XCHAT and it said... invalid base pub key I can't find much info on the issue Trying to compile my own now on windows. Pain in the butt. Getting errors and stuff. Will read through the vanitygen thread to see which library people are using now since I don't have vs2010 installed as they had originally.
|
|
|
Hey... there is the option -P
what would that give?
edit: ... nothing... invalid base public key...
Think you need to pass the 75 to -X instead of -P. Can you also pass in the prefix? Cause the prefix also needs to be changed to 0xCB. Did you compile vanitygen yourself or a precompiled version?
|
|
|
I've tried with the original vanitygen a while ago, but it screwed up the public key (it was way to long) and it didn't work with xchat I would like to test something...
I made myself a vanity adress for xchat would someone please try to contact me over xchat?
adress: XCHATsLztdvJxb2BkrgVuoq7uoC73u6ghj pubkey: Ro4rYufnJy7RYFnuJBaD1iz5Rrr8o77fyKbcnkAbqC57JCS148WVMabshBjHd1JsZGoJ2JZtj6LYtfP e8bavoY51
(I've noticed that my pub key is really long, that's why I want to test this)
If it works I'll explain it in a tutorial
If you got it working, defenitly let me now Did you modify the addrtype and privtype too?
|
|
|
On another note, I found a XC address that began with xchat! XCHaTxgu3cMtwokhSh2gsBBN5wUT77F6EK Took over a million searches.... How?! Did you generate the addresses while result | egrep -i '^xchat'? I modded the BIP38 paper wallet generator that Laredo created to find match based on some "vanity starting" parameters and it looped till it found it. It's really a rough hack job with no UI update for now.... I have to break into it to find out how many attempt it was at. My requirement was that it had to be BIP38, but of course... I really didn't have to really do that now since I know how to encrypt an existing private key using BIP38 now.... So, even a normal address creation would have sufficed.... You know there is a vanity gen creator that works even better. This was made for Darkcoin but seeing how both use the same address format, it should work. https://github.com/propulsions/DarkVanityGenDarkcoin prefix is 0xCC while XC is 0xCB. Network version is 0x4C for DRK and 0x4B for XC. Where can I change this prefix in the DarkVanityGen source? Edit: I think I found it. I need to change the addrtype and privtype in oclvanitygen.c right? I added this to the beginning of that parameter processing: while ((opt = getopt(argc, argv, "vqik1xNTXC:eE:p:P:d:w:t:g:b:VSh?f:o:s:D:")) != -1) { switch (opt) { case 'C': addrtype=75; privtype=205; break;
Let's see if it will work....
|
|
|
On another note, I found a XC address that began with xchat! XCHaTxgu3cMtwokhSh2gsBBN5wUT77F6EK Took over a million searches.... How?! Did you generate the addresses while result | egrep -i '^xchat'? I modded the BIP38 paper wallet generator that Laredo created to find match based on some "vanity starting" parameters and it looped till it found it. It's really a rough hack job with no UI update for now.... I have to break into it to find out how many attempt it was at. My requirement was that it had to be BIP38, but of course... I really didn't have to really do that now since I know how to encrypt an existing private key using BIP38 now.... So, even a normal address creation would have sufficed.... You know there is a vanity gen creator that works even better. This was made for Darkcoin but seeing how both use the same address format, it should work. https://github.com/propulsions/DarkVanityGenOooh nice. Thanks! I will definitely take a look.
|
|
|
Thank you After another million generation, I found an even better one. All caps! XCHATXJy4YhTscu7b3KJQi1Bc826EqmsUJ
|
|
|
On another note, I found a XC address that began with xchat! XCHaTxgu3cMtwokhSh2gsBBN5wUT77F6EK Took over a million searches.... How?! Did you generate the addresses while result | egrep -i '^xchat'? I modded the BIP38 paper wallet generator that Laredo created to find match based on some "vanity starting" parameters and it looped till it found it. It's really a rough hack job with no UI update for now.... I have to break into it to find out how many attempt it was at. My requirement was that it had to be BIP38, but of course... I really didn't have to really do that now since I know how to encrypt an existing private key using BIP38 now.... So, even a normal address creation would have sufficed.... Please give me a link to the paper wallet (I'd like address that starts with "XCurrency" and Node.js should do it in no time, but let's see). You probably also want to apply the change I made so it create compressed address: If you want the BIP38 generated address to be the same compressed format as the wallet (right now, it's in uncompressed format so it's not matching what you see in the receive coins address list): You will have to make the following change to line 7340: Change the false (2nd parameters): ninja.privateKey.BIP38GenerateECAddressAsync(ninja.wallets.paperwallet.intermediatePoint, false, function (address, encryptedKey) {
to true: ninja.privateKey.BIP38GenerateECAddressAsync(ninja.wallets.paperwallet.intermediatePoint, true, function (address, encryptedKey) {
Refresh the page. The generated address is now the same as you will see in the wallet and it will be easier for you to find an address that you like as a semi vanity address!
|
|
|
On another note, I found a XC address that began with xchat! XCHaTxgu3cMtwokhSh2gsBBN5wUT77F6EK Took over a million searches.... How?! Did you generate the addresses while result | egrep -i '^xchat'? I modded the BIP38 paper wallet generator that Laredo created to find match based on some "vanity starting" parameters and it looped till it found it. It's really a rough hack job with no UI update for now.... I have to break into it to find out how many attempt it was at. My requirement was that it had to be BIP38, but of course... I really didn't have to really do that now since I know how to encrypt an existing private key using BIP38 now.... So, even a normal address creation would have sufficed....
|
|
|
On another note, I found a XC address that began with xchat! XCHaTxgu3cMtwokhSh2gsBBN5wUT77F6EK Took over a million searches....
|
|
|
If you want the BIP38 generated address to be the same compressed format as the wallet (right now, it's in uncompressed format so it's not matching what you see in the receive coins address list): You will have to make the following change to line 7340: Change the false (2nd parameters): ninja.privateKey.BIP38GenerateECAddressAsync(ninja.wallets.paperwallet.intermediatePoint, false, function (address, encryptedKey) {
to true: ninja.privateKey.BIP38GenerateECAddressAsync(ninja.wallets.paperwallet.intermediatePoint, true, function (address, encryptedKey) {
Refresh the page. The generated address is now the same as you will see in the wallet and it will be easier for you to find an address that you like as a semi vanity address!
|
|
|
So it still just rewards % of xc owned?
XMixers get a fee from from each transaction they process, separate from staking interest Can the 550 XC being used for mixing still be staked?
|
|
|
|