Since some time now we have protocol specifications for authentication that can "gate" a Mint to a set of registered (and maybe KYC'd) users with OAuth 2.0.
Users receive an OAuth JWT token on registration that they can use to mint BATs (blind authentication tokens). The latter are just ecash, but for requesting access to the Mint API.
So even if the users are KYCd, their privacy can be preserved amongst all of the registered users (Mint doesn't who amongst the registered users is using the service).
This is Cashu's way of providing tools to the Mint runners for meeting the regulators at a middle ground, and the most we can do. Any requirement beyond this is tyranny that must be fought in the "shadows" like you said.
Thanks for that, that's really useful. I think there are reputable regulators out there that would be open to that as a middle ground, just a matter of sitting down with them, pencils, paper and coffee.
I'm thinking of putting together an Intro to Cashu deck for a few of the more promising regulators in Asia to test the response in person, if you know of anyone else doing the same please let me know, happy to coordinate.
Well, just been paged into this conversation, so don't really know the context. But if anybody wants to run anything by me, I can put a Regulator hat on and Give you an opinion. I've coordinated policy development with our regulator here for the last seven years.
Happy to help any project.
