Nostr notes by rafftyl

I went to hell and back after one particularly humongous dose. ...

2026-10-15T17:30:55Z

In reply to nevent1q…7qhy
_________________________

I went to hell and back after one particularly humongous dose. Never doing this again. Still worth it.

You should have a look at @npub17fe…nzuc

2026-10-11T07:33:48Z

In reply to nevent1q…4jvn
_________________________

You should have a look at nostrich (npub17fe…nzuc)

Armada for communities, @npub1980…hr0x for highlights and ...

2026-10-10T20:22:05Z

In reply to nevent1q…yv7p
_________________________

Armada for communities, Boris (npub1980…hr0x) for highlights and highlight feeds. ConduitMarket (npub1nkf…2svu) also shows a lot of promise, though Nostr marketplaces are still on a very early stage. If you're into short-form brain rot, you can have a look at c4a39f1291291d452405cd8ddd798c4a29a3858c52cd0d843f1f6852cf17682e (npub1cj3…klr7), but it's definitely not for me.

If you're using mainly kind 1 clients, I think you migh be ...

2026-10-10T18:39:22Z

In reply to nevent1q…hkr4
_________________________

If you're using mainly kind 1 clients, I think you migh be missing a lot of "other stuff" traffic happening: highlights, Concord comms, marketplace stuff, Divine videos, and probably all sorts of other arcane arts that I'm not even aware of.

@npub1der…xzpc are you aware of any tools for kind 1111 ...

2026-10-09T12:57:18Z

Gigi (npub1der…xzpc) are you aware of any tools for kind 1111 discussions tied to highlights (or better: tied to any kind)? Highlight feeds in Boris are quickly becoming more interesting than my kind 1 feed and it would be great to be able to get some conversations going.

Now that I think of it, daily might not be healthy, but nostr ...

2026-10-08T17:10:25Z

In reply to nevent1q…zytj
_________________________

Now that I think of it, daily might not be healthy, but nostr would greatly benefit from more art being posted regularly.

Please do. Social media is not that bad without the ragebait ...

2026-10-08T17:09:26Z

In reply to nevent1q…30q7
_________________________

Please do. Social media is not that bad without the ragebait algo.

Unless a social media break is a kind of break when you engage in ...

2026-10-07T14:14:34Z

In reply to nevent1q…uj7c
_________________________

Unless a social media break is a kind of break when you engage in social media. English confuses me.

Anyone seeing this note is most definitely not on a social media ...

2026-10-07T14:13:34Z

In reply to nevent1q…4fwp
_________________________

Anyone seeing this note is most definitely not on a social media break.

:red: :green: :cyan: :grey: :blue: :orange: :purple: :white:

2026-10-07T14:10:36Z

In reply to nevent1q…t9gs
_________________________

:red: :green: :cyan: :grey: :blue: :orange: :purple: :white:

I clanked it: ...

2026-10-06T19:52:16Z

In reply to nevent1q…lggr
_________________________

I clanked it: https://github.com/rafftyl/custom-umbrel-app-store/tree/master/rafftyl-custom-store-rustress

Still requires the user to generate a signing private key manually for NIP-57 to work, but it's good enough for me.

Archspire is a tech death metal band pushing the genre to the ...

2026-09-24T08:47:20Z

Archspire is a tech death metal band pushing the genre to the limits of absurdity. Their music is so dense that it's more funny than brutal. But we like funny, don't we? Their proficiency as musicians is on another level and I can attest that they really can pull this off live with no problems. An unbelievable band.

https://tidal.com/track/475956281/u

#music #musicstr #tunestr

Such a cool read, keep it up (please)! #naddr1qq…feaw

2026-09-23T16:11:00Z

Such a cool read, keep it up (please)!

quoting
naddr1qq…feaw

A note on AI usage: My reports and blogs are always handwritten. I do use LLM's for gathering information and minor (spell) error checking.

Ahh, it's been a while since my last report. Writing these actually help me reflect on the last few months and whether or not I made any progress on my goals. Sometimes I feel mixed about the progress, but this time I feel like I'm heading straight towards my goals. Though it didn't feel like that the whole way through.

My goal with these reports is to also tell you a story. A story about the windy road to simple solutions. Communicating that is not always easy and the order of developments can be very confusing, also for me during the process. There is more intuition involved in these things than I'd have anticipated. And the thing about intuition is that you can only start making sense of it when reflecting back.

The windy road to TollGate

About a year ago now I did the first experiments that helped dissect the protocols that make up the internet. TCP, IP, UDP. This was because we realized along the road to TollGate that in order for TollGate networks to flourish, they need to be built on a flat structure.

One TollGate needs to be able to trade data with every reachable peer nearby, not just with a mighty 'parent' gateway above it.

That has led to the creation of FIPS, which enables us to reshape TollGate into something that is only concerned with the accounting of the resource, which is data. And no longer with questions like "who do we connect to?", "how do we prevent spoofing (impersonation)?".

In the weeks and months prior to Sovereign Engineering I've been quietly working on redesigning TollGate around all the learnings we've gathered in the last year or so. Addressing our wrong or incomplete assumptions, like: - We always pay the gateway above us, they never pay us - TollGate is only a tool for traffic payments - TollGate needs to directly charge monetary value (sats) for its service

In the initial redesign I decoupled TollGate from the network aspect. Turning it into two parts:

TollGate-core This concerns itself with the basic messaging of the protocol, agnostic of resource, so it can sell data, electricity, liquids (fuel, water, beer), or anything else that makes sense.

TollGate-network This part specifies how to use tollgate with either an IP network or a FIPS network.

One thing didn't sit well with me though, and in some conversations with other people I expressed that something didn't feel right about how I was dealing with the monetary aspect of things. I added a 'pricesheet' mechanism where one TollGate advertises its price and tiers you could purchase. Which sounds fine at face value but it's almost impossible to automate the purchasing side. Because something felt off about my approach, I didn't really continue implementation for a while because of it.

Shortly after those conversations, at SEC-08, during a hike (THIS is what Sovereign Engineering (npub1s0v…rmq5) is great at) I got introduced to the idea of making each TollGate its own cashu mint. Where the cashu tokens don't represent sats, but they represent the provided resource. Bytes. Which get spent over x seconds, giving you a fixed bandwidth over the next x seconds. This changes the game entirely.

Why is that so special? Because then the protocol is solely concerned with the accounting of the resource consumed. The responsibilities of the monetary aspect get cleanly separated from the provisioning of the resource. I can give away bytes, I can sell bytes, I can exchange bytes.The TollGate protocol itself doesn't have to care anymore, because all it now cares about is that it received a byte proof, so therefore it will deliver a byte. Period.

The unit is not the only concern that has been resolved. Because a big piece of complexity came from the issue that a mint may not always be reachable by the customer. Well, with the TollGate now being the mint, it is always reachable, and it will be bloody fast as well.

Just the challenged assumption that we need to charge sats directly was the last puzzle piece. Following that conversation I reworked the design docs, which solved every open concern I had and the design got massively simpler.

Read the documentation for this model here.

The next months will be the moment to go full steam ahead on this design.

Bringing FIPS to mobile

I spent a good chunk of time on getting FIPS to work on mobile, mainly because I wanted to see the native transports work and bringing the mesh to a platform that can benefit a lot from a general-purpose mesh.

I created Myco as a test case for FIPS support on android. It was not very straight-forward to get FIPS to run on there because the OS has many more limitations as compared to desktops. You can have only one TUN adapter, which has to be spun up by the (android) app, rather than by the FIPS process. fips#127 Unfortunately Android only allows for one of those at a time to take its 'VPN slot'. That's quite annoying as you can't use the TUN adapter while having another VPN running. The node can still run and route traffic, but you can't use it yourself.

I also worked on WiFi-Aware support, which is peer-to-peer wifi between phones. And in order to bridge the mesh on mobile to a wired mesh, I added mDNS support on mobile as well myco#16. It lets any phone that's connected to an access point (SSID) to peer with other nodes in the same LAN network.

I did run into a plethora of issues that all stem from the assumption that each pair of peers has only one transport between them. But with BLE + WiFi aware, that assumption breaks. When 2 transports are available they just fight each other, causing instability. I quite enjoy uncovering these issues, it's all stuff that you wouldn't think about in any kind of traditional network. A solution is currently in pr fips#167 (open) on the fips side and myco#50 on the Myco side, which makes a mobile mesh way more stable.

Going forward

I'm not the only one to embed FIPS on mobile. Fr34ky also created his fips2go app. Our goal is to work together on a drop-in library that any app can use.

There's 2 problems we'd like to solve with that: 1) Stop every app from having to build its own embedding from scratch, so devs can ship FIPS apps, without requiring a separate FIPS app to be installed. 2) Since there's only 1 VPN slot, not every app that embeds it can be on at the same time. We'd like to provide a mechanism for the embedded version to delegate to a dedicated FIPS app if present.

FIPS

Aside from the mobile support I worked on getting the physical auto-mesh where you can chuck a router in the corner and it just starts meshing with other routers around.

I added this 802.11s mesh backhaul support to OpenWRT which enables the routers to send ethernet packets without an explicit access-point connection. This is a very important piece for TollGate as well as it alleviates TollGate of much of the decision making of who to connect to.

As mentioned in the mobile section, working with the physical mesh uncovered some issues around multi-transport peers not being supported (yet). This issue also occurred here as we might peer over wifi AND have a cable plugged in at the same time. It would cause constant flapping (=downtime). fips#167 (open) addresses that.

Another small thing on the OpenWRT side was to add an open "!FIPS" SSID that allows clients to roam around any AP with this name and auto-peer with it's FIPS node. This is especially useful for phones that may be on the move all the time, they will then auto-connect to that AP and be able to reach the greater FIPS mesh. I think this is really exciting because I think you can achieve cellular(5G)-like roaming this way.

FIPS as plumbing for Tollgate

As mentioned earlier, TollGate can be applied in more areas than just data, but here I want to talk about the 2 cases where it is applied to data.

Over the past months it became clear that TollGate as we've approached it so far hit too much complexity in the networking stack. The lack of identity and the forced IP tree-structure introduce a lot of complexity. Precisely the issues that led to FIPS, and now that it's there and the native transports for FIPS (ethernet, BLE) are becoming more usable it's the right moment to start using FIPS as the foundation.

This also means the nature of the payments changes. Instead of being one-directional (child pays parent), it becomes bidirectional: you pay for data I forward to you, and vice versa. A TollGate on FIPS has many peers and you don't know where the traffic will come from or go to, therefore you need to maintain communication and payment channels with each of them, simultaneously.

Since the mint will now live on each TollGate itself, you can always reach it during a session. Acquiring a peer's byte-tokens may still require connection to a mint like minibits of course, but that's now an interaction that can be solved outside of the TollGate spec.

A second (more scalable) initial use-case

Another use-case that I think will scale more on the short-term is that of IP exit-nodes, aka VPN's. A FIPS mesh will not have IP's, only gateways that are connected both to the mesh AND to the IP network can provide you with access to the wider internet.

This can be your own device at home, OR it can be a VPN provider which can use the TollGate protocol to charge for bandwidth. I stream sats to them, they open the (Toll)gate for me. I think this is a more immediate value and less complexity than physical router deployments.

I think this can be a great way to get more people to deploy TollGate and gather feedback that we can use in the physical TollGates. Any feedback on this topic is welcome.

Myco - Organic propagation of apps & data

I started to work on Myco for 2 reasons. To bring FIPS to mobile, and to get a point across about the new paradigm I believe we should be following with nostr. We can have fully functioning, high-speed networks, even if 'the internet' is down. I wrote Pillars of Propagation to explain what I mean, but I thought this vision would be better served by an example, which became Myco.

The point was to utilize Nostr + Blossom in a way that assumes only local, organic propagation, meaning zero central servers. And we can use that mechanism to not only transport relevant content that we produce with Nostr-based apps. but also transport the apps themselves. Completely removing our reliance on an active outgoing internet connection whatsoever. The combination here is important, it must be Nostr + Blossom + FIPS, take away one and the model won't work smoothly enough to make a difference.

In short, with the app you can bump phones (NFC) to share an app, which is an nsite or napplet. Then in turn that app can use the mesh in order to send out a nostr event, replicating to several hops away.

As an example app I built Bitchat and a disaster-response app (ICS). The nostr events get sent to people you bumped phones with and they forward it a couple more hops to their connections. Same for subscriptions. This makes it so that anything relevant gets seen and re-broadcast through the mesh organically. You benefit from the FIPS mesh, even when part of the mesh does NOT have Myco. And you benefit from Myco users that forward your Nostr events, even if they don't use this Bitchat or disaster-response app.

I recently added Napplet support. link

Talks & Events

I have attended a few events and done a couple podcasts over the summer.

Podcasts

I went on the Open markets podcast to talk about FIPS and some of its potential use-cases. link. And recently had a chat with Gigi about many of the topics in this report.

Freedom tech summit & BTC Prague

In June I was invited to speak about FIPS at the Freedom Tech Summit in Prague. I gave a talk about the Pillars of Propagation and a workshop on how to set up FIPS on your computer.

FIPS received a lot of interest during both conferences which I take as a good signal we're solving a real problem.

Sovereign Engineering SEC-08

Soveng saw a big boom in development around napplets and it really demonstrated its powers. It's like magic to be able to generate an app within 5 min, that then works across all platforms, and is not dependent on any compilation, or installation effort from the end user.

We also deployed a real FIPS mesh between routers using the 802.11s backhaul, this is a special mesh-mode supported by most modern routers. What's really interesting now is how FIPS by nature is SOOO good at bridging all transports. Because Android has only wifi-aware and wifi-direct but not this 802.11s mode. It can't naturally jump. But a phone that is wifi-connected (access-point) to a router CAN bridge this. Fusing the two different transports together. This is a really powerful characteristic and should not be underestimated.

Anyway, this real mesh was made by putting a massive antenna-dish up on the highest floor of the building we worked at, directed at one of the participant's apartments, creating a direct connection to their nodes. And we were able to connect to their apartment, solely over ethernet, with decent ping-times.

Another experiment I've done during SEC is the remote LUKS decryption of machines. For security of data at rest, people use LUKS, which encrypts an entire server's filesystem, and to decrypt it, the machine boots a stripped-down version of linux with almost nothing in it. By adding FIPS to it, we can ssh in over fips, without any accounts and enter the password remotely. This is something that can be quite a hassle to set up with something like TailScale, which requires logins etc.

Other than installing FIPS, there is no config required. Adding a new server could be nothing more than plugging in the cable.

I worked on a NixOS version: #1 & #2

Moving forward

TollGate

In the coming months I will focus my attention back to TollGate and work on implementing the new design and thoroughly testing it.

I want to have actual deployments for FIPS exit nodes up and running, preferably by other people than myself. As I think that will provide good feedback on the design and implementation.

It is now just a matter of putting my head down and working out the software.

FIPS

I will continue to work on FIPS the way I have been. My main focus there are the Android and OpenWRT deployment targets. This includes continuing work on multi-transport peers, bridging more transports and working on stability in environments with many (physically) moving nodes.

Johnathan is in the process of formalising the v2 specification as an RFC which I also read and provide feedback on. V2 will solve some fundamental issues that cannot be solved in the current V1 version of FIPS. Most notably: scaling from the current maximum of ~1600 nodes to about 4 million, application (pub)keys instead of a single node pubkey, and signed paths to root (Spanning Tree).

This will undoubtedly create more work on the integration/embedding side which I'll work on.

Myco

I will continue to maintain Myco as a testbed for both FIPS and as a Napplet Runtime for mobile. Planned features:

Account support, login using nsec/amber to use Napplets with your own npub

Add more demo Napplets that use mesh and create skills/tutorials on how to make them.

Reducing

“What is the most important thing you could be working on in the world right now? And if you're not working on that, why aren't you?”
― Aaron Swartz

Because I see that TollGate and FIPS are the most important thing I could be working on, I will reduce the time I spend on things that are less impactful.

I will not actively work on Loom, SugarDaddy and NoDNS anymore. I will happily consult with anyone that's interested on picking up those projects.

I personally feel that the last 1.5 years have been the discovery phase of the pieces of technology we need to truly decentralize our digital life. Now I think I have all the pieces, and it's time to pick the most important ones and work with those.

TL;DR; PRs/Code

Here's a bunch of the most relevant PRs over the past few months.

OpenTollGate/tollgate-rs (branch)

The greenfield voucher node lives on a branch. Or go directly to the Documentation.

Date Branch State What

2026-08-07 feat/greenfield-voucher-node unmerged Voucher-node implementation of the new TollGate design (58 commits, e4c72277)

jmcorgan/fips (13)

Features (8)

Date PR State Title

2026-06-17 #115 merged ci: bump Node 20 actions to Node 24 majors

2026-06-17 #116 merged packaging(openwrt): publish checksums-openwrt.txt + bump Node 20 actions

2026-06-20 #118 merged OpenWrt: SDK-free .apk packaging (OpenWrt 25+) + control-socket fix

2026-07-02 #123 merged feat(openwrt): 802.11s open-mesh backhaul support

2026-07-08 #126 merged feat(openwrt): open !FIPS access SSID layer

2026-07-14 #127 merged feat: Android-ready core — target_os gating, app-owned TUN

2026-08-10 #136 merged feat(node): publish the DNS responder's bound address for embedders

2026-09-07 #147 merged feat(transport): bind and rebind network interfaces dynamically

Bugfixes (5)

Date PR State Title

2026-06-08 #109 merged packaging: macOS resolver must point at ::1, not 127.0.0.1

2026-06-17 #114 merged fix(tun): loop back self-addressed packets for local delivery

2026-06-18 #117 merged fix(tun): complete L4 checksum on hairpinned self-traffic (macOS)

2026-06-25 #121 merged packaging(openwrt): default .apk WAN port to DSA name 'wan'

2026-08-31 #141 merged fix(lookup): accept our own lookup response instead of relaying it away

jmcorgan/fips-initramfs (2)

Features (2)

Date PR State Title

2026-09-08 #1 open Docs: state the design as a contract a port can be checked against

2026-09-08 #2 open Add a NixOS implementation beside the .deb

OpenTollGate/tollgate-module-basic-go (3)

Features (2)

Date PR State Title

2026-06-02 #157 merged ci: expand test matrix to cover standalone-buildable modules

2026-07-03 #184 merged docs: v0.5.0 release prep

Bugfixes (1)

Date PR State Title

2026-07-03 #183 merged ci: build-package fixes (psbt slash + x86_64 apk variant)

Origami74/myco (32)

Features (23)

Date PR State Title

2026-06-30 #1 merged chore: format the workspace and gate cargo fmt in CI

2026-06-30 #2 merged Bottom-sheet menus for Circle members + share/add, with NFC sharing

2026-06-30 #3 merged Settings sub-pages with storage controls, plus Circle Nearby polish

2026-06-30 #4 merged Add a peer speedtest to the Dev menu

2026-07-14 #10 merged feat: Wi-Fi Aware bulk-lane transport + adaptive peer speedtest

2026-07-14 #11 merged chore: bump embedded relay/Blossom ports to 4870 / 24243

2026-07-14 #12 merged feat(android): Discover as an icon grid with a Suggested apps row

2026-07-19 #16 merged feat(android): Wi-Fi AP lane — discover LAN fips nodes over mDNS, peer over UDP

2026-07-29 #20 merged Mesh names (<npub>.fips) system-wide, exit-node mode, and Wi-Fi AP lane fixes

2026-07-29 #21 merged Reach Circle members at any hop count, and address peers by npub

2026-07-29 #22 merged Circle, Discover and pairing UX — and stop the AP lane evicting its own session

2026-08-06 #24 merged First-run intro: grow the mark, dive through the pupil into the app

2026-08-07 #25 merged Phase 01: Make Peering Observable — plus early PEER-05/UX-01/PEER-03 fixes

2026-08-09 #26 merged Deep links: myco://app/<host>/<path>, and an app that arrives before it opens

2026-08-18 #29 merged Status panel behind the pill, and a device name that is actually yours

2026-08-19 #31 merged Swappable relay and blob store, and Wi-Fi Aware links that hold

2026-08-21 #35 merged feat(aware): carry several Wi-Fi Aware peers with a chipset-sized socket pool

2026-09-04 #42 merged chore(fips): build against fips master

2026-09-04 #43 closed feat(android): send a file from a Circle contact's sheet

2026-09-07 #48 merged build: add a Nix flake for the toolchain

2026-09-14 #50 merged Multi-path peer view, Network discovery switch, and tunnel/LAN/Aware reliability fixes

2026-09-14 #51 merged ci: gate clippy; exclude reference/fips from the workspace

2026-09-16 #52 merged Napplets: a NIP-5D runtime beside nsites

Bugfixes (9)

Date PR State Title

2026-06-30 #5 merged fix(ble): make the L2CAP radio a transparent byte pipe for the core's FMP reframer

2026-07-10 #6 merged fix(myco-core): persistent bidirectional peer-relay connection

2026-07-10 #7 merged fix(android): recover BLE scanning after a scan failure

2026-07-10 #8 merged fix(myco-core): fan chat to the whole Circle, not just direct neighbours

2026-07-10 #9 merged fix: keepwarm Circle relay links + resubscribe on reconnect

2026-07-23 #17 merged Background battery fixes + relay-connection resilience

2026-07-24 #18 merged Usability: crash-proof Wi-Fi Aware permissions, radio/VPN warnings, status-pill controls

2026-08-18 #27 merged Rebuild on current FIPS, and make the radios actually hold

2026-09-04 #44 merged fix: stop calling a peer "Wi-Fi Aware" when Aware is neither carrying it nor running

OpenTollGate/tollgate-os (1)

Features (1)

Date PR State Title

2026-07-03 #26 merged ci: mirror firmware to the same blossom set as basic-go

SatsAndSports/cashu_spilman_channels (1)

Features (1)

Date PR State Title

2026-08-01 #2 merged Let channel parameters round-trip a custom currency unit

fiatjaf/pyramid (2)

Bugfixes (2)

Date PR State Title

2026-09-05 #80 merged (bugfix): allow 63-octet domain labels (<npub>.<tld>)

2026-09-06 #81 merged http scheme: split the port off before matching, and recognise .fips

Date	Branch	State	What
2026-08-07	feat/greenfield-voucher-node	unmerged	Voucher-node implementation of the new TollGate design (58 commits, `e4c72277`)

Date	PR	State	Title
2026-06-17	#115	merged	ci: bump Node 20 actions to Node 24 majors
2026-06-17	#116	merged	packaging(openwrt): publish checksums-openwrt.txt + bump Node 20 actions
2026-06-20	#118	merged	OpenWrt: SDK-free .apk packaging (OpenWrt 25+) + control-socket fix
2026-07-02	#123	merged	feat(openwrt): 802.11s open-mesh backhaul support
2026-07-08	#126	merged	feat(openwrt): open !FIPS access SSID layer
2026-07-14	#127	merged	feat: Android-ready core — target_os gating, app-owned TUN
2026-08-10	#136	merged	feat(node): publish the DNS responder's bound address for embedders
2026-09-07	#147	merged	feat(transport): bind and rebind network interfaces dynamically

Date	PR	State	Title
2026-06-08	#109	merged	packaging: macOS resolver must point at ::1, not 127.0.0.1
2026-06-17	#114	merged	fix(tun): loop back self-addressed packets for local delivery
2026-06-18	#117	merged	fix(tun): complete L4 checksum on hairpinned self-traffic (macOS)
2026-06-25	#121	merged	packaging(openwrt): default .apk WAN port to DSA name 'wan'
2026-08-31	#141	merged	fix(lookup): accept our own lookup response instead of relaying it away

Date	PR	State	Title
2026-09-08	#1	open	Docs: state the design as a contract a port can be checked against
2026-09-08	#2	open	Add a NixOS implementation beside the .deb

Date	PR	State	Title
2026-06-02	#157	merged	ci: expand test matrix to cover standalone-buildable modules
2026-07-03	#184	merged	docs: v0.5.0 release prep

Date	PR	State	Title
2026-07-03	#183	merged	ci: build-package fixes (psbt slash + x86_64 apk variant)

Date	PR	State	Title
2026-06-30	#1	merged	chore: format the workspace and gate cargo fmt in CI
2026-06-30	#2	merged	Bottom-sheet menus for Circle members + share/add, with NFC sharing
2026-06-30	#3	merged	Settings sub-pages with storage controls, plus Circle Nearby polish
2026-06-30	#4	merged	Add a peer speedtest to the Dev menu
2026-07-14	#10	merged	feat: Wi-Fi Aware bulk-lane transport + adaptive peer speedtest
2026-07-14	#11	merged	chore: bump embedded relay/Blossom ports to 4870 / 24243
2026-07-14	#12	merged	feat(android): Discover as an icon grid with a Suggested apps row
2026-07-19	#16	merged	feat(android): Wi-Fi AP lane — discover LAN fips nodes over mDNS, peer over UDP
2026-07-29	#20	merged	Mesh names (`<npub>.fips`) system-wide, exit-node mode, and Wi-Fi AP lane fixes
2026-07-29	#21	merged	Reach Circle members at any hop count, and address peers by npub
2026-07-29	#22	merged	Circle, Discover and pairing UX — and stop the AP lane evicting its own session
2026-08-06	#24	merged	First-run intro: grow the mark, dive through the pupil into the app
2026-08-07	#25	merged	Phase 01: Make Peering Observable — plus early PEER-05/UX-01/PEER-03 fixes
2026-08-09	#26	merged	Deep links: myco://app/<host>/<path>, and an app that arrives before it opens
2026-08-18	#29	merged	Status panel behind the pill, and a device name that is actually yours
2026-08-19	#31	merged	Swappable relay and blob store, and Wi-Fi Aware links that hold
2026-08-21	#35	merged	feat(aware): carry several Wi-Fi Aware peers with a chipset-sized socket pool
2026-09-04	#42	merged	chore(fips): build against fips master
2026-09-04	#43	closed	feat(android): send a file from a Circle contact's sheet
2026-09-07	#48	merged	build: add a Nix flake for the toolchain
2026-09-14	#50	merged	Multi-path peer view, Network discovery switch, and tunnel/LAN/Aware reliability fixes
2026-09-14	#51	merged	ci: gate clippy; exclude reference/fips from the workspace
2026-09-16	#52	merged	Napplets: a NIP-5D runtime beside nsites

Date	PR	State	Title
2026-06-30	#5	merged	fix(ble): make the L2CAP radio a transparent byte pipe for the core's FMP reframer
2026-07-10	#6	merged	fix(myco-core): persistent bidirectional peer-relay connection
2026-07-10	#7	merged	fix(android): recover BLE scanning after a scan failure
2026-07-10	#8	merged	fix(myco-core): fan chat to the whole Circle, not just direct neighbours
2026-07-10	#9	merged	fix: keepwarm Circle relay links + resubscribe on reconnect
2026-07-23	#17	merged	Background battery fixes + relay-connection resilience
2026-07-24	#18	merged	Usability: crash-proof Wi-Fi Aware permissions, radio/VPN warnings, status-pill controls
2026-08-18	#27	merged	Rebuild on current FIPS, and make the radios actually hold
2026-09-04	#44	merged	fix: stop calling a peer "Wi-Fi Aware" when Aware is neither carrying it nor running

Date	PR	State	Title
2026-07-03	#26	merged	ci: mirror firmware to the same blossom set as basic-go

Date	PR	State	Title
2026-08-01	#2	merged	Let channel parameters round-trip a custom currency unit

Date	PR	State	Title
2026-09-05	#80	merged	(bugfix): allow 63-octet domain labels (<npub>.<tld>)
2026-09-06	#81	merged	http scheme: split the port off before matching, and recognise .fips

I should be zappable now thanks to @nprofile…da04 and his ...

2026-09-23T15:47:43Z

I should be zappable now thanks to fmar (nprofile…da04) and his https://github.com/frnandu/rustress

Damn, forgot about the link :D ...

2026-09-23T15:19:36Z

Damn, forgot about the link :D
https://npub1ekuzl82ewlx7s9xdz9uq6lmadt9slv8n9m47z5fxkp7k57vpfvysuhxzvu.fips:8080/

quoting nevent1q…nhlu
Same address?

A more permanent instance of Bitblik over FIPS is up. It's on ...

2026-09-23T14:17:02Z

A more permanent instance of Bitblik over FIPS is up. It's on a fucking Raspberry, so I cannot vouch for its stability. Let me know if it's reachable!

quoting
nevent1q…qsew
Very cool.
Do let us know when running 24/7
nevent1q…e9d4

Decentralized commerce needs decentralized infrastructure. A time ...

2026-09-20T11:38:08Z

Decentralized commerce needs decentralized infrastructure. A time will come when Bitcoiners will be forced to build in places that are harder to reach for the state apparatus, away from censorship, ID checks and takedown notices.

A central piece in all of that transitioning away from traditional internet domains that can be shut down easily. Luckily, achieving this has never been easier and it will take years before the machine catches up with us.

As a little demo, you can check out a BitBlik (nprofile…c3df) instance served over fips (nprofile…nsnk) from my personal PC: https://npub1d97zuys7eg0ehdsnrf8t3cs2xy0xfvrj4ukrx64hdrrda6r76nfsc0n7qr.fips:8080/

No domains, no static ip, no rented hosting, just a goddamn computer standing under my desk. To reach it, ask your clanker how to set up FIPS (from this repo: https://github.com/jmcorgan/fips) service and .fips name resolution on your machine. After it is done, you can just use your standard internet browser. And if you wanna reach it from an Android phone, just grab fips2go (https://zapstore.dev/apps/org.fips.android) from Zapstore, add your internet browser to the list of FIPS-enabled apps and voila!

Expect intermittent availability, from time to time I step away from the computer and shut it down :)

I figured out that it's a bug in lnSwitchboard, gotta wait ...

2026-09-19T14:08:09Z

In reply to nevent1q…m6t9
_________________________

I figured out that it's a bug in lnSwitchboard, gotta wait for a fix.

Holy fuck, I sometimes forget how deranged people can be. ...

2026-09-18T18:01:51Z

In reply to nevent1q…j8hg
_________________________

Holy fuck, I sometimes forget how deranged people can be. Luckily, I have my neighbor next door who keeps my memory fresh. And now this subreddit.

To jest skomplikowana sprawa, bo bawię się w self hosting, co ...

2026-09-18T16:47:49Z

In reply to nevent1q…x0j0
_________________________

To jest skomplikowana sprawa, bo bawię się w self hosting, co nie jest najlepszym pomysłem, jeśli chcesz, żeby coś działało. Ale za to jestem kurwa suwerennym indywiduum, heh.

Dobra, zdaje się że jeszcze Amethystowi coś nie pasuje. Z ...

2026-09-18T15:51:07Z

In reply to nevent1q…57kg
_________________________

Dobra, zdaje się że jeszcze Amethystowi coś nie pasuje. Z innych klientów już działa. Debuguję dalej. Ależ to jest gówno.

Shit, już byłem pewien że to naprawiłem. Amethyst?

2026-09-18T15:41:41Z

In reply to nevent1q…lqsm
_________________________

Shit, już byłem pewien że to naprawiłem. Amethyst?

The future is meshed. #naddr1qq…zc7r

2026-09-18T14:10:30Z

The future is meshed.

quoting
naddr1qq…zc7r

When the internet goes down, a lot goes down with it. All communication grinds to a halt. And communication entails more than WhatsApp, TikTok and other brainrot-catalyst apps. It is about getting in the new order for tomorrow's groceries that will await you fresh 'n green. It's about getting the truck-driver at the right loading-dock to pick up that load, and give him the right delivery address. It's his navigation to even get there. It's the Fuel-pump payment terminal to get him the gas to do it. And (nowadays), it's your good night's sleep.

F*cked would be an understatement to say the least. Now imagine that when the internet goes down, we simply...

...wouldn't care?

What if we can live in a way where we wouldn't even notice that the internet is down. That's what I want to talk about with you today.

The first two pillars

I want you to think about the physical location of data. Now what does that mean? I mean the physical location where a copy of data exists.

On the normal internet, this data is in a central data centre somewhere far away. When you visit a site, you pick up that data, it gets displayed on your browser, and discarded when you close the page.

This is a very wasteful and fragile model. If you visit the same page, and try to find the same information again, the whole circus starts all over, to once again throw away the data at the end. This means that you're incredibly dependent on all parts remaining accessible. Which we know isn't always the case.

Compare this to processes in nature, like a tree that gathers nutrients. A tree doesn't send out something to go to the roots and pick up a nutrient, go back, and deliver the nutrient. Go out and fetch, go out and fetch, and so on... Instead, a tree has liquids that flow up and bring along nutrients as they are needed, after which it travels down with products like sugars that go back into the soil. It's a continuous flow, with no start and no end.

This is exactly the model that's possible with Nostr and Blossom. Because the data integrity can be validated from the data itself, the data can flow freely. And since it's data, these flows can be filtered and duplicated at any point.

If that sounds a bit woowoo, let me give you an example: I go to a friend's profile on a Nostr social app and I load their posts, including the images, which are Blossom files. At that very moment I tap into an existing flow of data somewhere on a far-away relay & blossom server and filter it to my liking. But unlike the go-and-fetch model, the data is now physically replicated on my device. This means that the connection to that far-away relay is never again needed for this same information to propagate.

Let me repeat that: After receiving data from a far-away relay, that same connection is NEVER AGAIN needed for the same information to propagate.

Now that this data exists in my local community, ANYONE in need of this information can retrieve it from me rather than the far-away place.

THIS is what makes Nostr + Blossom so incredibly potent. Though few seem to realize it.

The monetary pillars

Because Nostr/Blossom are free of any interpretation of the data, we can transport anything with the model described above. AKA: relays don't care if it's a social media post or some event that makes a doorbell ring.

So, for example, this model can be used for propagating websites with nsite as well. Now anyone in my community can view a website that I've already collected from the other side of the world once.

I want to sketch a scenario here:

Let's say the internet is down and this (nsite) website happens to be a webshop for a local bakery. I've visited the webshop before, and just by doing that this data has already been propagated to my devices.

This means that anyone in my community can get this data from me, rather than from that connection to far away that's now unavailable. My neighbour who's a carpenter now loads the site and products by getting it from me, selects what he needs and goes to check-out.

Now we're stuck with a problem, because we can't pay without an internet connection. Except... we actually can. With Bitcoin Cashu mints. And not with fancy token-locking, but because our community has its own Cashu mint that continues to be accessible within the bounds of our local network.

Yes, we can't make bitcoin payments OUTSIDE our community as the internet went down, but we can definitely keep circulating the value that is already present within the community. Which accounts for MOST economic activity that we need to survive.

My neighbour can order his bread for later pick-up. I can pay him for that job he did for me the other day from the sats I have of this local mint.

Then, whenever the wider internet returns, we all pay in/out of the mint as we desire. I might top-up because I net spent and the bakery might cash out over lightning to pay their supplier for next week's flour.

Foundation for propagation

But, one huge problem remains... The internet's architecture doesn't support this organic flow of information. It is structured in a way that is too rigid to support a flow so organic, between parts that move around in physical space. The foundations are rattling and about to crumble...

It's not strange that it evolved this way, the great minds behind TCP/IP and adjacent protocols couldn't have designed for this world of flowing, self-validating data, as the tools we have at our disposal now simply didn't exist yet.

But we can't keep using a hammer now that we have screws. The tools may look similar and have similar goals. Yet, they're fundamentally different.

Many projects have come and gone that tried to create this new foundation, but never seemed to put all the parts in at once. Focussing on the reinforced concrete, but built on unstable ground. Or put in the pile foundation, but neglect the reinforced concrete. All these genuinely want to build a beautiful structure, but you need to get the touch-points between earth, foundation and structure exactly right.

In internet-land that means that we can't throw away 4+ decades of TCP/IP libraries for a new protocol. We have to be 100% compatible with the existing IP stack. You can't build a protocol and rebuild everything from the ping application up to Minecraft.

At the same time, we can't build on top of IP itself either, inheriting all its limitations. But, we won't get anywhere without fully supporting it either. It's a fine line and hard to get right, but I think FIPS has a good shot at making it work.

The harmonious hand-off

The key is in the touch points on top, where applications interface with the networking stack. And the earth, where the networking stack interfaces with the physical world.

Structure & foundation

This is the intersection where the pillars rest on their foundation. We can't require the whole structure to be designed around the foundation, it should just expect a sturdy footing.

Cashu mints, Nostr relays and Blossom servers currently rely on DNS as their de-facto identity, it's not truly theirs. An npub is. However, the system already exists, current tools expect a domain name. FIPS won't fight this fact, but interoperates with it. Npubs as domain names cover this gap, owning their identity, zero code changes.

Not forever, but as an in-road, possibly for decades, but it must be in place to invite the transition to Free Internetworking.

Foundation & Earth

The foundation & earth connection is the interface between FIPS and physical transport, which can be any medium and should be many of them at once. A good spider-web is attached at many places, a leaf, a piece of bark and a branch. Any of which can fail for its own reasons, amounting to a mere nuisance when it happens. No catastrophic failures like an interrupted network today.

In practical terms this means a network where fiber, Bluetooth and Serial all become your carriers, regardless of the application, or type of data. No application should be bothered with how Bluetooth transport works. And no Bluetooth transport implementation should care what application is using its link.

In closing

We're in a huge paradigm shift of data propagation, in a way we've never done, on a scale we've never seen. And with that scale I mean a scale so small that we tend to overlook it. A resilient internet is not one with huge backbone gateways, hyperscale compute clusters and fiber lines. It's a messy interplay of small relays, mints and Blossom blobs hopping over crappy links in all directions, right to where it needs to be. It is a network that persists through power-cuts, human error and shutdowns. It's a network where Bluetooth, USB cables and MicroSD cards become your carriers. Data will flow no matter the circumstances, or the scale. You can dam a river, but not the rain.

-Arjen

The meshed internet:

https://i.nostr.build/piKlq2vF2eo2Z5M8X0An75.jpg Browsing FIPS ...

2026-09-16T22:56:41Z

In reply to nevent1q…8nav
_________________________

Browsing FIPS sites from a fucking Chrome. This is magic.

Sound intriguing, but I'm afraid to touch this shit 🙃

2026-09-16T05:08:55Z

In reply to nevent1q…4g52
_________________________

Sound intriguing, but I'm afraid to touch this shit 🙃

Currently using https://github.com/RyleaStark/lnSwitchboard on an ...

2026-09-16T05:06:26Z

In reply to nevent1q…tsfh
_________________________

Currently using https://github.com/RyleaStark/lnSwitchboard on an Umbrel. Most of my problems were caused by reverse proxy setup and not lnurl itself.

Trying out fips2go by @npub1ypt…a52w. Is there any public index ...

2026-09-15T19:52:36Z

Trying out fips2go by fr34aky (npub1ypt…a52w). Is there any public index of fips (npub1y0g…00ly) sites that I could visit?

Today I learned that self-hosting a lightning address is a bitch. ...

2026-09-15T19:41:40Z

Today I learned that self-hosting a lightning address is a bitch. Should be working now, but boy why am I doing this to myself?

Are you aware of any relay tools that would allow the operators ...

2026-09-14T12:18:33Z

In reply to nevent1q…p3tf
_________________________

Are you aware of any relay tools that would allow the operators to analyze event kind stats?

Nie mom pojęcia o co może chodzić.

2026-09-14T06:15:45Z

In reply to nevent1q…csqd
_________________________

Nie mom pojęcia o co może chodzić.

Listening to Breedlove talking about harmony in music, I felt the ...

2026-09-13T10:10:41Z

Listening to Breedlove talking about harmony in music, I felt the need to set something straight. On X, unfortunately. I thought I should also post it here.

A steak of course. 1. Grab fatty ribeye 2. Put it on a fucking ...

2026-09-12T19:39:56Z

In reply to nevent1q…ee6q
_________________________

A steak of course.

1. Grab fatty ribeye
2. Put it on a fucking hot frying pan
3. Fry medium rare
4. Salt to taste
5. Add a fuckton of butter

10 minutes, best meal ever. I pity all those wretches who have to spend hours to make their food edible.

Cool idea! Do you have any info on cost-effectiveness (savings vs ...

2026-09-11T13:14:41Z

In reply to nevent1q…n259
_________________________

Cool idea! Do you have any info on cost-effectiveness (savings vs investment made)?

Haha, understandable. He's a great vocalist, but has some ...

2026-09-06T15:42:16Z

In reply to nevent1q…wrfn
_________________________

Haha, understandable. He's a great vocalist, but has some very distinct mannerisms that not everyone will like.

I can't believe I haven't shared anything by Leprous yet. ...

2026-09-06T13:43:22Z

I can't believe I haven't shared anything by Leprous yet. Definitely one of the most interesting prog (or however you'd classify it) bands out there. What really buys me are those rhythmic subtleties, syncopations and accents in unusual places that make this music extremely hard to perform, but in a way that's not obvious to an untrained ear on the first listen. And if you get the opportunity to see them live, I definitely recommend it.

https://tidal.com/track/75020188/u

#music #musicstr #tunestr

It's a badly kept secret - you just need to listen to 5 ...

2026-09-05T19:31:51Z

In reply to nevent1q…rfgw
_________________________

It's a badly kept secret - you just need to listen to 5 seconds of the drums to instantly recognize that it's him.

@npub1jr8…wwnw Warsaw. We're family friendly, as you can ...

2026-09-05T11:42:16Z

BitcoinWalk (npub1jr8…wwnw) Warsaw. We're family friendly, as you can see.

Wow, you Slovaks are fast. Here in Poland, still absolutely ...

2026-09-04T12:16:53Z

In reply to nevent1q…shct
_________________________

Wow, you Slovaks are fast. Here in Poland, still absolutely nobody outside of our Bitcoin circles has noticed.

Tomorrow we walk again. @nprofile…j4mx Warsaw. Starting 11:30 ...

2026-09-04T08:48:17Z

Tomorrow we walk again. BitcoinWalk (nprofile…j4mx) Warsaw. Starting 11:30 at the usual spot. https://maps.app.goo.gl/yedzYQTcnJWRrHLw7?g_st=ac

Anything Louis Cole does is dope (or at least interesting). My ...

2026-09-04T06:58:02Z

Anything Louis Cole does is dope (or at least interesting). My fav is definitely Clown Core (viewer discretion is advised):
https://www.bitchute.com/video/GTOe7ewclPkR/

quoting nevent1q…qgp7
stop, I want your impression of after first 70 seconds

https://www.youtube.com/watch?v=_AtSzBrW6mo

So called "white voice" is a type of folk singing common ...

2026-08-30T15:31:25Z

So called "white voice" is a type of folk singing common to all Slavic cultures (although it can be found all across the globe) and is characterized by a very strong, forward-placed resonance, producing a distinct "buzz". The buzz is the raw sound of fully connected vocal folds, not attenuated by any unnecessary tension in the vocal tract.

Anglophone sources speak of this type of singing as a "controlled shout", but this is a huge misconception, in my opinion. I would call it more of a call than a shout. You can hear it in our example below - even quiet, delicate sounds possess the same consistent quality. Too me, it's the most pure type of singing - no mannerisms, no hiding your shame behind various stylizations, no trying to sound impressive.

From my experience, people are either mesmerised by this song or (rarely) find the voice too harsh, too piercing. I wonder how you guys will react.

https://tidal.com/track/240158095/u

#music #musicstr #tunestr

@npub1jr8…wwnw Warsaw. The rain couldn't stop us. Join us ...

2026-08-29T11:50:45Z

BitcoinWalk (npub1jr8…wwnw) Warsaw. The rain couldn't stop us. Join us #everySat

You are both. And the priest. I guess.

2026-08-29T09:17:54Z

In reply to nevent1q…8kr5
_________________________

You are both. And the priest. I guess.

Tomorrow we walk. @nprofile…j4mx Warsaw. Starting 11:30 at the ...

2026-08-28T07:17:26Z

Tomorrow we walk. BitcoinWalk (nprofile…j4mx) Warsaw. Starting 11:30 at the usual spot.
https://maps.app.goo.gl/yedzYQTcnJWRrHLw7?g_st=ac

Every day is a steak for breakfast kinda day.

2026-08-22T18:01:06Z

In reply to nevent1q…0j8s
_________________________

Every day is a steak for breakfast kinda day.

How would they increase the rates without blowing up the interest ...

2026-08-22T13:28:25Z

In reply to nevent1q…jplh
_________________________

How would they increase the rates without blowing up the interest on govt debt? They would have to default on the bonds (at least partially). Not gonna happen.

A new discovery. Just listen to those brilliant transitions ...

2026-08-16T15:54:23Z

A new discovery. Just listen to those brilliant transitions between vocal registers and vowel placements. A thing of beauty.

https://tidal.com/track/324501710/u

#music #musicstr #tunestr

Yep, getting there!

2026-08-15T09:48:00Z

In reply to nevent1q…ktej
_________________________

Yep, getting there!

The ending part (from 03:53) is awesome. Goosebumps! Something ...

2026-08-15T08:52:39Z

In reply to nevent1q…8hja
_________________________

The ending part (from 03:53) is awesome. Goosebumps! Something about the timbres of all the layers coming together in a way that tickles my brain.

A lecture by my favorite biologist, Michael Levin, about his ...

2026-08-14T08:44:47Z

A lecture by my favorite biologist, Michael Levin, about his (cybernetic) theory of aging.

The ship of Theseus is not really the physical ship, but the plan of the ship that exists in the minds of the workers. It starts to age and degrade when the workers forget the plan or drop the goal of maintaining the ship.

Lifespan (and healthspan) extension could happen by reminding your tissues about their purpose.

https://www.youtube.com/watch?v=EeKnxXPy3Xs

Exchanges might not exist in a hyperbitcoinized world, but there ...

2026-08-13T19:03:09Z

In reply to nevent1q…mxh4
_________________________

Exchanges might not exist in a hyperbitcoinized world, but there will still be "economic nodes". To scale bitcoin to a couple billion users, we'll need a banking system (best if a free banking system) built on top of it.

How about taking cashu payments and running the thing through ...

2026-08-13T18:55:01Z

In reply to nevent1q…4k7n
_________________________

How about taking cashu payments and running the thing through routstr (nprofile…6nzx)?

Haha, I sometimes get the thought that it would be cool to make ...

2026-08-13T18:49:32Z

In reply to nevent1q…9p0w
_________________________

Haha, I sometimes get the thought that it would be cool to make music for a living, but in reality I just like to freely explore it, without the "for a living" stuff :D

I would die if I had to go on tour (or finish a project for once, for that matter).

I highly recommend looking up the original Greek term ...

2026-08-11T20:37:20Z

In reply to nevent1q…gqxq
_________________________

I highly recommend looking up the original Greek term "metanoia". It has strikingly different connotations than "penance" and much better captures the meaning of repentance in traditional Christianity. Overall, I think that Orthodox Christian thought (especially as represented by their monastic tradition) is much closer to truth than your typicall Western theology, portraying sin much less in terms of guilt and punishment and much more in terms of disease and healing.

Tried it, not compatible :(

2026-08-04T07:36:53Z

In reply to nevent1q…hf8u
_________________________

Tried it, not compatible :(

It's an add-on. Search for "note taking" on ...

2026-08-04T07:33:07Z

In reply to nevent1q…2jj3
_________________________

It's an add-on. Search for "note taking" on https://github.com/77elements/noornote/

The repo also lists NIP-33, so it might be compatible after all.

Is it interoperable with NoorNote's notes?

2026-08-04T06:08:48Z

In reply to nevent1q…sj4z
_________________________

Is it interoperable with NoorNote's notes?

Sorry for the noise at the beginning - seems to be an artifact of ...

2026-08-01T17:06:18Z

In reply to nevent1q…ttxx
_________________________

Sorry for the noise at the beginning - seems to be an artifact of the audio normalizer.

Today I took a short break from the grind to play some sad music. ...

2026-08-01T17:05:35Z

Today I took a short break from the grind to play some sad music. One take, one mic - no time to record it properly.

This is The Weight of the World by Antimatter.

#music #musicstr #tunestr

Jest to dla mnie jeden z najciekawszych projektów w przestrzeni ...

2026-07-19T08:02:25Z

In reply to nevent1q…rkgf
_________________________

Jest to dla mnie jeden z najciekawszych projektów w przestrzeni bitcoinowo-nostrowej obecnie. Tylko tworząc efektywne i prywatne mosty fiat-Bitcoin jesteśmy w stanie dokoptowywać mniej "ideologicznie nastawionych" ludzi do naszej bitcoinowej gospodarki. Brawo dla autorów!

@npub1g53…drvk Yo! I noticed that Nostr VPN drains the battery ...

2026-06-03T03:31:16Z

Sirius (npub1g53…drvk) Yo! I noticed that Nostr VPN drains the battery like crazy on Android. Do you think it's solvable or just the way it is?

A must-watch video summarizing the work of Michael Levin: ...

2025-11-16T13:05:51Z

A must-watch video summarizing the work of Michael Levin:
https://www.youtube.com/watch?v=YoRMZhuk3lY

Highlights:
- Intelligence can be found on much lower levels of organization than what we typically believe.
- We can use tools from cognitive science and psychology to interact with tissues and even individual cells. For example, even relatively simple chemical networks can exhibit pavlovian conditioning.
- Single-cell organisms with 100% human DNA.
- Regrowing limbs.
- Conscious exploration of the morphospace (the space of possible body-forms).
- Platonic space might be real after all.