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

[dooglus]

Is something wrong with the staking?  Because I haven't been getting any clams either..  I used to get around 1 per day, and have a somewhat good amount set for staking.  Haven't been getting anything for the last week.. which seems very unusual.  My time is sync'd, and block numbers seem fine too!

Or, is it just because tons more people are staking??

I estimate that each 360 CLAMs in your wallet should stake about once per day on average at the moment. This is based on a single datapoint (JD has 360k CLAMs and stakes 1k times per day). More datapoints from other large stakers would be appreciated.

There's another ~100k CLAMs staking outside of JD (since 400 blocks per day are being staked outside of JD) so I guess there are other big stakers out there.

[rocoro]

Is something wrong with the staking?  Because I haven't been getting any clams either..  I used to get around 1 per day, and have a somewhat good amount set for staking.  Haven't been getting anything for the last week.. which seems very unusual.  My time is sync'd, and block numbers seem fine too!

Or, is it just because tons more people are staking??

I estimate that each 360 CLAMs in your wallet should stake about once per day on average at the moment. This is based on a single datapoint (JD has 360k CLAMs and stakes 1k times per day). More datapoints from other large stakers would be appreciated.

There's another ~100k CLAMs staking outside of JD (since 400 blocks per day are being staked outside of JD) so I guess there are other big stakers out there.

Well for the set amount I have (actually above 360)  I haven't seen anything for days.
Time is sync'd,  block number same as block number at http://khashier.com/
Plus, the amounts that I have set up total above 360 and are split up in different addresses, so I'm not waiting for any maturing.

I don't know.. wallet is unlocked, icon says its staking.
Just seems strange.  

[dooglus]

I don't know.. wallet is unlocked, icon says its staking.
Just seems strange.

Have you been seeing orphan blocks, or just nothing at all?

If you PM me your IP address, I'll check my logs and see if I notice anything weird relating to your peer. I expect you will have connected to at least one of my peers recently.

[rocoro]

I don't know.. wallet is unlocked, icon says its staking.
Just seems strange.

Have you been seeing orphan blocks, or just nothing at all?

If you PM me your IP address, I'll check my logs and see if I notice anything weird relating to your peer. I expect you will have connected to at least one of my peers recently.

Nothing at all..  no orphaned blocks either. 
I'll try to send a pm soon!

[rocoro]

CLAM client v1.4.5 TEST-build


Windows 32bit
Windows 64bit
Linux 64bit
OSX

I installed the new win64 version and 5 of my staked clams disappeared. Here is the story: My wallet, ver 1.4.4, started to stake several times in an hour but after 2 confirmations the staked clam would show conflicted. Five of the staked clams held on for 9,12,15,16,18 confirmations. I installed new wallet and those five now show conflicted (22 total now show conflicted). So far new wallet has not staked and shows 10 days to next stake. I have 35 clams in wallet how often should they stake? I was getting one clam per week but the last two weeks nothing, other than the 22 conflicted.

Just out of curiosity,  what was the issue in this case?

Edit: never mind.. probably because of version 1.4.4 ?

[dooglus]

An issue was reported recently concerning a lack of connections in v1.4.5:
  https://github.com/nochowderforyou/clams/issues/137

Is anyone running v1.4.5 and actually getting incoming connections?

Running "getpeerinfo" in the debug console will show you "inbound" for each peer. Is it "true" for anyone?

[rocoro]

An issue was reported recently concerning a lack of connections in v1.4.5:
  https://github.com/nochowderforyou/clams/issues/137

Is anyone running v1.4.5 and actually getting incoming connections?

Running "getpeerinfo" in the debug console will show you "inbound" for each peer. Is it "true" for anyone?

Hey,  mine all show false ! 

How do I fix?

Thanks

[rocoro]

An issue was reported recently concerning a lack of connections in v1.4.5:
  https://github.com/nochowderforyou/clams/issues/137

Is anyone running v1.4.5 and actually getting incoming connections?

Running "getpeerinfo" in the debug console will show you "inbound" for each peer. Is it "true" for anyone?

Hey,  mine all show false ! 

How do I fix?

Thanks

Is it now mandatory to have to use UPnP or port forwarding???

I didn't have to do this in previous versions!

[rocoro]

So perhaps v1.4.5 clients are somehow failing to advertise themselves properly?

12 hours later, I still see no inbound connections even though if a peer tried to connect it would be accepted.

So this could be the problem I'm experiencing?  

I reverted back to 1.4.3 and seems like getpeerinfo peers are all still false but I do notice I have full / more connections!

Maybe staking on 1.4.3 will be better for me?,  I'll wait and see what happens..

[Small]

Would it be smart to make an online-wallet service for CLAM?

Just-Dice.com acts as an online CLAM wallet service, so long as you can trust yourself not to gamble.

I see, also a big staking pool too.
But I still want to try and see if making one would pop haha

[jd1959]

Hi Guys

Is there anyway to reject peers running 1.4.4 as there just sucking large amounts of data.

Jon 

[rocoro]

So perhaps v1.4.5 clients are somehow failing to advertise themselves properly?

12 hours later, I still see no inbound connections even though if a peer tried to connect it would be accepted.

So this could be the problem I'm experiencing?  

I reverted back to 1.4.3 and seems like getpeerinfo peers are all still false but I do notice I have full / more connections!

Maybe staking on 1.4.3 will be better for me?,  I'll wait and see what happens..

I turned on port forwarding for my 1.4.3 client,   still the same results..  inbounds are false in getpeerinfo. 
And still no stakes - but I realize might take awhile yet. 
I'm assuming the same for when I was running 1.4.5 ,  although I could try that again too.
I'll wait to see if there is any fix from devs.

[tadakaluri]

After importing my BTC and Doge wallets, nothing is happening - Why?

The only thing I found was Number of New Addresses Created (with the name of 'importwallet'.

[almightyruler]

An issue was reported recently concerning a lack of connections in v1.4.5:
  https://github.com/nochowderforyou/clams/issues/137

Is anyone running v1.4.5 and actually getting incoming connections?

Running "getpeerinfo" in the debug console will show you "inbound" for each peer. Is it "true" for anyone?

I just did 'getpeerinfo' and was shocked to find that I have only one (1) connection. This is on a dedicated server, with a dedicated static IP, that allows direct inbound connects. In addition, the CLAM client has been running (stable/uninterrupted) for nearly 2 months.

I haven't upgraded to any of the "free speech" clients yet. Are newer clients banning older? Here's part of my 'getinfo':

   "version" : "v1.4.3.0-g32a928e",
    "protocolversion" : 60014,
    "walletversion" : 60000,


Block 329156 has a hash of ccf61cfa3597334c74480c2da398b53d203ca4c50a04809fafe26c48947d62c4 , which matches with khashier, so I guess I'm not forked.

So the question remains... why do I only have a single peer?

edit: Just started the same version on another dedicated server, 5  8 connnections so far.

[rocoro]

So the question remains... why do I only have a single peer?

edit: Just started the same version on another dedicated server, 5  8 connnections so far.

I started up 1.4.5 again,  I'm showing only one peer with inbound = true.  & only 4 connections.

Edit: now 7 connections, with 3 inbound true peers.

[rocoro]

Why are there so many peers with 1.4.4 still ?!!!!
 

[almightyruler]

Why are there so many peers with 1.4.4 still ?!!!!
 

Was told earlier in this thread that it's not a mandatory update. As far as I can remember, the recent changes are mostly cosmetic (such as fixing the stake estimate), plus that 'free speech' thing, which doesn't interest me.

Second server up to 28 connections; first still on 1.

I thought that maybe the thread which connects to peers was dead, but I've had a look at debug.log, and it seems to be only trying to connect to one peer, which is down...

2015-02-07 02:24:16 connect() to 24.179.45.218:31174 failed after select(): Connection refused
2015-02-07 02:25:17 connect() to 24.179.45.218:31174 failed after select(): Connection refused
2015-02-07 02:26:18 connect() to 24.179.45.218:31174 failed after select(): Connection refused
2015-02-07 02:27:19 connect() to 24.179.45.218:31174 failed after select(): Connection refused

I suspect that restarting the client will kick it back into action, but the question is how it got to this point in the first place?

Hmmm. Now I can see there's nothing listening on port 31174, so it won't accept inbound connections. I guess the client must be partially crashed. This may also explain why it hasn't staked for nearly 2 weeks.

[dooglus]

Hmmm. Now I can see there's nothing listening on port 31174, so it won't accept inbound connections. I guess the client must be partially crashed. This may also explain why it hasn't staked for nearly 2 weeks.

Check the clam.conf and/or command-line options.

If you specify "connect=" anywhere, it will only connect to that/those specific peers, and won't listen for incoming connections.

It sounds like that's what you may have done.

[almightyruler]

Hmmm. Now I can see there's nothing listening on port 31174, so it won't accept inbound connections. I guess the client must be partially crashed. This may also explain why it hasn't staked for nearly 2 weeks.

Check the clam.conf and/or command-line options.

If you specify "connect=" anywhere, it will only connect to that/those specific peers, and won't listen for incoming connections.

It sounds like that's what you may have done.

Cheers, you're right. I'd forgotten I changed to a custom "outbound only to select peers" config when we had problems with clients on old chains repeatedly requesting blocks.

Back to a generic config, and crossing my fingers for a stake sometime soon.

[rocoro]

Hmmm. Now I can see there's nothing listening on port 31174, so it won't accept inbound connections. I guess the client must be partially crashed. This may also explain why it hasn't staked for nearly 2 weeks.

Check the clam.conf and/or command-line options.

If you specify "connect=" anywhere, it will only connect to that/those specific peers, and won't listen for incoming connections.

It sounds like that's what you may have done.

Dooglus,  would there be some way that I could reject all the 1.4.4 clients?