[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[crazyearner]

ok, another silly question. Is their any advantage to running more than one wallet, on different PC's verses using just one wallet on one pc? since clams can be split, or is there any limitations using one wallet for everything lol 
THX again,

Bad things can happen if you run the same wallet.dat file on multiple instances and/or computers etc..
I read in the past about how you shouldn't do that,  I would have to dig up a link
I think it would be ok with different wallet.dat files though on separate machines.

Yes you are very correct on that if using the same wallet.dat. What I am wondering is the latter, running say 5 wallets on their own pc, clean installs (own wallet.dat) So say, which is better or no difference? ex: 500 clams staking in 1 wallet on 1 pc, or 100 clams each staking on 5 different wallets. (100 on each wallet) Just didn't know if their is anything to be gained by multiple wallets, perhaps better for the client network I suppose but probably no real gain in actual staking rate or odds.... If you see what I am saying lol but I still wonder or maybe I am thinking to much into it 
THX

The only time it might be more efficient to split over multiple machines is in a situation where you have many thousands of outputs.
dooglus made some changes to the client over at Just-Dice, for instance.

The chance of a regular user hitting that bottleneck is almost non-existent.
So, unless you see the CPU on your system consistently maxed out; there is no benefit to having multiple machines.

In fact, it could possibly work against you, as you may orphan your own blocks.

Any guide on how to claim coins from doge or btc into clams. Cant find guide or process to do so?

If you are using standard wallet.dat files and clam-qt, the process is extremely simple:
We recommend that you empty the wallet before importing for security, though it is not required.

1. Back-up all wallet.dat files.
2. File -> Import Wallet.
3. Browse to wallet.dat file.
4. Done.


If you are using the clamd, the rpc/cli command is "importwallet".

So I just import each wallet for each coin like doge wallet.dat and then btc and so forth for the coins you support. How does this reflect my clams wallet tho does that remain not affected and stays theri and updates with each wallet.dat import with the coins etc?

[crazyearner]

so simple now have over 100 clams so far need to finish up importing rest of wallets and backups made over the years maybe have more clams

So looking at it you get 4.60545574 per address depending on how much it has on it or is this  base factor each address got 4.60545574 or so in the list you sent out too. Interesting idea tho to send coins out.

[MinermanNC]

ok, another silly question. Is their any advantage to running more than one wallet, on different PC's verses using just one wallet on one pc? since clams can be split, or is there any limitations using one wallet for everything lol  

THX again,

Bad things can happen if you run the same wallet.dat file on multiple instances and/or computers etc..

I read in the past about how you shouldn't do that,  I would have to dig up a link

I think it would be ok with different wallet.dat files though on separate machines.

Yes you are very correct on that if using the same wallet.dat. What I am wondering is the latter, running say 5 wallets on their own pc, clean installs (own wallet.dat) So say, which is better or no difference? ex: 500 clams staking in 1 wallet on 1 pc, or 100 clams each staking on 5 different wallets. (100 on each wallet) Just didn't know if their is anything to be gained by multiple wallets, perhaps better for the client network I suppose but probably no real gain in actual staking rate or odds.... If you see what I am saying lol but I still wonder or maybe I am thinking to much into it  

THX

Just show advanced options in send..  and use the inputs button.

Send coins to different addresses (that you create in same wallet) using that,   to split them up..   no reason to use other wallet.dat's  

You can keep them all split up in the  same wallet,  I'm guessing you could even split the inputs/stacks up in the same address.

I keep my coins split up in small stacks/amounts, so others don't get tied up while staking.

Is that what you're talking about?

Hey thanks, both great answers from you and superclam. I got the big picture now    and see how the splitting eliminates the need for other wallets etc. I sure wish I could have that problem one day of my cpu meter tacking out due to too many coins in a single wallet. (or bottle necking)  lol

As of now I have five receive addresses with an even amount of coin waiting to mature. I think its 8 hours is that correct, before staking can occur?

Thanks for the clarifications 

[dooglus]

As of now I have five receive addresses with an even amount of coin waiting to mature. I think its 8 hours is that correct, before staking can occur?

4 hours after they last were involved in a transaction, and 510 blocks after they were last staked.

510 blocks takes about 8 hours.

[dooglus]

What makes you think it is redownloading the data rather than just reindexing it?

- Length of time; it's been going for 12 hours, and it's only up to block 115670
- 650k+ lines in debug.log (from current run) referring to orphan blocks
- Many peers are showing large numbers for bytesrecv, tens or hundreds of megabytes worth of data
- Not sure if the txleveldb directory contents vary from install to install, but on the one which I upgraded, at block 5000 or so it was far smaller than my other install

Pretty convincing.

I don't know what to tell you then.

[MinermanNC]

As of now I have five receive addresses with an even amount of coin waiting to mature. I think its 8 hours is that correct, before staking can occur?

4 hours after they last were involved in a transaction, and 510 blocks after they were last staked.

510 blocks takes about 8 hours.

ok, got it, thats better yet! lol

THX

a cool concept by the way,  clams surprised it hadn't caught my attention sooner lol

[crazyearner]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

[Nthused]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

dooglus has made a bootstrap file for CLAMs, I used it myself last night to sync up the chain.

CLAMS Bootstrap.dat

https://s3.amazonaws.com/dooglus/bootstrap.dat

[MinermanNC]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

I used that bootstrap when I installed my wallet this afternoon, and was updated within a few hours or less

[crazyearner]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

dooglus has made a bootstrap file for CLAMs, I used it myself last night to sync up the chain.

CLAMS Bootstrap.dat

https://s3.amazonaws.com/dooglus/bootstrap.dat

Thansk for the info downloading now hope this sorts problem out. Wallet might need to be improved for blockchain to be downloaded maybe an improvement to add

[Nthused]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

dooglus has made a bootstrap file for CLAMs, I used it myself last night to sync up the chain.

CLAMS Bootstrap.dat

https://s3.amazonaws.com/dooglus/bootstrap.dat

Thansk for the info downloading now hope this sorts problem out. Wallet might need to be improved for blockchain to be downloaded maybe an improvement to add

Make sure to delete everything in your CLAMS roaming folder except the wallet & place the bootstrap in there for a clean sync.

[crazyearner]

Why this coin take so long to download have all updated nodes and taking so long to download blockchain.

dooglus has made a bootstrap file for CLAMs, I used it myself last night to sync up the chain.

CLAMS Bootstrap.dat

https://s3.amazonaws.com/dooglus/bootstrap.dat

Thansk for the info downloading now hope this sorts problem out. Wallet might need to be improved for blockchain to be downloaded maybe an improvement to add

Make sure to delete everything in your CLAMS roaming folder except the wallet & place the bootstrap in there for a clean sync.

What about the clamspeech.txt file is that needed. Left that in their along with wallet.dat removed everything else now waiting for import to finish off

[MinermanNC]

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 

[chriswen]

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 

Yeah, I also didn't need to delete anything.

[almightyruler]

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.

[SuperClam]

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.

[SuperClam]

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.

[dooglus]

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://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

[dooglus]

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.

[xploited]

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.

It was meant to be removed, it was for debugging. I write silly messages to myself. What can I say.