People like the Tezos group, asking for donations... it is disgusting that investors go for that. Demand equity. We always choose morality over legality. Following SEC rules technically, while ripping off investors ... I'd rather be in the clear ethically.
The blockchain part is for payments, so not that big of a deal. Though to raise money, we'd be better off finding a blockchain angle to the platform! Truthfully though, our app is not breaking new tech ground, apart from privacy and security (see the link in my original post).
We are ambitious though! I think we'll be the first blockchain-funded unicorn. Escorting is fragmented and high friction, and we're going to fix it. Our VP of Product is an active sex worker and very tuned in to the real issues facing workers and clients.
Extrajurisdictional does not just mean criminal. It means that we operate in a way that no specific jurisdiction can apply itself to us. It isn't a wild card to just do whatever we want. We fully intend to pay taxes where possible. We want to be as transparent as possible to avoid money laundering. We have a strict no drugs policy. Strict age requirements, and, as far as possible, no coercion/trafficking/pimping. (If we see one device managing multiple accounts, we'll investigate/ban.)
Would love to read a write up on:
> Our servers don't have persistent storage, RAM only. (At boot, it's a manual restore from something like Tarsnap.)
But think something like secure boot, serve up a basic image, download full image from provisioning servers, turn on DB, restore from backups.
>"Servers use full disk encryption and the key must be manually entered at boot."
I am curious how do you handle key rotation and storage of encryption keys?
But we think it is feasible to drop the disks entirely for the main servers. So the disk encryption is an issue for the systems holding our CI and imaging platforms.
1. No scammers. We require providers to be vetted in some way (references). Clients are going to need to provide screening to see providers.
2-A. We use our custom login system. Verifying your social media account is just a read-once thing we do; we don't ever have access to post. In fact, it is unlikely we'd even get approved for an API key on most platforms.
2-B. For launch we're pretty exclusionary :(. Focusing on cishet couplings, female provider. We're going to address that as soon as possible. Queer sex workers face additional challenges for sure.
3. Data safety. Due to our company's legal status (extrajurisdictional), we have to deeply hide all data. Our servers don't have persistent storage, RAM only. (At boot, it's a manual restore from something like Tarsnap.) Only a few people have root or raw DB access. This does not include most devops people - they go through a change approval process. Real access is limited to core members heavily vested in the company with a need-to-know. More at [1], please ignore the clickbait title.
Another key point: connectivity is heavily restricted. App servers only have inbound socket from their hidden service, plus outbound to the DB layer hidden service. DB layer only has that inbound socket. DB requests are rate limited globally plus per user.
4. We'll wipe your data shortly after deactivation if there are no abuse reports on your account. In which case we keep a photo ID and birthdate so you can't sign up again and get a clean record. This is needed to protect user's safety. But at least a photo is not so readily searchable. Maybe Facebook can do it, but if we were to somehow
1: https://medium.com/@PinkApp/pink-app-trading-latency-for-ano...