• 1 Post
  • 5 Comments
Joined 6 months ago
cake
Cake day: November 21st, 2025

help-circle

  • As your joke about github vs privacy, I fully agree. But I did this a certain way of several reasons, all design choices has a explanation if you read the docs. And one is the transparency, it’s like 3 clicks then you could verify. It wasn’t about my privacy in relation to the code, it’s privacy regarding real world/“titts-for-tatts”/seller-buyer transactions. But in general my imposter syndrome doesn’t like to much discussions in forums. So I’m pretty good at “post&run” to quietly watch on a distance like a creep. And that’s pretty much what you could expect from me.




  • Existing platforms settle real-world transactions too, but the rails they run on are owned and operated by someone. That operator can raise fees, gate access, extract data, be acquired, be regulated into compliance, or be pressured by any sufficiently motivated actor. The settlement behavior is only as neutral as the operator chooses to be. These protocols have no operator. The fee is immutable at the protocol layer. The contracts are deployed with renounced ownership. There is no entity that can modify the behavior, no platform that can be captured, and no intermediary between the user and the settlement rail.