[RE-ANN] Galaxycoin Revival! KGW, POS/POW hybrid [TRADING ON CRYPTSY]

almightyruler

legendary

Activity: 2268

Merit: 1092

If anyone is interested in connecting again, try:

Code:

# coin: galaxycoin
addnode=91.121.221.51
addnode=149.28.164.168

Last blocks were mined (from my client's perspective) back in October 2019. I inadvertently staked and minted several blocks when I restarted a few days ago, but I rolled back to the 2019 version of the blockchain, just in case it has already been extended elsewhere. Last block is 0000000287521d3186d3b994519b68bc7cc1fda3b333bb6dda355758b26aa7ed

NoobKidOnTheBlock

hero member

Activity: 770

Merit: 500

FLY DONATION ADDRESS IN SIGNATURE

I would love to keep myu wallet open but I need connections and can't find any???

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: NoobKidOnTheBlock on October 07, 2019, 12:13:36 AM

Is anyone still staking or mining this coin? I hope so because I got a nice chunk I've been holding onto for a long time now lol

I am. You can help by keeping your wallet open.

NoobKidOnTheBlock

hero member

Activity: 770

Merit: 500

FLY DONATION ADDRESS IN SIGNATURE

Is anyone still staking or mining this coin? I hope so because I got a nice chunk I've been holding onto for a long time now lol

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: almightyruler on May 02, 2017, 02:46:49 PM

Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.

There were 103 keys successfully imported, but a rescan doesn't match any of them against a transaction. Sad

It could just be an empty wallet with a pool of keys that were never used, or it could be that the base58 import format isn't quite correct ('close enough' isn't going to work.)

Could also be that the wallet is truncated (it is less than a default wallet size of 128k) or corrupt, and it originally held more valid+used private keys...

I know this post is from 2 years ago, but I just had another go at recovering funds from the Cryptsy wallet.

This time my recovery efforts considered the entire wallet.dat file to be a byte stream full of keys - my system doesn't care about file formats, magic numbers, indexes, metadata, whatever; just whether each 32 bytes of raw data can be mapped to an address that's in the blockchain.

Again... zero matches. It seems the keys/addresses in this wallet have never been referenced in the Galaxycoin blockchain. So it's either an empty wallet that was created but never used, or perhaps a wallet from another coin.

FYI, there are 91584 different addresses present in the Galaxycoin blockchain.

soopy452000

legendary

Activity: 1302

Merit: 1001

Founder - NavCoin Ⓝ

Hello All,

How are things going on. Sweet memories.

Cheers!
˜SoopY˜

Aimee1993

hero member

Activity: 630

Merit: 500

Quote from: almightyruler on January 15, 2018, 07:22:21 PM

Quote from: Hobbyist on January 13, 2018, 08:40:12 PM

Quote from: almightyruler on May 02, 2017, 02:46:49 PM

Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.
[...]

for pywallet and Galaxy try, --otherversion=98

I used a slightly hacked pycoin.

I can send you a list of the extracted private keys (in raw hex format, not coin-specific WIF) if you want to have a go at importing them using pywallet.

How many COINS does pos need?

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Hobbyist on January 13, 2018, 08:40:12 PM

Quote from: almightyruler on May 02, 2017, 02:46:49 PM

Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.
[...]

for pywallet and Galaxy try, --otherversion=98

I used a slightly hacked pycoin.

I can send you a list of the extracted private keys (in raw hex format, not coin-specific WIF) if you want to have a go at importing them using pywallet.

Hobbyist

hero member

Activity: 588

Merit: 503

Quote from: almightyruler on May 02, 2017, 02:46:49 PM

Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.

There were 103 keys successfully imported, but a rescan doesn't match any of them against a transaction. Sad

It could just be an empty wallet with a pool of keys that were never used, or it could be that the base58 import format isn't quite correct ('close enough' isn't going to work.)

Could also be that the wallet is truncated (it is less than a default wallet size of 128k) or corrupt, and it originally held more valid+used private keys...

for pywallet and Galaxy try, --otherversion=98

Cryptoneer

jr. member

Activity: 116

Merit: 7

Quote from: almightyruler on January 03, 2018, 04:34:55 AM

Quote from: Cryptoneer on January 03, 2018, 01:09:01 AM

I get two nodes, but it doesn't sync. How about you guys?

Can you give some more detail on what the problem is? At this point my client has 1492961 blocks and the last block (PoS) was minted 12 mins ago.

# coin: galaxycoin addnode=217.65.8.75 addnode=85.236.188.28 addnode=193.68.21.36 addnode=203.20.114.252 addnode=137.119.66.89

Ahh cool, this seems to work, let me see if I can get the whole enchilada this way. Thanks! Grin

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Cryptoneer on January 03, 2018, 01:09:01 AM

I get two nodes, but it doesn't sync. How about you guys?

Can you give some more detail on what the problem is? At this point my client has 1492961 blocks and the last block (PoS) was minted 12 mins ago.

# coin: galaxycoin addnode=217.65.8.75 addnode=85.236.188.28 addnode=193.68.21.36 addnode=203.20.114.252 addnode=137.119.66.89

Cryptoneer

jr. member

Activity: 116

Merit: 7

I get two nodes, but it doesn't sync. How about you guys?

tu0666047zish

jr. member

Activity: 56

Merit: 10

And proportional distribution absolutely fair for all.

almightyruler

legendary

Activity: 2268

Merit: 1092

Just an update on GLX. I'm mining on one node (GLX is allocated a gridseed unit about 90% of the time - but it does drop out sometimes) and occasionally staking on another.

Doesn't look like much else is happening? Am I the only one mining this?

danbi

sr. member

Activity: 393

Merit: 250

It may be, that the Cryptsy wallet used differen db version. The expected/standard version is 4.8, but I have compiled wallets with other versions as well -- they work just fine, as long as you don't try to exchange it with outher software. Just a wild guess.

almightyruler

legendary

Activity: 2268

Merit: 1092

Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.

There were 103 keys successfully imported, but a rescan doesn't match any of them against a transaction. Sad

It could just be an empty wallet with a pool of keys that were never used, or it could be that the base58 import format isn't quite correct ('close enough' isn't going to work.)

Could also be that the wallet is truncated (it is less than a default wallet size of 128k) or corrupt, and it originally held more valid+used private keys...

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Stouse49 on April 28, 2017, 11:08:32 PM

Quote from: almightyruler on April 28, 2017, 10:40:54 AM

Quote from: Stouse49 on April 27, 2017, 11:50:18 PM

Thanks for the link to the wallet source and the addnodes. Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

I tried the -salvagewallet, but still there were no coins in this wallet. Must have been a dud.

I can have a poke around if you like. Send me a copy? A 'proper' wallet.dat contains some recognizable clear text strings, so if this wallet also contains them, it may be possible to reverse engineer from that point, and figure out the offsets of private keys.

Maybe even something brute forcish like importing every possible 20 byte sequence in the file as a private key may work... to do this with a 48k file would generate around a million potential keys.

Stouse49

full member

Activity: 209

Merit: 100

Quote from: almightyruler on April 28, 2017, 10:40:54 AM

Quote from: Stouse49 on April 27, 2017, 11:50:18 PM

Thanks for the link to the wallet source and the addnodes. Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

I tried the -salvagewallet, but still there were no coins in this wallet. Must have been a dud.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Stouse49 on April 27, 2017, 11:50:18 PM

Thanks for the link to the wallet source and the addnodes. Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

Stouse49

full member

Activity: 209

Merit: 100

Thanks for the link to the wallet source and the addnodes. Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

Topic: [RE-ANN] Galaxycoin Revival! KGW, POS/POW hybrid [TRADING ON CRYPTSY] (Read 51743 times)