Topic: [ANN] Catcoin - 0.9.1.1 - Old thread. Locked. Please use 0.9.2 thread. - page 46. (Read 131044 times)

Sorry I miss read your post, thought you said 22817

the cat coin block explore hasn't worked for a while,  Block 22017 is 4 days old

Team cat is working on block 22811
coinium is working on 22817

point my computer to your pool 

sorry but this is the right chain or not??  http://catchain.info/chain/Catcoin

teamcatcoin, my wallet and coinedup and all on the same chain

cat.e-pool and coinium look to be on a different chain.


Teamcat may not be getting any blocks, but atleast on that chain you can send coin to an exchange

my pool is on right block but i need power to pass this block 22017   

http://cat.e-pool.net:9993/static/

PS: my laptop make only 20-25Khash

I'm not sure, but are the only blocks that are

is it on the right chain?

conium is taking all blocks

I'd also take the chance and say thank you developers for doing your awesome work. kudos. greetings vondi1122

Who knows what will happend with all round shares mined till period of pool problems? Reset...?

Doge is running fast, I hope cat is not dead for now.

I won't be doing any cat mining until I receive the coins that I've already mined. Fool me once, shame on you, fool me twice and shame on me.


 I will say that it's a bit unethical to not shutdown mining at a pool while there is such a big issue. Just letting people come and waste resources and electricity/$ when they won't be paid is bad karma and just plain wrong. I have much more respect for a pool that would just shut everything down and warn people about the problem instead of ignoring emails/trouble tickets. This is the new frontier, there will be bumps on the road for sure. It is understandable and to be expected. It would be nice if pool admins had the common decency to step up to the plate and deal with these bumps responsibly and ethically.

On a positive note, us cat groupies are quite lucky to have good folks actively researching and brainstorming solutions to these challenges. The day there are no dedicated developers involved is the day the dead cat doesn't bounce back. Kudos to Slimepuppy and the team!  

So once again

Teamcat at block 22785, but they havn't found a block for 36hours,  (last block found 22647) block still moving forward thou and still in sync with my wallet

Coinium at block 22747, and they are still finding block


who's right, who's wrong??

It is not "slightly different difficulty numbers" that are causing the DoS logic to kick in, it is a bug in ComputeMinWork and out-of-date checkpoints.

Here is what I am seeing, clients are getting disconnected in ProcessBlock by the DoS logic with this error message:
ERROR: ProcessBlock() : block with too little proof-of-work

The Blocks are being rejected because:
1) The latest checkpoint is on block 20000 from Dec 30
2) deltaTime passed into ComputeMinWork is about 3921600 (about 6 weeks)
3) ComputeMinWork is using nTargetTimespanOld*4 (2 weeks * 4) instead of nTargetTimespan*4 (6 hours * 4) because nHeight of the last checkpoint is less than 20290.
4) The diff at the last checkpoint was 64, causing ComputeMinWork to return a Diff of 16 instead of a proper value below 0.015625.
5) Pools are attempting to submit blocks with a diff that is valid (above the 2-3 diff currently floating around), but is below 16 that ComputeMinWork is returning.
6) The pool is DoS'ed for publishing a "invalid" block and cut off of the network.
7) The pool continues to build what it thinks are valid blocks in the 2-16 diff range the the rest of the network rejects, and it lands on a fork.

(The reason you did not see it on testnet is because ComputeMinWork returns bnProofOfWorkLimit.GetCompact() for testnet, and it never gets to the spot where the bug is.)


The solution is simple:
Create a new checkpoint with nHeight > 20290.

Thanks for the hard work and feedback SlimePuppy!

Should we be mining before the fix comes out? Which pools are on the right fork? TeamCatCoin hasn't found a block for 34 hours now - that doesn't seem right. p2pool found a block half an hour ago - if they're on the right fork, I'll be moving to them until we know what's happening at TeamCatCoin.

Excellent news! CAT seems to have been very sick lately.
 

And pools that get more than 2 blocks in a row look like an attacker to the rest of the network.

The only pool that does not have this property is p2pool, because the block generation is distributed among the p2pool participating nodes.

The lesson: if you are a pool operator, you will eventually get forked and banned by the rest of the network if you and your users get greedy.

If you want to properly rate-limit your pool, or use p2pool under the hood so this is not an issue, I am happy to offer professional development services to help you do this for free for any catcoin pools. Other coins have to pay. In catcoin

Why? Because izzy

We have testnodes running new code now.  Once we confirm this fixes the problem we'll get production code and wallets on the streets.  Should be a matter of a few days, but that's a guess right now.

We have about a month to be upgraded and stable for episode six of the Diamond Collar show.  That's our 'make or break' point.  The network will be stable well before that, however.

Thanks for not giving up!

PS:  "Official" song of the Dev team: The Year of the Cat.   

Awesome news SlimePuppy. thanks for the update and all yours and the rest of the Dev teams hard work.