Probably should remove the "now listed on cryptsy" from the topic title
Peg! Good to see you around these parts!
As jwinterm guessed, none of the current players have access to modify the top of this thread. At the same time, I have felt constrained by the expectation that a new ANN should only be created for new releases, and I didn't want a vaporware or hype thread. So I had been planning to create a new thread once I finally got NYAN2 built.
But as jwinterm also stated: there's actually a new build now!! This is entirely due to /u/vmp32k and /u/stellarseahorses on Reddit. I actually came to this thread to make a post mentioning it. I'm glad that jwinterm got the link here already; thanks!
It's being considered a public beta for now, and I've been too busy / lazy to test it out or do code review myself yet. But I absolutely will get to that, and I believe that within the month we should be ready to consider it an official release: the first new release of the revival. This is the biggest thing to have happened for Nyancoin during this revival, and I'm incredibly proud to have Nekonauts like this active in the community.
I plan on making a new ANN once we declare the release officially ready unless /u/vmp32k is interested in maintaining the thread. I'm also going to suggest rebranding to NYAN2 rather than the current NYAN 1.3.0 designation being used, because I think the critical vulnerability fix (same forking vulnerability Peercoin hit months ago; we've been aware but hadn't gotten an updated client to address it yet) merits it, as well as reflection of the change from the original development team.
I need to study the solution in detail, but I think this will not changing the mining behavior (presumed to be on Linux 64-bit) but instead will just correct the client (meaning Windows or Linux 32-bit nodes) vulnerability to having a different interpretation of the validity of the particular edge case transaction than the miners. This means that it will be a required update for "clients" as defined but that we should be able to expect it to be recommended but less critical for pools and the exchange.
I'm staying pretty busy with work, and that's hopefully going to be continuing, but I'm going to be trying to help get to the point where we're confident enough to call this the official release and be able to finally be on a modern client and not have a known critical vulnerability (the difficulty function is annoying and not as good as I would like for dealing with hit-and-run, but that's going to take a hard fork and is not critical; we'll address that along with expanding the block size hard cap just to show we can in NYAN3, tentatively scheduled for release in early 2017 and activation sometime in 2017).TO INFINITY AND BEYOND!