alright guys, we have looked at the code and fully understand what it is doing, i am going to try and contact the supercoin dev to see if he has left some of the code out because based on the description of what he says it does it seems like he might have left a part of the code missing for privacy. i am also going to ask them to release the usernames / passwords for the BitcoinTalk, FB, twitter, etc accounts so that we can takeover management of the PR for the coin as well.
I doubt you really understand the code. The code is complete and I did not miss out or leave out any code. Please compile the code and run it. Use debugger as I suggested before if you need more details about workflow etc.
Again, let me be clear:
1. The code I released is the complete code for supercoin 3.1.1.
2. It compiles and runs as the executables we released a few months back
3. No garbage talks about code that it is not right, not correct, not implemented etc (all healthy comments are welcomed), as the wallet has been running for many months without any problems
4. I don't have time to walk through the code with people, just read the code (there will be people who understand the code, this code is not for mediocre "devs" - they can't write any code like this anyway. Otherwise you will see many coins having new techs like supercoin). If you can't figure out the code (there are many logic/workflows inside), then use debugger to follow the flows.
5. There maybe some posts on "reviews" of the code, citing this wrong and that wrong, the community can believe whatever they want, but just remember that the supercoin wallet 3.1.1 has been working very well and very fast for many months, this is the
fact and the code in its entirety is released now. So it is your choice to believe in fact or some "devs" "reviews" - this is actually the main reason I released the code to public, instead of letting some incompetent people to own and comment at will at my code.
Anyway, I won't be there often, and in general I wont reply to comments and messages (especially fuds). If you really get into the code and have some detail questions (which proves that you are a competent dev), I may be able to help if I have time.
I will take a leap of faith and stand by supercoindev as long as they keep showing the supercoin community useful attention.
Note: I released the complete code for phase 2 - p2p anonymous system with multisig technologies (Supercoin version 3.1.1). In the code you will see some limited comments too (I did not have time to put detailed comments in code).
There's also a codebase for 2.x which is the centralized mixer system. I don't think there's a need to release the code, as it is considered as a common and obsolete technology, which many other coins (such as Blackcoin) used too (though my implementation is unique and from scratch). Therefore I won't release this part of the code.
since you say you have released all of it. id like to point something out. your code does not do anon. it just mixes transactions around, passing them through side nodes to get to the real destination. its basically like taking the scenic route when driving instead of staying on the main highway.
let me explain why i dont think supersend fits what the average person thinks of when they hear anon.
SuperSend will be abriviated to SS for the following:
SS has a max of 1000 coins per transaction. ok, thats fine. it has a 1% Additional fee. umm ok. and a max fee of .05 super. ok.
what your mixer system is doing. and it is very well designed btw. is taking the 100 coins. + fees. sending it through multiple mixing nodes until the 1% fee has been used up as transaction fees by the network to pass from mixing node to mixing node, and then it hits its destination. there is a few more complicated sig signs and fails in that process, but im explaining it for the average person.
There is a shortened version in your explaination paper of SS as A->X->B where as is the sender. X is a sum of all the mixing nodes it hits. and B is the intended recipient. it will jump as many times as is needed to burn the 1% to hit the intended mark with the amount the user intended to send them.
the reason why i dont call this anon, is because if you look at the BE, there is a nice neat richlist all sorted out. and if you REALLY wanted to. you can click on there wallets, find SS transactions and trace them back to the sender by clicking on the blocks and tx IDs of the mixer nodes. Annoying? yes. anon? no.
what i consider anon, and i get the feeling most people do think of anon as the same thing, is that if the transaction is sent with anon it cant be traced back to the sender. we all know of course that, with computers because of the way they work, TRUE anon is impossible. but we all want to get as close as we can.
what i did with multishift for MWC was i actually changed the wallet addresses when a transaction sends. as a result, the richlist compilations for that coin are complete shambles/gibberish (assuming the user uses MutliShift for all of their transactions). to clarify it changes the sending address, not the recieving so no you dont have to look to see what your new address is every time someone wants to send you coins.
ideally, i think a good anon solution is a mix between what the two coins have. you built a good mixing system. i have addresses actually changing themselves. and i will probably do that for the coins next.
TL;DR you have a mixing system, not anon. SuperSend transactions are traceable after X number jumps. i will post an example of this later.
EDIT: the super send also delays the transactions a considerable number of blocks before it actually hits its destination