I don't have experience with the bootstrap.dat, but it seems like you used the method of combining all the bootstrap partial files to make a single bootstrap.dat, maybe you should try using the bootstrap.dat  that comes in a single file, in case you want to keep the one that you have atm just rename it, copy the bootstrap that is a single file, it goes to Sat Aug  5 23:18:40 UTC 2017, so you will only have to sync around 10 days after that. you can find it at this dooglus' post it's the first link, the second is the same but for torrent. below a quote about how to figure out if your bootstrap is working, from the same post linked before.

 Hi Robert Erlandson, I'm not an expert in the matter of Copyright, but I think since Clam like many others coins is released as open source code and the logo is in many cases, part of the code too, I think then the license should give you the ability to use the logo with no problems specially for your noble research case, for example if you get ClamClient's source code you can find under the path clams/COPYING instructions about how Clam handle his Copyright statement, it basically says that you should give credit to the people that created the software.


 So I think you just need to add the quoted text above on your book or article and you will be covered by the Permission granted there. You can find the source code in the Clam's github and you can even check or visualize the files that I'm telling you in the github page without the need of downloading the source code i guess. Also in the source code, at this path clams/src/qt/res/icons/clam-128.png you can find the Clam logo with an acceptable quality.

 I saw that you have posted the same request like 1 time before and maybe the answer was too simple to convince you, maybe a Dev can tell how right or wrong my point of view is and email you or allow me to email you. Also if things works like I explained before that will be good news for you because I have seen many wallets that are based in the same code so you will be able to check probably most of the Cryptocoins that you must be willing to add to your book or article, just looking to their source code and see what does their COPYING file or license file says, instead of waiting for a Dev to reply to you Cryptocoin by Cryptocoin.

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

There is also other criteria that should be meet in order to get your BTC/LTC/Doge wallet to be funded, not just having or owning the address before May 2014, you need to meet some balance threshold, so your account is not considered a dust holding account, also you need to have that amount in the address at the moment that the snapshot of the different blockchains was taken. I don't use Coinbase but I doubt they give the private keys, even to their "vault" multisignature users, also doubt that "vault" function was around when the Clam distribution was made.


 Usually on Windows you can find it at this location:

C:\Users\YourUserName\Appdata\Roaming\Clamcoin (on Windows 7)
C:\Documents and Settings\YourUserName\Application data\Clamcoin ( on Windows XP)

For linux you can try to look for this location:

~/.clamcoin/

 Exactly like chilly2k said you make the claim of your clams using the private keys or the wallet.dat (that is a file that where the BTC/LTC/Doge wallet usually store private keys) and import it in your Clamclient, in addition to that, usually some wallets are more easy to claim because of the way they stores the private keys.

 Maybe is this what you are asking for, as an example there are some wallets that use the Hierarchical Deterministic (HD for short) address generation method that compared with wallet that doesn't use this way and store the private keys in a normal wallet.dat file, those HD wallets (for example Multibit HD) are more complicated to claim because they use a 12 words mnemonic, that is a group of 12 words that is used to backup the seed that is used to create your wallet addresses (private keys) and if this hasn't change, I was checking recently and didn't, you can't retrieve you private keys or export it straight from the software. They are workarounds to extract the Private Keys but not as easy as click "show private key" or "export ".

So if your wallet has the ability to import and export private keys or store you private keys in a wallet.dat, those wallets are way more easy to be claim. In this category you can find BitcoinQT client, Electrum, Multibit Classic (dunno if still available) and many others.

 When you refer to working official, maybe you're referring to the a "stable" version because the code provide by the developer's github is considered official, also i guess that older versions still are able to sync. Between the 2 versions that you have pointed out that you have the version 1.4.17 is the latest stable version at the time that I wrote this, don't let the .7 fool you, that version is behind 10 versions from the lastest version. You can see in the quote below, there is a v1.4.18 but is not released as a Stable version yet, you need to build it if you need it and test it. For last in the link that says Release Repository you can check the releases chronology.

 I'm not sure if when you mention "import" the bootstrap, you are referring to try to import it like a wallet, if that is the case look at the link that was given previously because it explain how you should do to get the bootstrap running, as you may see dooglus has said that is up today which is very good.

 For the second question, you can import your private keys one by one or in a group using several Bitcoin, Litecoin and Doge clients, the client that you use must allow you to "import" your private keys, some clients that use hierarchical deterministic wallet doesn't allow you to import private keys, I know that clients like Electrum allow you to import several Private Keys at once other like the clients QT version of the above mentioned crypto currencies allow you to do that using the console or command line interface with the command "importprivkey" (or something very similar in name), I don't remember if the command line allow you to import multiple at once but you can check the help of the command and see if there is a way, at least you can import it one by one. Using this method you can convert your Private Keys into a Wallet.dat file because it will be contained in the file to where you are doing the importing, it becomes part of it in most clients. Then you can use that file to get it imported in the ClamClient.

Did you tried using dooglus' bootstrap?


 I heard from other people that used this method, it will speed up the process, but still it will take some time to sync. dunno how updated the bootstrap.dat is because I asked someone about the blockchain size file and he seems to be stuck in the same point as you.

 As far I know there is no lightweight wallet for Clam, in the github I saw that someone was asking for a Electrum server for clam and they did some testing trying to create one but it seems like is not in the way to be implemented.


Depend on multiple factors, someone can come and tell you x amount, but to calculate it properly you need to know if you are solo or pool staking, how many clams are staking at the same time as yours, how properly you is your ClamClient configured to stake efficiently if you're solo staking also if you let your ClamClient stake all the time 24/7 or partially.


I don't use Armory but since the "root key" seems to be very specific for the Armory Wallet client and you will need to decrypt the wallet so the ClamClient can import it (not sure of that part), if you don't have lots of address you can try to export your private keys, i think that will give you a format that will be more ease for the ClamClient to import and redeem your Clams.

Here you can check 2 links if you want read more about you can do that.
how to obtain the private key of an armory wallet
a post here in bitcointalk about how can obtain your private keys


 I don't know if you are talking to me or to the OP, but we discussed previously about the "airgapped" offline system and with dooglus we confirmed that was viable to do it that way, similar to your explanation , in the case of the OP this only have few workarounds if you don't want to use the ClamClient or anyone else service, check the code by yourself, trust code provided or forget about claiming your Clams. anyways thanks for your thoughts.

 There are some key features that I can point out, First like BayAreaCoins said the method of distribution of Clam, it implemented a method to give out the coins in a way that it can reach most crypto currencies users in a set of very popular (at the time that was take the snapshot) crypto currencies, some can say things like "litecoin sucks" or "doge is joke" but those crypto currencies were chosen because they have some good amount of user that at least tested their waters.

 The method is so unique in his kind, that can literally only be done once if it works or at least will need to use the same point as the Clamcoin's blockchain snapshot or prior to avoid gaming in the distribution. Some people can argue that it benefit one more than others, but in general it try to give equal chances to everyone in the distribution, I mean each fund address give equal to everybody, no matter if you have less than 1 btc or have a lot more, you'll get 4.60 per funded address, well people more involved in crypto can usually have more addresses like BTC, LTC or Doge that's how thing goes, some people with "bad practices" like not implemented cold storage can had a disruptive advantage, Clam tries to find the most fair distribution method, no a perfect one.

 Contrary to BTC the Proof-of-stake imply that Clam users doesn't need to invest in mining equipment in order to get a share of the staking process, that is a good concern because don't imply equipment that will become obsolete and not able to find another purpose for they and are expensive and waste much electricity, also are hard to setup for the average user.

 The coin is deflationary but only by the amount of blocks produced per day at a reason of 1 Clam per staked block contrary to BTC, this promote that users protect the network by staking and receive in exchange a share that in the least case (of staking constantly) is enough to absorb the inflation dilution or in the case of less people staking, gives profit by interest gain. Also depending the point of view, the stake can protect early adopters against the inclusion of new undug Clams in the money supply, I mean there is gonna be dilution but those Clams that have been staking will have an advantage against those recently dug.

 In the development part you can find features like the ClamSpeech (that I don't understand well), I think it has a notarization feature, but a feature that was somehow hard to implement because they were trying to find consensus about how to do it was the the Clamour a kind of consensus tool to make development more decentralized. I'm sure that if you explore what the Clamour is and how it work you can see what others proposals are in the way to be add to the coin and what type of acceptance it has. Also if you have the knowledge you can check the clam github and see how the code goes and i think it also has a place for people check "issues".

 There must be some other things that i must be forgotten, like proposals for dynamic fees, no related to the coin directly like loaning Clams for margin trade in site poloniex but this should give you some ideas.

Did you tried using dooglus' bootstrap? and btw it's Clam not Claims 


 I don't use Mac so I don't have any idea or found references if it works for Mac ClamClient. good luck

 Absolutly right, I don't recommend the use Re-use of btc addresses or use the same address as a change address, but I did it went I was new to bitcoin and more focused on getting the satoshis than reading about how it works, for example my first address can't be empty, because it contains dust that "now" will cost me more in fee that the value that they have, but i don't know if in the future will be anything that allows that dust to be used, also to proof ownership of address that was active since year X month Y, and is not consider a leaked or cracked address. In relation with the "look-alike" like address another good point because for vanity and non-vanity is relative easy, doesn't even need gpu power just proper knowledge to create something that will fool a fast visual inspection, so be aware from where you retrieve your public addresses and full visual inspection letter by letter must be recommended if from where you copied your public key is not trusted.

 I must clarify that I don't have any reasons to doubt about Clamclient's source code, It have been reviewed by dooglus and many others in the community and has enough time around for someone to point anything that doesn't looks right, anyone that has the ability can review it. The decision that I have take may not have sense and not necessary is what the others should do and in the future I can change opinion and decide to dug it.

 The way you explain things is very well and you speak with the authority of being able to understand the code, I try to explain but is more harder because I'm not 100% sure about what I'm talking about because i do guessing in some cases about how something is supposed to work, your opinion is very appreciated doog.

 He have a case very similar to me, I have a couple of addresses that i don't want to empty, my options were clear, check the code by myself (required knowledge is still on 101), try to follow the best security practices to minimize risk and trust the clam client with my private keys or never claim those clams. I opted for the third one, sometimes an address like your first btc address or a vanity one that you like can be very important in some way, if you don't gonna feel comfortable with a certain action is better to try find another way to get those Clams.

 I suggested that to him, but he said that he doesn't want "clamd" to access his Private Keys


 At least the way that I see it, he wants to sign a the clam transaction that will allow him to dig his Clams, but he doesn't want to do it with Clamclient because he is worry about the possibility that the software will add to the signature some "theorical" trace of his Private Key encoded in the way of comments or a 'hidden message' so he told that even an airgapped offline Clamclient is not trusted for him.

 As far I can see he trust Electrum to do signing for unsigned transaction or raw transactions on an offline airgapped environment but even if he creates a raw transaction with a Clamclient, he's won't be able to sign that transaction with his Bitcoin client that he use to sign Bitcoin transactions and he feel will not add anything "extra" to the transaction, because like was pointed before many altcoins including Clam use a different 'version byte' than Bitcoin. Some type of modification to the source code should be needed to allow for example his Electrum wallet to sign the Clam raw transaction and that open the question 'would you trust your bitcoin client after been modified?' because if you don't make the changes to the code by yourself knowing what the new added feature does, you end up in the same situation as trusting the Clamclient just that is even worse because if the new feature is not public available as open source other peers won't be able to review and warn you about something suspicious in the code.

 I think the best way to solve a case like this will be (if it's possible) to explain in a easy way the differences between how does the Bitcoin Client and Clam Client creates the signature for a transaction, that way maybe, someone could see well that the process is almost equal to how Bitcoin do it and the parts were is not equal is because of for example 'version byte' and how that doesn't compromised or add anything extra. Of course that will require the ability to read the code and understand how it works, because it probably won't be something too easy to be explain.

 I understand your point in this, but like I quoted before the key point in this is


 I don't know if  you're familiar with how the "version byte" can change the first letter of a given altcoin, it's mostly shown in things like vanitygen for altcoins address generation.

 In theory i guess that if it is the same Private Key as for example your BTC address, but the 'version byte' is the only thing that is different, the process to generate a signature for a transaction must be the same, the only change should be the 'version byte' that way if you have programming knowledge you could in theory  be able to modify or create a program to make it able to sign your Clam transaction and that way you know that the signature generated doesn't contain any external data that could help "someone" to guess or obtain your Private Key, that in theory will allow you to sign your clam unsigned transaction with for example a modded 'version byte' sign transaction command added to your Electrum btc wallet.

 But you may noticed that I mentioned a lot the in "Theory" here, this is because Clam doesn't have a typical 'version byte' at least for the case of vanitygen, the way that is used for that program for obtain the 'version byte' of a give altcoin for example Dogecoin is not the same as for Clam, even Dooglus needed to do make a custom version of vanitygen just to generate the addresses correctly, I don't know if it that is a minor tweak to the code make it work properly, but at least you need to know that changing the 'version byte' may not be enough to modify or create your own clam transaction signature generator.

 Getting back in reality, maybe you won't be able to claim your Clams because the coin was designed, to claim ownership of your Clams with signed transaction, I doubt that a signed message will do it. Of course only a programmer that know about how the signing process goes can tell what is right or wrong in all my blah blah blah.

 I was looking for an answer for your question and found this and I think is related to the topic, after that quote, I will write my suggested option for your case.


 Disclaimer: the following steps are supposing that clam client allows to create signed transactions able to be push by other clam client, also this not intended to be a full guide that you should follow, is just few ideas about how you can approach to get your clams.

 My suggestion is that maybe is possible for you to set up a clean OS where you can install the Clamclient and let it fully sync with the clam blockchain, maybe a full sync won't be needed because I think since the undug clams were assigned prior the Clam blockchain started running, those clams must be at the beginning of the Clam blockchain (but at least you will need a few blocks in your clam blockchain), then you can unplug/block/disconnect it from the Internet from your freshly installed OS, import your btc/ltc/doge wallet, check how many Clams you got and them create a transaction and sign it with you Private Keys, you will need to create a receiving address and properly make a backup of it, so you don't send your Clams into oblivion.

 All this done without Internet connection should protect you from the possibility of your Private Keys being sent by the software to the Internet, then with the transaction saved in a file you can find a way to decode the transaction, there you can see if there is something wrong with the code or signature, then you can push the transaction to the clam blockchain and your transaction should be mined and validated, usually you'll have few option with clam to push your transaction, you can make another Clean OS and this time I think you should have to fully sync it, so you can push your transaction or you can ask a friend with a sync clam client to push it for you (coz as far I know there no risk for your Clams to be stole by being push by other person).

 After all that, you need to properly delete your clean OS (the one were you put you btc/ltc/doge wallet) so you don't let any possibility of your Private Keys being compromised, Probably occupy the Entire disk with new data and proper format should do it.

 Yes you are still able the to claim (we call it dig) your clams from old address, if you have access to your private keys belonging to those address and they were funded when the distribution was made, you can claim it can enjoy your clam for whatever you wish to.

You can use a Clam wallet, like the clam client (a local wallet) to check if your addresses got funded, you will get around 4.60 clam per each diggable address, also you can use services like Just-dice to do check if your address, in the chat there is a function to dig with a command that is /dig (address) that is for checking if it's funded, you can find more info about how to dig in the FAQ if you want to do the claim via Just-Dice. Also you can use other methods like BayAreaCoins site in case you want you clams in btc for a fee they can do that for you I think. 

As far I can see in the Clam thread, no online clam wallet are available, you can use exchange sites or sites that offer Clam services like Just-Dice but that is not very secure, specially with exchanges sites, Just-Dice is fine because is a service that have been running without issues for more than 3 years, also most all the Clams in circulation are there, but is usually because people want to stake and invest there.

 If you're looking to have control of your Clams locally you should consider the official Clam Client that is on the Clam thread, you will need to take a time to sync it, but after that you will have control of your wallet better than using a 3rd party. Also you need to take measures to protect your clams in your computer like encrypting your wallet and stuff like that. Anyways if someone knows about a trusted online Clam wallet option besides Just-dice they will soon or later inform us here.

Congratulations BayAreaCoins, after half year he set a trade, now it's time to start thinking about a proper waterproof, dust proof, etc card protector. 

I don't know the exact amount now, but dooglus has said in the past that Just-Dice usually stakes an average of 1200 clams per day, but since the site have invested almost the same percentage (over 75% of all Clams in circulation) as in the past I think they should not be a huge difference in the amount that is staked daily on Just-Dice now, recently dooglus also told that Just-Dice staking wallet has show some strange variance that has made the performance drop a little bit so I guess that must put the average a little under the 1200 Clams per day.

As external data you may be interested, Clam produce 1 stake per minute with 1 Clam as Block Reward that give a total of 1440 Clams per day to the Clam Blockchain, as you can see Just-Dice is a huge staking machine.