The words "Test-Build" in the links makes me think that maybe it's worth waiting a while before upgrading.
To be honest, the change from joking about this coin being a euphemism for a female part, to suddenly being a strong advocate for free speech, makes me wonder... It was never a joke or euphemism for a female part. The word clam has been used as both a slang for the word money.. and an actual currency in the past. When CLAM was decided on as a name none of the people involved in deciding saw the relation to said female body. Flintstones used clams as there monetary system and is where we came up with the name from. I just wanted to set that straight. Also, we've always been an advocate for free speech... just now we support it directly in the block chain. |
|
|
|
What is the conversion rate from BTC, LTC & DOGE to CLAM? In other words, how many CLAMs do you get for your BTC, LTC & DOGE? Was scanning & searching the thread but missed it.
There is no direct conversion. It doesn't matter how many btc/ltc of doge you had. An address with 1M btc would get the same ~4.6 CLAM's as an address with .0001 btc. Any address that was over dust for the respective coin (.0001 for ltc and btc, .1 for doge) were all given the same amount. Unless you mean current trading value, then of course, there is a conversion as BAC said |
|
|
|
How to import the wallet.dat if its encrypted ?
Like you would an non encrypted wallet. The import dialogue will ask you for the password but your clam wallet needs to be either unlocked, or have no encryption. |
|
|
|
it looks like importing the whole doge wallet.dat via file works, having ids now
Yes, there are no issues with importing the wallet.dat file directly. Only individual private keys. |
|
|
|
Thanks for the help  I go through all this and all i got is Invalid private key (code -5)  same here!? Theres a known issue with importing a BTC/DOGE or LTC key into the client using importprivkey, it will be fixed in the next release. It was missed, but the influx of new users digging clams from sources other then wallet.dat files made it clear. The issue will be resolved in the next client release. Until then, just-dice.com's dig command will work. |
|
|
|
. Can you also address the issue with Chrome flagging the client download?
go under setting/privacy then remove the flag from "activate phishing and malware protection" I'd rather not.. Download needs to be fixed, not my settings. I just activated these features on my chome to see, and chrome never flagged the download. I'm unclear how it could? Does it actually extract the zip file? How does it know? I'm not expert in malware detection but I'm uber confused as to why its being flagged. |
|
|
|
Is there a way to import the (DOGE) private keys? The console's importprivkey gave me Invalid private key (code -5) Thanks The last update accidentally removed this in some code merge's. It would currently have to be converted back to the original hex key, then the proper Clams prefix applied to it before it could be imported. I'm working on pushing out the new release today, its top on my priority list. Theres been a bunch of new useful changes I really want to get out there. This has been added back in also, so it will allow importing doge/ltc or btc keys directly. |
|
|
|
Anyone have any ideas why my network-weight is showing impossibly high? I'm fully synced and am following the block count according to the block explorer.  The numbers are not correct, they'll be fixed in the next update. Although, the network weight is correct, just it should be divided by 100000000 to get a more expected number. |
|
|
|
Signing messages is a possibility but the ambiguity of which addresses your coins are stored makes me and the rest of the dev team hesitate to do so.
I think it's too late for that now, anyway. The way things are set up, distribution CLAM coins are at addresses which have *the same* private key as the corresponding BTC/LTC/DOGE addresses. I guess a change to the protocol could theoretically allow it, and I don't think the ambiguity you mentioned is important - if I can sign a message with the BTC form of a private key, I can trivially convert the private key to DOGE, LTC, or CLAM and sign a message with that form instead. So the protocol would need to modify the meaning of "OP_CHECKSIG" to be "the provided signature is valid for the provided pubkey (as before) OR (the input being spent was created before block 10k AND the provided signature is a valid message signature of "CLAMDIG" as signed by the BTC, LTC, or DOGE address corresponding to the provided pubkey)". Then people could dig up their outputs without needing to provide anything more than a useless message signature. There's a risk that people could be tricked into providing a scammer with a message signature that the scammer can then use to dig up the victim's CLAMs. Oh, but there's a bigger risk that the scammer just scans the network for people digging up their CLAMs using message signatures, and modifies the outputs of those transactions to send the dug CLAMs to their own address... to prevent this, the message to be signed would need to include the destination address rather than being a constant (like "CLAMDIG" above). Then what if there are multiple destination addresses. We can limit this kind of transaction to only work with a single destination address (then the scammer sends 0.001 to the destination address and gives the rest to the miners, so we have to fix the amount too, to be 4.60xxx minus the 0.0001 fee - etc.) I think in theory it's possible to find a workable solution that would allow people to safely dig up their distribution CLAM using just a signed message, but it would need careful consideration. This is absolutely on point, and articulate as always. I hadn't considered a few of your points, especially a scammer tricking someone into sending then a message signature they could use to redeem the clams. How you suggest doing it was exactly what I had in mind, and your right, it would need careful consideration. I am a big supporter of the bitaddress style page that could allow everything to happen safely offline, its a great idea imo. As for moving the information, a usb key, while it does have some associated risk is a reasonable option. there are also QR codes which would be easier if you were using a mobile device with a camera. Offline signing seems like it should be looked at first. It provides a level of security that you can be sure your private keys are not going anywhere and requires no modification to the protocol. |
|
|
|
CLAM address [xTKu6k9t] corresponding to BTC address [1L2GCsKR] was funded with 4.60545574 CLAM when the initial distribution was made; the CLAMs have not been spent and are waiting for you to collect them; use /dig ADDRESS PRIVKEY to have them dug up and sent to your deposit address for this account; the private key you provide will not be logged, and will be discarded immediately after use; having said that it is best to move any BTC/LTC/DOGE at that address to a new address first just to be on the safe side the next step is what? http://khashier.com/address/xTKu6k9twi8xSvGVsrwRb16MhLiruqhYw9this clam address is not my own Not sure I follow the question. Did you use the /dig command on just-dice.com? if so they would be automatically put into your balance at just-dice.com If your bitcoin address corresponds to 1L2GCsKR.... then that does look like the correct clam address. |
|
|
|
U import ur bitcoin wallet backup , it checks all addyes if they had balance on the day when claim distribution was made , and credits u .
Not bad idea but i don't feel good giving my priv keys away.
Your not actually giving them away either, they always remain in your possession. Its just like private keys in any client. There your's and only yours. For me the biggest concern is exposing your privkeys. Yeah, I can move my coins to another address in another wallet, but it means that I have to give up all addresses in the current wallet.
It ought to be enough to sign a message with your privkey in order to claim the CLAMS.
There was a suggestion on JD last night that the entire process could be mostly completed offline. Signing raw tx's and such. Im going to work on such a process and document it once I can finally get this new release finished. Its priority #1 Signing messages is a possibility but the ambiguity of which addresses your coins are stored makes me and the rest of the dev team hesitate to do so. |
|
|
|
I've got a couple of fixes for the issue of private keys not importing from paper wallets. Hope to have it out after some more testing but so far I've managed to import the keys generated by the digibyte paper wallets.
I pushed a pull request to the digibyte repo for this. Just need to test before merging but this will fix the issue https://github.com/digibyte/digibyte/pull/35 |
|
|
|
This coin is awesome, Just-dice accepts it, to da moon  I am curious about how it happened, you dev team contacted dooglus to add CLAM, or dooglus is a CLAM super fan? Dooglus has been helping with clams now since almost the beginning. We consider him part of the clams team and if you look at the commit history in git you can see some of the help he's provided. He also added quite a few new features recently including the current supply total in getinfo, among other awesome updates but they've yet to be rolled out. You can also find him giving great information throughout this thread. I'm not exactly sure what enticed him to help Clam in the beginning, but I'm just personally glad something did |
|
|
|
A bug.
What did I do? Synced the wallet, delete wallet.dat. Imported a new wallet.dat.
Now, It doesn't sync. T.T
If your still having issues drop by our irc channel #clams on freenode and we will work on getting you sorted out. |
|
|
|
Why is this pumping?
I personally wouldnt call it pumping so much as increased demand due to just-dice.com reopening and accepting CLAM's. |
|
|
|
any one had success to get Clam in electrum wallet? and how long coins will mature its been 16 days now my coins havent stake yet..  last stake 11/21/2014 You might want to view https://bitcointalk.org/index.php?topic=612143.0 It explains a way to generate the addresses and private keys based on your master seed. I'm not an electrum expert but it appears it wouldn't keeps them around after the funds have been moved. You will likely have to regenerate them again. I would personally generate a good amount and import them all. It would likely be tought to determine where to stop. If that makes any sense, I'm tired and about to pass out here. Hope it helps! |
|
|
|
Whoever falls for this SCAM is a dumb a** and deserves to have their coins stolen.
In the 6 months clams has been live not a single coin has been stolen nor will it ever be. The code is there in git, the binarys are compiled with gitan builder and are verifiable. Do research before you just bash our coin with your nonsense. As ALWAYS we tell people to move there coins to a new wallet if they are concerned and that migrates the risk to 0. |
|
|
|
The clamclient website seems very confusing... It's really awkward to get around.
I'm compiling the client from the git repo right now.
How exactly do you find it awkward? In all the people we asked they all seemed to like the new layout. I understand its impossible to please everyone but we'd still like to try If anything I find the new layout easier to navigate. The side menu also provides an easy way to get anywhere without side scrolling through if that what your referring too. |
|
|
|
|
Show Posts
