Thanks
Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 381. (Read 1151252 times)
February 10, 2015, 09:32:39 AM
I'm looking for information about the clam qt-based client and whether or not if it supports the same JSON/RPC commands that the bitcoin client uses.
Thanks
Thanks
February 09, 2015, 11:10:12 PM
smoothly walllet , n only staking .
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
Bittrex exchange has been contacted multiple times, via multiple channels, initiated by multiple people.
In the last response that I am aware of staff agreed to re-review CLAM at a future date for consideration.
https://twitter.com/BayAreaCoins/status/554996228497235968
February 09, 2015, 10:31:46 PM
it's good .
I hope that in the near future
I hope that in the near future
February 09, 2015, 10:04:29 PM
smoothly walllet , n only staking .
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
Bittrex exchange has been contacted multiple times, via multiple channels, initiated by multiple people.
In the last response that I am aware of staff agreed to re-review CLAM at a future date for consideration.
February 09, 2015, 09:28:58 PM
smoothly walllet , n only staking .
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
dev dou u can add Clams to bittrex ?
i think clams earn big volume ... n the price stable
February 09, 2015, 09:19:26 PM
How many clams does it take to give a steaking weight 
February 09, 2015, 08:20:47 PM
Also one imported can I just dump privekey of main wallet to keep and the delete wallet dat and import from old one as theirs over 80 to 100 addresses or so addresses in list so far.
It's pretty hard to understand what you're asking.
If you mean:
Also once imported can I just export the privkey of the main wallet, make a note of it, delete wallet.dat then import just the exported privkey into a new wallet?
Then no, you can't. You have 4.6 CLAMs at 20 or 30 different addresses at the moment. You can go to the debug console and run "listunspent". It will give you a list of the funded addresses. Then you can dumpprivkey for just those addresses, make notes of them, delete wallet.dat, make a new wallet, and import them again. That will result in a much smaller wallet.dat file with the same balance.
Or you can send your whole balance to a single address, and just import that address into a new wallet. But then all your CLAM are at a single address in a single output, and will be sitting idle for 8 hours each time they stake.
Does that help?
February 09, 2015, 06:58:13 PM
New wallet up and syncing 
February 09, 2015, 05:53:13 PM
How often is stake generated on coins and whats the % of stake you get for leaving in wallet to stake on etc.
The network aims to stake 1 block per minute, and the block reward is 1 CLAM plus transaction fees.
There's about 480k CLAM attempting to stake, so each 1 CLAM can expect to stake every 480k minutes, or every 8000 hours, or every 333 days.
Alternatively, if you have 333 CLAM, you can expect it to stake once per day on average.
That's about 24*7*100.0 / 8000 = 2.1% per week.
It will get harder over time as we can expect more and more CLAMs to be attempting to stake as time goes on.
Well so far am at about 100 CLAMs Need to find me other wallets and add them into it. Also one imported can I just dump privekey of main wallet to keep and the delete wallet dat and import from old one as theirs over 80 to 100 addresses or so addresses in list so far.
February 09, 2015, 05:50:01 PM
How often is stake generated on coins and whats the % of stake you get for leaving in wallet to stake on etc.
The network aims to stake 1 block per minute, and the block reward is 1 CLAM plus transaction fees.
There's about 480k CLAM attempting to stake, so each 1 CLAM can expect to stake every 480k minutes, or every 8000 hours, or every 333 days.
Alternatively, if you have 333 CLAM, you can expect it to stake once per day on average.
That's about 24*7*100.0 / 8000 = 2.1% per week.
It will get harder over time as we can expect more and more CLAMs to be attempting to stake as time goes on.
February 09, 2015, 05:05:21 PM
How often is stake generated on coins and whats the % of stake you get for leaving in wallet to stake on etc.
February 09, 2015, 01:44:08 PM
Hi Dooglus.. with all these issues is there any way to verify or confirm that let's say you have a current version (1.4.7) wallet, and it would be staking correctly??
I get the feeling a lot of people are not getting the stakes they should.
What should we look for .. are there signs in Debug.log ?
And what would help continue staking.. simply keep restarting the wallet and hope to connect to "good" peers
I get the feeling a lot of people are not getting the stakes they should.
What should we look for .. are there signs in Debug.log ?
And what would help continue staking.. simply keep restarting the wallet and hope to connect to "good" peers
As long as you are running v1.4.7, seeing the same chain as khashier shows, and your client claims that it is staking... then you are.
February 09, 2015, 12:35:22 PM
a) Because v1.4.4 gets a lot of peers to de-sync and keep requesting the same blocks over and over again, wasting other peers' upload capability.
b) Also because v1.4.3.1 to v1.4.5 have a bug that makes most peers fail to advertise their external IP address, making them impossible to discover, severely limiting peer availability.
c) v1.4.5 also has a bug that makes it identify itself as v1.4.4, meaning we can't even easily ban v1.4.4 from the network to work around a) above.
So together we have less available peers, each of which has their bandwidth being wasted, and no easy way of fixing this waste. The three bugs together make the network crappy for the few up to date peers on the network.
Hi Dooglus.. with all these issues is there any way to verify or confirm that let's say you have a current version (1.4.7) wallet, and it would be staking correctly??
I get the feeling a lot of people are not getting the stakes they should.
What should we look for .. are there signs in Debug.log ?
And what would help continue staking.. simply keep restarting the wallet and hope to connect to "good" peers
Edit: removed non-essential question
February 09, 2015, 12:29:35 PM
Edit: while fixing the problem I found this line in the source:
In the event that the client discovers that one of my wallets is corrupted do I really want to see a badly punctuated and capitalized unfunny Lost In Space joke? I'm probably sad enough at that point.
Code:
printf("Corruption will robinson\n");
In the event that the client discovers that one of my wallets is corrupted do I really want to see a badly punctuated and capitalized unfunny Lost In Space joke? I'm probably sad enough at that point.
It was meant to be removed, it was for debugging. I write silly messages to myself. What can I say.
February 09, 2015, 11:46:07 AM
On that note, a minor niggle: clamd (headless) writes the results of the RPC 'importwallet' command to the terminal, rather than the log, even if it's backgrounded. Not quite as bad as the 'fix' on another coin which printf'd debug info about every KGW retarget to the terminal.
Thanks.
The best way to make sure such issues are not forgotten:
https://github.com/nochowderforyou/clams/issues
I made an issue for this, and will push a fix as soon as I've tested it.
https://github.com/nochowderforyou/clams/issues/140
Edit: while fixing the problem I found this line in the source:
Code:
printf("Corruption will robinson\n");
In the event that the client discovers that one of my wallets is corrupted do I really want to see a badly punctuated and capitalized unfunny Lost In Space joke? I'm probably sad enough at that point.
February 09, 2015, 11:31:14 AM
Why this coin take so long to download have all updated nodes and taking so long to download blockchain.
a) Because v1.4.4 gets a lot of peers to de-sync and keep requesting the same blocks over and over again, wasting other peers' upload capability.
b) Also because v1.4.3.1 to v1.4.5 have a bug that makes most peers fail to advertise their external IP address, making them impossible to discover, severely limiting peer availability.
c) v1.4.5 also has a bug that makes it identify itself as v1.4.4, meaning we can't even easily ban v1.4.4 from the network to work around a) above.
So together we have less available peers, each of which has their bandwidth being wasted, and no easy way of fixing this waste. The three bugs together make the network crappy for the few up to date peers on the network.
Work around the problem by getting a copy of bootstrap.dat:
https://bitcointalksearch.org/topic/m.9772191
February 09, 2015, 11:16:53 AM
Compiled Release, CLAM 1.4.7 Test-Build
Windows 32bit
Windows 32bit Installer
Windows 64bit
Windows 64bit Installer
Linux 32bit
Linux 64bit
Mac-OSX
Fresh out of the compiler; please let us know if there are any problems.
Windows 32bit
Windows 32bit Installer
Windows 64bit
Windows 64bit Installer
Linux 32bit
Linux 64bit
Mac-OSX
Fresh out of the compiler; please let us know if there are any problems.
February 09, 2015, 04:38:04 AM
How long it will take to scan the whole blockchain.
If you mean importing the wallet, I tried earlier, and on an Intel i5 it took about 3 minutes.On that note, a minor niggle: clamd (headless) writes the results of the RPC 'importwallet' command to the terminal, rather than the log, even if it's backgrounded. Not quite as bad as the 'fix' on another coin which printf'd debug info about every KGW retarget to the terminal.
Thanks.
The best way to make sure such issues are not forgotten:
https://github.com/nochowderforyou/clams/issues
Why this coin take so long to download have all updated nodes and taking so long to download blockchain.
Getting our network code up-to-snuff is a primary concern (and has been the topic of multiple recent updates).
We aren't there yet.
Speak of which, the current compiled clients listed on the OP post are both "test" builds with known issues.
You will likely want to update to the newest version when it is released very soon.
February 09, 2015, 03:21:26 AM
How long it will take to scan the whole blockchain.
If you mean importing the wallet, I tried earlier, and on an Intel i5 it took about 3 minutes.
On that note, a minor niggle: clamd (headless) writes the results of the RPC 'importwallet' command to the terminal, rather than the log, even if it's backgrounded. Not quite as bad as the 'fix' on another coin which printf'd debug info about every KGW retarget to the terminal.
February 08, 2015, 11:51:41 PM
I just dropped the bootstrap in the roaming folder and didn't delete anything lol, but all seems to work fine either way I guess. 
I also did a doge wallet today and used a bootstrap and simply dropped it in as well, no issues. But I have read it best to delete all else but the wallet.dat etc., but seems to make no difference. Food for thought
I also did a doge wallet today and used a bootstrap and simply dropped it in as well, no issues. But I have read it best to delete all else but the wallet.dat etc., but seems to make no difference. Food for thought Yeah, I also didn't need to delete anything.
Jump to: