Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 344. (Read 1151252 times)

Can you not just specify a change address when creating the raw transaction? I think this would help alleviate that issue (and if there is no change, having the change address shouldn't be destructive).

Thanks for the reply...Will jump in when i get my BTC

At the current difficulty, If i have to start staking today, how many clams should i have it in my wallet to get at least 1 stake per day?

Good luck. I can provide more details if necessary.

One thing to watch out for: the transaction you create offline should spend all of your clams. Otherwise there's a chance the rest of your clams will go to some change address that only your offline computer has the private key to. Then when you turn your offline computer off, those clams would be lost.

Well, I'll try this option, I hope that I will succeed.

If someone wants to claim their clams and doesn't want to trust the clam client with their private keys, here's a way that should work:

1. Download the client and one of dooglus' bootstrap files. Copy them to an offline ("airgapped") computer.

2. Start the client on the offline computer. Import your private keys there. Create and sign a transaction sending your clams to another clam address. (Maybe just a shapeshift address if you just want to convert them to BTC.)

3. Copy the long hex string of the signed transaction to an online computer.

4. Push the signed transaction onto the network. There may be a website that lets you push signed transactions onto the clam network. If not, just start the client online (without importing your private keys) and when it connects use "sendrawtransaction" with that long hex string.

I haven't done this myself, but it seems clear enough that it should work.

Marjorie,

Please feel free to stop in to the freenode IRC #clams channel - we would be happy to assist.

Cheers!

I wonder if that's the same issue that bittrex was having yesterday.

This is an untested change that I made yesterday, which I hope will stop the buildup of dust outputs in the wallet, and so prevent these issues from continuing to happen.

Thank you for getting in touch with us.
Clam is currently experiencing a delay when it comes to processing transactions, especially withdrawals
and will be repaired soon. Please be patient as we repair the issue and get your withdraw moving to you.
If you want, you may have this withdrawal cancelled until the issue with this coin is resolved.
Thank you kindly for your patience and understanding.


Sincerely,
Marjorie
Cryptsy.com

Glad to hear

It is messages like that re-affirm we made the right decision with our distribution!

Enjoy

Wow, I just learned this CLAM on justdice today, it means I have some CLAMS!

CLAM v. 1.4.11 has been in the wild now for a bit.

Please submit any major issues you have had with this new version.

---

If we don't see any major issues - CLAM v. 1.4.11 will be bumped to STABLE.

It seems the bittrex wallet got so full of dust outputs that it was unable to make any outgoing payments without exceeding the transaction size limit.

I made a change to my CLAM repository which aims to prevent this from happening again in the future. It could do with some peer review and testing before it gets into the official releases.

Thanks for the quick reply and assist... wallet is open again...

richie@bittrex

Can the dev team please get a hold of us?  having some issues with the wallet

richie@bittrex

ShapeShift.io has released the first-ever cryptocurrency exchange app for iPhone. Buy or sell CLAMs instantly and on-the-go with the ShapeShift App.

Download the app: http://apple.co/1FU6Njm

Learn about the app in this Forbes article: http://onforb.es/1dtZqVX

NOTE: ShapeShift will be adding their Android app soon. Stay tuned!

Well written; as always.

---

I think this portion deserves emphasis.

If someone wanted to steal your BTC, LTC and/or DOGE - there are easier, less suspect, ways to go about it.

I can try to explain how it works...

Replace BTC with LTC or DOGE throughout, because it applies to them just the same... for the sake of simplicity I'll assume you're importing a BTC private key.

When the initial distribution was made, the CLAM developers looked at the BTC blockchain, and made a list of all the addresses that had funds. They converted each BTC address into the corresponding CLAM address. The only difference is the "version number" that is used to convert the RIPE-MD hash into an address - in BTC it's version 1 (which makes BTC addresses begin with a '1') and in CLAM it's version 137 (which makes CLAM addresses begin with an 'x'). Then they funded each of the corresponding CLAM addresses with 4.6 CLAMs.

To spend those 4.6 CLAM outputs, you need the addresses' private keys. The private key for each CLAM address is the same as the corresponding BTC address' private key. To spend an output, you create a transaction that moves the value to a new address, and sign it using the private key. Then you broadcast the signed transaction to the network. The private key itself is only used for signing and isn't broadcast.

Whether "the keys are secure" or not depends on whether the CLAM client software is trustworthy or not. You are giving it your private keys, and trusting it to only use them to sign a transaction that moves your 4.6 CLAMs for you. In theory it is possible that it could also check whether there is a balance at the corresponding BTC address. It could, in theory steal any such BTC. There have been no reports ever of the CLAM client software stealing anyone's BTC, so it's likely safe. Also the source code is open source. You can inspect it, and build the client for yourself from source. That's what I do.

Incidentally, note that any random shitcoin wallet you download is just as able to steal your BTC. When you download and run a program, it can do whatever it wants on your computer. There's nothing to stop it looking in your bitcoin folder and uploading your BTC private keys to its author. There's nothing to stop it watching you type your wallet passphrase into the Bitcoin wallet, and then telling the passphrase to its owner. The message here is to be careful *whenever* you download and run programs from the Internet. Any program is potentially coin-stealing malware.

This probably isn't what you were hoping to hear, but it's the truth. Downloading and running programs basically allows the program's author to do whatever he likes on your computer, whether or not that program has an "import wallet' menu entry.

Personally I trust the CLAM client, and have imported wallets which have hundreds of BTC still in them without any issue.

Thank you. 

Not to worried about this key in particular (old empty wallet) but I will be following to see if there is a good explanation to what happens to the keys.