Hi Guys

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

Jon 

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

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.

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.

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.

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

---

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

---

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.

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.

(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.)

---

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.