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

[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?

[SuperClam]

We don't censor our thread

(much)

(Only once that I remember, it was spam; and pretty sure I even quoted the post before deleting it for posterity )

Anyway, my poor laptop spent the night compiling historical day-by-day stats of the total and active supply stats so coinmarketcap.com can fill in the history on their CLAM market cap chart. As a result I was able to generate this chart showing block count and active supply over time:
The raw data is here: http://privatepaste.com/18a59b4f72
The post to the coinmarketcap thread is here: https://bitcointalk.org/index.php?topic=199685.msg10379165#msg10379165

Absolutely awesome.
Making another promise to myself to fiddle with gnuplot sometime soon

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'.

Please ensure that your client is sync'd past block 10,000.
The initial distribution CLAMS were all distributed by that point.

If you are absolutely certain your addresses held a balance above dust on May 12th, and your client sync'd past block 10,000, yet you still do not see any claimed CLAMS: please stop in to #clams on freenode irc.  If you do not have an IRC client, you can visit the official website at http://www.clamclient.com and click the "support" tab to use a web client and connect directly to the channel.

[SuperClam]

Re-Post from dooglus, via IRC #clams:

<@dooglus> running clamd -externalip=a.b.c.d with your actual external IP address seems to fix the problem

So, if anyone is having connectivity problems with 1.4.5, a possible work around would involve running the client with the -externalip=yourIP flag.

[rocoro]

Re-Post from dooglus, via IRC #clams:

<@dooglus> running clamd -externalip=a.b.c.d with your actual external IP address seems to fix the problem

So, if anyone is having connectivity problems with 1.4.5, a possible work around would involve running the client with the -externalip=yourIP flag.

Interesting,  thank you..  I will try that

[dooglus]

We don't censor our thread

(much)

(Only once that I remember, it was spam; and pretty sure I even quoted the post before deleting it for posterity )

(You deleted one of my posts once when I wrote "Careful. The CLAMS listed on that page isn't the CLAMs that this thread is about.")

[dooglus]

Re-Post from dooglus, via IRC #clams:

<@dooglus> running clamd -externalip=a.b.c.d with your actual external IP address seems to fix the problem

So, if anyone is having connectivity problems with 1.4.5, a possible work around would involve running the client with the -externalip=yourIP flag.

Interesting,  thank you..  I will try that

Alternatively, I found the cause of the problem and fixed it.

See https://github.com/nochowderforyou/clams/issues/137 for details.

I tagged a new release, v1.4.6, which I'm guessing will have binaries made available soon-ish.

[BayAreaCoins]

We don't censor our thread

Says the self-modded thread

Kinda like the Police that don't shoot you,  but carry a full auto in their trunk  

Sorry I couldn't resist

[SuperClam]

We don't censor our thread

(much)

(Only once that I remember, it was spam; and pretty sure I even quoted the post before deleting it for posterity )

(You deleted one of my posts once when I wrote "Careful. The CLAMS listed on that page isn't the CLAMs that this thread is about.")

(Crud, you are right, that makes two. The spam one and also the link to that fake-clam-coin thread. Your post quoted the fake-clam-coin link, thus had to be cleansed [As you simultaneously removed the link from the quote]. I remember a subsequent apology.)

We don't censor our thread

Says the self-modded thread
Kinda like the Police that don't shoot you,  but carry a full auto in their trunk  
Sorry I couldn't resist

May not believe me, but we considered and even preferred to not make it a self-modded thread.
Then, considered the possible impact if a malicious person posting a fake coin stealing version of the client.


So, we plea bargained; and decided to make it self-moderated just in case, but almost never use it.

Considering the rampant troll infestation 'round these parts, I think two occasions of using it in what is now 2,362 posts..... is well..... not too bad?


Also, your Police reference doesn't hold.
 
Clearly based on recent news, they do shoot you.  

[dooglus]

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

Yes, if you can build from source.

See https://github.com/dooglus/clams/commit/0022ff97

Edit: except it appears that v1.4.5 also calls itself v1.4.4, so that commit will probably reject v1.4.5 peers too.