Author

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

legendary
Activity: 1554
Merit: 1001
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.
sr. member
Activity: 332
Merit: 250
I like the clowns and the little dogs
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.
legendary
Activity: 2968
Merit: 1198
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.
full member
Activity: 164
Merit: 100
Ok
So digging has ended
sr. member
Activity: 332
Merit: 250
I like the clowns and the little dogs
So claiming clams has ended ?
Old addresses btc ltc and doge doesn't work anymore?  Undecided

This is inaccurate.  You can certainly still claim your Clams.
full member
Activity: 164
Merit: 100
So claiming clams has ended ?
Old addresses btc ltc and doge doesn't work anymore?  Undecided
legendary
Activity: 2968
Merit: 1198

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

newbie
Activity: 19
Merit: 0
Thanks ill give that a try and report back.
waiting for your feed back
sr. member
Activity: 332
Merit: 250
I like the clowns and the little dogs
legendary
Activity: 2968
Merit: 1198
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.
legendary
Activity: 963
Merit: 1002

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.

Quote
Oh wow. Interesting. Did he provide proof?

He signed 2 messages from 2 of the addresses.

Quote
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.
hero member
Activity: 592
Merit: 500
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.
legendary
Activity: 2674
Merit: 1083
Legendary Escrow Service - Tip Jar in Profile
Curious???  Any chance his first name is Clement?  The creature who searches the sea for his toys who gets help finding them from an insider.....HHmmm?

http://www.storyjumper.com/book/index/13078592/Clement-the-Curious-Clam#

Very fishy!

Damn! You got me.

By the way, if anyone wants to buy clams OTC, let me know.

I probably missed some part in this fast going thread but the last posts sound like you might be the digger? Or is he still unknown and avoided the community for some reason?

curious confessed to being the digger.

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.
legendary
Activity: 2968
Merit: 1198
Thanks ill give that a try and report back.
legendary
Activity: 963
Merit: 1002
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.
legendary
Activity: 1176
Merit: 1017
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.



Try using the bootstrap.  The same thing happened to me awhile back but then I put the bootstrap in the folder with my wallet and it fixed the problem.
legendary
Activity: 2968
Merit: 1198
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.

full member
Activity: 179
Merit: 100
We can at least say that it appears to have ended for now:



I guessed he had around 517k CLAMs to dig. The chart shows a little less than 500k being dug since he started, so my estimate may have been a hair on the high side:

Checking my clam logs, I see something strange about the recent 'digging':

So it looks like this guy, whoever he is, is able to claim around 3.5% of the rewards in each block, and is working his way backwards through the blocks.  According to xploited, the initial distribution ordered the rewards randomly, so there's no reason to think that he won't be able to claim a similar percentage of the rewards from all the blocks.

3.5% of the initial distribution means around 517k CLAMs. In which case this digging spree is only just getting started.

Yes! Time to buy. Maybe. )
legendary
Activity: 1049
Merit: 1001
I could only stake one block in 2 weeks, with around 200 CLAM

What size stacks did you have the 200 split into?

Since he only staked once, it doesn't really matter. Even if the 200 CLAM was in a single output the one stake will have frozen it for 8 hours only, so he was still actively staking for 13.6 days of the 14.

Seems like a better option would be to split that 200 into smaller amounts say 10-15 in size and allow for a month to pass. Having a large stack locked up for 8 hours seems like a waste
legendary
Activity: 2940
Merit: 1333
I could only stake one block in 2 weeks, with around 200 CLAM

What size stacks did you have the 200 split into?

Since he only staked once, it doesn't really matter. Even if the 200 CLAM was in a single output the one stake will have frozen it for 8 hours only, so he was still actively staking for 13.6 days of the 14.
Jump to: