Mints and Fees

I went ahead and made my changes ready for a v0.0.4 release of our package.

I still ran into a design-issue with mint fees, they are not as predictable as thought. Because of how Cashu works, only the customer can know the fees associated with the ecash they’re holding. The operator can make a guess based on the mint but it can never be sure how much the fees will be before receiving the ecash.

This is because fees are tied to keysets, which are effectively a ‘batch’ of ecash notes defined by the mint. each of these keysets/batches has their own fee associated with it.

A cashu token can contain a mix of ecash notes from different keysets/batches, therefore the customer will have to calculate the fees on their end.

The most likely way forward is that the operator will communicate wether the listed price includes the fees yes or no. And then the customer can calculate how much they need to ‘overpay’ to cover the fees when the operator does not include the fees into the price.

TollGate Release Explorer

I added alpha/beta channels to the build pipelines so we can more easily test (automated) before we release. I came to the idea to vibe out a website where people can find the releases because we get that question often and i want to lead people away from legacy tech like GitHub.

It literally took me <60 min to vibe out the entire site. Then, i spent 3-5 hours of trying to deploy the thing on CloudFlare pages. Why CloudFlare? Well i wanna host it under releases.tollgate.me and i couldn’t get custom domains to work yet with nsite. I might need some help from @hzrd149 and @Sync for that.

my post about it