OK first let me thank all who care about this coin. Due to the fact that I see no experienced dev come forward to take over the code and people expressed their opinions to release the source code, I released it now at github
https://github.com/supercoinproject/supercoin-p2pSo we have an open source now, anyone can maintain and continue developing it. I developed the p2p anonymous system with multisig technologies in a little more than a month time, it was an exciting and intense month that I spent a lot time developing the code and testing. A few people helped me testing the code, especially supercointeam, and with whom we supported the supercoin community for many months. The code works very smoothly, though it still have many aspects to be enhanced which I will list below for the potential future developers.
It was fun and exciting with supercoin. We have many great supporters, also enough fudders. I still see sometimes people doubt if the code is real. Imagine this, how can I put fake things inside that can work so flawlessly? and with dynamic log messages that everyone can use the console and see? There are so many dumb people in this domain, and so few people who really understand the technologies.
Now the code is public, please review the code (well for those who really know the code, otherwise it will be tough for you... very tough). If you have issues with the code, please use debugger, you will understand it better. I may come back from time to time to check the comments and questions, but as I am busy, I won't reply unless it is really needed.
For the future developers, please note that the p2p anonymous code with multisig is done in about one month time, therefore while I ensure the main scenarios working fine, there are some codes I haven't got time to complete, this is mainly in the domain of error handling and reverting back the transaction, this should be easy to add (though it could be tedious) based on the existing code. Another potential issues is the out of sequence messages. I handled many such cases during my tests, all occurred scenarios are handled. But due to the potential high number of combinations, in rare case there may still be some potential cases due to out of sequence messages that the transaction may fail.
Anyway, have fun with the code, and if you understand it well, you can copy-paste to another coin. But doing so only if you understand the code, since it is complex code. I'd be really sad if you copy-paste the code but don't know how to handle issues when they occur