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

[sulfurtank]

It seems like someone (no strings attached) is trying too goddamn hard to crush it. Also there was a market manipulation attempt that flash crashed the price which rippled across the market. Leave the OP more red trust to speedup this exponential blowup.

[seedtrue]

Oh wow. Interesting. Did he provide proof? Where's the wallet coming from and why did he chose to crash the price the way he did instead playing the game calmly and earning more that way?

Guess the recent talk of stopping the digging ability of clams was the next bad result coming from that wooden hammer method he used.

Oh wow. Interesting. Did he provide proof?

He signed 2 messages from 2 of the addresses.

Where's the wallet coming from and why did he chose to crash the price the way he did instead playing the game calmly and earning more that way?

He did not admit to where it was from, but suspicions seem to be that it was a wallet used for cheating faucets.

[smooth]

Is anyone able to sync successfully using the current client?

I find that it syncs for a little way (a few days worth of blocks) but gets slower and slower with a lot of crap like this in the debug.log:

Code:

ProcessBlock: ORPHAN BLOCK 751, prev=cc9762dc76933edc7f7c68dfc0df712836271d72f48ccca5edeef667f4f321ac
ProcessBlock: ORPHAN BLOCK 751, prev=987d2c79733720773ba0233b75a0b6d969c714ee99f28b4275a5c005553bec67
ProcessBlock: ORPHAN BLOCK 751, prev=b0f70379e39a45015ac2935fb3b285694a72c5cb13ee555c5329cbbbbac63d95
ProcessBlock: ORPHAN BLOCK 751, prev=1d3937bc80f7581f29d94ff2cc47aec641a8d8f6b90d26d13e7bbbf76a15cfcd
ProcessBlock: ORPHAN BLOCK 751, prev=8464dd8674416bc22c784628e0e0bbcc1624b57026d4151cd99cb46299c7b108
ProcessBlock: ORPHAN BLOCK 751, prev=ad95e18ebabc22dd8d25fc7aa00aeb080e8453e666fc08a3a22c8703c7bf2255
ProcessBlock: ORPHAN BLOCK 751, prev=02cb0d66bdb9ee823b434e9c243ca902c9e39e4833f13d64b31edf50a56e4534
ProcessBlock: ORPHAN BLOCK 751, prev=1bb9f0cacbaf73162a0b6d804d78577e2d59b718f303aaf7e1df2c3e2d7a13cf
ProcessBlock: ORPHAN BLOCK 751, prev=e4b57a49036abb692715a151d3bd344a69b8c7b9ea33b76b6da3f1b3c9ff2695
ProcessBlock: ORPHAN BLOCK 751, prev=0711b87091fdc7d37d21185456b4a12a8373e40cbb5cccc72b43e8f155ddefbb
ProcessBlock: ORPHAN BLOCK 751, prev=87130f485e73f9d3bc780abe852dec09398453668a33665bd750fd22f04bf75c

I can stop it and restart it which gets another few days of blocks but then it gets clogged again before too long.

I had this problem as well on various versions of the client. I blamed it on "bad nodes", and limited max connections to 5-10. It usually worked after that.

No good. I tried maxconnections=5 first and that didn't work. Went right back to the ORPHAN BLOCK messages. Then I tried maxconnections=1 which has it only connecting to my own node (addnode) and that works for quite a while longer (was able to get through 1-2 months of blocks instead of a few days before getting stuck) but still gets stuck with the flood of ORPHAN BLOCK messages eventually. Confirmed in getinfo there is only 1 connection.

[doothewop]

No good.

Did you try the bootstrap?

[ChiefCoin]

Thanks ill give that a try and report back.

waiting for your feed back

[smooth]

No good.

Did you try the bootstrap?

No I'm trying to sync from the network. That should at least be possible, right? I have very good network connectivity.

[nix_on]

So claiming clams has ended ?
Old addresses btc ltc and doge doesn't work anymore? 

[doothewop]

So claiming clams has ended ?
Old addresses btc ltc and doge doesn't work anymore? 

This is inaccurate.  You can certainly still claim your Clams.

[nix_on]

Ok
So digging has ended

[smooth]

Ok
So digging has ended

No. †he only thing that has ended, apparently, is that the current 'whale digger' seems to have reached the end of his stash. More digging will certainly occur in the future, but for now not at the same high rate.

[doothewop]

Ok
So digging has ended

The digging that one person with a lot of addresses has been doing has apparently ended.

This does not affect any one else's ability to get their clams.

[Nthused]

Ok
So digging has ended

The digging that one person with a lot of addresses has been doing has apparently ended.

This does not affect any one else's ability to get their clams.

Take note that over 8K CLAMs was invested into just-dice in the past 24hours, who knows how long that has been going on for but the big excavator fella could have been slowly investing it so when the price bounces back he is continuing to make profit when he disappears.

[Hippie Tech]

Oh wow. Interesting. Did he provide proof? Where's the wallet coming from and why did he chose to crash the price the way he did instead playing the game calmly and earning more that way?

Guess the recent talk of stopping the digging ability of clams was the next bad result coming from that wooden hammer method he used.

I did not choose to crash the price. The unfortunate revealing of my large potential dig caused the price to crash, because everyone sold fearing that I will crash the price. That's how market works. It will find the true price based on available information.

Ti kanis malakismenos bvleema ?

Thanks BIP38 seems like what I want. But there doesn't seem to be an easy tool to do the encryption or decryption yet. I don't run Windows.
And here's my dead man's switch: h tt p :/ / www . deadmansswitch . net /

https://who.is/domain-history/deadmansswitch.net

Registrant Name: STAVROS KOROKITHAKIS
Registrant Organization:
Registrant Street: PSYLLAKI 22
Registrant City: CHANIA
Registrant State/Province: CRETE
Registrant Postal Code: 73134
Registrant Country: GR
Registrant Phone: +30.2821051710

https://twitter.com/stavros

https://who.is/domain-history/stavros.io

https://who.is/domain-history/stochastic.io

https://www.linkedin.com/company/stochastic-technologies

https://github.com/skorokithakis/

[P-Funk]

Not sure why you're trying to play neckbeard detective on curious but it doesn't sound like he owns that service, more that he might use it.

[GordoZ]

So.. the digging problem has fixed itself?
We have to hope that the walle wont sell all his clams at same time.

[dooglus]

No good.

Did you try the bootstrap?

No I'm trying to sync from the network. That should at least be possible, right? I have very good network connectivity.

I remember seeing the client get stuck on a bunch of "orphan" messages before too. I don't remember how I got past that point.

What if you try connecting to just one of the known-good peers? ie. use connect=x in clam.conf where x is one of:

104.236.149.112:31174
144.76.185.69:31174
88.198.207.8:31174
199.233.246.224:31174

Do you still see the orphan issue?

Take note that over 8K CLAMs was invested into just-dice in the past 24hours, who knows how long that has been going on for but the big excavator fella could have been slowly investing it so when the price bounces back he is continuing to make profit when he disappears.

Note also that when the price dropped from 0.002xx to 0.001xx around 70k CLAMs disappeared from the JD bankroll, presumably to go into the poloniex orderbook. Some of the 8k you saw being invested could be some of that 70k coming back now that the panic is over.

Or it could be the whale digger, like you say. Maybe both.

[dooglus]

So.. the digging problem has fixed itself?
We have to hope that the walle wont sell all his clams at same time.

Well, this particular BTC whale has stopped digging for now.

There's no guarantee that he won't start again (although he says he has no more addresses to dig) or that another similarly sized whale won't turn up tomorrow.

So I wouldn't say it has really "fixed itself". And some would argue that nothing was ever broken, and that everything is working as planned.

[smooth]

@dooglus

It seems to be making progress. After several restarts, I've gotten synced up to a few days ago using my other node (which is working fine) as a source. I'll finish doing it that way and then see what happens.

[smooth]

I was able to complete the sync, just by doing several restarts (>10 though).

I found this back in the thread which seems to be the same problem (although I'm not seeing the "duplicate proof-of-stake" message).

Syncing a virgin db, and clamd seems to be getting "stuck" on orphan blocks...

ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(31c8d98ed4, 1), 1409328810) for orphan block ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8
ProcessBlock: ORPHAN BLOCK 751, prev=ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(4b4c0aacd4, 2), 1409328811) for orphan block e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6
ProcessBlock: ORPHAN BLOCK 751, prev=e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(df96fd5846, 1), 1409328935) for orphan block 331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0
ProcessBlock: ORPHAN BLOCK 751, prev=331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(d93414f7d2, 1), 1409328928) for orphan block f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656
ProcessBlock: ORPHAN BLOCK 751, prev=f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3f2c6d206d, 1), 1409329004) for orphan block 6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec
ProcessBlock: ORPHAN BLOCK 751, prev=6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(7b54b4e3b6, 1), 1409329082) for orphan block a9ad274839def4b39c0d2e8a44fa14f9d15a7665f37f202d1f9ab80edf56fc85
ProcessBlock: ORPHAN BLOCK 751, prev=e8be94c3aa50abd60dbe64dde7b76672b5a97c8d4ec50da9afa9b70dc10f3550
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(770d08c5c8, 1), 1409335177) for orphan block ebb678b09629ae0657500521b73aafd4fa66f441458a14c70380c0ca05eccfbb


At this point it's just a bunch of "ORPHAN BLOCK 751" messages, although the block hashes for each seem to be different. It doesn't seem to be accepting new blocks. Is the client hitting some sort of limit? I have to stop and restart it in order for it to accept more network blocks. Once it hits 751 orphan blocks it gets stuck again. This has happened about 5 times now.

The phrase "ORPHAN BLOCK 751" currently appears 51327 times in my debug log. Now on 6th restart.

Guys I'm getting this same problem. ORPHAN BLOCK 751 and gets stuck. I am running the latest clamd built from the source code on an AWS micro instance (ubuntu).

[tspacepilot]

So.. the digging problem has fixed itself?
We have to hope that the walle wont sell all his clams at same time.

Well, this particular BTC whale has stopped digging for now.

There's no guarantee that he won't start again (although he says he has no more addresses to dig) or that another similarly sized whale won't turn up tomorrow.

So I wouldn't say it has really "fixed itself". And some would argue that nothing was ever broken, and that everything is working as planned.

Wait, I think I missed something.  The whale has self-identified and said that he's out of addresses?