Loving Lyn Alden's sci-fi book "The Stolguard Incident". Just halfway through now. So many topical themes coming together nicely And characters that I care about! @Lyn Alden

Austrian economists claim they're the experts in predicting what will naturally become money, without realising that billions have happily used fiat and bank credit for decades, choosing the "wrong money" A paraphrasing by Claude of Austrian thinking: "here are the properties that make a good money (divisibility, durability, portability, scarcity, etc.), and market processes will tend to select for those properties over time." If your Austrian model can't predict the last few decades, then it's not a serious model 😜. Maybe there needs to be a modernization of Austrian thought that acknowledges that speed is critical. I guess it comes under "portability" Instant settlement is crucial. Privacy is important, not just as a good in itself, but because a lack of privacy is risky to the finality #LightningFixesThis

Join the FIPS mesh directly in your browser with one click, using a Linux kernel and FIPS stack, both of which are running in JS/WASM in your browser tab. A new platform (Linux in the browser) for @npub1y0gj...00ly , and a new transport too (websockets, because web apps aren't permitted to do raw TCP). Just one of the many fun things demoed at @Sovereign Engineering . This requires my webtransport-aware node being online, so that it can be your gateway. But maybe we'll have many such nodes in future!

FIPS Browser VM

Using Claude Code for the first time in months, after a few months where I was using Opus in OpenCode Claude Code is weird. Even in 'plan mode', it's constantly asking to change things. In Plan Mode, I want it to just answer my questions and suggest things to do. I don't want it to (try to) do anything until I decide to exit plan mode and type 'go' Maybe I'll get used to it

Anybody extending Cashu so that my wallet doesn't share a Bolt11 invoice with the mint, but instead just shares a path computed by the wallet? I don't want the mint to know what is being paid, but the Bolt11 invoice shares a lot of info with the mint Bolt12 is kinda relevant, but I don't think there's any way for me to take someone else's Bolt11 and then convert it to a Bolt12 by adding my own blinded hops

Is there a signature scheme where you can confirm that my DM to you really came from me, but where you can't share that proof with others? ... Maybe a scheme where you'd have to release your private key in order to share the proof? (Maybe some form of Gift Wrap already does this?)

I like how agents just answer the question, giving a simple 'Yes' or 'No' if that is appropriate for the question How do I train humans to do the same?

Steve Keen is a great economist Like me, he's (post-)Keynesian. I've listened to many great discussions involving him. Like the MMT folks, he understands how fiat money works, especially credit cycles and crashes. They understand economics better than many Bitcoiners But he still hasn't learned about the difficulty adjustment So bullish In a much older interview, he implied that the energy needed by Bitcoin is proportional to the number of transactions If he learned that this is false (i.e. the difficulty adjustment), we could all benefit from his intellect! Hyperbitcoinization is going to be fascinating and dramatic, and will require people who are able to analyse the interaction between fiat and credit and Bitcoin Steve Keen and @Lyn Alden would be my dream team for that analysis A clip I saw just today on X, which inspired me to post this: (this old interview is where, I think, he first discussed bitcoin:

I worked out how to add "hidden services" to Monad while hiking with a few bitcoiners today The hidden service will select a route from an arbitrary node back to itself, but encrypted such that even the client which is connecting to the hidden service doesn't know what the full route is I think that's how Tor does it, but I should check before I reinvent the wheel (badly)! But there are other things related to @npub1y0gj...00ly that I'll finish first ... View quoted note →

archive this please https://chaum.com/wp-content/uploads/2021/12/Untraceable_Electronic_Cash.pdf @NAAN

I'm making great progress(*) working on MONAD, which I just seriously started researching and planning on Sunday night Monetized Onion Network Access Deamon It's like a VPN or Tor, but you pay the relays via Cashu Spilman Channel micropayments. You can connect through any number of relays, paying for more relays if that might help with privacy I'm very happy with the networking design (**), and I have a working system where the sessions are paused when the client needs to 'top-up' the balance needed in the session. I'm just working now on getting it working well with the Cashu Spilman payment channels I'll reply immediately with more of the internal details, including links to code that's already a few hours out of date (a long time when being a Slop Cannon).... (*) having lots of fun mostly, and learning more networking stuff (**) I have some relevant background in encryption and networking, but I'm not an expert in mixnets or traffic analysis

So happy that my clanker uses printfs everywhere, unlike all that complicated technology that Big Debugger tries to push

I found this very interesting (even though it didn't mention bitcoin)

The source for Claude Code was accidentally released Now we have proof that smaller codebases are always the best 😀 #OpenCode4EVER

It's Noise-y Cashu-funded Onions all the way down #ComingSoon

My next step in the cashu spilman channel will be a 'client proxy' and a 'server proxy'. The server proxy will sit in front of typical services like Nostr relays or Blossom, but they will enforce payment and will raise 402 errors if the payment is missing Similarly, the client proxy will run on your device to insert the payment into the request before it's send to the server Blossom seems like a good place to start, to charge for uploading; I checked a few details about the protocol today, BUD-02 allows to upload to one server (the server proxy) where the server proxy will 'redirect' the client to the *real* Blossom server for future reading, and I think that typical Nostr clients will 'do the right thing' when they are behind the proxy It should be easy for us to extend the functionality of this 'server proxy' over time. Nostr and Blossom today, but it could wrap other things in future

A tiny Cashu Spilman channel update; I should make these more often: While the server side (i.e. payment receiver) code is in a reasonable state for now, in terms of flexibility and a clear state machine, I'm now catching up with a similar approach on the client side Just today, I'm adding an 'Opening' state to the client, just before 'Open'. The client opens a channel by creating a 'funding token' with the mint, a token which is in a 2-of-2 multisig very similar to a Lightning channel. If the swap (or melt) which creates that fails (or *appears* to fail, from the client's point of view), then the client should probably try again or use NUT-09 to get the response. So I'm implementing and testing that now

GitHub

nuts/09.md at main · cashubtc/nuts

Cashu protocol specifications https://cashubtc.github.io/nuts/ - cashubtc/nuts

The code is now a library which depends on the CDK, i.e. no longer a (disorganized!) fork of the CDK:

GitHub

cashu_spilman_channels/ARCHITECTURE.md at main · SatsAndSports/cashu_spilman_channels

Contribute to SatsAndSports/cashu_spilman_channels development by creating an account on GitHub.

After big code changes, ask your agent if there were any surprises while it was working. I always find it interesting; sometimes it raises important details that it otherwise wouldn't have told me about Ask it what changed and what didn't. If you think that a particular task is a conventional refactor of a particular module and it shouldn't affect any tests or any other modules, it's good to verify this afterwards