Quote from: TheMightyX on May 01, 2014, 01:24:11 PM

Quote from: danosphere on May 01, 2014, 04:25:21 AM

.. and my mac-

heh

Thanks Dano, I did get the note earlier about you being behind on emails so I wasn't expecting a quick response anyway.
Looking forward to getting more info about the current state of affairs.

I lol'd

Ok so I had some time to go back through the posts I missed a bit more and lemme catchup (I STILL need to catchup on kittehcoin email i am very sorry and I haven't been on reddit or IRC as much I should be but I'm trying my best). I'm also doing that magic trick where i've "abandoned" the coin yet I'm still here responding to all these posts and questions. Pretty neat eh? Roll Eyes

So, first off- I saw shai_ added KGW updates to Kittehcoin! I fully encourage this! Other people should commit additional code too. Shai_ has been a Kittehcoin contributor for a long time and has authority to approve pull requests as well as make his own updates to the official Kittehcoin code. He is a good guy- just got a bit emotional about how things were going with Kittehcoin a few posts back I see and I understand where he's coming from, he has been working on Kittehcoin for a while just like lots of the dev team who relaunched kitteh. And because of that I won't say anything about his comments except I have not abandoned kitteh just scaled back my time commitment and hey- relax Wink

.

Next- I replied to TheMightyX just now and he seems like he may have some solid plans to move Kittehcoin forward with the other people who have stepped up. I don't want to say anything preemptively I'll let him announce the news when he's ready.

Quote from: kahir on May 01, 2014, 09:42:56 PM

POS +1

This seems to be catching on lately and I would encourage investigating this.

Also as shai_ mentioned a few posts back we will need to decide on a new fork height. There are two ways we can do this (still playing manager here until things are switched over):

1. Review the KGW fix and fork ASAP fixing the diff issues plaguing the network, there aren't a ton of pools so it might be painless (but that almost ensures it will be a pain cause that is how software works)
2. Wait til I have had time to implement the other changes mentioned in my update and fork at that height in a month or so (tops)

1 is best for the network. 2 is less risky. Of course I have not had a chance to test the KGW updates made by shai_... what concerns me is part of the reason KGW is ineffective with Kittehcoin today is because the network hashrate is so low... so when it varies wildly KGW can't cope. @Shai_ - how thoroughly were you able to test you KGW updates?

If the KGW updates need addtional tweaking we may want to look into DigiShield as others have mentioned. I would also be willing to bring over some of the KGW vars from Syscoin which uses very "tight" KGW vars to respond to network spikes very quickly- that was my original plan of action until people started talking about switching to DigiShield (which may have network benefits as well as marketing benefits).

In any case I'm here to help and I'm looking happy to see people stepping up to recruit and move this effort forward! I am here to support them with cut code as well with whatever time I can contribute!