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

I made as you describe but when I insert in the console my BTC address private key it says that it's not a valid private key (error -5).
I write importprivkey

heard a few complaints about yobit not withdrawing clam requests. any news on this?

Once you have coins on your address it will be seen by the network.

Dooglus, thank You.
One more question, unlocking for staking is valid for some time or until wallet is closed?

I am considering to put 5 btc on staking (in Clam of course) for long time.
Safety is very important for me.

Am I safe if wallet.dat is stolen and encrypted (but unlocked for staking only).

Only transactions are broadcast to the network, therefore only those addresses referenced in transactions are “seen” by the network.

Cheers

Graham

hello, i just download clam wallet Windows 1.4.17 64.. after wallet complete sync. i create some address. xPBHcqCd4tJE4tXSNxVZh2HACCF6ckgwzX.. i check at http://www.khashier.com/address/xPBHcqCd4tJE4tXSNxVZh2HACCF6ckgwzX is got some msg say Address not seen on the network. how to i fix ?

You can't stake if the wallet is encrypted and not unlocked.

You can unlock it "just for staking".

RPC:

    walletpassphrase [stakingonly]
    Stores the wallet decryption key in memory for seconds.
    if [stakingonly] is true sending functions are disabled.

Is it going to disable staking rewards?

Thank you Dooglus.

Command line:

  clamd encryptwallet

GUI:

  Misc -> Encrypt Wallet

The CLAMs were given out years ago. You can claim them whenever you like.

That's not how it works.

To claim your CLAMs you need to sign a transaction using your BTC private keys. There's no mechanism to claim your CLAMs simply by signing a message.

Your CLAM private keys are *the same* as your BTC private keys. You claim your CLAMs in exactly the same way as you spend your BTC - by signing a transaction using your BTC private key.


Signed messages aren't going to help you.

What you could do:

1. download the CLAM client on your online machine
2. run it, and let it sync up to at least block 10,000
3. shut it down, and copy the client and the whole CLAM data directory onto your offline machine
4. on the offline machine, import your BTC private keys; let it rescan the first 10k blocks
5. on the offline machine, create a transaction that spends your CLAMs; maybe to your exchange deposit address
6. on the offline machine, 'getrawtransaction ' to get the raw transaction data
7. copy the raw transaction information to the online machine
8. on the online machine, 'sendrawtransaction ' to broadcast it to the network

That way you've not exposed your private keys to anything other than the offline machine.

So exchanges are having problems with the CLAM wallet but won't tell anyone what problems they are having.

What do you want the CLAM team to do about that? I have tried talking to poloniex about their issues but they won't reply to me.

I hear that xploited has a new version of the CLAM client almost ready to go. It's based on a much newer version of Bitcoin Core, so should be better at syncing the chain.

I suspect that a lot of the problems the exchanges are having is due to receiving tens of thousands of dust payments from a faucet. The wallet software really doesn't deal well with receiving so many deposits. At Just-Dice I configured the wallet to simply ignore any deposit less than 0.001 CLAMs, simply by putting

  mininput=0.001

in the clam.conf configuration file. That entirely solved the problem. I would recommend that the exchanges do the same (if they would listen to me).

I believe so.


Yes. You can supply information about unknown transactions in the 2nd argument to 'signrawtransaction'.


I tried doing this earlier today with the dogecoin client. Someone had converted their Just-Dice CLAM deposit address to a DOGE address and sent some DOGE there, thinking for some reason that the site would convert it to CLAMs. What happened was nothing, and the DOGE just sat there. He made a ticket asking for them back, and I was able to create and sign a raw transaction in my out-of-date DOGE client using just information from a DOGE block explorer (and, of course, the private key). When I tried to broadcast the transaction using my unsynced DOGE client it told me:


so I had to use an online transaction broadcasting site - and that worked.

So I would guess that using your unsynced CLAM client also won't work for broadcasting the tx, but using the just-dice pushtx page will work.


Here's how I did the DOGE thing:

1. on the Just-Dice hot wallet, I extracted the private key of the user's CLAM deposit address:

p=$(clamd dumpprivkey $depost_address)

2. on my laptop I used a script to convert the CLAM private key to a DOGE private key. You won't need to do this, since the CLAM client accepts BTC private keys natively I think:

d=$(~/Source/Python/clampriv.py $p | grep DOGE | awk '{print $2}')

3. Create and sign a raw transaction:

dogecoind signrawtransaction $(dogecoind createrawtransaction '[{"txid":"b9e37a2fd9403fe4c893fd414757dcf5d85d9a22066895d5931ea13b2b774ca2","vout":1}]' '{"XXX":554.77419355}') '[{"txid":"b9e37a2fd9403fe4c893fd414757dcf5d85d9a22066895d5931ea13b2b774ca2","vout":1,"scriptPubKey":"76a91459646c4f28260793d958b9c46c5cb78aa9a4616388ac"}]' '["'$d'"]'

Then encrypt it

TY BayAreaCoins.

Still I am concerned about open wallet issues.

You can't stake with an encrypted wallet FYI.

Maybe it is obvious, but not to me...

How can I encrypt my wallet with clams.
I am considering security issues.

Tnx

yes, forever.

Are they still giving free CLAMs?

Signing / Verify an address to claim my clams.

I have some old paperwallets that are still in use, so I'd rather not expose any information outside of a signed message, using an offline computer running brainwallet software.

However, I open the software, change the network to CLAM, and then sign a very basic message - it is during the verification process on my QT client that I get a verification failure error.

I have even performed this in 'reverse'.  Basically signing a message on the QT client, just to be sure that the data elements that I'm using are in fact correct.  Any ideas greatly appreciated.

Running The CLAM Client v.1.4.17 (aka QT client).