The Melt Saga in Coco is probably the most interesting piece of software I have written in a while. First of all sagas by themselves are also really cool, and I had a lot of fun writing the first one for the Send API. Now melt adds more complexity by needing to support different methods, that will have different behaviour. While the SendOperationService owned all behaviour the melt one does not. This is where I added the MeltHandlerProvider, a little piece of code that provides handlers based on the method used to the Saga. The saga will get the required behaviour from the provider when it needs to advance. This way each method can implement its own behaviour, and consumers can even add their own methods via plugins or at runtime.

PSA ⚠️ There has been report of data-loss when upgrading coco to the latest RC33! We are still investigating the issue, but for now you should not upgrade to this version. Unfortunately npm doesn’t let me plush the version, but as the RCs are alpha releases npm will not upgrade you without explicit permission

I have evaluated all available monetization pathways and determined that the prefrontal-cortex-to-Claude exchange rate is surprisingly competitive. Updating life strategy accordingly.

Sell kidney and get Cursor 200$ subscription?

Yeah, I am on the 60$ plan and usually don’t even hit my limit. With Opus 4.5 I hit my limit in 8 days… but it was one really really productive week!!

Opus 4.5 (Cursor) cost is only reduced for another four days… what are you building?

Coco RC31 has been released! This new RC includes a bunch of bug fixes, as well as the long awaited send API. Sending tokens was fully refactored to use a saga under the hood, allowing for much better error handling and safety. It also allows users to preview transaction details before executing a send. If something goes wrong Coco will do it's best to recover the operation (and the sats). A nice side effect of the saga is that we now got real time updates for send operations as well! New send state events were added to the event hub and the History API now exposes "state" for send operations. The full explanation of the SendAPI can be read here: https://cashubtc.github.io/coco/pages/send-operations.html

"Before you change anything review this proposal critically" is a game changing prompt for me

Both are LUD16 compliant payment addresses. Money sent to an .cash address can not be retrieved through npub.cash UI. Instead in will be withdrawn through a wallet the implements it's API, like Cashu.me or Sovran

PSA: npub.cash is experiencing some issue right now. This morning we had some DDOS-like activity that caused rate-limiting issues with Minibits upstream. Meanwhile .cash is running fine and also has some protections in place to avoid this kind of issue. If you are currently using npub.cash, this might be a great time to look into .cash. You can use it inside Cashu.me by enabling .cash in the experimental settings.

Thanks for the heads up! Investigating! .cash is running fine right now, if you need an alternative in the meantime

Right now 100k for version 1 and 500k for .cash

Good point! Npub cash uses arbitrary limits right now. I will change that

I am not too familiar with the Python way of setting things up. Easiest is to install docker and run the command from the repo. If all you need is a test mint to test against there is a public one at https://testnut.cashu.space

👀🥜

Never forget to add some triple negatives to your tests!!

GM ❄️☀️

This isn’t a dip. It’s whales messing with the market specifically so you look dumb at Thanksgiving. The bull run resumes right after, I swear. 🤭

The prize pool of the #NutNovember hackathon just exceeded 1M Sats! Builders, what are you waiting for??