-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vanitygen for MOONcoin #13
Comments
You can just add its configuration into file base58prefix.txt. Format is:
You need to know the ‘address base58 version’ and ‘private key base58 version’. |
tnks! |
@bobkasho Have you found ‘address base58 version’ and ‘private key base58 version’ for Mooncoin? |
unfortunately I don't quite understand this question :( |
@bobkasho I have commit the code, help me to verify it. Here is an example:
|
https://chainz.cryptoid.info/moon/address.dws?2abcdz7jEQUXNxFhqoqNX4duPw8LUkR2G8.htm |
The coin also has a prefix "M" - it is more modern. "2" is already deprecated |
I am not very familiar with Mooncoin.
The value You can customize prefix MMMM, please don't send too much coin to the generated address before you verified. All coins may be lost forever. Use as your own risk. |
but what is correct for Windows? "C:\vangen152>vanitygen.exe -C MOON -F script -X 50 -Y 131 Moon C:\vangen152>" |
@bobkasho Have you see any Mooncoin address starts with 'Moon' ? May be it's impossible, you can try another prefix:
|
@10gic C:\vangen152>vanitygen.exe -C MOON -F script -X 50 -Y 131 Mmnm C:\vangen152> |
@bobkasho There is no vanitygen.exe in this project, only vanitygen++.exe. How did you get this program? |
@10gic please link |
I don't use Windows. You can build it by yourself, or download a prebuilt https://github.com/10gic/vanitygen-plusplus/releases/download/v0.1.0/prebuilt.win32.v0.1.0.zip As file base58prefix.txt is not shipped in package, you can't use |
@10gic dont cool :( |
@10gic |
@bobkasho The second character doesn't required be "M", it's just an example. You can use another prefix:
Again, I am not familiar with Mooncoin, use as your own risk. You need verify the generated private key. |
Currently, Many people report that oclvanitygen++.exe doesn't work in Windows. Could you help me check if oclvanitygen++.exe works for legacy mooncoin address? Just run:
See what happens? |
@10gic |
It seems calc_addrs.cl is missing. Could you download file https://raw.githubusercontent.com/10gic/vanitygen-plusplus/master/calc_addrs.cl into the same directory of oclvanitygen++.exe, and run it again? |
|
Thanks for share the result. This is not good news. Currently, I don't have a windows device, and I don't have time to fix this problem. Suggest you use vanitygen++.exe in Windows, or try oclvanitygen++ in CentOS. The fix of this issue is welcome. |
@10gic |
There are two common types of P2SH address: MULTISIG and segwit address. The vanitygen-plusplus/vanitygen.c Line 114 in b48cca3
Very likely, the "M" address in Mooncoin is the segwit address. If so, you would not get the matched address after import private key. I will check it later. |
@bobkasho Could you help me confirm that the following information matches?
|
OK! I started importing. it will take up to one hour |
@bobkasho I see a button "Generate native segwit (Bech32) address" in GUI, is the "M" address a native segwit (Bech32) address? BTW, what's the address derived from private key: 5PiUadgWDWjGcVHCKctSq1RiCRY1Y2CCKZrX8PgaJTwKUBeYnKs ? I can't find the technical doc about Mooncoin address derivation. The BTC address derivation is very clear: https://en.bitcoin.it/wiki/Invoice_address. I want to find similar technical doc for Mooncoin. Please share me if you known this. |
I didn't get the address in the shossel from this private key 5PiUadgWDWjGcVHCKctSq1RiCRY1Y2CCKZrX8PgaJTwKUBeYnKs
I will clarify |
@10gic |
I would like to use the program for the mooncoin [MOON].
Thank you
sources:
site: https://mooncoin.eco/
wallet: 0.17.1.0 https://github.com/mooncoincore/wallet/releases
prefix: "M" and "2"
The text was updated successfully, but these errors were encountered: