Cool - I like the idea that they were sent to holders of existing other coins (Bitcoin, Litecoin, Dogecoin) to get them out there...just wondering what percentage have not yet been claimed. Sorry if this is not the correct section to ask that question.
In Just-Dice chat we have a command that help with that statistics, it show how many sets (each set refer to a funded BTC/LTC/Doge address) of 4.60 clams have been claim of the total of possible claimable sets, also the amount of Clam in circulation and how many come from claiming (we refer to it as dug Clams) and how many come from the Staking process. It also give you the theoretical money supply if all the Clams get claimed all at once. This command is "/supply" without the quotes.
At the moment that i wrote this the statistics goes like this:
222,562 of 3,208,032 sets of 4.60545574 CLAM were dug, This is around if my the calculator didn't fail me 6.93% have been claim so rounding we can say that there is 93% that have not been claim yet.
1,024,999 CLAM were dug up and 1,472,515 CLAM were staked for a total of 2,497,514 CLAM
if all the distributed CLAMs were dug up, the total money supply would be 16,246,916 CLAM
I set it to show hidden files and still do not see it.
I am wondering if the file is not there because I have not made any changes to the clam client since installing it?
I don't know of the case of ClamClient but I read that in the case of Bitcoin, the bitcoin.conf file is optional and not usually created automatically, When I had wallets installed the .conf file was always there, I don't remember a case that need to create it from scratch, It was there when I needed to add things like nodes IP, maybe it's part of how your OS works with the wallet, so if you don't have it and you know that you're in the right directory where the file should be, you should try to find a sample to use it as a template for your configurations or just add the parameters that apply to your case and create the .conf file. This can be done in many plain text editors just by saving the file as .conf