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

[almightyruler]

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.

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...

[danbi]

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]

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?

[tu0666047zish]

And proportional distribution absolutely fair for all.

[Cryptoneer]

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

[almightyruler]

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]

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! 

[Hobbyist]

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.

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

[almightyruler]

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.

[Aimee1993]

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?

[soopy452000]

Hello All,

How are things going on. Sweet memories.

Cheers!
˜SoopY˜

[almightyruler]

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.

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.

[NoobKidOnTheBlock]

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]

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]

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

[almightyruler]

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

[almightyruler]

2.5 years later, the blockchain hasn't changed from my point of view. Last blocks in October 2019.

My coin server is back up 24/7 now, but there's been no obvious connection attempts over the past couple of weeks. Anyone want to get out their old client?

addnode=149.28.164.168

Code:

23-Oct-2019 07:27:25 UTC+0 height: 2167394  mint: 64  difficulty: 0.00024414  flags: proof-of-work  tx: 1  hash: 00000e9e1bd6aec47e49fa799f2dd8a8aaba952df932f6e2a6dddff58061f2f3
23-Oct-2019 07:27:28 UTC+0 height: 2167395  mint: 64  difficulty: 0.00024414  flags: proof-of-work  tx: 1  hash: 00000073ab61335df0073509436681de14a49af5005ef704d5c96c825b4989b9
23-Oct-2019 07:27:30 UTC+0 height: 2167396  mint: 64  difficulty: 0.00024414  flags: proof-of-work  tx: 1  hash: 00000445e9d1d1e163f22a9c43a35a0f6ce4a75be176f6fd0141e5729839d286
23-Oct-2019 07:27:37 UTC+0 height: 2167397  mint: 64  difficulty: 0.00024414  flags: proof-of-work  tx: 1  hash: 00000cab4f821756aad374bb4c475c77043ed1e20317d5e4bbffba3922941369
23-Oct-2019 07:27:52 UTC+0 height: 2167398  mint: 64  difficulty: 0.00024414  flags: proof-of-work  tx: 1  hash: 00000cf7f9f92011a28f953d00b3c83a168bc899b305c30234e4b355421ac8b7
23-Oct-2019 07:27:56 UTC+0 height: 2167399  mint: 64  difficulty: 0.00048827  flags: proof-of-work  tx: 1  hash: 000005ffc6a4a5536cc99d0a876eb904a731ae7608c7367c90cc29b713459a10
23-Oct-2019 07:28:03 UTC+0 height: 2167400  mint: 64  difficulty: 0.00097655  flags: proof-of-work  tx: 1  hash: 00000396a519e7dbf50fba7bec687a7675a55a3ac36c515bf6adb3f705641ea6
23-Oct-2019 07:28:53 UTC+0 height: 2167401  mint: 64  difficulty: 0.00195311  flags: proof-of-work  tx: 1  hash: 0000012e9c1609b62ea414c209bd6f255bfde589dfc79e72e32988c6c69c53fc
23-Oct-2019 07:29:40 UTC+0 height: 2167402  mint: 64  difficulty: 0.00390625  flags: proof-of-work  tx: 1  hash: 000000dcb0fa87829d9249dcb40b93f26ebe7bd7d19b06fa5626cbb1e0d9b0b6
23-Oct-2019 07:29:55 UTC+0 height: 2167403  mint: 64  difficulty: 0.0078125  flags: proof-of-work  tx: 1  hash: 0000007a36288715c92dd044d4849f51adb5e59d3e052544cc7b0a6cb57b1e5b
23-Oct-2019 07:30:52 UTC+0 height: 2167404  mint: 64  difficulty: 0.01531863  flags: proof-of-work  tx: 1  hash: 0000000287521d3186d3b994519b68bc7cc1fda3b333bb6dda355758b26aa7ed