Topic: [ANN] Catcoin - 0.9.3.0 - page 20. (Read 57656 times)

are you serious for this coin dev ? 

I have deleted the latest BS from Hozer.  I will continue to delete posts from him and all of his sockpuppet aliases unless/until he posts something that doesn't violate the rules of this forum that have been linked to the OP since the start of this thread.  He's been warned multiple times and has violated forum rules sufficiently to result in being banned.  Next post will be forwarded to the forum mods for proper handling.

(Please note that 'vampirus's posts about the status of his wallet and his conscious decision to promote an orphaned fork remain in this thread and have not been edited or deleted, in spite of this being a known alias.)

CATs - it looks like we've delivered a difficulty adjust mechanism that successfully stands up to rapid additions of mining.  There are two 'pulses' on the chart that represent the addition of more than 1.7GH/s of hash when our difficulty dropped solidly into the 'very profitable to mine' range - and there was no insta-mining and our difficulty did NOT go to the moon!



Let me repeat that - we resisted more than 10x of hash input from a profit switch pool without giving away CATs and without huge difficulty swings - and we did it without minimum block time kludges, without merged mining, and without using ANY method that any other coin on the street has tried.

The pre-fork leased miners ended about 0500 GMT and as you can see from the chart, we're have some long blocks since.  This morning, as far as I can find, we have ~2.5 MH/s on Bejjan (my two GAW Furys), about 400 KH/s on Hashnova (Blaksmith), and about 18 MH/s on GeekHash (my GAW Black Widow and Blaksmith's Furys).  One thing about crypto that is universal is that we have to have miners on the network to solve blocks.

So - CATs - we've brought you code that's unique in the entire crypto industry and that just might finally be a way to reset the balance of power since the arrival of ASICs and profit-switch pools.

I just restarted my other two Black Widows to pop a couple of blocks and get things moving a bit more quickly, but I can't leave them running 24/7 - it's the hot part of summer here in S Texas and the miners cook in a 105°F/40.6°C garage.

0601 GMT edit...  Perfect timing - I mined the diff down, we hit the profitable list, and got hit HARD from at least three pools - and only gave up six blocks.  Now we have to mine the diff back down.  The algo works, but we still need some network hash rate.  Even self-driving cars need someone go get in and tell it where to go...  /edit

In other news, we're still beating on Cryptsy - feel free to open tickets and/or customer service complaint chats and let them know that you're disappointed in the 40+ days they've had us off-line.  If a Windows user like me can install *nix, a build environment, and can compile a catcoind in under an hour, there is absolutely no reason why they shouldn't be able to get us running in at least a week!  

The next phase of this transition is in progress.

As most of you know, it took a fair amount of constant hash rate to keep PID relatively consistent.  It's time now to remove the leases and bring the difficulty back down.

When we did this on testnet, there was always one longish block on the way down before things started to move easily.  As we ease the leases off, we expect some slower than normal block generation.  This should take at least eight hours.

As with anything else, though, it depends on the community - feel free to bring in your '24/7' cat miners if you have them around - let's take this new network for a test drive!

All right CATs - we're here!  It'll take a few more blocks for things to settle in - then we can see if things work in the real world as well as they worked on testnet.

Comments, questions, or thoughts?  Bring them!

46300.   31 to go.

It looks like we're settling in on ~10 minute blocks again - and that's a good thing!  

We have 84 blocks let to go - looks like Wednesday, 5th Aug is when V9.2.0 activates - block 46331.

I've been reading through (and re-living!) the launch thread these past few days and while it's taken more time than we all expected, this might finally be the solution we all hoped for since December 2013.

Fingers crossed.

BTW - expect a significant announcement before the weekend.

Violate forum rules and posts will be deleted.

Goodbye, Hozer.

I make some observations and suggestions about the coin and my post is deleted???

Seriously??

You guys are out of control with the 'moderated thread' thing.

Goodbye catcoin.

Sorry CATs - today's block progress was less than stellar.    We had two lease management challenges that got us galloping again - and it's been slow work to get it back under control.

In the last 24 hours we only found 94 blocks.  We've still got 166 to go to our fork at 46331.  At today's galloping pace, we should fork sometime late Wednesday or early Thursday.  Hopefully we'll be able to flatten the difficulty chart a bit, get back to crunching about 120 blocks a day, and fork late Tuesday or early Wednesday.

Either way, we're almost there.  Please pass the fork...and another bottle of antacids?

Andy

This afternoon, CAT is the 2nd most profitable coin on Coinwarz after Casinocoin - 213.54% more profitable than BTC yet Cryptsy still has us off-line.
http://www.coinwarz.com/cryptocurrency

Catcoin (CAT) Cryptocurrency

Exchange(s) Offline 0.00001435 (Cryptsy)

$10.97 / $7.37 ($3.60 for electricity)

Earn 1 BTC in 25.77 days (0.03879999 BTC / day)

213.54 %  /  NaN

Feel free to open a ticket with them and ask why.
https://cryptsy.freshdesk.com/support/home


Tickets open to date:

Ticket ID - 193353  25th June  (V9.2.0 upgrade)
Ticket ID - 195252  7th July  (Any progress on 192253?)
Ticket ID - 194673  7th July  (Deposit not credited - Taiga)
Ticket ID - 195687  9th July  (Deposit not credited - SlimePuppy)
Ticket ID - 196077 10th July  (link to block explorer - their explorer's still down)
Ticket ID - 198519 24th July  (customer service chat - when will we be up?)
Ticket ID - 198520 24th July  (customer service chat - request to speak to a human. denied.)
Ticket ID - 198548 24th July  (customer service chat - request for update on 196077)
Ticket ID - 199436 30th July  (customer service chat - request for update on all of the above)
Ticket ID - 199451 30th July  (Blaksmith - escalated to 2nd level tech support.)
Ticket ID - 199969 3rd Aug   (customer service chat - when will we be up?)
Ticket ID - 199995 3rd Aug   (Cannot withdraw CAT balance - when?)

Today's block generation rate has been absolutely beautiful!  287 blocks to go - less than 3 days to fork at this rate.

Go CAT go!

It's been a fun day of node attacks, fake blocks, and amateurish DoS attempts.  Yet CAT blocks just keep flowing towards 46331.  Life is Good!

CATs!  Amazing block flow the past few days!  We have 399 block to go till the fork - THANK YOU!

 

Taiga - your wallet should sync easily with no addnodes at all.

It's normal for a wallet not to sync if there's a longer block - check the chart to see.  If the message says you are 1 hour behind, and we have a long block, then the wallet will finish synchronizing on the next block.  We are still having occasional long blocks as we move to the fork at 46331.

Post a CAT address if you want a test transaction.

http://catcoinwallets.com/



Andy

Hi dev, what happened wallet, no sync , addnode=167.160.36.82, addnode=173.254.235.58 

Moving beautifully!  485 blocks to go.   

Folks - as far as I'm concerned, it's open season on Cryptsy.  Feel free to open tickets and ask when they'll have us back running.  I think it's 'squeaky wheel' time.  Don't forget to ping Bittrex either.  We are CAT - hear us roar.

Here's what we have open and what's been happening since 25 June:

Ticket ID - 193353  25th June  (V9.2.0 upgrade)
Ticket ID - 195252  7th July  (Any progress on 192253?)
Ticket ID - 194673  7th July  (Deposit not credited - Taiga)
Ticket ID - 195687  9th July  (Deposit not credited - SlimePuppy)
Ticket ID - 196077 10th July  (link to block explorer - their explorer's still down)
Ticket ID - 198519 24th July  (customer service chat - when will we be up?)
Ticket ID - 198520 24th July  (customer service chat - request to speak to a human. denied.)
Ticket ID - 198548 24th July  (customer service chat - request for update on 196077)
Ticket ID - 199436 30th July  (customer service chat - request for update on all of the above)
Ticket ID - 199451 30th July  (Blaksmith - escalated to 2nd level tech support.)