DeepSeek persists Cache even after 27 mins!! Unheard of. DeepSeek v4.1 Flash has been live on Routstr for 2 days. One of the best models for the cost you’re paying. It’s blazingly fast. Frontier flash!

Deepseek V4.1 Flash Beta is live on @routstr before the official release. Model id: deepseek-v4.1-flash-expires-on-0910 If you have a deepseek upstream you can add a custom model in your Routstr node with this model id. (Not officially available on the api yet).

We exploit them everyday. 😬 We use nsytes internally for many frontend deployments, especially PRs on ngit. Ngit and nsites. Kudos to

GitHub

GitHub - sandwichfarm/nsyte: deploy, manage and inspect websites served over nostr and blossom (nsites)

deploy, manage and inspect websites served over nostr and blossom (nsites) - sandwichfarm/nsyte

by @sandwich View quoted note →

There's a model called `mercury-2.5-preview` that's being served at 800 tok/s. It's not a big model, it's good for some operational tasks. But it's a pleasure to work with super fast models. Check it out :). PS: Misses a lot of cache reads, but well, it's cheap.

If you've noticed, routstrd now requires a lot fewer sats reserved for even big models like Kimi-K3. Kimi-K3 requires just 1.2k sats to make a request and usually 50 sats per request. View quoted note →

Translation: Eating, sleeping, walking, meditating, journaling, reading, reflecting. The rich life as I understand it. View quoted note →

Took us a while to fix all these issues. Sorry about the inconvenience in the last week or so. Please update and try the new version of Routstrd let me know if you have issues: routstrd update Or if you’re using an older version: bun i -g routstrd Officially releasing soon! View quoted note →

A part of this is also because of the recent Minibits changes. If your default mint has been Minibits, you're essentially bricked until we handle this migration. This and in combination with a commit that went into the last routstr-core release will cause you disruptions despite having a second mint in your Routstrd. View quoted note → View quoted note →

To all routstrd users, I’m really sorry about the infrastructure has been sub par this last week or two. We are not actively being attacked by anyone. It is simply because this stuff is hard (combining Nostr, Bitcoin+Lightning+Cashu and LLMs) and we made a mistake of pushing a change to Routstr Core that should’ve been in the next release. We are responsible for the disruptions in your workflow. I’m really sorry about it. We’re working on making it a lot more stable with the upcoming release of routstrd.