Quote from: gjhiggins on May 27, 2014, 03:23:26 PM

Quote from: SuperClam on May 24, 2014, 04:33:19 AM

If you do want them, well.... then: Your Welcome

Your -> You're

You're apparently contradicting yourself ...
Your instructions in the OP:

Quote

9. Run the CLAM Client with the commandline argument -salvagewallet.

...

Quote

8. Run the CLAM Client from the command line adding the -salvagewallet argument.

And from a subsequent response of yours:

Quote

run the CLAM Client with --salvagewallet. The double -- is important.

HTH.
Cheers,
Graham

Thank you very much for the corrections.
Indeed, the command line mistake was a very important one!

Think the OP post should be correct now, and reflect the changes.

Quote from: gjhiggins on May 27, 2014, 04:11:31 PM

Quote from: Bouwens on May 24, 2014, 05:26:35 AM

Anybody had successfully received some CLAMs?

Yes. After reading through the instructions and subsequent confirmatory posts, I decided to take the direct route.
I have standard linux wallets for BTC, LTC and DOGE.
BTC and LTC wallets are empty, never seen any transactions so neither are due to receive CLAMs because the addresses have never been recorded in the bitcoin blockchain as part of a transaction.
But all is not lost, I am a (lapsed) Shibe and my DOGE wallet address has at some time in the past been recorded in the Dogecoin blockchain as part of a transaction (when I acquired the DOGE and when I credited the tipbot's address).

Code:

$ cat /etc/issue
Ubuntu 14.04 LTS \n \l
$ cd /tmp
$ git clone https://github.com/nochowderforyou/clams
$ cd clams
$ qmake-qt4 # Qt5 menubar icons and ubuntu unity don't place nice.
$ make -j4 # entry-level core i3 (Sandybridge) Acer laptop
# I ignored several compiler warnings about an unchecked
# return type, might hack up a PR later.
$ ./clam-qt -printtoconsole -debug
^C
$ cp ~/Documents/BackupWallets/dogecoin-unsecured-backup-wallet-00.dat ~/.clam/wallet.dat
$ ./clam-qt

Works for me, better than expected, I got 4 separate credits of 4.60545574 CLAM.
Why 4 credits, I wonder?
And it's successfully staking, a transaction just showed up in the wallet, itemised as "Mined", totalling 0.00136895.
The overview states I have 13.8-odd CLAM to spend and I am staking 4.6-odd CLAM

Quote

Status: 1/unconfirmed, broadcast through 5 nodes Date: 27/05/2014 16:55 Source: Generated Debit: 0.00 CLAM Net amount: -4.60545574 CLAM Transaction ID: 1e605b6726a3682ac739dfe8f2fa96e9479b7271d2da484a40946a9dc62a2da5 Generated coins must mature 510 blocks before they can be spent.

(I shuffled the transaction hash id before posting)
Congratulations on what's beginning to look like a solid implementation of a really well-considered approach.
Cheers,
Graham

Super happy to hear you've had a good experience with the import process Grin

And a stake right away!
Likely due to the fact that the coins had been accruing "coinDays"/age since the sends were done.
That effect should only get more powerful as time goes on.
New users will have a great deal of coinDays accrued and hopefully stake quite quickly on the network!

Concerning the 4 separate credits:

The block chain does not (thankfully) store information connecting multiple addresses within the same wallet. Evidentally, there were 4 separate outputs on the DOGE block chain to 4 separate addresses in your wallet -> thus 4 separate credits!

We did our best to try to formulate rules that would be as fair as possible, alas there is only so much data on the block chain.

Like we've said previously, it isn't perfect: but it includes everyone!