If I were you @tonbi I would ask for specific issues here. So specifically what will not work, what is an impossible solution that will not work?
I would say you need to do this and be clear, we have not seen any specifics from @nemgun but I would be always interested if anyone can point to a specific and say it cannot be done. By specific, take one of the (modular) libraries, find fault in that design etc. or fault in the RFC or whatever and come back to us. If your god tells you this and you still present NVO as running on SAFE then you are heading for a bad place.
Otherwise you will be purposefully misleading people who supported your ICO and that is where there will be repercussions. Just the spamming and trolling by your team member/god/co-founder etc. will ring alarm bells. I do think you need to clear this up.
If you guys have code it would be wise to post it for comment/review etc. It’s just easier to be open and honest. If you have a dev who has fully read and inspected the network, where are the findings? As a CEO you need to ask for some kind of evidence surely, perhaps not though, but that would be weird and ignorance is not a defence in law in the UK. You do really need to know.I need to know if there are real deficiencies in SAFE, the whole community do, but we have a plethora of ways to find that out, including testnets.
I would distance myself from unfounded claims/critiques until you have solid facts, one second this guy knows nothing, then he knows everything, he asks for papers but then you say he has read them all? The dichotomy of this situation is not good for your project and will harm our project, unless you get specifics and stick to a single truth. Does the guy understand SAFE and how it’s built or not? If so has he specific issues ? Why are there no questions in github/dev forum or user forum about any such issues?
I say this as I hope it will help, otherwise you are in a place where you are acting with no evidence and it’s a lot of money you raised. As a director of a company it’s your duty to act on information and validate it, seriously, you need to.
Your current get out would be to say “we have no faith in SAFE” and run away from it, but explain it to your investors and really that means refunding people, but trying to stay and poke holes like this is actually putting you in a bad place as a director of a business, if indeed you are (I am not sure of the company structure you have). The other option is to say you have created SAFE and prove that or say you will prove it in X days/weeks and perhaps buy time that way, in any case you will need to be clear what you are doing with the funds and a pivot is OK, but you do need to be very clear.
In any case this is very shaky ground for you, I would get facts of any issues your team think exist and ask specific questions. This forum and the dev forum are great for that.
I hope this helps.