gandlaf21's avatar
gandlaf21 _@www.gandlaf.com 1 year ago
Imagine this: - you want to provide LN/ecash services to your family and friends -you don't want to know who is doing what payments, to offer them better privacy - You end up running an ecash mint - you don't want any rando to be able to use/abuse your mint - you need auth (preferably blinded) Also know this: - It's an optional spec - No one is forced to add auth to their mint - you are not forced to use a mint that implements auth Auth has a lot of drawbacks for ecash mints, but in some cases it is an absolute requirement
↑ Parent

Replies (3)

gandlaf21's avatar
gandlaf21 _@www.gandlaf.com 1 year ago
If governments and corps will use ecash, i will be thrilled. It's better than the other shit they are trying to force on us anyway. It won't affect me much, since I will try to avoid their stuff as much as I can, but at least it would be an improvement for the fiat pleb
1 replies ↓
/dev/fd0's avatar
/dev/fd0 floppy@joinstr.xyz 1 year ago
Corporations (custodians) will use it to get more users and it's an attack on self custody. A disrespect for the developers trying to improve self custody. Governments will use it to target other mints that do not comply. Even if optional, providing a tool built in the protocol shows the intent. It is possible for a pool initiator in to add such requirements for others who join the pool but they won't be part of joinstr protocol as it's not defined in the protocol. This also makes it easier to censor users and collect information that affects their privacy.
↑