
Full recording, about 85 min. Plays from youtube-nocookie.com. Watch on YouTube
Jump to a chapter (29 chapters)
- FIPS: what it is and why it exists
- What is a mesh network? Centralized vs decentralized vs distributed
- Every node gets an identity: Nostr npubs
- Why FIPS: getting around IP and DNS
- One mesh, many links: Wi-Fi, Bluetooth, radio, LoRa
- Does FIPS still use IP? The OSI model
- Bitcoin scales in layers, like the internet
- Why VPNs and Tor are only workarounds
- IP addresses and domains need permission
- FIPS wrap-up and homework for next time
- Why we do these calls: more reviewers, more contributors
- Razor: a peer-observer case study
- Inside a node's address table (addrman)
- bnoc post: Address relay under stress
- ADDR and ADDRv2 messages explained
- Address relay for beginners (whiteboard)
- addrman is a phone book
- How this connects to peer-observer
- Addresses per ADDR message: before vs during the spam
- The attack: bogus addresses
- Why not just test every address first?
- The new and tried tables
- The puzzle: fewer new addresses during the spam
- stonepillar: hello, Floresta and the fellowship
- The Floresta repo: Rust, Utreexo, its own addrman
- Fix: anchors.json now survives a node shutdown
- Implementing Bitcoin Core's RPCs (good first issues)
- RPC authentication: why it is harder than it looks
- Wrap-up: Decoding Bitcoin and Privacy Track next week
TL;DR
- FIPS replaces IP addresses and DNS with keys you make yourself: every node's Nostr npub is its address, and messages find their way through a mesh over Wi-Fi, Bluetooth, radio or the internet.
- Decentralized is not the same as distributed. If one node going down can cut off a branch, there is still a choke point. A true mesh has many paths.
- Bitcoin nodes find each other by gossiping addresses into a phone book called addrman. In 2026 someone flooded it with fake addresses, and oddly, fewer real new addresses got in.
- Floresta is a light Rust node that runs on a Raspberry Pi or a phone. stonepillar is spending his fellowship making its RPCs match Bitcoin Core, and there are first issues waiting for you.
Mission board0 XP
Three talks. Three mini-games. One quiz.
Each game below is one big idea from the call. Finish it and its badge lights up. Pass the quiz at the end for the last one. Progress stays on this device and adds XP to your builder passport.
Highlights
1FIPS with Alex
An internet where your address is a key you make yourself. Today, to reach anyone online you need an IP address from your internet provider and a domain from a registry. Both are handed out from the top down, both can tell where you are, and both can be switched off. FIPS, the Free Internetworking Peering System, swaps them for something Bitcoiners already know: every node makes its own key pair, and its Nostr npub is its address. Nodes find each other and route messages through a self-organizing mesh, with no central server in the middle.
Alex met the creator, Jonathan, in Madeira, where Nostr developers had FIPS apps talking over Bluetooth.
Mini-game 1 · Mesh Maker✓ badge earned
Knock out a node. Who gets cut off?
A question from the call: what is the difference between decentralized and distributed? Pick a shape, then tap any node to take it offline. Try all three shapes to earn the badge.
Tap the big node in the middle first.
The answer the group landed on: in a decentralized network there are clusters, and each cluster hangs off a head node, so between two nodes there is often only one route. Lose a cluster head and a whole branch goes dark. In a distributed network every node has several ways to reach every other node, so one crash barely matters. FIPS is the distributed kind. It has no hierarchy at all: nodes compare addresses to build a spanning tree and pick a good path.
Does FIPS still use IP?
Swap one layer, keep the rest
The clever part: FIPS only replaces the addressing layer, so apps that speak IP can run on the mesh without changing anything. Moving a server onto FIPS should not need a rewrite.
Why not just use a VPN? A VPN only hops your traffic through another company’s servers. Those servers sit on a known family of IP addresses, so they are easy to spot and easy to block, and the company is one more middleman. Tor helps but has its own problems. As Alex put it, both are workarounds on an internet that was never private by design. FIPS tries to fix the root: a permissionless internet, the same idea Bitcoin brought to money.
“You generate your identity yourself, instead of an IP address you have to request from your ISP.”
Alex, on why FIPS matters
Homework from Alex: spin up a FIPS node before the next session. Next time he will demo sending messages between nodes from the terminal.
2A peer-observer case study with Razor
Learn Bitcoin Core by studying a real attack. peer-observer is a set of tools that watches the Bitcoin peer-to-peer network for attacks. There is no single starting point, so Razor’s advice is to start from real incidents and ask “how would we have spotted this?” This time: the 2026 address spam, written up on the Bitcoin Network Operations Collective forum (bnoc) as Address relay under stress.
First the basics. If nobody knows your node exists, nobody can connect to it. So nodes gossip about each other: you tell your peers “here I am” in an ADDR message, and they pass it on to their peers, and so on.
Mini-game 2 · Gossip✓ badge earned
Get D’s address all the way to A
Razor’s whiteboard: A, B, C and D sit in a line. D is new and only connected to C. Press the button to pass D’s ADDR message along.
Each node keeps a phone book of addresses (the boxes under each letter).
That phone book is addrman, the address manager in Bitcoin Core (src/addrman.h). It is simpler than a routing table: no paths, just a list of addresses you can try to connect to directly, plus who told you about each one. Here is what a few rows of a real dump look like:
Inside addrman
A phone book of peers
| Address | Port | Network | Learned from |
|---|---|---|---|
| 203.0.113.42 | 8333 | IPv4 | 89.21.7.x |
| 2001:db8::5 | 8333 | IPv6 | 89.21.7.x |
| exampl3abc….onion | 8333 | Tor | 198.51.100.9 |
Swipe to see the whole table →
Why peer-observer helps: Bitcoin Core only keeps today’s phone book. peer-observer dumps it every day, so you can see how it changed over months.
An ADDR (or the newer ADDRv2, which also fits Tor and other address types) can carry up to 10 addresses at once. Normally the average was about 2 per message. From around April 2026 it climbed to about 3.5. Small, but clearly not normal. Someone was spamming the network with bogus addresses that do not exist.
So why not test every address before you save it? Because honest nodes go offline. If your node crashes for an hour and everyone deletes you, you have to start gossiping from zero, and that is slow. Bitcoin Core needs forgiveness, so it keeps two tables.
Mini-game 3 · Bouncer✓ badge earned
You are addrman. Sort the guest list.
Six addresses just arrived in ADDR messages. Try to connect to each one, then file it: Tried (it answered, trust it more), New (no answer yet, try again later) or Delete. Get all six right for the badge.
Tried tableanswered when we called
New tablenot reached yet, retry later
Hint: a node that does not answer might just be rebooting.
Razor’s puzzle
More spam, but fewer new addresses?
Simplified sketch of the shapes from the bnoc post, not real numbers. You would expect a flood of fake addresses to push the second line up. Razor ended his talk right here: “I hope by the end of my talk you will also be confused.”
Spoiler: what the bnoc authors think is going on
The spam filled up the new table with fake entries that nodes could not easily throw away. With the table clogged, there was little room left for real new addresses, so fewer got added each day. A follow-up post discusses relaxing the rules for evicting old entries, and the tricky part: address gossip, unlike blocks or transactions, costs nothing to send, so spam is hard to price out.
3Floresta with stonepillar
Meet our newest fellow. stonepillar is a contributor to Floresta, a lightweight Bitcoin node written in Rust. It uses Utreexo to keep the data a node needs tiny, so you can validate your own transactions on a Raspberry Pi or even a phone instead of trusting someone else’s node. He will spend his three-month Code Orange fellowship on Floresta, and Floresta developers we met in Korea already speak highly of his work.
Working on Floresta is a great way to learn Bitcoin Core, because Floresta copies many of its parts. It even has its own address manager crate, the same idea Razor just explained. One recent fix stonepillar reviewed:
A recent Floresta fix
Remember your best peers across a restart
Before
After
His main fellowship work: making Floresta’s RPCs (the commands apps use to talk to a node) behave like Bitcoin Core’s. There is a tracking issue full of RPCs still to build, and it is a good place for first-time contributors. His biggest piece so far is RPC authentication, which looks like “just check a password” until you read how Bitcoin Core does it:
Why it takes so many reviews
“Just a password check”, in layers
Key takeaways
- Distributed beats decentralized for resilience. If one node going down can cut off a branch, there is still a choke point. FIPS aims for a true mesh where your npub is your address.
- Learn Bitcoin Core through incidents. Address relay is just nodes gossiping “here I am” into a phone book. The 2026 spam shows why that phone book needs a forgiving “new” table, and why it can get clogged.
- There is real work waiting for you. Floresta has a list of RPCs to build and PRs to review. Reviewing is how you start, and the people presenting on these calls are the ones learning the most.
Final level: the quiz
Three questions from the call. Get all three right and the Reviewer badge lights up on the mission board.
Test yourself
Resources shared
FIPS and mesh networking
- FIPS (Free Internetworking Peering System), Jonathan Corgan: the project Alex presented: a self-organizing, encrypted mesh network where every node's address is its Nostr npub. Alex's homework: run a node before next time
- BitChat: the example Alex used for chatting over Bluetooth with no internet. FIPS wants to make that kind of link work for any app
- OSI model: the seven-layer picture of a network that came up when we asked whether FIPS still uses IP. FIPS swaps out the addressing layer
Address relay
- Address relay under stress, bnoc, August 2026: the forum post Razor walked through: the address spam from about April to July 2026 and how it showed up in peer-observer data
- Address relay under stress: attack characteristics and measuring its effects, bnoc, August 2026: the companion post with the graphs, including new addresses per day falling during the spam
- Peer Observer, 0xB10C: tools that watch the Bitcoin P2P network for attacks. It dumps a node's addrman every day so you can see how it changes
- Bitcoin Core addrman.h: where address relay lives in Bitcoin Core, with addrman_impl.h and the matching .cpp files. Start with the comments at the top
- Address relay (Bitcoin Core Academy): a plain-English chapter on how nodes share addresses, if you want more after the whiteboard
Floresta
- Floresta: the lightweight Utreexo node in Rust that stonepillar contributes to. Look for the RPC tracking issue if you want a first contribution
- Utreexo, Tadge Dryja, MIT DCI: the idea that lets Floresta keep a tiny summary of the coin set instead of the whole database
Code Orange
- Decoding Bitcoin cohort: 10 weeks, every Monday, starting 16 November. Alex runs it
- Privacy Track: next up: Silent Payments on Tuesday 17 November, with a wallet demo
- Developer fellowship: how stonepillar is spending three months on Floresta
Also mentioned without a link: Jeff Booth's point that Bitcoin scales in layers like the internet (Lightning, ecash, Nostr on top), FIPS's encryption saved for a later session, and the RPC authentication PR on Floresta that is close to merging. stonepillar will bring Floresta PRs to future Code Review Clubs.
These notes are also on GitHub: code-orange-dev/session-notes. Free to share and reuse (CC0).