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

[BayAreaCoins]

\
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!

[1713873435]

1713873435

[1713873435]

1713873435

[picolo]

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?

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.

[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

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!

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

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.

[shawn2025]

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]

I've tagged a new release now, v1.4.7, which will identify itself correctly.

I'm starting to see it show up on my nodes already:

      7         "inbound" : false,
     96         "inbound" : true,

     41         "subver" : "/Satoshi:1.4.3.1/",
     18         "subver" : "/Satoshi:1.4.3/",
     41         "subver" : "/Satoshi:1.4.4/",
      3         "subver" : "/Satoshi:1.4.7/",

[almightyruler]

I've just downloaded (via github) and compiled v1.4.7.0-unk; initial run dies and advises to try -reindex, but redoing with that switch seems to have deleted the db, and it's now syncing from scratch via peers. Is this normal?

edit: I note that the OP mentions "Requires resync/reindex" for the CLAMspeech client, but that seems ambiguous, since resyncing and reindexing are two quite different things...

[dooglus]

I've just downloaded (via github) and compiled v1.4.7.0-unk; initial run dies and advises to try -reindex, but redoing with that switch seems to have deleted the db, and it's now syncing from scratch via peers. Is this normal?

edit: I note that the OP mentions "Requires resync/reindex" for the CLAMspeech client, but that seems ambiguous, since resyncing and reindexing are two quite different things...

It depends what version you were running before. If it was anything from the last couple of months it shouldn't have asked you to reindex. Even if it did, it shouldn't need to redownload anything, just reindex it, so I've no idea what went wrong there.

Incidentally, see https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191 for a bootstrap.dat file that will let you download the blockchain quicker than getting it from the p2p network.

[almightyruler]

I've just downloaded (via github) and compiled v1.4.7.0-unk; initial run dies and advises to try -reindex, but redoing with that switch seems to have deleted the db, and it's now syncing from scratch via peers. Is this normal?

edit: I note that the OP mentions "Requires resync/reindex" for the CLAMspeech client, but that seems ambiguous, since resyncing and reindexing are two quite different things...

It depends what version you were running before. If it was anything from the last couple of months it shouldn't have asked you to reindex. Even if it did, it shouldn't need to redownload anything, just reindex it, so I've no idea what went wrong there.

I was running a pre-clamSPEECH version, identified as v1.4.3.0-g32a928e, so I expected to have to reindex... but not sync from scratch.

I've had some (bad) experiences with Bitcoin-QT where it pops up a dialog informing me that the database is corrupt, and would I like to rebuild it - except that 'rebuild' means a sync from scratch. Perhaps this is the same sort of thing which is happening with the headless clamd.

Incidentally, see https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191 for a bootstrap.dat file that will let you download the blockchain quicker than getting it from the p2p network.

Can't the newer versions of clamd generate their own bootstrap file? I have a complete and valid blockchain db here, but it's apparently useless to the new version!

Does the upgrade require a REINDEX (local thrashing of HD to rebuild index) or a RESYNC (complete download of blockchain via the internets) ?

[SuperClam]

Does the upgrade require a REINDEX (local thrashing of HD to rebuild index) or a RESYNC (complete download of blockchain via the internets) ?

Data was added to the chain for the extra data added to getinfo, regarding the currently "dug" money supply.

Either will solve the problem, a re-index is fine if you already have the chain; and in fact, the client should have advised you to reindex via prompt.

[almightyruler]

Does the upgrade require a REINDEX (local thrashing of HD to rebuild index) or a RESYNC (complete download of blockchain via the internets) ?

Data was added to the chain for the extra data added to getinfo, regarding the currently "dug" money supply.

Either will solve the problem, a re-index is fine if you already have the chain; and in fact, the client should have advised you to reindex via prompt.

I'm using the headless clamd.

Error loading block index database : try running with -reindex

Did as instructed...

[picolo]

0.007/BTC is very unsustainable when some bitcoin businesses have tens of thousands of CLAM and some will dump them on exchanges.

[dooglus]

Can't the newer versions of clamd generate their own bootstrap file? I have a complete and valid blockchain db here, but it's apparently useless to the new version!

Does the upgrade require a REINDEX (local thrashing of HD to rebuild index) or a RESYNC (complete download of blockchain via the internets) ?

Just a reindex.

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

It really shouldn't be, unless for some reason it's using a different data directory.

[almightyruler]

Can't the newer versions of clamd generate their own bootstrap file? I have a complete and valid blockchain db here, but it's apparently useless to the new version!

Does the upgrade require a REINDEX (local thrashing of HD to rebuild index) or a RESYNC (complete download of blockchain via the internets) ?

Just a reindex.

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

It really shouldn't be, unless for some reason it's using a different data directory.

- 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

[picolo]

What price will we see when dooglus leaves CLAM and start just-dice with Bitcoin?

[chilly2k]

0.007/BTC is very unsustainable when some bitcoin businesses have tens of thousands of CLAM and some will dump them on exchanges.

What price will we see when dooglus leaves CLAM and start just-dice with Bitcoin?

   Is somebody looking for cheap clams?      And Douglus has already said several times he will not be going back to bitcoin. 

[MinermanNC]

Hey gang, new to clam here. I am downloading client 1.4.5 is this the latest wallet to use? and also am downloading a bootstrap mentioned in previous post here. Ok, just don't want to waste time with wrong client

THX

[Nthused]

I've just found some CLAMs in my old wallets

[rocoro]

Hey gang, new to clam here. I am downloading client 1.4.5 is this the latest wallet to use? and also am downloading a bootstrap mentioned in previous post here. Ok, just don't want to waste time with wrong client

THX

v1.4.7 will be available soon as binaries,  if not already.  
Its' already available as sourcecode: https://github.com/nochowderforyou/clams/releases

So, I wouldn't install 1.4.5..  wait for 1.4.7

[MinermanNC]

Hey gang, new to clam here. I am downloading client 1.4.5 is this the latest wallet to use? and also am downloading a bootstrap mentioned in previous post here. Ok, just don't want to waste time with wrong client

THX

v1.4.7 will be available soon as binaries,  if not already.  
Its' already available as sourcecode: https://github.com/nochowderforyou/clams/releases

So, I wouldn't install 1.4.5..  wait for 1.4.7

ok  thanks, Ill check it out