This response is a classic example of PR damage control. Let’s address each point one by one.
Let's Address Each Point
1/ Standard operational setup for Wyoming shell company?
30 N Gould St, Sheridan, WY isn't just common practice it's documented by
@ICIJorg as a shell company hub, appearing in hundreds of fraud cases on ScamAdviser and MalwareTips. Legitimate startups use Delaware C-Corps, Stripe Atlas, or YC not Wyoming shells.
malwaretips.com/blogs/30-n-g…
2/ Integrates with multiple liquidity providers
Original claim, "Proprietary privacy execution layer"
Current admission, "We use SimpleSwap, ChangeNOW, FixedFloat APIs"
That's not integration that's being an affiliate wrapper with SIMPLESWAP_AFFILIATE_ID in your SDK.
3/ Experimental code unintentionally included
trade.veillabs.app was your PRODUCTION endpoint routing all swaps through SimpleSwap's API. That's not "experimental" that's your entire execution system. Why was the privsol repo deleted after this was discovered?
4/ Communication may not have fully reflected implementation
Translation, "Yes, our marketing didn't match what we actually built." That's called misleading users.
5/ The core issue remains,
You marketed "privacy infrastructure" while running a SimpleSwap wrapper from a documented shell company address. Users thought they were getting proprietary privacy tech. They got an affiliate link with extra steps.
6/ What would real accountability look like?
Open source the actual architecture
Explain the SimpleSwap affiliate revenue model
Address the SDK commit emails (asdsadsad6421421@gmail.com)
Explain why repositories were deleted
Transparency means showing, not just telling.
This is not our issue. If you said you were making a meme token, there would be no problem. We would say it has no purpose, and that would be the end of it. But do not sell this to people by saying, "We are marketing technology, we even established a company in the US, privacy protocol, innovation, etc. Because the investor thinks they are investing in technology. Furthermore, when the first button is buttoned incorrectly, everything else goes wrong. Addressing the issues above is enough for our report to change.
Additionally, our a team member is preparing a GitHub repository regarding what a real privacy protocol looks like. You can fork it and use it completely for free.
We are trying to protect the crypto community.