SatsAndSports

https://cashutube.satsandsports.cash/

Into bitcoin, specifically cashu.

When I'm not working in the fiat mines, I'm into cycling and camping

I'm trying to use White Noise (different npub), but don't have many contacts there yet!

Public Key

npub1zthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnq6wxm56

Profile Code

nprofile1qqsp9msr6ytgfgf9mkrmapuu9qvsg9d78ua3ajntfmt580t5llvgpespp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezumrpdejqz9mhwden5te0dehhxarj9e3ksctfd4sju6twvehshfqw65

Publishing to

nos.lol

nostr.land

nostr.chaima.info

Author Public Key

npub1zthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnq6wxm56

Show more details

Last Notes

2026-03-04 07:55:58 UTC

- reply

"New use cases should always get consent from the network"
I'm with him, as long as he agrees that a few dozen nodes are sufficient to grant that consent 😂
Large OP_RETURNs were formally approved by the relay network in 2024, by a few dozen nodes deciding to relay them. Therefore, the debate ended then
https://xcancel.com/BitMEXResearch/status/2024952265719611458

2026-03-04 00:20:24 UTC

- reply

Use nostr for players to find each other and to record the results of each battle
Use conventional network connections during game play
Pay continuously with bitcoin micropayments for the infrastructure, including for the blossom servers that provide the game binaries to those that don't already have the binary
With good containerization, so that we don't mind running those random binaries

2026-03-03 22:51:57 UTC

- reply

Why does every movie have a quote that reminds me of Bitcoiners?
https://image.nostr.build/4c8165db86f86a4baeccbe607a2ab7dc71f6cf0bc2108c84ccc0169fa36d09fc.png

2026-03-03 21:49:38 UTC

🤯
https://image.nostr.build/3ff6ecae3f3b3f1aecd102e3cafe2e22b25c60e5256ed9b72ef3ff9a92e580e3.png
I don't actually know anything about zero knowledge proofs, so no real idea how serious this is
https://xcancel.com/osec_io/status/2028901596965552572

2026-03-03 21:46:25 UTC

"Rebasing 442 commits on top of 132 new ones is a significant operation."
No excuses, Claude. No mistakes, I've got a movie to watch while you're working
====
Seriously though, I've had a very mentally stimulating two days, lots of discussion of bitcoin and nostr tech, and a couple of more weeks of this ahead! So I'm finally watching The Hangover (2009), which I'd never watched before. It's excellent
(Actually, using OpenCode instead of Claude)

2026-03-03 21:28:09 UTC

- reply

Duke Nukem 3D

2026-03-03 19:53:29 UTC

- reply

@npub1d7e…lrf3 , any thoughts on Cashu mints using FROST for their collaborative signing?
I'm slowly learning a bit about how Frost works. It's allows n-of-m signatures, so maybe a Cashu mint could use this with multiple-signers so that it can keep running if one of the signers is down

2026-03-03 18:58:13 UTC

- reply

Brands on Amazon have crazy names because Amazon insists that they have a registered trademark. And a crazy unpronounceable name is easier for the intern at the USPTO (US Patent and Trademark Office) to confirm as new and distinct from all the existing names
https://stemerlaw.com/2025/07/16/why-are-amazon-brand-names-so-weird-understanding-trademark-registration-and-2d-and-2e1-refusals/

2026-03-01 07:04:44 UTC

- reply

Can you explain further? I don't get what point you're making

2026-02-27 08:36:20 UTC

- reply

For what it's worth, I'm not a bot
But I would say that, wouldn't I? 😀
My guess is this is a scam, where I can 'verify' my human-ness by paying a subscription to the owner of the bot

2026-02-26 19:32:46 UTC

Love the progress on quantum-resistant signatures
324 bytes is great. The "stateful" is convenient, but I think there will be cases (Lightning?) where we're willing to pay that price
https://image.nostr.build/9f33e7bf032c81f8f2c78b57b0522c1a4b969a2018789cf9c11d3311307a8161.png
By the way, this long video is excellent on how quantum computers can factor numbers, and on the hash- and lattice- based alternatives for signatures and key exchange https://www.youtube.com/watch?v=aw6J1JV_5Ec

2026-02-19 20:41:08 UTC

- reply

Interesting! Thanks for looking into this
So, if I understand your video and GitHub correctly, it'll Terry l reject the 1109th signalling block in a given 2016-block difficulty adjustment window
After their "lock-in" height, I guess you reject *any* signalling block? I ask because they start rejecting immediately at the lock in height
So I think that means having a threshold of 1, instead of 1109, from height 961632
https://blossom.primal.net/c9dd4dd2ffdfc4b22065bd4df6975b3ef2e2f6a1a0c1f06fa714f50567d58868.jpg

2026-02-19 06:46:29 UTC

- reply

Well actually (🙂), the feet and metres do eventually line up
An inch is now officially defined at 25.4 millimetres
I think all the "standard" units are now defined in terms of the metric units
Anyway, brilliant video!

2026-02-19 06:34:00 UTC

- reply

What if it's a successful open source project? i.e. no money is made, but they might claim copyright over the code produced?

2026-02-18 17:17:58 UTC

- reply

I can see this, from Amethyst. Haven't tried any other client
Maybe it depends on the relays?

2026-02-18 10:38:43 UTC

Giving up X for at least a couple of weeks
I might check once a day to see if I have an interesting notification, like an interesting reply to something I said
Prior to summer 2025, I had avoided X for about three years. Maybe I should do that again!

2026-02-17 22:17:12 UTC

- reply

Yep. I quit a few months ago after going on and off for a couple of years
First time I quit it, I had (mild) headaches for a few days and some kind of depression

2026-02-14 14:36:22 UTC

- reply

At 1:30:05 Mechanic says "are you going to URSF? I don't think so. .. Seems unlikely to me"
There are many of us willing and able to URSF. At a minimum, we'll call "invalidateblock" on the first BIP110 block (if it ever finds a block)
This isn't an idle threat, it's an obvious truth. Mechanic might strongly dislike our opinion, but it's bizarre to pretend that we literally don't exist
For example, I have no problem agreeing that many (dozens, or thousands) of people will run BIP110 nodes through the activation height. (In fact, I'm one of them!)

2026-02-14 14:26:41 UTC

- reply

At 1:26:10 , Mechanic agrees with Guy (correctly) that "15 folks with AR15s" can be very effective
In relay policy that's also true, for the nodes that wish to*relax* policy.
15 LibreRelay nodes have a bigger effect on relay policy then a million filtering nodes

2026-02-14 14:00:02 UTC

- reply

Around 1:11:30, Mechanic falsely said that Gloria is no longer a Core developer
She's no longer a Core *maintainer*
Maintainer ≠ Developer
and then another one of you randomly made the claim that she was encouraged to leave by Chaincode. Bizarre claim
And then Mechanic literally says that the "Devs think bitcoiners are shitty people" "She was obviously in contempt of bitcoin and bitcoiners"
and then bizarre claims that "the Devs" and "VCs" successfully pushed her out. Obviously false frankly

2026-02-14 13:21:26 UTC

- reply

Context: I've learned a lot about the Bible, including Luke's gospel, in recent years. (Despite never believing any religion)
https://youtu.be/5KY-lZ5s-D4

2026-02-14 09:33:50 UTC

Now, I sometimes use 'Gemini Flash 3' for planning and 'GPT-5.2 Codex' for building. This is only because, in Opencode, I've noticed that Gemini kinda crashes in build mode; it's works for some time and then just stops in the middle of the task. Maybe just a funny detail in how Opencode is integrated
Anyway, in practice, I'm still mostly using my Claude subscription inside Opencode, but that's cheap. But I like the ideas Gemini has for improving the codebase

2026-02-14 09:26:01 UTC

- reply

Exactly!
TL/DR: Welcome to open-source, where people work on what's important to them. If you don't like it, fix it - or fund it - yourself 😀

2026-02-12 22:10:45 UTC

- reply

Why didn't you respond to anything I said in my post?
Your generic response suggests you didn't read anything that I said

2026-02-12 07:14:01 UTC

- reply

Indeed
Does anyone remember that Maduro is still kidnapped in the US somewhere?
I wonder what they'll come up with next? Kidnap the Canadian or Danish prime ministers?

2026-02-11 09:48:10 UTC

- reply

But if I use the same address on many sites, then they can be linked to each other
And it would be easy to link to a Nostr identity
Bolt12 is better. I can easily generate many Bolt12 offers from my node, and they'll be different from each other and can't be linked

2026-02-11 09:20:00 UTC

- reply

Looks like fun. Thanks to whoever made it!
A suggestion: it shouldn't require a Lightning address to play. It would be nice to have more privacy-focused approach, like Bolt12

2026-02-09 20:27:03 UTC

LLMs duplicate code too much. I got it to reorganize a bunch of code for the client-side of my system (the cashu channels). It liked and understood the changes I made, both for security reasons and maintainability.
I immediately asked it to apply the same thing to the server side. It immediately understood and saw the great similarities between the client side and server side
It did it, but didn't realize it has duplicated lots of code until I asked it to check.
This isn't really a complaint. I'm actually glad that it (Opus 4.6) makes this mistakes as it means I'm still relevant as the architect and designer 😀
https://image.nostr.build/0e00cfaf888cc376a764e3b3932ea9199012e9b21ab0d8ac6777fab399c943ce.png

2026-02-09 18:21:26 UTC

- reply

Very interesting! Danke

2026-02-09 11:19:56 UTC

LLMs still (I basing this mostly on Opus4.6) don't appreciate how to order items in their todo list
If we're working on component A, where A depends on B, and then we realize that B needs to be updated before A can be updated, then the priority should (depending on the precise circumstances) be to get B correct before updating A.
It's too keen to do major refactorings, redesigning everything in one step. That's still too likely to result in everything breaking. I often have to intervene to help it identify the best (least likely to break) order in which to change things.
Get the interfaces right between your components, starting with the lower levels, before working your way up
Of course, as the LLMs are getting better, I'm allowing them to be more 'ambituous' and to try to do bigger changes at once. But, as of now, their level of ambition in complex protocols/systems doesn't quite match their ability, and I have to intervene regularly: "Yes, we want to change X,Y,Z, but don't you think that we can change Y first and ensure that all tests keep passing before we proceed to X and/or Z?"
https://image.nostr.build/922c1d6d07c1d53119abb3636664f1062dec5cf5b35ac85d0992e6a17966e292.png

2026-02-09 09:21:44 UTC

- reply

Given that Rust has no UB! , why do people say that Rust is Co(re)mmunist?
🤔

2026-02-09 09:19:10 UTC

- reply

The world is very lucky that, in the US, code is considered speech and is therefore protected by the First Amendment. This legal idea developed only in the 1990s
In much of Europe, as I understand it, code is classified much like an act of creative expression like a song. And therefore it's more subject to regulation such as copyright and so on
So we need to fight for "code is speech' also, not just "free speech", globally
https://en.wikipedia.org/wiki/Code_as_speech?wprov=sfla1

2026-02-08 23:50:50 UTC

- reply

😀. You mean -10 points for using my terminal with black text on a light background? I think it's among the first changes I make when setting up any new machine 😀
When AIs take all our jobs, I guess this is all we'll have left to distinguish ourselves as human sloperators. What colour scheme do you use when typing with your agent?
PS: I posted the wrong image first time; and the Nostr 'edit' thing doesn't seem to be picked up correctly by all clients. This is what I meant to share:
https://image.nostr.build/6cf117e7bb4b72b47f18627705194f214d0e3389826abea8505aa7b3ad55cad8.png

2026-02-08 23:38:04 UTC

Your daily reminder that property-based testing is the the way. OpenCode/Opus4.6 is happy that it can make the change I requested (hashing a shared secret) without having to change any of the 50+ tests:
https://image.nostr.build/5face9150de26cf2c81a02d65eaf18f98cb427b3fb6f9606086ec1fad2ff0923.png

2026-02-08 23:17:54 UTC

In the Cashu channels, I'm using a DiffieHellman shared secret to add a little more privacy in places. For example, it's used to compute the channel_id in order to make it more difficult for third parties to guess what the channel_id would be between two parties.
But AI has helped me realize that both parties should immediately hash the shared_secret upon computing it. In practice, this probably doesn't help much, but it's nice to hide any algebraic structure any time it's possible
https://image.nostr.build/827f1db985c32ab6c469f2a530d832bea63ccf40b08115c65c5797edf66d7257.png
you might say I'm overthinking this 😀. But it's fun to give these tasks to AI and continue watching a movie on a Sunday night while it executes:
https://image.nostr.build/554579a646f559682d996f4c3b1d7fb28bcdfd3dd37eecf79c82ce52279557c6.png

2026-02-08 16:46:15 UTC

Scaling bitcoin. Censorship. Why do we run nodes? The irrelevance of the "spam debate"
I just got zapped 21k for this long reply I posted on these topics. Thanks @nprofile…5jqx !
#nevent1q…yll3

2026-02-07 11:34:38 UTC

- reply

Thanks! I've edited it now. Hopefully people will see the edited link, or will follow the link you sent

2026-02-07 11:29:43 UTC

Sharing this might be illegal in the UK
#StreisandEffect #NostrFixesThis #EpsteinFiles
Peter Mandelson was the British Ambassador to the UK, and prior to that was a major political figure for decades previously, especially under Tony Blair.
He's also alleged to be one of the enablers of Jeffrey Epstein.
He's now abusing press regulations in the UK that were designed to protect victims of crimes from being harassed by journalists. See below for how his legal henchman are helping him with his coverup:
Reported by a major Scottish mewspaper yesterday: https://www.thenational.scot/news/25834517.full-secret-notice-peter-mandelson-just-sent-uk-media/#Echobox=1770404545-2
IPSO = Independent Press Standards Organisation
======
CONFIDENTIAL – STRICTLY NOT FOR PUBLICATION: Ipso has asked us to circulate the following advisory:
Ipso has today been contacted by a representative acting on behalf of Peter Mandelson.
Mr Mandelson’s representatives state that he does not wish to speak to the media at this time. He requests that the press do not take photos or film, approach, or contact him via phone, email, or in-person. His representatives ask that any requests for his comment are directed to [REDACTED]
We are happy to make editors aware of his request. We note the terms of Clause 2 (Privacy) and 3 (Harassment) of the Editors’ Code, and in particular that Clause 3 states that journalists must not persist in questioning, telephoning, pursuing or photographing individuals once asked to desist, unless justified in the public interest.
Please do not hesitate to contact me to discuss any Code issues on [REDACTED] or out of hours on [REDACTED].
[IPSO official]

2026-02-07 07:22:35 UTC

- reply

I'm way ahead of you 😜. When I look at posts like yours, I see very few retarded replies, and that's because I've already blocked many of them
It's true that they still add more bots, but it's easy to block them quickly

2026-02-06 21:45:00 UTC

- reply

Any updated thoughts on this, Jimmy?

2026-02-06 17:18:00 UTC

Liking Opus 4.6 so far
I still sometimes use Gemini or Codex out of curiousity to see what they would do

2026-02-06 14:01:12 UTC

- reply

You originally asked a question, and I provided an answer
Now you're trying to turn it into a debate, and you are not making good points. I'm moving on from this thread

2026-02-06 11:48:53 UTC

- reply

BIP 110 contains literally nothing that a "monetary maxi" (whatever that is) would want to see in a Bitcoin Improvement Proposal. Nothing to help Layer 2s to scale. Nothing to help the relay network with DOS attacks. Nothing to help privacy. Nothing to help small mining pools to see the same transactions that the big pools are getting. Nothing to help with the faster block propagation that will benefit the small pools. Nothing like Cluster Mempool, which will help small pools to play on a level playing field with the big pools.
The long term future of Bitcoin depends on anonymous miners being able to connect to the network, see all the transactions that are likely to be mined, quickly see the other blocks so they can mine on top of them, and be able to broadcast their blocks and have them propagate quickly and be built upon by the other miners. This is needed to ensure the small miners and small pools can mine profitably, i.e. they have an incentive to mine things that the government-controlled big pools are unwilling to mine. They must be able to include any consensus-valid transaction; i.e. have no corporation or committee or government which blocks the 'naughty' transactions
BIP 110 contributes nothing to any of this. It doesn't even try to do so
If you want less spam in the blocks, maybe them smaller. Luke Dashjr has suggested 300kB. Why not go further? 100kB, 10kB. 0kB would get rid of all the spam.
That might seem like a stupid point in the last paragraph. But I'm actually making a very important point. Our goal is to make Bitcoin the best money, to maximize its ability to instantly settle our private transactions at a very high frequency. If you "fight spam" and you don't care that you are harming the moneyness of bitcoin, then I can't talk to you. "Fighting spam" simply isn't a valid goal in itself; it best, it's a means to an end. Every proposal that somebody makes to fight spam will be judged exclusively on how to helps or hinders our real goals
We want and need our Layer 2s (Lightning, Ark, Lightning on Ark's Channel Factories) to massively scale, along with other Bitcoin scaling ideas like Cashu, in order that billions of people can make dozens of payments each day. (I'm working on extremely-high-frequency micropayments within Cashu)
We want as much as possible to stay off-chain in order to keep fees on blockchain as low as possible. Low fees today gives us room to onboard billions of people. Low fees help with security of the Layer 2s, as users of Lightning need the ability to quickly and cheaply access Layer 1 if their channel partner is cheating
We will continue to work on all the above, making the fees on L1 as low as possible
This means that blockspace will, if we succeed, stay cheap for a long time. Also, there is a basic fact:
Basic Fact: Steganography exists
If blockspace is cheap, then spammers will fill it with spam. This is a meaningless and fully-expected side effect.
There are lots of ways to encode spam in the blockchain. Some methods involve contiguous bytes and some do not. Nobody really cares about the distinction. Pseudo-lawyers will try to pretend that contiguous bytes are more dangerous than non-contiguous
But they are wrong legally, wrong technically, and wrong in every possible way about "contiguousness". The "contiguous" discussion is now over
Remember Mike Hearn and his "RBF derangement syndrome"? Remember MempoolRBF? If big pools are getting consensus-valid transactions via out-of-band systems (e.g. Mara's Slipstream) and are including them in blocks, then this is an advantage to big pools and a disadvantage to small pools
We know that a critical responsibility of the public relay network is the help the small pools so they can earn money at the same rate as the big pools. This is what decentralized mining is all about
Therefore, there will always be people who will help to relay those kids of transactions, in order to help the small pools. They'll mine fee-bumping transactions where the original transaction didn't signal willingness to be fee-bumped. They'll mine under 1-sat-per-vByte. They'll mine large OP_RETURNs if the big pools are benefiting from them
When a spammer posts a large OP_RETURN via an out-of-band system, we don't care about the fact that a spammer posted the transaction. It could be a heroic freedom fighter getting important information - or important payments - onto the chain. Spammer-vs-monetary is not the issue. BigPool-versus-SmallPool is the issue
As every Bitcoiner has learned in recent years, it's sufficient for a few dozen people to switch on relaxed nodes (LibreRelay, Core with lower fees rates, ...) and they will win. Moving policy close to consensus is easy to do, simply by firing up a few nodes. Trying to do the opposite, firing up thousands of filtering nodes, is laughably stupid
There will always be many people willing to help the small pools by relaxing their policy in cases where the big miners are getting this advantage. If you don't like it, you must engage your brain to think of a good response. If your opponents can trivially beat you by switching on a few dozens nodes, then you need to accept their existence as a fact in your game theory
The Knots movement pretends to be for decentralization of mining. If that was true, they would encourage (in the right circumstances) things like LibreRelay. It's truly bizarre that they took literally the opposite approach, and are trying to make it difficult for small pools and small miners.
Why do people run nodes? There are broadly two categories of reasons. Obviously, we run them for our own ability to make transactions and to monitor that our transactions go through correctly. But there are also less "selfish" motivations. I run my node in order to help small pools. We need to keep the miners divided, working for us, and that means allowing small miners to mine whatever consensus-valid transactions they want, and it means ensuring it's economically viable for them to do so.
That is the main role of the relay network, and a few dozen 'non-filtering' nodes are sufficient; and this is why Bitcoin will win.
Finally, BIP110 explicitly attacks many important things for the moneyness of Bitcoin. Attacking the OP_SUCCESS opcodes is particularly dumb. No sane person thinks that Bitcoin won't be having dozens of OP_SUCCESS opcodes for centuries to come. Just get over it
There's a lot more that I can say on this. Clearly, the orchestrators of BIP 110 relish in all the sexist and abusive rhetoric that is spread by their retarded bots and lapped up by some plebs. But I'm too lazy to write about that
Basically, my first paragraph above sums it up nicely
#bip110 #AskNostr #Spam

2026-02-06 08:25:23 UTC

- reply

As you can see, I didn't see that loser's comment as I had already blocked them before you made your post
Just block and move on. Let their bots talk to each other in the void
https://blossom.primal.net/9cacffebf4e04e5aa7430cbdf866aa47340373826ce96bc0b7eb9e0055469cad.jpg

2026-02-06 07:53:20 UTC

Arthur C Clarke, in 1953, writing about a post-scarcity future. The last few words are interesting to a bitcoiner!
(In this paragraph, "drone" means a lazy person)
https://blossom.primal.net/16fc7580556a584ae8198c18264fdf2cc344722e15802c657d740ff1e058cae2.jpg

2026-02-05 17:01:26 UTC

- reply

True, and a lot of racists too, but also I don't think there's any such thing as "a Bitcoiner". People with Bitcoin are as varied in their political views as those without
There are millions of "Bitcoiner" bots online, rage-baiting everybody, but that's a different thing

2026-02-05 14:28:24 UTC

- reply

Badly worded market. It's currently *expected* to activate around September 5th, four days after this market is supposed to close
Currently, there are 965664 - 935127 = 30537 blocks until activation, i.e. 305370 minutes. That's 305370 / 60 / 24 = 212 days from now, which is September 5th
They should have timed it to be about two weeks after the activation height

2026-02-05 00:03:57 UTC

- reply

It's time to accept there is no such thing as "a bitcoiner". It falsely implies a single shared coherent ideology

2026-02-04 20:52:56 UTC

- reply

And the merkle root is of a tree of equally-size blobs?
I ask because that might make it easy to skip to the relevant part of the video. Do we know the depth of the tree?
Although, I guess you have this size (and runtime?) metadata somewhere in the nodes of the tree?

2026-02-04 20:41:27 UTC

- reply

"Merkle roots can be published to get mutable npub/tree/path addresses"
Cool! So a query to that will return a signature of the hash by that npub, perhaps in a header in the response?

2026-02-04 20:14:07 UTC

- reply

Nice!
I'm going to have to steal that idea for CashuTube 😀, the site that serves HLS-encoded via (adaptive bandwidth) and which requires cashu payments
Of course, the server doesn't need to know the decryption key. And so web players could have the decryption key in the # portion of address.
https://cashutube.satsandsports.cash/

2026-02-04 19:00:30 UTC

- reply

My guess is that this is a Blossom hash combined with some video-specific metadata

2026-02-04 08:59:24 UTC

- reply

Are you ever not cooking! 🙂

2026-02-03 17:16:16 UTC

- reply

Imma need an openclaw just to keep checking for all these great community calls and remind me to attend!

2026-02-02 22:53:47 UTC

I just discovered BIP-42. Good fun, with nice digs at Satoshi
https://image.nostr.build/efa0421b9c1ee1055ddeaeec69aa07acb69ec7105a6b851c11bea955492ee21a.png
https://bips.dev/42/

2026-02-02 19:27:08 UTC

- reply

I've been thinking about that a lot recently, partly while trying to explain to my parents over Christmas about how LLMs will change the industry. I'm assuming for simplicity that LLMs won't get (much) smarter than they are now; a convenient, if unrealistic, assumption.
I'm probably oversimplifying, and my thoughts change a lot, but here goes:
For simple projects, a small group of mediocre humans was sufficient. If the project was complex and struggling, adding more (mediocre) humans didn't fix it
When a certain level of complexity/scalability/correctness/reliability is needed, you need at least one genuine human expert. This hasn't changed; LLMs are great, but are not geniuses
Without a real expert, a complex project will fail no matter how many LLM tokens and (mediocre) humans are thrown at it

2026-02-02 12:34:07 UTC

- reply

Maybe you've jinxed it now ☺️
I orange pilled a friend in the summer, and I'm very proud of them that they're still interested in Bitcoin

2026-02-02 12:31:30 UTC

- reply

I remember being glad that this failed. But I wonder if I'm being hypocritical when I don't care about things like USDT
I guess USDT is different, as it's not controlled (yet) by a media empire
But will that become a problem when Tether buy Meta!?

2026-02-02 11:30:49 UTC

- reply

Nice. I'm glad you mention "out of order", as it's something I was interested in when I played with the MDK.
If the events are not fed to the MDK in the right order, it's rejected. (I forget the exact error message)
Ideally, we can just trust the timestamps in the Nostr events, but I guess those timestamps can't always be trusted. Also, relays - prior to the Websocket's EOSE event - don't guarantee to return the events in the order of the Nostr timestamp
So I guess a defensive algorithm is to keep all the 'not-yet-accepted-by-the-MDK' events in a buffer, as they might be accepted later after other 'gap-filling' events have been processed?

2026-02-02 11:26:25 UTC

As I'm going to Madeira in March to meet some freedom-tech folks, I'm going to try to make a plan for what to do this month on the cashu spilman channel
- First, write and share an INTEGRATION.md, to explain how to easily integrate payment-receiving code into your service provider. I wouldn't use it for real sats yet, just testing! But I think it's ready for some feedback on the engineering side
- While there is blinding of pubkeys already and it's working, it's not identical to the spec in the P2BK nut; it will be easy to synchronize them, I just need to get around to doing it soon. This would be a breaking change, so while it's not urgent, it definitely has to be done
- Integrate it into another fun demo. I've made a lot of progress understanding the protocol that is used by many of the LLM providers, so I'll finish a little demo showing how I can resell access to an LLM api key. This might help with getting this tech into Routstr
- Then, I should really review all the code again, to tidy up the AI slop 😀. Some parts have received a lot of attention from me, others I've ignored.
- And I generally need to get it out there, and get people to review the protocol properly
Very rough overview of the architecture:
1. A 'cryptographic' core, which does all the singing and verification and constructs all the outputs deterministically. Has no opinion on transport (JSON, websockets, http), nor on pricing, nor on the service being sold. Written in Rust
2. A 'Bridge' system - written in four languages currently - to expose a convenient wrapper on the server side of things, making it easy to process a payment and either succeed (updating records of the balance and the usage of the channel) or fail (returning a suitable error message). Again, this tries to be *un*-opinionated. It manages the state, but you tell it exactly how to store things (in memory, in sqlite, ..., you just plug in whatever you want). Also, this doesn't care what you're "pricing policy" is; maybe you charge per request, or per megabyte, or per token. You provide the code what computes the price.
3. There are automated tests of the Bridge - via a demo server selling ASCII art - in Python, Go, Rust, and Typescript

2026-02-02 08:17:06 UTC

- reply

I've been trying to start an openclaw on my VPS inside either docker or podman (podman is very similar to docker), but without much success. Keep getting annoying problems (probably just my fault)
Are you doing something like that?

2026-01-31 21:54:10 UTC

Been using Kimi K2.5 today a lot (free now, via OpenCode Zen). Very happy with it. Much better and faster than I expected from an open source model
I didn't really try anything complex today, so maybe I'll change my mind when I try something more complex

2026-01-31 21:47:00 UTC

The blob discovery in Blossom will eventually need to be made more scalable I think. Imagine the nostr/blossom decentralized equivalent of CDN systems like Cloudfare, where your client keeps a large set of servers in a list, prioritizing those with the lowest latency and the best reliability, constantly hopping around as needed to get the blobs
And, when we're paying for blossom servers and nostr relays with micropayments, you can prioritize for low cost too of course
#naddr1qv…u4ga

2026-01-31 20:49:21 UTC

- reply

You might find it interesting to check out Strategy's balance sheet
They have Bitcoin worth $54 billion
Their liabilities are valued at about $8 billion, and they have enough cash on hand to pay their liabilities for the next two years
So Bitcoin would need to go to about $15k, and stay there for a few years, before they would be in any trouble

2026-01-31 15:09:06 UTC

- reply

My White Noise npub: @npub16w8…7ehf
I have zero contacts there at the moment.
My key packages are on relay.damus.io, relay.primal.net and nos.lol. I think those are the default relays
=====
A few months ago, I played around with their MDK library and was very impressed. I got a my own chat client running and I found it very fast. The White Noise team are currently overhauling a lot of their code and I'm optimistic that their next release will be good

2026-01-31 13:28:32 UTC

- reply

The agents should just build it themselves

2026-01-31 00:11:36 UTC

- reply

I guess they need some variant of a captcha to keep the humans out

2026-01-30 12:16:52 UTC

- reply

It might be different, but this kinda reminds me of something I'm doing with my library for processing payments cashu spilman channels.
(I have a question at the end of this long comment)
I have Rust code for processing payments, wrapped around a transport-neutral and stateless core
The wrapper needs to do complex stuff, while also managing state ("how many payments have been made on this channel so far?"). But I didn't want the wrapper to hardcode an arbitrary choice about how to store the state, e.g. SQLite
So, I have a relatively dumb 'Host' interface, where the developer specifies how state is managed. For example, it has a methods "mark_closed(channel_id)" where the developer fills in the code that writes to the database of their choice to record that a channel is now closed.
The developer will typically not call those functions directly from their code. They just call a higher level "process_payment" method in my library which does all the complex stuff and which calls the Host object when needed
The Host also handles all the "pricing policy"
Anyway, I should get back on topic and ask a question 🙂: I guess you might have something similar? The MDK doesn't need to know where state is stored?
I vaguely remember dealing with this when I used the MDK a little on my toy app. I think I had to do something special to get it working with localStorage in the browser, but I forget the details

2026-01-30 11:45:30 UTC

- reply

I'm not certain this if the right repo, but this is an open source project, so they'll share the code along with any release, if it's not already released
https://github.com/marmot-protocol/whitenoise-rs

2026-01-30 09:23:07 UTC

- reply

You mean $100k (or €100k) as the one-off cost of buying the hardware? (Maybe I misunderstood, I haven't been following the economics of this)
I guess one disadvantage of local hosting is that it (the hardware) is under-utilized, and that motivates sharing the hardware among multiple users
I guess that's where Routstr ( @nprofile…mt7m ) comes in, enabling a large marketplace of (small) providers, paid via bitcoin of course

2026-01-29 22:02:22 UTC

- reply

I added spaces between 'coin' and 'join', and then it worked. Maybe they just have 'coinjoin' (no spaces) on a blocklist
I think it's the first time I've seen that message on X
#NostrFixesThis
https://image.nostr.build/0cabda174b87e524c57829e9faa185e26a5f17a0943fce77ed4d36917325d5f0.png

2026-01-29 22:00:35 UTC

X not allowing me to post about coinjoins?
(See the blue text at the bottom. I've retried a couple of times)
https://image.nostr.build/9158d6ca2a0269489003ed814ab3b0b019f6d2d70440f4e0c148cc1ad2a6a2b0.png

2026-01-29 21:49:29 UTC

- reply

I can do silver, not gold

2026-01-29 20:19:50 UTC

- reply

I didn't know this podcast existed! I've just started the first episode and love it so far
I love Bitcoin Optech, so I'll be adding this to be my list of podcast to binge on long cycles

2026-01-29 20:17:45 UTC

The cashu spilman channel uses public keys and so we're using P2BK ( @npub1emq…a3jz ) , Cashu's version of Bitcoin's 'Silent Payments', so that the mint doesn't see the real public keys of the channel participants.
Nice to see that the LLM understands that it's working across all four languages that I'm testing with (Rust, Go, Python, Typescript)
https://image.nostr.build/35801aa5d67e8c8d1907e466b1e55913674d652a12ca1ea0bba2f55a249b79ed.png

2026-01-29 07:27:24 UTC

- reply

The earliest graphical depiction is this infamous piece of graffiti from around 200 AD. It depicts Jesus as a donkey!
https://en.wikipedia.org/wiki/Alexamenos_graffito

2026-01-28 22:48:51 UTC

- reply

I think yes, unfortunately
We needed bitcoin (especially Lightning) earlier. If we already had bitcoin in the 90s, it could have funded a lot of open infrastructure

2026-01-28 22:41:48 UTC

- reply

Doesn't matter. Just stay active if you want, regardless of the consequences

2026-01-28 12:41:33 UTC

- reply

I'm using it today for the first time. I'll see how it is with my cashu dev stuff. I like it so far, but I need a few hours use to form a definite opinion
Are you hosting it locally? I'm accessing it via OpenCode Zen

2026-01-28 08:48:05 UTC

- reply

The engineers that aren't better than the LLMs will struggle
Up to a certain level of complexity, the LLMs can work without any human engineer. A product manager might be able to ship things without any engineers
But above a certain level of complexity, an expert human is needed. Those experts will thrive, as they are necessary to building the best software (secure, scalable, correct,...)
Humans will either be 1000x engineers, who are supercharged by the LLMs, or 0x engineers, who are worse than the LLMs on every dimension

2026-01-28 00:02:33 UTC

Reading a little about how Tor works, thinking of having the user pay the relays via Cashu channel micropayments
https://arti.torproject.org/

2026-01-27 22:01:22 UTC

I'm genuinely struggling to stop coding every evening. With LLMs, it's just too much fun to continue. I think I'll initiate a 9pm coding curfew

2026-01-27 21:31:22 UTC

- reply

This is kinda cool about the bunker, but it seems like a confusing step for a nostr noob.
But anyway, I should be grateful to whoever put that nstart.me together! We definitely should use it
The final page, which links to various app/websites, could perhaps be improved a bit. It could link directly to the app stores if possible. The web links could be something like jumble.social/welcome-new-login/npubXXX which would welcome the user based on their Kind0 and then ask them to enter the nsec which created a little earlier in the flow.
https://image.nostr.build/227af75209b3741aadf28245ada839330aee3ebd0f09b8bb7691c95f30de90af.png
https://image.nostr.build/ba9354ea1f224ba2d8359ae5e9663cb98cb61dd4d616e76ca0b80997fd658841.png

2026-01-27 20:54:42 UTC

- reply

I'm going to blame AI

2026-01-27 13:51:45 UTC

- reply

Thanks for writing this. You're right
With Nostr being a protocol, as opposed to an single open source project, then I think it might fit in nicely there. The EU could encourage development of many Nostr projects without the 'centralization' risk that you mention
But I guess I'm naive, and I shouldn't obsess about Nostr 😀
(I tried to zap you, but you don't see to have an address set up)

2026-01-27 12:05:14 UTC

- reply

What I see on Android:
https://blossom.primal.net/887e54de8aef8198c5962717c9def89720983e9c05b845e97b03d1cf9441679d.jpg

2026-01-27 11:57:38 UTC

- reply

Like a true altcoin
When can we call it a memecoin? A shitcoin?

2026-01-27 00:41:15 UTC

- reply

Many systems (including bitcoind) don't directly have Tor support built in and they instead connect to a local socks5 proxy which is exposed by the Tor instance which is running locally too. So, after a little LLM research, here's what I'm thinking that somebody could do:
- Run the above, but expose the socks5 proxy to the internet. This exposes a socks5 proxy which directly forwards the request into Tor.
- But tweak the sock5 proxy so that it requires cashu spilman payments
- Now, given that we need a custom client which sends the payments, which can also encrypt the connection to socks5:
https://image.nostr.build/aa1f4f4c51a257d81514a6d32fd804c6349ebfaf215669a16b5d3c11f3aea769.png
(but maybe that's exactly what epoxy did 😀)

2026-01-26 23:46:00 UTC

- reply

Yes, '(paid) socks5 proxy' is a simpler way to say what I said. But I (we😀) hope that Bitcoin changes things now by paying for a massive rollout of this. And we could pay Tor nodes too
How were payments made in Epoxy?

2026-01-26 09:09:30 UTC

- reply

I don't know enough about Tor, but I'll ask anyway:
While I'm too scared to run a Tor exit node, I wonder if we could all help the Chinese people by running what I might call a Tor "entry node"?
The idea is that we all run something that can help the Chinese to access Tor, by forwarding connections to Tor. We could hide them inside our normal websites, so that connections to this entry node look like typical HTTPS connections.
We could be motivated to run these via bitcoin, where the users have to pay small amounts of bitcoin if they want a high bandwidth connection. If we all run these, then the Great Firewall would have to block very many entire websites
( @nprofile…4qea )

2026-01-26 08:55:39 UTC

- reply

This is the first winter in many years when I won't be doing any winter sports, and then you post this to make me jealous of all the fun I'm missing 😜

2026-01-26 07:17:52 UTC

- reply

What do you do when Musk turns it off?
I guess the answer is that there is no one-sit-fits-all solution, yet. Let's hope things like bitchat and Lora catch on, for permissionless mesh networking

2026-01-25 21:10:29 UTC

- reply

I think it's possible to make something like njump.me which is a PWA - i.e. it works entirely in your browser and will work even if the system is down. I hope to make time to implement it sometime (but I'm busy vibe coding other stuff 😀)

2026-01-25 11:08:18 UTC

- reply

Ah yes, I kinda forgot about that. Good point

2026-01-25 11:02:55 UTC

- reply

Putting aside clients for a moment, what are all the different ways that relays can be used? Would it make sense for me to run relay that does two things:
- store the events that I create, in order to help them stay visible if other relays go down.
- copy the events of the users that I follow, so that I can access them efficiently, but also so that I have a record of what I have read just in case others try to delete their message. (And I also find it annoying when - in some clients - I see ant even is missing because my client can't find it)
(also with a blossom server, playing similar roles)
Does that make sense? Although, maybe they should be two separate relays
Even though I've used Nostr for a while, and even written some tools that use Nostr, I still feel unsure what is the right thing to do around relays.

2026-01-25 10:53:00 UTC

- reply

I know relays and clients are separate logically. I was wondering there was an open source system that was a good relay and also hosted a good client

2026-01-25 10:28:06 UTC

- reply

So it's just the browser pages
I thought for a moment that a Jumble server would provide assistance to the client, by being a nostr relay focussed on helping me. It could pre-load all the events from the people I follow, so that whenever I connect via my client (Amethyst or Jumble client, or whatever) it would be faster
In any case, I do like Jumble as a client, so I'm tempted to run it even if it's *just* a web server servings the (static) web app

2026-01-25 09:51:48 UTC

- reply

I've used both, but I don't understand
Both have the Plan-vs-Build distinction. Are you saying that the prompts in Claude Code nudge it in a different direction, which you prefer?

2026-01-25 08:05:55 UTC

- reply

While I use the Jumble website, I don't know what you mean by a self hosted instance
Jumble have their own relay software, which you run somewhere?

2026-01-24 11:47:53 UTC

Using docker to bring all the cashu spilman channel code together and run all tests against various combinations:
- While the core is in Rust, there are 'bridges' written in Go and Python and Typescript.
- All tests are repeated with two mints, the cdk's built in mint and also NutMix.
The 'bridges' make it easy for service providers to accept these payments, regardless of their pricing policy and their policy for storing the data (sqlite, postgres, in-memory, ...) necessary to manage the state of the channel
I thought I knew Docker, but I learned a lot more about it while setting this up yesterday
https://github.com/SatsAndSports/demo_of_spillman_cashu_channel/blob/spilman.channel/scripts/Dockerfile.test