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

shawn2025

jr. member

Activity: 47

Merit: 1

Quote from: dooglus on February 07, 2015, 07:39:07 PM

Quote from: dooglus on February 07, 2015, 07:38:37 AM

Quote from: rocoro on February 06, 2015, 10:12:09 PM

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.

Releases v1.4.5 and v1.4.6 both incorrectly identify themselves on the p2p network as being v1.4.4, so the approach I took in the above commit doesn't work.

I've tagged a new release now, v1.4.7, which will identify itself correctly. Once it has been adopted we can start rejecting peers calling themselves v1.4.4, but until binaries for it are available doing so would probably severly limit our chances of getting connected to enough peers.

There's probably a way to detect v1.4.4's misbehaviour and ban it according to that, but I don't have time to look into doing that at the moment.

MacClient running 1.4.5 Thanks! My symptoms are on and off staking, synchnode false etc. Lots of 1.4.4 still running.
Thanks for the information! Much appreciated!
I'll keep my eye out for MacOS vers. 1.4.7

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dooglus on February 07, 2015, 07:38:37 AM

Quote from: rocoro on February 06, 2015, 10:12:09 PM

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.

Releases v1.4.5 and v1.4.6 both incorrectly identify themselves on the p2p network as being v1.4.4, so the approach I took in the above commit doesn't work.

I've tagged a new release now, v1.4.7, which will identify itself correctly. Once it has been adopted we can start rejecting peers calling themselves v1.4.4, but until binaries for it are available doing so would probably severly limit our chances of getting connected to enough peers.

There's probably a way to detect v1.4.4's misbehaviour and ban it according to that, but I don't have time to look into doing that at the moment.

rocoro

legendary

Activity: 938

Merit: 1000

Quote from: dooglus on February 07, 2015, 07:16:42 AM

Quote from: rocoro on February 06, 2015, 10:59:18 PM

Quote from: SuperClam on February 06, 2015, 10:37:36 PM

Re-Post from dooglus, via IRC #clams:

Quote

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

Thanks Dooglus !! Awesome!

picolo

hero member

Activity: 1022

Merit: 500

Quote from: dooglus on February 05, 2015, 03:19:20 PM

Quote from: Chuck on February 05, 2015, 02:36:52 PM

Shouldn't we assume that the developers moved their own BTC/LTC/DOGE into many addresses, sometime before May 12th, and that CLAMS are maybe one of the greatest premines in altcoin history? Wink

It's brilliant because we don't know if the unclaimed CLAMS belong to random people, an exchange's hot wallet, or the devs.

They claim they didn't do this, but there's no way to know for sure.

One thing I'd point out is that CLAM was around for 6 months before Just-Dice started using it, and for that 6 months the price was pretty steadily falling to zero. I would expect most people knowingly sitting on a big pile of unclaimed CLAM would have dug it up and sold it at some point during that 6 months rather than watching as it became increasingly worthless.

That argument possibly doesn't apply to the CLAM developers themselves who would be more likely to be optimistic about CLAM's future, having so much time and energy invested in it.

Some people sold but like you said developers that created a lot of BTC/DOGE/LTC addresses probably kept the lion share of them.

No coin is perfect anyway.

BayAreaCoins

legendary

Activity: 4004

Merit: 1250

Owner at AltQuick.com

Quote from: SuperClam on February 07, 2015, 07:37:01 AM

\
Then, considered the possible impact if a malicious person posting a fake coin stealing version of the client.

Ahhh ya that would suck donkey dick!

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: rocoro on February 06, 2015, 10:12:09 PM

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.

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Quote from: dooglus on February 07, 2015, 07:13:51 AM

Quote from: SuperClam on February 06, 2015, 10:14:24 PM

Quote from: dooglus on February 06, 2015, 01:52:24 PM

Quote from: SuperClam on February 06, 2015, 08:46:21 AM

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

Quote from: BayAreaCoins on February 07, 2015, 07:30:24 AM

Quote from: SuperClam on February 06, 2015, 08:46:21 AM

We don't censor our thread

Says the self-modded thread Tongue

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

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

BayAreaCoins

legendary

Activity: 4004

Merit: 1250

Owner at AltQuick.com

Quote from: SuperClam on February 06, 2015, 08:46:21 AM

We don't censor our thread

Says the self-modded thread Tongue

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

Sorry I couldn't resist

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: rocoro on February 06, 2015, 10:59:18 PM

Quote from: SuperClam on February 06, 2015, 10:37:36 PM

Re-Post from dooglus, via IRC #clams:

Quote

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

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: SuperClam on February 06, 2015, 10:14:24 PM

Quote from: dooglus on February 06, 2015, 01:52:24 PM

Quote from: SuperClam on February 06, 2015, 08:46:21 AM

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

rocoro

legendary

Activity: 938

Merit: 1000

Quote from: SuperClam on February 06, 2015, 10:37:36 PM

Re-Post from dooglus, via IRC #clams:

Quote

<@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

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Re-Post from dooglus, via IRC #clams:

Quote

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

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Quote from: dooglus on February 06, 2015, 01:52:24 PM

Quote from: SuperClam on February 06, 2015, 08:46:21 AM

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

)

Quote from: dooglus on February 06, 2015, 01:52:24 PM

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://bitcointalksearch.org/topic/m.10379165

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

Quote from: tadakaluri on February 06, 2015, 07:23:21 PM

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.

rocoro

legendary

Activity: 938

Merit: 1000

Quote from: dooglus on February 06, 2015, 09:55:13 PM

Quote from: almightyruler on February 06, 2015, 09:33:52 PM

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?

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: dooglus on February 06, 2015, 09:55:13 PM

Quote from: almightyruler on February 06, 2015, 09:33:52 PM

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.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: almightyruler on February 06, 2015, 09:33:52 PM

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

legendary

Activity: 2268

Merit: 1092

Quote from: rocoro on February 06, 2015, 09:13:42 PM

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

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

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.

rocoro

legendary

Activity: 938

Merit: 1000

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

rocoro

legendary

Activity: 938

Merit: 1000

Quote from: almightyruler on February 06, 2015, 08:30:00 PM

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

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.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: dooglus on February 06, 2015, 02:37:00 PM

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

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

Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 384. (Read 1151252 times)