Is a brain-child of me, inspired by Louis Rossmann, who fights for right to repair, privacy and transparency.
the idea is to create a service provider in the near future that works on a token-base, which does not create a connection between services provided, payments and ownership of said services.
as there are legal and accounting challenges comming with an idea like this, some legal perks need to be worked out.
in general terms it should work in a 3-pool-system.
Pool 1:
- provide cloudfront applications, infrastructure and other front facing items.
those will be soly be owned by the entity that pays for them (the company)
Pool 2:
- Acounting, client front to manage client orders and services, passwords and general access in a easy way
Pool 3:
- Air gapped connection pool between pool 1 and 2 .. which is only to be used for legal issues, not to be online at any time.
- complete privacy as even Support will not be aware of purchase history, names or other things
- authentication for connections as a online service in form of hash-tokens to link actual service to a specific client when support is provided.
