I'm not asking for credit, I don't brag about my contributions to the coin. I'm not trying to goad you into an argument. I acknowledge your skills and have consistently done so. I have never asked to be a clone of any existing coin, if you misread that, then here is what I was saying. It's far easier to bring an existing system into a coin than it is to code it from scratch and vet all the possible scenarios that exist in the logic.
The questions I asked were in my view at times exposing short falls in the system. I still see several loopholes (and have stated a few of them) and don't agree with your assessment that we will be able to sufficiently test a brand new system as I feel we'd need a ten or more fold increase in testers which would mean nearly half our active users would need to test. The issue is you seem to believe we will see a sudden influx of both testers and users. If you have knowledge of a contingency waiting to come, the community would benefit from that knowledge. However, I don't see the path to such increases. Finally, I stand by my position that even the best programmer won't be able to test for conditions they've not thought of.
Thank you West for this and I want to say that I want to work with you closely on identifying and mitigating any potential issues you might see in POG, for the greater good.
I'm glad to know that you agree that this is not about either me or you being the smartest or first analyst to discover a flaw, its about us making a solid product for BiblePay, and even if it means that we discover the product not ready, so be it, I wont have my feelings hurt.
I think I have quite a different perspective of the POG vulnerabilities from the code standpoint and I think it will be very valuable for us to try to see each others perspective over in testnet.
So lets meet over there and try to come up with any attack vectors.
Currently from my standpoint I view POG as solid- I only know of one type of attack vector (the ability for a whale to cash out a sanc, create a bankroll of 300 5000' bills manually) and use that as a POG tithe edge over others, however this particular attack is going to be mitigated - the user will have a new command available (exec bankroll), empowering them to do the same thing as a feature - and diff will rise above the min_coin_amount during this whale attack making it useless until diff drops (another words by empowering the user with the same feature - no one has an edge).
After this - from my standpoint I cannot see any potential attack, from any scenario covering 1 wallet to multiwallets, or whales to small fish, and thats what we need to cover in testnet.
The code is not ready yet but should be ready by the evening - Ill make a post on the main forum then lets all meet there.