[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

Quote from: istvandv on August 22, 2014, 09:38:34 AM

i suppose because of fear in general of importing other wallets (no matter how much we try to show that it is completely safe in CLAMS) they would like to check first before diving in

would running "listreceivedbyaddress 0 true" in the debug console printout all the addresses in the wallet including change addresses? or is there a better command

That's a great idea.

The '0' is the number of confirmations needed to list an address - so if we can find out how many blocks there have been since the CLAM snapshot of the Bitcoin blockchain was taken, that's the number we need to put there. And the 'true' means to list addresses that never received any coins, so we don't want that.

Checking blockchain.info I see that block 298520 has a timestamp of 2014-05-01 01:02:33, which I'm guessing is around the time the snapshot was taken - but the CLAM developers should be able to give us the exact block number for all three snapshots.

Then at a Linux shell prompt I can run:

Code:

bitcoind listreceivedbyaddress $(($(bitcoind getblockcount) - 298520)) | grep address

to get a list of all the addresses which were funded on or before that block number and so should have CLAMs (if the funding wasn't just dust)

[ Edit: some of the addresses it lists may have had a balance before the snapshot, but been empty at the time of the snapshot and so won't have any CLAMs to dig; it would be nice if I could improve my script to only show addresses which had a "balance" (I hope lukejr doesn't see this) at a certain block number, but I don't see a way of doing that; I was excited when I converted the list of addresses in my wallet into CLAM addresses, then used 'validateaddress' in the clam wallet only to find that none of them had been imported - but it turns out all the listed addresses were empty at the dump date, because my whole wallet was empty at the time - apparently all my coins were invested on a dodgy dice site ]

Or, better, I can run:

Code:

bitcoind listreceivedbyaddress $(($(bitcoind getblockcount) - 298520)) | grep -E '^ *"(address|amount)"' | awk '{print $3}' | while read address; do read amount; echo $amount $address; done | sort -n

to get the same list, but with the amount received, sorted in order of amount received:

Code:

0.00000001, "1Mi3enEMy3GSAYSoifs9L8jZ2c4A2EZ7co",
0.00000008, "1Pqn9rAJup6cWzd6JrhJVPCmBTqVLN1y3W",
0.00005669, "1JXDq76gJirgk5v2djmdo5DjtncrGXw4Tm",
...
3538.96307960, "1DodGYjF5LFoKg186jANZV9U8znXjagSzS",
4673.25920093, "1PwncQYDQDUAhrr2Ag5cTj3QNurMc3kWJu",
14700.00000000, "1PwgycpEn4G2Tb8wVNgMrhACukXLfvYsRf",
562890.27306771, "14Fu4z4EBmX8Lq7H3whG9bUJFLAdBDEevY",

If you don't have a Linux shell prompt, you can use the console in bitcoin-qt:

Run 'getblockcount' to get the current block number
Subtract 298520 from it, to get the depth of the CLAM snapshot (replace 298520 with the real number if it becomes known)
Run 'listreceivedbyaddress NNNN' where NNNN is the result of the above subtraction

	Author	Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" (Read 1153890 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.