Slimcoin | First Proof of Burn currency | Decentralized Web

[johnwhitestar]

dumping and importing all privkeys in fresh wallet show that i have only 6k burning coins instead of 20k really

Can you still access the old wallet file, at least for a short time? So you can get a complete list of your addresses?
I guess your list of imported private keys is incomplete ... which command did you use to see the addresses? The list in the qt wallet or the command listaddressgroupings?
Try listaddressgroupings (in the Debug console or with the slimcoind daemon) and check if there is any address missing where you still have to import the private key into the new wallet. listaddressgroupings (afaik) lists all addresses which were used at least once to send coins, so the addresses to access your burned coins should be definitively there.

listaddressgroupings
Method not found (code -32601)

i just open my wallet.dat in notepad and found all addresses by searching for word "name"

What wallet version are you on?

[1715252750]

1715252750

[1715252750]

1715252750

[1715252750]

1715252750

[1715252750]

1715252750

[1715252750]

1715252750

[d5000]

listaddressgroupings
Method not found (code -32601)

Oh, you're totally right, sorry! Slimcoin doesn't have this command still ... later Bitcoin/Peercoin versions have, thus I was confused ...

In Slimcoin you would have to do two steps:

Code:

listaccounts

and then for each account:

Code:

getaddressesbyaccount ACCOUNT

i just open my wallet.dat in notepad and found all addresses by searching for word "name"

I actually never tried this, looks interesting, will try it with a fresh wallet file. However, it would be cool to have a proper wallet management tool like pywallet.

[johnwhitestar]

...it would be cool to have a proper wallet management tool like pywallet.

Why not consider it? Especially once we have the PoD token launched.
Where is the code to port?

[d5000]

Why not consider it? Especially once we have the PoD token launched.
Where is the code to port?

I think it's this one:

https://github.com/jackjack-jj/pywallet

There's another one which is older and described as the "original". If the update to modern code delays, this could be a better option:

https://github.com/joric/pywallet

[johnwhitestar]

Why not consider it? Especially once we have the PoD token launched.
Where is the code to port?

I think it's this one:

https://github.com/jackjack-jj/pywallet

There's another one which is older and described as the "original". If the update to modern code delays, this could be a better option:

https://github.com/joric/pywallet

We'd need a python dev here, right?

[gjhiggins]

client v6 stucks on win&lin with my old wallet.dat, with size of this over 4mb

Yes, it's an old client and is beginning to struggle when indexing the blockchain and is unresponsive while that is happening. Try leaving it for a day, see if it manages to settle down.

dumping and importing all privkeys in fresh wallet show that i have only 6k burning coins instead of 20k really

Yes, I've experienced temporary misreporting of the burned coins data, I've had to restart the client a couple of times to get accurate reporting in the GUI. Try the console command getburndata, see if that shows the correct burned coins data.

Cheers

Graham

[gjhiggins]

There's another one which is older and described as the "original". If the update to modern code delays, this could be a better option:

https://github.com/joric/pywallet

We'd need a python dev here, right?

Not really. Use this version from the repos. Save the page as pywallet.py, change addrtype = 0 to addrtype = 63, create a subdirectory datadir, copy your wallet.dat into it and you should be able to get a JSON dump of the wallet keys with:

python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet

(note, Python 2 required).

Cheers

Graham

[johnwhitestar]

There's another one which is older and described as the "original". If the update to modern code delays, this could be a better option:

https://github.com/joric/pywallet

We'd need a python dev here, right?

Not really. Use this version from the repos. Save the page as pywallet.py, change addrtype = 0 to addrtype = 63, create a subdirectory datadir, copy your wallet.dat into it and you should be able to get a JSON dump of the wallet keys with:

python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet

(note, Python 2 required).

Cheers

Graham

Wow! So we basically can use it right away?

[gjhiggins]

you should be able to get a JSON dump of the wallet keys with:

python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet

Wow! So we basically can use it right away?

Worked for me.

Cheers

Graham

[d5000]

Thanks gjhiggins, that's awesome! I tried it out and it seems to have worked. I guess "sec" are the private keys (in WIF format probably), right? (So the list printed by this program should definitively not be shared here ).

We could simply fork this version into the slimcoin-project repo and change the datadir and addresstype parameters.

However, one question remains: Is it safe to use also for the

Code:

--importprivkey

(edited) option? This one seems to write on the wallet file, so it should be used carefully (only with a backup of the wallet).

[gjhiggins]

Thanks gjhiggins, that's awesome! I tried it out and it seems to have worked. I guess "sec" are the private keys (in WIF format probably), right? (So the list printed by this program should definitively not be shared here ).

We could simply fork this version into the slimcoin-project repo and change the datadir and addresstype parameters.

However, one question remains: Is it safe to use also for the

Code:

--importwallet

option? This one seems to write on the wallet file, so it should be used carefully (only with a backup of the wallet).

?? That option isn't supported in the committed version that I used:

Code:

Usage: pywallet.py [options]

Options:
  --version            show program's version number and exit
  -h, --help           show this help message and exit
  --dumpwallet         dump wallet in json format
  --importprivkey=KEY  import private key from vanitygen
  --datadir=DATADIR    wallet directory (defaults to bitcoin default)
  --testnet            use testnet subdirectory and address type
  --password=PASSWORD  password for the encrypted wallet

The importprivkey succeeded for me.

I was focused on the original task, dumping privkeys from the wallet.db file, didn't explore further.

Cheers

Graham

[d5000]

Oh, you're right, I meant importprivkey of course.

[johnwhitestar]

dumping and importing all privkeys in fresh wallet show that i have only 6k burning coins instead of 20k really

Can you still access the old wallet file, at least for a short time? So you can get a complete list of your addresses?
I guess your list of imported private keys is incomplete ... which command did you use to see the addresses? The list in the qt wallet or the command listaddressgroupings?
Try listaddressgroupings (in the Debug console or with the slimcoind daemon) and check if there is any address missing where you still have to import the private key into the new wallet. listaddressgroupings (afaik) lists all addresses which were used at least once to send coins, so the addresses to access your burned coins should be definitively there.

listaddressgroupings
Method not found (code -32601)

i just open my wallet.dat in notepad and found all addresses by searching for word "name"

Were you able to solve your issue?

[casper77]

Were you able to solve your issue?

still no
i finally moved away from windows and am looking for solutions for linux
it turns out my clients were version 0.5.0
i have two computers, one for mining with a fresh wallet, the other more precious with a lot of burned coins, but very freezy

[johnwhitestar]

Were you able to solve your issue?

still no
i finally moved away from windows and am looking for solutions for linux
it turns out my clients were version 0.5.0
i have two computers, one for mining with a fresh wallet, the other more precious with a lot of burned coins, but very freezy

Have you tried to extract your keys with the tools mentioned above?

[casper77]

Not really. Use this version from the repos. Save the page as pywallet.py, change addrtype = 0 to addrtype = 63, create a subdirectory datadir, copy your wallet.dat into it and you should be able to get a JSON dump of the wallet keys with:
python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet
(note, Python 2 required).

it works, but too much addresses, maybe 400 or 500
it is impossible to dump privkeys of them all

[johnwhitestar]

Not really. Use this version from the repos. Save the page as pywallet.py, change addrtype = 0 to addrtype = 63, create a subdirectory datadir, copy your wallet.dat into it and you should be able to get a JSON dump of the wallet keys with:
python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet
(note, Python 2 required).

it works, but too much addresses, maybe 400 or 500
it is impossible to dump privkeys of them all

Hmm...

Do you mean it's too much work to recover 20k?
Or you mean that once you've transferred all of those addresses to your new wallet it may become slow again?

[d5000]

@casper77: I've coded a small script to do a lookup at block explorer Cryptoid so you can filter out all addresses which have 1) no coins on it and 2) from where you did not burn any coins. Will upload it to Github together with an adapted version of pywallet. Just a moment

Edit: Uploaded it. It is here:

https://github.com/slimcoin-project/slm-pywallet/

I also included a pywallet.py file with Graham's changes.

To run the lookup script, clone the Git repository and run:

Code:

cryptoidlookup.py PYWALLET_DUMP_FILENAME

(you must have saved the pywallet dump to a text file before)

It will lookup all addresses in the file, and print out those who were used for transactions (including burn transactions). The empty addresses are ignored.

Note: One little oddity is that pywallet uses Python 2 and the cryptoidlookup script Python 3, maybe this can be later changed.

[casper77]

@casper77: I've coded a small script to do a lookup at block explorer Cryptoid so you can filter out all addresses which have 1) no coins on it and 2) from where you did not burn any coins. Will upload it to Github together with an adapted version of pywallet. Just a moment
Edit: Uploaded it. It is here:
https://github.com/slimcoin-project/slm-pywallet/
I also included a pywallet.py file with Graham's changes.
To run the lookup script, clone the Git repository and run:

Code:

cryptoidlookup.py PYWALLET_DUMP_FILENAME

(you must have saved the pywallet dump to a text file before)
It will lookup all addresses in the file, and print out those who were used for transactions (including burn transactions). The empty addresses are ignored.

python3 cryptoidlookup.py 2.txt

Traceback (most recent call last):
  File "cryptoidlookup.py", line 80, in <module>
    main(sys.argv)
  File "cryptoidlookup.py", line 52, in main
    wdump = getdump(args[1])
  File "cryptoidlookup.py", line 44, in getdump
    walletdump = json.load(f)
  File "/usr/lib/python3.6/json/__init__.py", line 299, in load
    parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode
    obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Expecting ',' delimiter: line 1129 column 1 (char 40918)

[d5000]

Can't reproduce your error, on my computer it works fine. I guess your text file where the dump was saved has an error, there seems to be a comma missing. Maybe you saved it manually from the terminal output?

Try to dump again with pywallet:

Code:

python2 pywallet.py --datadir=`pwd`/datadir --dumpwallet > walletdump.json

Code:

python3 cryptoidlookup.py walletdump.json

PS: The command can take some time, there is an intentional 15 sec pause between addresses to avoid the server rejects your requests. So simply leave it alone for a while.