We did it. Billy’s gone. 4-8, 2-6 in the SEC, and the promise I made last year to wear black until either a natty or a firing turned out to only need one of those things. Didn’t need Vegas, didn’t need a miracle. Just needed one more bad year and an athletic director with a spine.

This is the first real coaching change of the Ctrl+Alt+Vent era, which feels like it should mean more than it does. I’ve been doing this preview thing for what, two years now, and both of them were basically “please, Billy, figure it out.” Now I get to do the fun version. New guy, clean slate, no more pretending a 6-6 season with a decent bowl game is actually progress.

Who Is This Guy

Jon Sumrall. 43-12 combined at Troy and Tulane. Three conference titles. Got Tulane into the CFP last year. On paper this is about as good as a Group of Five hire gets, and I don’t say that as a backhanded compliment the way people usually mean it when a school “settles” for a G5 guy.

Here’s the thing that actually matters to me: Napier’s whole pitch was “trust the process,” which is a phrase that should be legally banned from college football after about year three of not working. Sumrall’s pitch is simpler. He wins wherever he goes. That’s it. No vision boards, no five-year plan, just a guy who’s taken over two different programs and immediately made them better. I don’t need him to reinvent Florida football. I need him to be the kind of coach who’s already proven he can do the boring stuff well, and let the talent and resources here do the rest.

The QB Battle Wasn’t Much of a Battle

Aaron Philo is the Week 1 starter over Tramell Jones Jr., and honestly, I called this one. Philo’s Buster Faulkner’s guy from Georgia Tech, and Florida specifically brought Faulkner in as OC knowing Philo would follow. That’s not a coincidence, that’s the plan working exactly as designed. Familiarity with the system wins these things nine times out of ten, especially in year one when nobody wants to spend the first month of the season also relearning the playbook.

What I actually want to watch, though, is snap counts in the first two games. If Jones is getting real run, not garbage time, but real run against FAU and Campbell, that tells me this competition isn’t as settled as the depth chart says it is. Something closer to a 60/40 split and Sumrall’s basically telling us he’s still deciding. A clean Philo takeover and it’s exactly what it looks like on paper.

The Good News

Jadan Baugh is legitimately one of the best backs in the SEC, and maybe even the country. 1,100-plus yards last year on a team that couldn’t do much else offensively, which tells you everything about how much of that offense ran through him and how good he actually is. Dallas Wilson and Vernell Brown III give this receiver room some juice if the injuries cooperate, which is doing a lot of lifting in that sentence, but it’s more than we had last year.

And defensively there’s actual continuity for once. Bryce Thornton at safety and Cormani McClain at corner both stuck around, which after the portal era Florida’s had, feels almost quaint. Having returning starters in the secondary is not something I expected to be excited about, but here we are.

The Bad News

No proven pass rush. 3.5 sacks led the team last year, which is not a typo, that’s just how bad it was. The secondary lost real starters to the portal even with Thornton and McClain sticking around. And the offensive line took a real hit losing Jake Slaughter at center, which isn’t the kind of thing you just paper over with a good tackle transfer. Centers make an offensive line work as a unit, and replacing one mid-rebuild is not nothing.

The one thing giving me some hope up front is Phil Trautwein running that room. Former Gator tackle, two BCS titles as a player, back in Gainesville coaching the position he used to play. He’s on record saying he doesn’t know his starting five yet, “just because you started last year doesn’t mean you start this year,” which is either exactly the open competition this group needs or a sign nobody’s separated themselves. I’m choosing to read it as the former. If anyone can find a functional line in that room, I like the odds of it being the guy who actually played the position at a high level here.

So the formula here is pretty clear. If the defensive front can generate any pressure at all and the O-line holds together around a new center, this team is dangerous. If either of those things goes sideways, we’re looking at a long year no matter how good Baugh is. Not just my read either, those are the same two things the preview podcast circuit keeps flagging, so at least I know I’m not just being a pessimist for the sake of it.

The Actual Questions I Have

This is really what Part 1 is about, more than any single stat or roster note. Does Sumrall’s culture reset actually show up on the field this year, or is Year One just about not being an embarrassment while the real payoff comes in year two or three? I don’t think anyone honestly knows yet, including probably Sumrall himself.

And is this a “reset the vibes” year, where we’re just happy to have a coach who seems competent and isn’t dodging questions about his job security in August, or is this an actual “we should be winning these games” year? Those are two very different ways to watch a season, and I think most Gator fans haven’t fully decided which one they’re doing yet. I know I haven’t.

Honest temperature check: fan mood feels better than it has in years, but it’s the specific kind of better that comes from lowered expectations, not raised ones. Nobody’s talking playoff. Everyone’s just relieved the vibes aren’t actively bad anymore. That’s a real improvement. It’s just worth being honest that “not actively bad” and “good” are not the same thing.

So What Do I Actually Think Happens

Outside consensus has this team at 7-5, but I like the floor/ceiling framing I keep hearing on the preview podcast circuit better than picking one clean number. Floor’s 2-10, if the only games we can actually pencil in as wins are FAU and Campbell and everything else breaks wrong. Ceiling’s 8-4. Realistic expectation is somewhere around 7-8 wins, and I’ll take that, with the same disclaimer I gave last year: I can confidently say 8-4, or 7-5, or, whispering now, 2-10 if the O-line completely falls apart and the pass rush stays nonexistent. Probably somewhere in the middle, closer to the optimistic end, because I think Sumrall’s floor is higher than Napier’s ever was even in a rebuild year.

Part 2 gets into the schedule itself, week by week, including a rivalry game that’s leaving Jacksonville for the first time since 1995, which deserves its own several paragraphs of complaining.

I’ve started noticing a pattern about myself.

Whenever I pick up a new hobby, I tell myself I’m just going to keep it simple.

“I’m going to train for a marathon.”

“I’m going to learn more about Bitcoin.”

“I want to smoke a really good brisket.”

Normal enough.

But somewhere between deciding I want to do something and actually doing it, my brain takes a detour.

I start reading.

Then I read some more.

Then I find a Reddit thread from 2018 where two people are arguing about something so ridiculously specific that I didn’t even realize it could be debated. Naturally, I have to figure out who’s right.

One article turns into YouTube videos. Those turn into podcasts. Then books. Then blog posts from people who have dedicated an alarming percentage of their lives to whatever niche thing I became interested in three days ago.

Eventually I look up and realize I’ve spent ten hours learning how to do the hobby and maybe two hours actually doing it.

Running was probably the first time I really noticed it.

I thought marathon training meant... well... running.

Instead I learned about heart rate zones, cadence, fueling, VO₂ max, recovery, hydration, shoes, socks, stretching, strength training, sleep quality. Every answer seemed to come with three more things I “needed” to understand first.

Then, because apparently I can’t leave well enough alone, everything got connected together. Runna feeds Strava. Strava feeds Apple Health. My watch knows how well I slept, how hard I trained, whether I should recover, and probably what mood I’m in before I do.

The funny part is none of that actually makes you a runner.

You still have to go outside.

Bitcoin went exactly the same way.

I bought a little because it seemed interesting.

That somehow turned into learning how mining works, why proof of work matters, what private keys actually are, why people care about running their own node, and eventually... running my own node.

If you’ve never done that, just know there’s something objectively funny about spending an entire Saturday making sure software whose primary job is to quietly exist... is quietly existing.

For a while I thought this was just an engineer thing.

And maybe it is. We like systems. We like understanding how things work. If something feels random, our first instinct is to find the underlying rules.

But I don’t think that’s the whole story.

I think I genuinely enjoy learning.

Not learning in the “I want another degree” sense.

More like pulling on a thread because I want to see where it goes.

I like getting to the point where I stop memorizing facts and start understanding why things work the way they do.

That’s true whether it’s Bitcoin, marathon training, barbecue, sports betting, or trying to figure out why one soccer team keeps outperforming its expected goals. Once I feel like I can see the system underneath everything, that’s the part I really enjoy.

The downside is there’s no finish line.

Every hobby has another article to read.

Another expert to listen to.

Another piece of gear someone swears changed everything.

Another rabbit hole.

If you’re not careful, the preparation quietly becomes the hobby.

I’ve caught myself researching the perfect long run instead of just going for one. Reading reviews instead of buying the thing. Watching videos instead of trying it myself.

It’s kind of like sports betting.

At some point, more information stops making your prediction meaningfully better. You’re just finding new ways to feel more confident about the same uncertainty.

Learning can work the same way.

At some point, you’re not learning because it’s useful anymore.

You’re learning because learning itself has become the hobby.

I’m not even sure that’s a bad thing.

I just have to remind myself every once in a while to close the laptop and actually go do the thing.

Otherwise I’ll eventually become the world’s leading expert on hobbies I’ve barely started.

Last week, while packing for our family trip to Mexico, my daughter made sure to put Harry Potter and the Chamber of Secrets in her suitcase.

Not a swimsuit.

Not a stuffed animal.

Not one of the seventeen random items children somehow deem essential for international travel.

A 352-page novel.

Her reasoning was simple: she was pretty sure she’d finish Sorcerer’s Stone while we were gone and wanted to make sure she had the next book ready.

Thankfully, she did.

Otherwise I probably would have spent half the vacation listening to complaints about not having the sequel.

The funny part is that this level of planning required a second trip to a different library before we even left. Our local library didn’t have a copy available, and apparently “waiting” was not an acceptable solution.

This wasn’t a casual reader preparing for vacation.

This was an addict making sure her supply chain remained uninterrupted.

The whole thing started a few weeks earlier when I took her to the library because I wanted her to read something more challenging.

At eight years old, she had been tearing through Magic Tree House books at an alarming rate. I don’t mean she was reading them quickly. I mean she was consuming them. We’d check out a stack and a day later she’d be asking when we were going back for more.

As a parent, this is the kind of problem you’re thrilled to have.

Still, it felt like she was ready for something bigger.

So I casually suggested she look at some different options.

Very casually.

The kind of casual that only parents think is casual.

“Well,” I said, “there’s Harry Potter. Or Percy Jackson. Or...”

I don’t remember what came after that because she had already locked onto Harry Potter.

To be fair, she saw right through my little performance. She knew exactly what I was doing.

Children are much better at detecting parental agendas than we give them credit for.

The funny thing is that she’d already seen all the Harry Potter movies. Multiple times. I figured that might reduce some of the magic. She already knew the story. She already knew who the characters were. She already knew where everything was headed.

I was wrong.

Very wrong.

Within days she had become completely obsessed.

She carries the book everywhere.

At one point she brought along a Harry Potter spell book because she wanted to cross-reference spells mentioned in the novel and learn more about them.

Again, this is not normal behavior.

This is what happens when a child discovers a new special interest and decides to make it everyone else’s business.

The part I’ve enjoyed most is listening to her compare the books to the movies.

Every few pages she’ll excitedly point out a scene that wasn’t included or a detail that was changed.

It’s like listening to a tiny literary critic.

“Dad, they left this part out.”

“Dad, this makes way more sense in the book.”

“Dad, that’s not what happened.”

She’s not wrong, either.

Which brings me to another unexpected discovery.

In an effort to keep up with her, I started listening to the new Harry Potter audiobooks.

The ones with the full cast.

As an aside, they’re really good.

I wanted to be able to talk to her about the books while she was reading them. What I didn’t expect was realizing how much I had forgotten.

Entire scenes.

Entire chapters.

Entire plot points.

In fact, I eventually realized something even stranger.

I don’t think I ever actually read Sorcerer’s Stone.

At least not when it first came out.

I think I saw the movie and then started with Chamber of Secrets.

Which means that while my daughter was experiencing the first book for the first time, parts of it were effectively new to me too.

That felt oddly fitting.

Harry Potter was one of the defining stories of my childhood.

I remember waiting for the midnight releases.

I remember racing through the later books.

I remember reading Deathly Hallows in what felt like a single weekend because there was absolutely no chance I was waiting to find out what happened.

More than that, I remember how universal it all felt.

Everybody read Harry Potter.

Everybody talked about Harry Potter.

Every new movie felt like an event.

The books weren’t just books. They were part of the culture.

You could walk into school on Monday and instantly have something to talk about.

For a lot of kids my age, Harry Potter wasn’t just a story. It was a shared experience.

Most childhood obsessions don’t survive long enough for you to revisit them with your own children.

Some disappear entirely.

Others get frozen in time.

Harry Potter is one of the few that managed to stick around.

Despite all the complicated conversations surrounding the author in recent years, the books themselves continue to find new readers.

And now, somehow, one of those readers is my daughter.

What’s funny is that the books aren’t really the thing I’ve been thinking about.

What I’ve actually been thinking about is how quickly kids grow up.

There wasn’t some dramatic moment where I suddenly realized she was old enough for Harry Potter.

If anything, I’m glad we waited.

Could she have read it a year ago?

Probably.

But now she wanted to read it.

That’s the difference.

You can’t manufacture curiosity.

You can’t force obsession.

You can hand your kid a book, but you can’t make them love it.

That part has to happen on its own.

Lately I’ve been having more and more moments like this.

She’s on a competitive dance team now, and every time I watch the older girls perform, they seem so grown up on stage.

Then you see them afterward.

They’re laughing.

Being goofy.

Talking about snacks.

They’re still kids.

The same thing is happening here.

My daughter is old enough to disappear into a three-hundred-page novel.

Old enough to make connections between books and movies.

Old enough to have strong opinions about adaptation choices.

And yet she’s still bringing a spell book to Mexico.

She’s still my baby girl.

That’s the weird thing about parenting.

The changes happen so gradually you barely notice them.

Then one day you’re standing in a library watching your kid walk toward a shelf that once defined your own childhood.

A few weeks later you’re both talking about Hogwarts over breakfast.

And suddenly two decades disappear.

When I handed her Harry Potter, I thought I was giving her a harder book.

What I was actually giving her was an invitation into a conversation that started long before she was born.

A conversation I once had with my friends.

A conversation that now belongs to us.

Books have a unique ability to do that.

They connect people who would otherwise be separated by years, decades, even generations.

The magic was never really Hogwarts.

The magic was always that shared stories allow us to experience a little piece of someone else’s world.

And every once in a while, if you’re lucky, they allow you to experience your own world all over again.

I am a Florida Gators fan who watched his program go 4-8 last season. I watched four years of press conferences where the head coach spoke exclusively in process-language, the kind of coach-speak that sounds like something but contains nothing, where “building the right culture” and “trending in the right direction” became a kind of white noise you stopped hearing after year two. I watched a program that once had Spurrier, Meyer, and a murderers’ row of NFL talent turn into a program where the main storyline by October was whether the coach would survive the week.

I am not getting my hopes up about Jon Sumrall.

I’m just noticing some things.

On recruiting

I don’t put a lot of stock in recruiting rankings. Classes are ranked in May, games are played in September, and those two facts have a complicated relationship. So when I tell you that Florida’s 2027 recruiting class is currently ranked fifth in the nation, that’s just a number. It doesn’t mean anything yet.

It’s worth noting, in a completely neutral way, that at this point last year under Billy Napier, Florida had two recruits committed. Two. Sumrall has thirteen, landed three in a 24-hour window, and did all of this in five months. The class includes Maxwell Hiller, a five-star left tackle who is the highest-rated offensive line recruit Florida has signed since 2015. Not since Napier. Since 2015. That tells you more about the last decade than any record does.

If I were the kind of person who read into momentum, I might also mention that recruits keep committing before they even take official visits. Rivals analyst Sam Spiegelman called it a “recruiting heater” and said this is just the beginning, with official visit season in June and July still ahead. I noted that, filed it away, and moved on with my life.

On character

I’ve been burned enough times to know that press conferences are theater. Coaches say things. The camera loves them. I’m not reading into any of it.

That said, a few things happened in Sumrall’s first 48 hours on the job that I am simply going to describe without editorializing.

Before he landed in Gainesville, he got on FaceTime with his Tulane commits and told them to honor their commitment to Tulane. He said he didn’t want to poach his own class. His first press conference was not about schemes or systems. He looked at the players already in the room — DJ Lagway, Dallas Wilson, Myles Graham — and told them directly: “Future Gators matter to me. Current Gators matter more.” He said he has a sign in his office that reads “Coach the team.” His recruiting pitch to top prospects is not a soft sell. It’s closer to a challenge: “If you like us now, you’re going to love us later. If you don’t like me now, go somewhere else, because I’m not changing.”

I’m not saying any of that means anything. I’m just describing what happened.

On keeping the Fab Five

This one did not have to go well.

When a program goes 4-8 and the head coach gets fired, the portal opens and good players leave. That’s not a scandal, it’s just how college football works now. The question for any new coach is not whether they’ll lose anyone. It’s whether they can hold the guys who matter.

Sumrall held all five of them.

Jadan Baugh, who became the first Gator back to rush for 1,000 yards since 2015 and followed that up with a 266-yard demolition of Florida State, was the most coveted. Jayden Woods was in high demand across the portal. Vernell Brown III and Dallas Wilson, both true freshmen who showed genuine star-level flashes despite a brutal season, had every reason to test their options. Myles Graham, a Gainesville native and second-generation Gator, announced he was staying before the calendar even hit January.

All five came back. All five cited Sumrall directly as the reason.

Woods put it best: “I lost Coach Napier, Coach Roberts, and Coach Peterson, the three guys I mainly came here for. I just wanted to do my due diligence.” Then he met Sumrall, heard the plans, looked around at Graham, Baugh, Brown, and Wilson staying, and decided the foundation was worth building on. “People truly make the place,” he said.

If you want to understand the difference between how this transition has felt versus the Napier years, that quote is the shortest path there. Under Napier, players were leaving programs to come to Florida hoping the culture would catch up. Under Sumrall, players are staying at Florida because the culture is already visibly different.

I’m not making predictions. I’m describing what Woods said.

On accountability

Billy Napier, in four years, never once said anything that made me think he was operating with genuine urgency. He always sounded like a man managing a timeline, executing a plan, running a process. When the losses piled up, the language got more careful, not less. The final press conferences of his tenure were exercises in institutional damage control.

Jon Sumrall was asked recently about bowl eligibility. His answer: “We better be, or I’m going to be up on the roof of the stadium getting ready to do something stupid.”

That’s a man who expects to win football games. That’s a man who understands that bowl eligibility is not an achievement at the University of Florida, it’s the floor. You can argue about coaching pedigree, about whether Tulane translates to the SEC, about what a 43-year-old who’s never coached at this level can do in Gainesville. Those are fair questions and I don’t have answers yet.

But I’m also noticing that the language coming out of that program right now sounds nothing like what I was used to hearing.

I’ve been a Gators fan long enough to have been genuinely happy and genuinely devastated by this program. The Spurrier years made us believe this was normal. The Meyer years made us believe it could come back. The Mullen years made us believe, briefly, that close was good enough. The Napier years made me stop believing in the offseason entirely.

I’m not there yet with Sumrall. September hasn’t happened. The SEC doesn’t care about recruiting rankings or vibe shifts or five-star offensive tackles. The SEC cares about fourth-and-one in the fourth quarter, and we won’t know anything real until we’re in those moments.

But I’ll say this, quietly, with full awareness that I might regret it: for the first time in a while, I’m paying attention to Gators football in May. Not because I have to. Not out of some grim sense of fan loyalty. Because something is happening over there that feels like it might actually be real.

I’m not getting my hopes up.

I’m just noticing things.

You don’t know. Not without a spreadsheet and a Saturday afternoon you don’t have.

I’ve been running a Lightning node on Umbrel for five years. I DCA through Strike and River. I hold a small position on Coinbase from before I went self-custody. My node routes payments and earns fees. Each of those pieces has its own interface, its own export format, its own version of the truth. None of them talk to each other. None of them give me the one number I actually want: my total Bitcoin position across everything, and what it cost me to build it.

So I built Satsbook; a general ledger for your Lightning node. It stitches together your node’s routing income, your exchange purchases, and your cost basis into one view, running entirely on your own hardware. I’m going to explain why this gap exists, why nobody has filled it, and what Satsbook does about it.

The three problems nobody’s solving

You can’t see your node’s ROI

ThunderHub shows forwarding events. RTL shows channel balances. Neither shows earnings over time. There’s no YTD view. No way to ask “how much did this channel earn relative to the capital I locked in it?” No comparison between what I spent on rebalancing and what I earned in routing fees. The data is there, it’s in the LND database, but nothing surfaces it in a way that answers the question a normal person would ask: is this node making money?

I found myself SSH’d into my Umbrel at 11pm, running SQL queries against the LND database to answer questions that should have been one click on a dashboard. That’s when I knew something was missing.

Your tax records are siloed across five tools

Strike has a CSV. River has a CSV. Coinbase has a statement. My LND node has on-chain transactions from channel opens and closes. I’ve got BTC that moved from an exchange into a Lightning channel that later got closed back on-chain, and none of these tools have any idea about the others.

The IRS treats every disposal of Bitcoin as a taxable event. That arguably includes every Lightning payment you make. If you can’t reconstruct the full history — what you bought, when you bought it, what you received as routing income, what you spent — you can’t file cleanly. You’re either overpaying, underpaying, or guessing. None of those options are good.

The cost basis problem is genuinely hard when your Bitcoin lives across five different systems and two different layers. It’s not that people are lazy about taxes. It’s that the infrastructure to do it correctly doesn’t exist for Lightning operators.

The tools that do exist aren’t built for you

I looked. Here’s what I found:

Amboss is excellent if you’re a professional routing operator running Lightning as a business. If you’re a home-lab operator running Umbrel on a Pi, it’s overkill in some ways and doesn’t cover the accounting side at all.

Koinly and CoinLedger handle crypto taxes, but they pretend Lightning doesn’t exist. No channel opens, no routing fees, no understanding of the HTLC lifecycle. They’re built for people trading on centralized exchanges, not people running infrastructure.

Cryptio and TRES are enterprise tools with enterprise pricing. They’re for companies with compliance departments, not for someone running a node in their closet.

ThunderHub and RTL are node management UIs. They’re indispensable for what they do — managing channels, monitoring liquidity, watching the mempool. But they’re not accounting tools. They don’t track cost basis. They don’t know about your exchange purchases. They show you what’s happening right now, not what happened over the last twelve months.

There’s a specific person who falls through all of these cracks. The sovereign operator running Umbrel at home. Real Bitcoin in channels. Real opinions about custody. A real need for clean financial records. And absolutely nothing that gives them a unified view of what their stack is doing.

That’s the whitespace. That’s who I built Satsbook for.

Why nobody built this

The gap is structural, not accidental. Four reasons:

The market is small and technical. There are maybe 20,000 people running Umbrel who care about routing fees and cost basis. You can’t raise a Series A for that. No VC is going to fund “a general ledger for home Lightning node operators.” The total addressable market makes investors’ eyes glaze over. So nobody with funding attempts it.

The integrations are unglamorous. LND’s gRPC API. Strike’s CSV format and its idiosyncrasies. River’s export layout. Coinbase’s transaction statements. Each one has its own edge cases, its own date formats, its own way of categorizing transactions. Stitching them together into a single coherent ledger is the kind of boring, detail-heavy work that nobody wants to do as a startup.

The tax treatment is uncertain. How do you account for a Lightning channel open? A splice? A circular rebalance? The IRS hasn’t issued clear guidance on any of it. Big players stay away from uncertainty because they can’t afford to build something that might be wrong. A side project doesn’t have that constraint — I can build what I think is right and update it when guidance comes.

The audience hates cloud tools. This is the catch-22. The people most likely to need this product are the most likely to refuse to upload their node data to a SaaS platform. Self-sovereign means self-sovereign. Which means the whole thing has to run locally, on their hardware, with no outbound connections they didn’t ask for. That’s harder to build and harder to monetize, which is why nobody attempts it.

These are exactly the reasons I was in a good position to build it. I’m in the audience. I already had LND integration experience from a prior side project. And I’m happy with a side-hustle-sized market that a VC would never touch.

What Satsbook actually looks like

I’ll show you instead of telling you.

This is the screen that made me realize the project was worth finishing. One number: your total net BTC position across every source. Node earnings, Strike purchases, River DCA, Coinbase holdings; all rolled up into a single figure with the USD equivalent at current price. Below it, the breakdown showing where each piece came from.

Before Satsbook, if someone asked me “how much Bitcoin do you actually have?” I’d have to open four tabs and do arithmetic in my head. Now it’s one number on one page, and I trust it because I can see where each component came from.

This is the strip I check every morning. Three numbers: what my node earned in routing fees this year, what I purchased through exchanges this year, and my net position change. One line that tells me whether my stack is growing and where the growth is coming from.

This is for the routing nerds. Daily fee income charted over time, with a per-channel breakdown underneath. You can finally see which channels are earning their keep and which ones are just sitting there consuming capital.

This is the unlock. Three tabs — Strike, River, Coinbase. Drop a CSV, hit upload. Satsbook parses it, deduplicates by content hash so you can re-upload safely, and folds those transactions into your unified ledger. Each vendor has a danger zone at the bottom if you need to clear and re-import. The whole cycle takes about thirty seconds.

How it’s built

For the readers who want to know what they’re running before they install it — and I respect that instinct completely.

Satsbook is a single Go binary. No CGO, no Python, no Node.js. It cross-compiles cleanly to linux/arm64, which means it runs natively on your Raspberry Pi without emulation. The binary is about 25 MB.

The database is SQLite, embedded via a pure-Go driver (modernc.org/sqlite). No separate database process. No Postgres. No Redis. Your data lives in a single file on your node.

The frontend is HTMX — server-rendered HTML with no JavaScript framework. Every request is visible in your browser’s network tab. There’s no client-side state, no build step, no npm. If you open the source, you can read every template.

All assets are embedded in the binary via Go’s embed.FS. There are no runtime file dependencies. The binary is the whole app.

Satsbook connects to your LND node using a read-only macaroon. It literally cannot sign transactions, send payments, or modify anything on your node. It reads forwarding history and channel balances. That’s it.

The only outbound connection is a single price lookup to CoinGecko for the current BTC/USD rate, used to display dollar equivalents on the dashboard. You can disable it.

Syncing is incremental. Satsbook maintains a cursor so it never re-fetches data it’s already stored. First sync pulls your full history; every sync after that picks up only new events.

If you want to audit it, it’s about 14,000 lines of Go. You can read the whole thing in an afternoon.

Free is real. Paid is coming.

I want to be transparent about the business model, because I think the Bitcoin community deserves that.

The free tier is the dashboard and exchange imports. Net BTC position, routing fee income, YTD summary, Strike/River/Coinbase CSV import, per-channel breakdown. Full stop. It’s not a trial. It’s not time-limited. It’s not a demo with the good features grayed out. It’s genuinely useful on its own, and it will stay free.

Pro ($9/mo) is the tier you’d pay for at tax time. Full history export, FIFO and LIFO cost basis calculations, Form 8949 output. If you’ve ever spent a Saturday afternoon in a spreadsheet trying to reconstruct your cost basis, this is the thing that makes that Saturday go away.

Power ($19/mo) is for the operators who want more. Monarch and YNAB sync, Telegram alerts, multi-node support. These features are under development.

Here’s the quiet part out loud: the free tier is the acquisition funnel. The paid tier is the sustainability model. I’m building this as a side business, not a VC-scale land grab, and the pricing reflects that. If the free tier is all you ever need, great — use it, tell your friends about it, file an issue when something breaks. That’s a win for me too.

Try it

Three things I’m asking:

Install it. If you’re on Umbrel, add the community app store and install Satsbook in about thirty seconds:

Umbrel → App Store → Community App Stores → Add Store
https://github.com/satsbook/umbrel-app-store

Import one CSV. Look at your dashboard. Tell me what surprised you.

Tell me what’s broken. I built this for my node. Your node is different. Your channels, your exchange history, your edge cases — I want to hear about them. The fastest way to help is a post in GitHub Discussions that says “this doesn’t match what I see in ThunderHub.” Those posts are gold.

Share it with someone who needs it. If you have a friend running a node who complains about tax season, or who’s been meaning to figure out what their routing fees actually add up to, point them at this post.

It’s MIT licensed. It runs on your hardware. It never phones home. I built it for myself, and I hope you find it as useful as I have.

Satsbook is open source at github.com/satsbook/satsbook. Built by BrewGator. Not financial or tax advice.

Scroll for five minutes and you’ll see it everywhere. The new blockbuster? Mid. That buzzy Netflix show everyone swore you’d love? Mid. The album that took three years to make and six producers to finish? Yeah, fine. Mid.

It’s become this reflex. A shrug with Wi-Fi.

And I can’t shake the feeling that maybe, just maybe, we’re aiming at the wrong culprit. What if the stuff itself hasn’t deteriorated? What if we have? Not morally. Not intellectually. Just… experientially. Maybe we’ve forgotten how to sit with something long enough to actually like it.

That sounds dramatic. I know. But stay with me.

The “Good Old Days” Were Edited for You

Whenever someone says, “Movies were better in the ’90s,” I want to ask a follow-up question: which ones?

Because what they usually mean isn’t every movie that came out in 1996. They mean the handful that stuck. The cultural landmarks. The ones that still get anniversary screenings and nostalgic podcast episodes. Time did a ruthless cleanup job for us.

We remember the bangers. We forget the filler.

No one is hosting watch parties for the painfully average network sitcom that aired for eleven months in 1997 and then evaporated. No one is passionately defending the $38-million studio drama from 2003 that made $12 and a coupon for Chili’s. Those projects sank quietly into the swamp of obscurity. What floated to the surface became “the era.”

That’s not proof the past was superior. It’s proof memory has a highlight reel function.

Psychologists call it nostalgia bias, which sounds sterile and clinical, but it’s basically this: your brain airbrushes yesterday. It cranks up the emotional saturation and softens the rough edges. So when you compare today’s perfectly decent movie to the best film of your teenage years, today never had a fair shot. It was outmatched before the opening credits rolled.

And honestly? That’s kind of unfair.

The Numbers Don’t Panic

If storytelling had truly fallen off a cliff, we’d expect to see carnage in the data. Ratings should nosedive. Reviews should crater. The long arc of cinema should slope downward like a ski jump.

But when you scan aggregate scores across IMDb, Rotten Tomatoes, Metacritic—take your pick—the decline people swear they feel doesn’t really show up in dramatic fashion. Decade by decade, the averages huddle in roughly the same neighborhood. Not identical, sure. But not catastrophic.

What has exploded is output.

We are absolutely drowning in content. Streaming platforms multiply like rabbits. Studios crank out sequels, spin-offs, prestige limited series, docuseries about the making of the docuseries. There’s more to watch on a random Tuesday than there was in an entire season of television twenty years ago.

That doesn’t lower the creative ceiling. It just makes the middle feel massive.

When ten great things coexist with a hundred “pretty solid” ones, and another hundred you’ll forget by Thursday, mediocrity seems omnipresent. It’s not that excellence vanished. It’s that it’s buried under sheer volume. The algorithm keeps feeding you, and not all of it is filet mignon.

Back in the day, you had fewer choices. The bad stuff didn’t stalk you through personalized recommendations. It aired once at 8:30 p.m., you shrugged, and you moved on with your life.

We Quietly Raised the Bar to the Moon

Here’s something we don’t admit out loud: “pretty good” doesn’t satisfy us anymore.

There was a time when a well-acted, competently written, entertaining movie counted as a win. You left the theater pleased. You told a friend, “Yeah, it’s worth seeing.” End of transaction.

Now? If it doesn’t reinvent the genre, deliver at least three meme-able moments, emotionally devastate you, and spark a 40-tweet thread, it risks being filed under “mid.” We’ve inflated our expectations like we’re blowing up a parade float and forgot to stop.

Take a film that’s polished, coherent, genuinely enjoyable—but not revolutionary. Ten years ago, that’s a solid night out. Today, it’s something you stream while folding laundry and then forget to rate. Not because it failed. Because it didn’t change your molecular structure.

Maybe we’ve confused “not life-altering” with “not good.” That’s a subtle shift. But it matters.

And yeah, I catch myself doing it too.

Nostalgia Isn’t Just a Feeling; It’s a Business Model

Studios understand our soft spots better than we do. Familiar intellectual property is safer. Known characters reduce risk. So we get sequels, reboots, cinematic universes with lore charts that require a spreadsheet.

Then something like Deadpool & Wolverine lands, and the reactions are… intense. It’s not just a movie at that point. It’s a referendum on childhood, on earlier phases of fandom, on the memory of how it felt when superhero films were still fresh and a little unhinged.

If the new installment doesn’t outshine the emotional imprint of the original, disappointment rushes in. Even if, objectively speaking, it’s fine. Entertaining. Well-crafted.

But “fine” struggles against nostalgia. Nostalgia fights dirty.

The older version of something has the unfair advantage of first impact. It hit you when you were younger, maybe more impressionable, maybe less distracted by email notifications and group chats. You can’t recreate that exact cocktail of timing and innocence. And yet we keep expecting to.

Comfort Television Is a Warm Blanket

Be honest. How many times have you rewatched The Office or Parks and Recreation instead of trying something new?

I have. More than I’d like to admit.

There’s a reason comfort shows feel so good. They’re pre-vetted. The jokes land where you remember them landing. The characters feel like people you’ve already forgiven for their flaws. There’s no cognitive risk involved. No fear of wasting eight hours on something that fizzles out in episode six.

New content, by contrast, demands trust. It asks for patience. It risks boredom. And we approach it armed, skeptical, half-scrolling on our phones, ready to pronounce judgment by minute twelve.

If you walk into every experience braced for disappointment, you’ll find it. Humans are weirdly talented at confirming their own suspicions.

Maybe It’s Not the Art. Maybe It’s Us.

I don’t think movies, television, or music have collectively lost their spark. That feels too tidy. Too convenient.

What’s changed, unmistakably, is how we consume.

We binge. We multitask. We live-comment while watching. We compare everything instantly to a canon that lives in our heads. We expect novelty, emotional catharsis, technical brilliance, and cultural relevance, immediately, on demand, no slow burn allowed.

That’s not really how enjoyment works. It never has been.

Some stories need breathing room. Some songs get better on the fourth listen. Some shows don’t click until episode three. But patience is expensive now, and our attention spans are, well… not what they were. Mine included.

So when we label everything “mid,” I can’t help but wonder if we’re holding up a mirror.

Burnout masquerading as discernment. Overstimulation dressed up as critical taste. We’re chasing the feeling we had when something was new; not just new to the world, but new to us. And that’s a high bar. An impossible one, really.

The past glows because we were different inside it. Younger. Less jaded. More available.

Maybe the better question isn’t whether media has declined.

Maybe it’s this: do we still know how to let something be good, simply good, without demanding that it rearrange our soul?

I’m not sure we do.

And that might be the real plot twist.

Most Bitcoin wallets hide a surprisingly complex optimization problem behind a simple “Send” button. When you spend bitcoin, your wallet must choose which UTXOs (Unspent Transaction Outputs) to use as inputs. This choice directly impacts how much you pay in fees and whether your transaction even succeeds.

This is the coin selection problem, and solving it well separates efficient wallets from wasteful ones.

In this article, we’ll rebuild the mental model needed to implement coin selection from scratch. The goal isn’t to hand you working code, but to develop correct intuition about transaction construction, fee calculation, and UTXO management. By the end, you’ll understand what’s actually happening when you click “Send” and why your wallet sometimes seems to make puzzling choices.

Resources:

• Bitcoin Transaction Fees Explained

• Learn Me a Bitcoin - Transaction Fees

What The Problem Actually Is

A coin selection algorithm answers one question:

Given a wallet’s available UTXOs and a payment requirement (destination, amount, fee rate), which UTXOs should we spend?

This seems simple until you realize:

• Different UTXO types have different spending costs

• Fee rates change dynamically based on network demand

• You might need a change output, which costs additional bytes

• Combining too many UTXOs wastes block space

• Combining too few might mean insufficient funds

The algorithm must satisfy hard constraints:

Total input value > total output value
Fee rate >= required minimum

And optimize soft constraints:

Minimize total fees paid
Avoid creating dust
Consolidate when fees are low

Sanity check: If your algorithm always selects the largest UTXO first, you’re probably overpaying during low-fee periods and might fail during high-fee periods.

Resources:

• Bitcoin Optech - Coin Selection

Understanding Effective Value

A UTXO’s nominal value (what you see on block explorers) isn’t what matters for coin selection. What matters is its effective value at a given fee rate.

effective_value = nominal_value - cost_to_spend

The cost to spend depends on:

• UTXO type (P2WPKH, P2TR, P2SH, etc.)

• Current fee rate

Example

Consider two UTXOs at a fee rate of 10 sat/vB:

UTXO A (P2WPKH):
- Nominal value: 100,000 sats
- Input size: ~68 vBytes
- Cost to spend: 680 sats
- Effective value: 99,320 sats

UTXO B (P2TR):
- Nominal value: 100,000 sats  
- Input size: ~58 vBytes
- Cost to spend: 580 sats
- Effective value: 99,420 sats

At 10 sat/vB, both are viable. But at 200 sat/vB:

UTXO A effective value: 86,400 sats
UTXO B effective value: 88,400 sats

The Taproot UTXO is now clearly superior.

Sanity check: If your algorithm ignores input types, you’re leaving money on the table or selecting inefficient inputs.

Resources:

• Bitcoin Stack Exchange - Transaction Weight Calculation

• BIP141 - Transaction Size Calculations

Transaction Anatomy and Virtual Size

Bitcoin transactions have weight measured in “weight units” (WU). Four weight units equal one virtual byte (vB).

Transaction size:
├─ Base transaction (4 WU per byte)
│  ├─ Version: 4 bytes
│  ├─ Inputs: variable
│  └─ Outputs: variable
└─ Witness data (1 WU per byte)
   └─ Signatures and scripts

Virtual size in vBytes:

vsize = ceil(weight / 4)

Fee calculation:

fee = fee_rate × vsize

Why This Matters

You cannot know the final fee until you know:

1. How many inputs you’re using

2. What types those inputs are

3. Whether you need a change output

This creates a circular dependency: selecting inputs affects the fee, which affects whether you need more inputs.

Sanity check: If you calculate fees before knowing your final input set, your transaction might underpay and get rejected.

Resources:

• BIP141 - Segregated Witness

• Bitcoin Core - Transaction Weight Calculator

Input Type Sizes (Reference Table)

Different script types consume different amounts of block space:

TypeInput Size (vBytes)NotesP2PKH (legacy)~148Avoid; expensiveP2SH-P2WPKH~91Nested SegWitP2WPKH (native SegWit)~68Good efficiencyP2TR (Taproot)~58Best efficiency

Output sizes are more uniform:

TypeOutput Size (vBytes)P2WPKH31P2TR43

Overhead:

• Transaction version, locktime: 10 vBytes

• Each input adds prevout (36 bytes) + sequence (4 bytes)

• Each output adds value (8 bytes) + script

Sanity check: A transaction with one P2TR input and two P2TR outputs should be approximately 153 vBytes. If yours is significantly different, something’s wrong.

Resources:

• Bitcoin Optech - Payment Batching

The Change Output Decision

After selecting inputs, you must decide: do I need a change output?

surplus = total_input_value - target_amount - estimated_fee

Three scenarios:

1. Surplus is negative: You need more inputs
2. Surplus covers a change output: Create change
3. Surplus exists but is too small: Donate to miners

The threshold is approximately:

change_threshold = fee_rate × change_output_size

If surplus < change_threshold, creating change costs more than it’s worth. Better to overpay the fee slightly.

Edge Case: Dust

Bitcoin Core considers outputs below 546 sats to be “dust” and won’t relay transactions creating them. Your algorithm must respect this.

DUST_THRESHOLD = 546  # sats

Sanity check: If your algorithm creates change outputs smaller than 546 sats, your transactions will be rejected.

Resources:

• Bitcoin Core - Dust Threshold

Basic Selection Strategies

Strategy 1: Largest First

Select UTXOs by descending value until you have enough.

Pros:

• Simple

• Minimizes input count

• Works reliably

Cons:

• Wastes large UTXOs during low-fee periods

• Doesn’t consider effective value

• Poor long-term UTXO set management

Strategy 2: Smallest First

Select smallest UTXOs first.

Pros:

• Consolidates dust during any spend

• Preserves large UTXOs

Cons:

• May require many inputs

• High fees during high-rate periods

• Can fail when only small UTXOs remain

Strategy 3: Best Effective Value First

Sort by effective value and select highest first.

Pros:

• Accounts for spending costs

• Adapts to fee rates

• More efficient than naive strategies

Cons:

• Still greedy; not globally optimal

• Doesn’t look ahead

Sanity check: Run your algorithm against the same UTXO set at 1 sat/vB and 100 sat/vB. If the selections are identical, you’re ignoring fee rates.

Resources:

• Bitcoin Core - Coin Selection

The Actual Algorithm Flow

Here’s the high-level process:

1. Filter available UTXOs (confirmed, non-locked)
2. Calculate effective value for each UTXO at target fee rate
3. Remove UTXOs with negative effective value
4. Sort by selection strategy (e.g., effective value descending)
5. Iteratively select UTXOs:
   a. Add next UTXO to candidate set
   b. Calculate total input value
   c. Estimate transaction size based on input count
   d. Calculate required fee
   e. Check if we have enough for target + fee
6. If insufficient funds, fail
7. If surplus exists, decide on change output
8. If change needed, recalculate with change output included
9. Return selected UTXOs and change decision

The critical insight: You must account for the transaction size of your own selections.

Sanity check: Your algorithm should sometimes select 2 UTXOs when 1 would “technically” cover the amount, because the fee increases with the additional input.

Resources:

• Murch’s Thesis on Coin Selection

Size Estimation Formula

Rough formula for transaction virtual size:

vsize = overhead + (num_inputs × input_size) + (num_outputs × output_size)

For P2TR → P2TR transactions:

overhead ≈ 10 vBytes
input_size ≈ 58 vBytes  
output_size ≈ 43 vBytes

vsize = 10 + (num_inputs × 58) + (num_outputs × 43)

Example: 1 input, 2 outputs:

vsize = 10 + 58 + 86 = 154 vBytes

At 10 sat/vB: fee = 1,540 sats

Sanity check: Serialize your actual transaction and measure it. If your estimate is off by more than 10%, your math is wrong.

Resources:

• Bitcoin Stack Exchange - Calculate Transaction Size

Fee Rate Strategy

Fee rates determine urgency:

• 1-3 sat/vB: Low priority, next day confirmation

• 10-30 sat/vB: Normal priority, few hours

• 50-100 sat/vB: High priority, next block

• 200+ sat/vB: Emergency, premium block space

Your coin selection must respect the required fee rate but can opportunistically consolidate during low-fee periods.

Advanced strategy:

If fee_rate < threshold:
    Select additional UTXOs to consolidate

This “spends” cheap block space to reduce future costs.

Sanity check: During a 1 sat/vB period, consolidating 10 small UTXOs costs ~580 sats. This could save thousands later.

Resources:

• Mempool.space - Fee Estimates

• Bitcoin Optech - Fee Estimation

Handling Insufficient Funds

If your algorithm can’t satisfy the payment:

available = sum(effective_values)
required = target_amount + estimated_fee

if available < required:
    return "Insufficient funds"

This is not the same as having insufficient nominal balance. You might have 1 BTC in total but only 0.5 BTC in effective value at 500 sat/vB.

Sanity check: If your wallet shows a balance but can’t send that amount, the issue is likely effective value, not a bug.

Testing Your Algorithm

Good test cases:

1. Single UTXO sufficient: Select exactly one

2. Two UTXOs needed: Select both, no change

3. Change required: Select inputs, create change

4. High fee rate: Verify effective value filtering

5. Mixed UTXO types: Verify type-aware selection

6. Exact amount: No change, perfect fit

7. Dust scenario: Surplus below dust threshold

Sanity check: If your algorithm passes basic tests but fails on a live wallet, you’re probably not handling input type sizes correctly.

What You Should Now Understand

After implementing coin selection, you know:

• Why wallets sometimes use more inputs than seem necessary

• Why high fee rates can cause “insufficient funds” errors

• Why Taproot adoption improves wallet efficiency

• How transaction size affects cost

• When to consolidate UTXOs

This is the hardest conceptual part of wallet development after key derivation.

Implementation Checklist

• Filter UTXOs by confirmation status

• Calculate effective value per UTXO at target fee rate

• Implement sorting strategy (largest, smallest, or effective-value-first)

• Iteratively select inputs until target + fee is met

• Estimate transaction virtual size dynamically

• Handle change output decision based on surplus

• Respect dust threshold (546 sats minimum)

• Validate final transaction meets fee rate requirement

• Handle insufficient funds gracefully

Going Further

The algorithms described here are greedy heuristics. Production wallets use more sophisticated approaches:

• Branch and bound: Explore multiple combinations

• Knapsack optimization: Minimize waste

• Simulation: Test selections against future scenarios

These improve efficiency by 5-20% but add significant complexity.

For most use cases, effective-value-first selection with proper change handling is sufficient.

Resources for Deeper Study

• Bitcoin Optech - Coin Selection

• Mark Erhardt’s Thesis

• Bitcoin Core Coin Selection Code

• BIP141 - Transaction Weight

• Bitcoin Stack Exchange - Coin Selection

In Part 1, you built a wallet that could derive keys, scan the blockchain, and understand its own balance. That alone already puts you ahead of most people who say they “understand Bitcoin.”

In Part 2, things get real.

You are going to create actual Taproot transactions, including a 2-of-2 multisig locked behind a Tapscript, and then spend it via the script-path. This is not a toy example. This is the same transaction machinery used by Lightning channels, DLCs, and modern multisig wallets.

If Part 1 was learning how to read Bitcoin, Part 2 is learning how to speak it fluently, without stuttering, and without relying on libraries to finish your sentences.

What You Are Building

You will construct two transactions, back-to-back.

Transaction 1: Key-Path → Script-Path

Spend a simple Taproot UTXO and fund a 2-of-2 multisig Taproot output.

• Input: One of your existing Taproot UTXOs (key-path spend)

• Output 0: 0.01 BTC to a Taproot script-path multisig (keys 0 and 1)

• Output 1: Change back to yourself

Transaction 2: Script-Path → OP_RETURN

Spend the multisig output you just created.

• Input: The multisig output from Transaction 1

• Output 0: 0 BTC OP_RETURN containing your name or handle

• Output 1: Change back to yourself

Why this matters: You will exercise both Taproot spending paths in a single flow. That is the core mental model behind most modern Bitcoin protocols.

Sanity check: If you can do this without Bitcoin Core holding your hand, you actually understand Taproot.

Bitcoin Transaction Structure (Quick Refresher)

A Bitcoin transaction is just bytes. Opinionated bytes, but bytes nonetheless.

Transaction (no witness):
├─ Version (4 bytes)
├─ Input count (1 byte)
├─ Inputs
│  ├─ Previous TXID (32 bytes, reversed)
│  ├─ Output index (4 bytes)
│  ├─ ScriptSig length (0x00)
│  └─ Sequence (0xffffffff)
├─ Output count (1 byte)
├─ Outputs
│  ├─ Value (8 bytes, little-endian)
│  ├─ ScriptPubKey length (1 byte)
│  └─ ScriptPubKey
└─ Locktime (4 bytes)

Witness (separate):
├─ Marker: 0x00
├─ Flag: 0x01
└─ Witness stack items

TXID is computed from the transaction without witness data. If you include witness bytes, you get a WTXID instead.

Sanity check: If your TXID changes when you tweak a signature, you accidentally hashed witness data.

Part A: Funding the Multisig (Key-Path Spend)

This first transaction is intentionally familiar. You are spending a regular Taproot output using the key-path, just like in Part 1.

The difference is where the money goes.

Step 1: Create the 2-of-2 Multisig Script

In Tapscript, multisig is built using OP_CHECKSIGADD instead of legacy OP_CHECKMULTISIG.

OP_0 <key0_x> OP_CHECKSIGADD <key1_x> OP_CHECKSIGADD OP_2 OP_EQUAL

This works by counting valid signatures and checking that the total equals 2.

Serialized form:

00
20 <key0_x>
ba
20 <key1_x>
ba
52
87

Why x-only keys

Taproot and Tapscript use 32-byte x-only public keys. If your derived public key has an odd Y coordinate, you must negate the private key first.

Sanity check: If you skip Y-parity normalization, everything will compile beautifully and fail cryptographically.

Step 2: Build the TapTree

With a single script, your TapTree is trivial.

TapLeaf = tagged_hash(
  "TapLeaf",
  0xc0 || compact_size(script) || script
)

Because there is only one leaf:

TapTree root = TapLeaf hash

No Merkle branches, no sibling hashes, no drama.

Step 3: Construct the Script-Path Output Key

To force script-path spending, you use a NUMS internal key.

internal_key = NUMS_point

tweak = tagged_hash(
  "TapTweak",
  internal_key_x || taproot_root
)

output_key = internal_key + tweak·G

The witness program is:

OP_1 <output_key_x>

Sanity check: If key-path spending works here, you accidentally used a real internal key instead of NUMS.

Step 4: Build and Serialize Transaction 1

Constraints simplify your life:

• 1 input

• 2 outputs

• Fixed fee

Output 0: 1_000_000 sats → multisig Taproot program
Output 1: change → your key-path Taproot address

No VarInts. No optional fields. No excuses.

Step 5: Compute the Taproot Signature Hash (BIP341)

Taproot signatures commit to everything.

sig_msg = (
  epoch
  hash_type
  version
  locktime
  sha256(outpoints)
  sha256(amounts)
  sha256(scriptPubKeys)
  sha256(sequences)
  sha256(outputs)
  spend_type
  input_index
)

Then:

sighash = tagged_hash("TapSighash", sig_msg)

Sanity check: If you hardcode any hash here, the network will notice. Immediately.

Step 6: Tweak, Sign, Witness

Key-path signing requires tweaking:

tweaked_privkey = privkey + tagged_hash("TapTweak", pubkey_x)

Sign using Schnorr. The witness stack is just:

[ signature ]

At this point, Transaction 1 is complete.

Part B: Spending the Multisig (Script-Path)

Now comes the good part.

You are going to reveal the script, prove it was committed to, and satisfy it with two signatures.

Witness Structure

Script-path witnesses have four items:

[ sig0, sig1, script, control_block ]

Execution is LIFO. What you push last executes first.

Sanity check: If your signatures are valid but verification fails, your stack order is probably wrong.

The Control Block

With one script leaf:

control_block = control_byte || internal_key_x

• control_byte = 0xc0 | parity_bit

• Parity bit reflects the output key, not the internal key

Script-Path Signature Hash (BIP342)

Script-path signatures extend the key-path hash:

+ spend_type = 0x02
+ tapleaf_hash
+ key_version
+ code_separator

No tweaking required. You sign with the raw private keys.

Sanity check: If you tweak here, your signature will be mathematically valid and totally useless.

OP_RETURN Output

This is your on-chain signature, literally.

OP_RETURN <ascii(name)>

Value must be zero. Fees still apply. Immortality is not free.

Implementation Roadmap

1. Reconstruct wallet state

2. Build multisig script

3. Compute TapTree and witness program

4. Construct Transaction 1

5. Sign key-path spend

6. Compute TXID

7. Construct Transaction 2

8. Sign script-path spend

9. Broadcast both

Common Mistakes (All Seen in the Wild)

• Forgetting to negate keys

• Hashing witness data into TXIDs

• Tweaking script-path keys

• Reversing TXIDs incorrectly

• Misordering witness stack items

• Forgetting compact-size prefixes

If you hit one of these, congratulations. You are learning the hard way, like everyone else.

Validation

Use:

bitcoin-cli -signet testmempoolaccept '["<tx1>","<tx2>"]'

Both must return allowed: true.

What You Now Understand

You have implemented:

• Taproot key-path spending

• Taproot script-path spending

• Tapscript multisig

• Schnorr signatures

• Control blocks and TapTrees

• Full transaction serialization

This is not academic knowledge. This is production-grade Bitcoin plumbing.

Closing Thoughts

You started with a seed phrase.

You ended with a fully functioning Taproot multisig wallet that can construct, sign, and broadcast real transactions without any Bitcoin libraries.

That is how you actually learn Bitcoin.

Everything else is just UI.

Most Bitcoin wallets feel magical. You import a seed phrase, and suddenly balances, addresses, and transaction history appear. But nothing about this process is magic; it’s deterministic, mechanical, and surprisingly small in scope.

At its core, a wallet does only four things:

1. Derives keys from a root secret

2. Turns those keys into output scripts

3. Scans the blockchain for matching outputs

4. Subtracts what has been spent

In this article, we’ll rebuild that process for a Taproot (P2TR) wallet on signet, without using Bitcoin Core’s wallet functionality or any Bitcoin-specific wallet libraries. The goal isn’t to produce production-ready code, but to develop a correct mental model of how modern wallets actually work.

This is Part 1. We stop once we can deterministically recover a wallet’s confirmed balance from the blockchain alone. In Part 2, we’ll spend those coins.

Resources:

• Signet Documentation

• Mastering Bitcoin - Chapter 5: Wallets

What This Wallet Actually Knows

An important framing:

A wallet does not “know” its balance.

Instead, it knows:

• A descriptor that defines how keys and scripts are derived

• A set of derived witness programs it cares about

• A list of unspent transaction outputs (UTXOs) it has discovered so far

Everything else, balances, transaction history, and “accounts”, is derived from those three inputs.

Sanity check:
If you delete your local UTXO set and rescan the chain, you should recover the exact same balance; if not, your wallet is stateful in the wrong way.

Resources:

• BIP32 - Hierarchical Deterministic Wallets

• BIP86 - Taproot Key Derivation

Wallet Descriptors as Executable Policy

We start with a descriptor like:

tr(tprv8ZgxMBicQKsPe.../86h/1h/0h/0/*)

This string encodes policy, not just a key.

Breakdown:

tr(                     # Taproot output
  tprv...               # Extended private key
  /86h/1h/0h/0/*        # BIP86 derivation path
)

Key observations:

• The descriptor fully defines how addresses are generated

• The * means “derive as many child keys as needed”

• No blockchain data is required to derive addresses

If two wallets share the same descriptor, they will derive the same addresses forever.

Sanity check:
Import the descriptor into Bitcoin Core or another wallet and confirm that the first derived address matches yours exactly; a single mismatch here invalidates everything downstream.

Resources:

• Learn Me a Bitcoin - Wallet Descriptors

Extended Keys: What’s Actually Inside a tprv

An extended private key is not just a private key. Conceptually, it contains:

Extended Private Key
├── depth
├── parent fingerprint
├── child index
├── chain code (32 bytes)
└── private key (32 bytes)

The chain code is what enables deterministic key derivation; without it, you cannot derive siblings or children.

After Base58Check decoding, most wallet logic only needs:

• private_key

• chain_code

The remaining fields exist for bookkeeping and compatibility.

Sanity check:
The private key must be a 32-byte integer strictly less than the secp256k1 curve order; if it’s zero or ≥ n, decoding failed.

Resources:

• Mastering Bitcoin - Chapter 5: Wallets

Walking the Derivation Path (BIP32 + BIP86)

The derivation path:

m / 86h / 1h / 0h / 0 / i

means:

• 86h → BIP86 (Taproot single-key wallets)

• 1h → test networks (signet/testnet)

• 0h → wallet / account

• 0 → external (receiving) chain

• i → address index

Each step produces a new (private_key, chain_code) pair.

Hardened vs Non-Hardened

Hardened derivation (h) uses the parent private key as input; non-hardened derivation uses the parent public key.

This distinction matters:

• Hardened steps prevent key-compromise attacks

• Non-hardened steps enable watch-only wallets

By the time you reach /0/i, derivation is intentionally non-hardened.

Sanity check:
Child public keys derived from a parent public key must exactly match the public keys derived from the private path at the same index.

Resources:

• BIP32 - Hierarchical Deterministic Wallets

From Private Key to Taproot Witness Program

Taproot introduces a few non-obvious but mandatory steps.

Step 1: Compute the Public Key

Using secp256k1:

P = k × G

Taproot uses x-only public keys, which introduces a constraint.

If P.y is odd:

k = n − k
P = −P

This ensures the Y coordinate is even.

Sanity check:
After normalization, the public key’s Y coordinate must be even; normalizing twice will silently break key correspondence.

Resources:

• BIP340 - Schnorr Signatures

• BIP341 - Taproot

Step 2: Apply the Taproot Tweak

Even a key-only Taproot output must be tweaked.

Conceptually:

tweak = H_TapTweak(internal_pubkey)
output_pubkey = internal_pubkey + tweak × G

Visually:

internal key  ──┐
                ├─ hash + scalar add ──► output key
(empty script) ─┘

The tweak commits to the script tree. When no scripts exist, it commits to an empty tree, but the tweak is still required.

Sanity check:
The tweak must use a tagged hash; a plain SHA256 will generate valid-looking but unusable outputs.

Resources:

• Bitcoin Optech - Taproot Workshop

Step 3: Build the Witness Program

The final output is a versioned witness program:

OP_1 <32-byte output public key>

In hex:

51 20 <32 bytes>

This 34-byte program is what appears in transaction outputs and what the wallet scans for.

Sanity check:
The witness program must be exactly 34 bytes; any other length indicates encoding errors.

Precomputing Wallet Witness Programs

Your wallet now:

• Derives N child keys (e.g., indices 0–1999)

• Converts each into a Taproot witness program

• Stores them in a fast lookup structure

Conceptually:

wallet_programs = {
  program_0,
  program_1,
  program_2,
  ...
}

This defines the wallet’s search domain.

Sanity check:
Re-deriving index 0 across runs must produce identical witness programs; any nondeterminism invalidates scanning.

Resources:

• Mastering Bitcoin - Chapter 5: Wallets

How Balance Recovery Actually Works

Wallet balance recovery is UTXO accounting.

Conceptual Algorithm

UTXOs = {}

for each block:
  for each transaction:
    for each output:
      if output.script in wallet_programs:
        UTXOs.add(outpoint, value)

    for each input:
      if input.spends(outpoint in UTXOs):
        UTXOs.remove(outpoint)

Balance is:

sum(utxo.value for utxo in UTXOs)

No addresses, no accounts; only scripts and outpoints.

Sanity check:
If you stop scanning at height H, your balance must match a full node’s balance at height H for the same descriptor.

Resources:

• Bitcoin Core RPC Documentation

Edge Cases Worth Handling Explicitly

• Coinbase transactions
  Have no inputs; maturity affects spending, not balance discovery

• Receive and spend in the same block
  Possible; transaction ordering matters

• Reorgs
  Out of scope here; real wallets must rewind state

Sanity check:
Scanning blocks in a different order must not change the final balance; order dependence indicates flawed logic.

Bitcoin Core as a Stateless Data Source

Bitcoin Core can run with:

disablewallet=1

RPC is used only to:

• Fetch block hashes

• Retrieve full block data

• Decode transactions

All wallet logic lives outside the node.

Sanity check:
Restarting Bitcoin Core must not affect your recovered balance.

Resources:

• Bitcoin Core Configuration

End-to-End Data Flow

Descriptor
   │
   ▼
Extended Private Key
   │
   ▼
BIP32 Derivation
   │
   ▼
Private Keys
   │
   ▼
Public Keys (x-only)
   │
   ▼
Taproot Tweaks
   │
   ▼
Witness Programs
   │
   ▼
Blockchain Scan
   │
   ▼
UTXO Set
   │
   ▼
Balance

Sanity check:
Every step above must be deterministic; if any output changes across runs, downstream debugging is pointless.

Why This Is Worth Doing

After implementing this, you understand:

• Why wallets must rescan the chain

• Why Taproot outputs look uniform on-chain

• How balance recovery works without trusting software

• Where wallet abstractions come from

This is the hardest conceptual part.

Next: Spending What You Found

In Part 2, we’ll:

• Select UTXOs

• Construct Taproot transactions

• Spend via key paths and script paths

• Understand exactly what Bitcoin nodes verify

Balance recovery answers where your bitcoin is;
spending answers why the rules work.

Additional Resources:

• Learn Me a Bitcoin - HD Wallets

• BIP341 - Taproot: SegWit version 1 spending rules

• Bitcoin Optech - Taproot Workshop

Before we talk about what Florida did, we need to talk about how they ended last season.

Beating FSU Still Matters, A Lot

You can measure progress in recruiting rankings, SP+ charts, EPA per play, and whatever new metric someone just invented to dunk on rivals, but there are still moments that define whether a season feels like it’s moving forward or spinning its wheels.

Beating Florida State is one of them.

Ending the year by beating your biggest rival does something important, it resets the emotional temperature of the fanbase. It turns “fire everyone” into “okay, but let’s see,” turns doomscrolling into cautious optimism scrolling, and gave Florida the ability to enter this offseason with momentum instead of desperation.

That matters more than people realize, especially on Twitter.

The Lane Kiffin What-If

Let’s be honest, a lot of Florida fans wanted Lane Kiffin. The offense. The swagger. The memes. The idea of winning games and quote-tweeting recruits at the same time.

Missing out on him felt like losing. For at least 48 hours, Gator Twitter was in full “this program is unserious” mode.

But the longer this offseason has gone on, the more it’s started to look like Florida may have sidestepped a very loud, very public, very chaotic transition.

Between LSU’s ongoing circus and the fallout at Ole Miss, the coaching carousel has reminded us that high profile does not equal high stability. Hiring Lane means you’re not just hiring an offense, you’re hiring discourse, burner accounts, rumors, and weekly “is he leaving?” threads.

Hot yoga gyms around Gainesville can finally exhale.

Jon Sumrall Is the Opposite of Chaos

When Florida announced Jon Sumrall, the immediate reaction was muted at best. It wasn’t outrage, but it also wasn’t joy. It was mostly a collective, “oh… that’s it?” from a fanbase that had spent weeks refreshing FlightRadar24 and manifesting unrealistic dreams.

He didn’t feel like a win; he felt like a reset, and resets don’t trend.

Then he walked into his opening press conference and immediately started cooking.

Sumrall was self-aware, like, actually self-aware. He acknowledged the moment, the noise, and the fact that Florida is a proud, impatient, scarred fanbase that has been promised too many “processes” and not enough Saturdays worth bragging about. He didn’t pretend this was a quiet rebuild. He didn’t try to sell patience. He sold accountability.

And then he said the line that quietly changed the temperature in the room:

"Judge me for who I am. I'm a winner. We're going to win."

Which is an insane thing to say unless you fully understand where you are and what you’re walking into. He wasn’t promising dynasties. He wasn’t promising miracles. He was promising that this program doesn’t end with him, it starts with him.

He was passionate, confident, and just cocky enough to make you feel like he believes he belongs here, without crossing into “I’m about to fight a reporter” territory. It wasn’t quite the Cignetti “Google me” presser, but it was a very respectable knock-off.

Since then, he’s backed that tone up with actions. He didn’t show up and hire his friends, he didn’t bring in a pre-packaged system and dare the roster to survive it. He’s been consistent about building around the talent already here, not forcing square pegs into philosophical round holes, which somehow still feels like a novel concept in Gainesville.

Most importantly, he seems to understand where Florida football actually is. Not where Twitter wants it to be, not where the brand commercials say it should be, but where it really is: talented, frustrated, hungry, and in desperate need of functional structure. That awareness alone is refreshing; the rest of the offseason is starting to make it feel intentional.

Early Signing Day: Stability Is the Story

Florida didn’t dominate the early signing period. They didn’t chase every five-star with a ring light and a TikTok edit. They didn’t try to “win December,” but they also didn’t bleed talent, which is, frankly, a win.

Holding things together after hiring a coach two days before signing day is quietly impressive. That doesn’t happen without organization, communication, and a staff that understands how recruiting actually works, not just how to tweet about it.

Credit goes to Sumrall and his staff, but also to Billy Napier and Billy Gonzales for leaving behind a recruiting foundation that didn’t immediately collapse the moment a new head coach walked in the door. For once, Florida benefited from continuity instead of being haunted by it—a strange feeling, almost unsettling.

The Staff Hires Are Where This Gets Interesting

If Sumrall is the foundation, his staff is the blueprint, and this is where the offseason actually starts to cook:

• Buster Faulkner, offensive coordinator from Georgia Tech, brings a modern, QB-friendly system built on tempo, spacing, and efficiency. He’s adapted his offense to wildly different personnel groups over the years, which suggests he understands football as a game, not a philosophy podcast.

• Brad White, defensive coordinator from Kentucky, brings SEC-level physicality and development. I don’t love everything about the Kentucky scheme, but it’s also hard to separate White from Mark Stoops, who might actually be powered entirely by defensive meetings.

• Phil Troutwine, offensive line coach from Penn State, is a program-shifting hire. Development, toughness, identity. For years, Florida has tried to skill-position its way out of trench problems like it’s playing NCAA 14 on freshman mode. Troutwine is a former Gator and arguably the best offensive line coach in the country. The fact that Sumrall landed a guy Billy Napier was allegedly trying to hire for years tells you everything you need to know.

This staff wasn’t assembled for vibes; it was assembled to fix actual problems.

The Schedule Is… Reasonable?

There are no easy SEC schedules anymore, that’s the baseline. But next year’s slate is manageable, which is not something Florida fans have been allowed to say recently without being accused of cope.

Better spacing, fewer back-to-back nightmares, actual opportunities to build momentum instead of immediately being tested like it’s a CFP semifinal in September. Nine wins isn’t a dream scenario anymore; it’s a realistic one, assuming competent quarterback play, functional offensive line development, and the football gods taking a single year off from tormenting us.

The Portal: DJ Out, Stability In

Yes, DJ entering the portal hurts; that’s real. But if we’re being honest, how upset can we really be about losing the quarterback of a four-win team? He cost Florida games last year, which is unfortunately more memorable than the games he won the year before.

The bigger story is who didn’t leave.

So far, there aren’t many departures that genuinely hurt, with one massive potential exception, Jadan Baugh. Texas thinks they have him; Florida is reportedly fighting like hell to keep him. Nobody knows anything for sure, which means Twitter definitely knows everything. TBD.

Still, the roster has largely stayed intact, and that hasn’t been the norm around here lately. That’s one of the clearest signs that something has changed inside the building.

What This All Means

Games still need to be played, you don’t win anything in the offseason, and I am going into this staff extremely skeptical; I’ve been scarred by too many relationships in the past and refuse to feel joy too early.

But so far, I like the direction.

This offseason wasn’t loud, it wasn’t flashy, it didn’t dominate timelines, and for Florida football right now, that might be exactly the point.

Seriously. I know what happens. I’ve seen the homages, the parodies, and the TikToks. Here’s your definitive guide to movies people freak out over, why I don’t need to watch them, and modern alternatives that deliver the same experience without requiring me to memorize the original scripts.

Caveat: To be clear, this doesn’t mean I haven’t seen or won’t watch older movies, just that if I haven’t seen it by now, I’m good.

1️⃣ Goodfellas (1990)

What I know:
Ray Liotta laughing like his soul depends on it. Joe Pesci yelling “Funny how?” at someone who dared to exist. A one-shot through a restaurant dissected in every film class ever. Mobsters doing mobster things until consequences arrive.

Why I don’t need to see it:
Everyone post-1995 copied it anyway, and I’ve seen all the knockoffs. I’m culturally fluent without ever pressing play.

Modern Alternative: The Departed (2006) — Chaos, betrayal, and a mob underworld that feels just as brutal, but with cell phones, modern editing, and fewer lectures.

2️⃣ Citizen Kane (1941)

What I know:
Rosebud. A guy dies. Critics insist it’s the greatest movie ever because they once had a film theory class. Iconic shots and angles that are now so normal nobody notices.

Why I don’t need to see it:
Every joke and reference has already reached me. I’ve got the cultural gist. No need to watch a newspaper magnate mope around his mansion.

Modern Alternative: The Social Network (2010) — Rise-and-fall of a brilliant, morally complicated man. Same energy, better pacing.

3️⃣ Casablanca (1942)

What I know:
A smoky nightclub. Tragic romance. Bogart looking world-weary. Lines like “Here’s looking at you, kid”. I’ve heard these quotes more than my own voicemail.

Why I don’t need to see it:
Quote montages and memes have already shown me the emotional beats. Watching it now is basically bonus content.

Modern Alternative: La La Land (2016) — Big romance, dramatic choices, same longing, with jazz hands and color that doesn’t make your eyes go gray.

4️⃣ Gone With the Wind (1939)

What I know:
Scarlett O’Hara. Plantation drama. Four-hour runtime. Debates about whether it aged like fine wine or spoiled milk.

Why I don’t need to see it:
Length + cultural baggage = I already have the gist. Watching it wouldn’t teach me anything new.

Modern Alternative: Titanic (1997) — Epic romance, historical stakes, long runtime, infamous sinking. Less homework, more icebergs.

5️⃣ 2001: A Space Odyssey (1968)

What I know:
Monoliths. Primate evolution. HAL refusing to open pod bay doors. Psychedelic tunnels. Confusing but iconic.

Why I don’t need to see it:
Every sci-fi film since 1970 has already referenced it. Watching feels like reverse-engineering a meme.

Modern Alternative: Interstellar (2014) — Philosophy, space, emotional stakes, clear explanations, same awe factor, faster pacing.

6️⃣ The Fugitive (1993)

What I know:
Doctor wrongly accused of murdering his wife, chased across the country. Iconic train and hospital scenes. Everybody references the chase, suspense, and moral righteousness.

Why I don’t need to see it:
The story exists in pop culture fragments. I’ve effectively seen it via memes and parodies. No need to sit through it.

Modern Alternative: The Prestige (2006) — Twists, deception, obsession, and morally complex decisions. Sleek, modern, and keeps you guessing.

7️⃣ Taxi Driver (1976)

What I know:
“You talkin’ to me?” Lonely, angry antihero spiraling through 1970s NYC. Gun violence, moral ambiguity, neon-lit despair. I’ve seen his archetype in every brooding character since.

Why I don’t need to see it:
Every gritty, morally ambiguous protagonist since 1980 is basically Travis Bickle in slow motion.

Modern Alternative: Joker (2019) — Same descent into chaos, color grading, modern music, city that feels like it’s unravelling.

8️⃣ A Clockwork Orange (1971)

What I know:
Milk bars. Eye clamps. Stylized ultraviolence. Film everyone insists you watch to prove you’re edgy or cultured.

Why I don’t need to see it:
Its visuals are more famous than its story. I’ve absorbed the aesthetic without pressing play.

Modern Alternative: V for Vendetta (2005) — Dystopia, rebellion, moral ambiguity, and stylized violence accessible to mortals.

9️⃣ Blade Runner (1982)

What I know:
Neon rain. Replicants. Harrison Ford exhaustedly brooding. Everyone calls it a masterpiece but warns it’s “slow.”

Why I don’t need to see it:
Decades of inspired movies, video games, and anime have delivered the aesthetic. I get it.

Modern Alternative: Blade Runner 2049 (2017) — Same universe, modern pacing, sound design that rattles your soul.

🔟 Lethal Weapon (1987)

What I know:
Two mismatched cops. Explosions. Christmas lights. Classic one-liners. “I’m too old for this shit.” Every buddy-cop movie since 1990 is basically fan fiction.

Why I don’t need to see it:
I’ve absorbed the energy, jokes, and chemistry via countless imitators and references.

Modern Alternative: Bad Boys II (2003) — Banter, chaos, car stunts, explosions, and Will Smith being charmingly unhinged.

The Takeaway

These films mattered. Once. But their fingerprints are everywhere: memes, quotes, shows, and modern blockbusters. I’ve absorbed the cultural energy without ever needing to hit “Play.”

Cultural osmosis: undefeated.
Movie gatekeepers: permanently frustrated.

And hey — feel free to add more movies to this list in the comments, and I promise I’ll make sure not to watch them.

Every offseason, some fanbase starts the same cycle:
“Trust the process.”
“Year five is when it finally clicks.”
“He just needs his recruits.”

The sport keeps running the same experiment — and the answer never changes.

Since 1990, national championship coaches have needed about six seasons to win their first title.
In the modern era — BCS and Playoff — that number falls closer to five.
The sport’s gotten faster. Expectations have too.

The Four-Year Reality Check

When you look at the rare coaches who needed more than four years, the pattern barely changes.

Of the seven who took longer in the BCS/Playoff era — Bowden, Mack Brown, Dabo, Kirby, Fulmer, Day, and Harbaugh — six had already:

• Won a conference title,

• Reached the national championship, or

• Made the playoff
  by the end of Year Four.

Only Jim Harbaugh at Michigan broke that pattern — the single outlier in three decades.

That means 86% of national-title coaches had already hit major contention benchmarks within their first four years.

📊 The Pattern Is Clear

*(Side note: Bobby Bowden’s 1993 title came 18 years in, but Florida State didn’t join the ACC until 1992. From that point forward, he immediately won nine straight conference titles and played for multiple national championships. His clock started later — and he was elite from the jump.)

What That Means for Athletic Directors

The takeaway isn’t that patience never pays. It’s that proof shows up fast.

When you hire the right coach, you don’t have to squint to see it — the wins, the energy, the recruiting all show up early.

• Urban Meyer had Florida in the BCS title game in Year 2.

• Kirby Smart won the SEC and nearly a natty in Year 2.

• Dabo Swinney had Clemson winning the ACC by Year 3.

• Nick Saban? LSU in Year 4, Alabama in Year 3.

These aren’t coincidences. They’re patterns.

A coach doesn’t suddenly figure out how to win a national title after six mediocre seasons. They either set that trajectory early, or they don’t.

The Clock Starts Now

So the next time a program tries to sell patience as a strategy — that “it just takes time” — remember this:

Since 1998, only one national championship coach didn’t have a conference title or a playoff appearance within their first four seasons. One.

The slow-build story sounds nice on talk radio.
But history doesn’t buy it — and neither should you.

As a data-minded Gator fan, I want a coach who wins through tactics and precision, not noise. Here’s who fits, who doesn’t, and who’s staying put.

Why Florida Still Matters

This is the number one job currently available, and it’ll likely stay that way unless LSU pulls the trigger on Brian Kelly. That’s an advantage we didn’t have last cycle.

Resources & Support:

• Top-15 athletic budget ($200M+) with aggressive NIL infrastructure through the Gator Collective

• SEC membership means College Football Playoff access and national TV exposure every week

• $90M football facility upgrades completed in 2023, among the best in the country

Recruiting Advantages:

• Most talent-rich state in America. Seven of the top 50 recruits nationally come from Florida every year

• Natural recruiting territory from Jacksonville to Miami, minimal in-state Power 4 competition

• Brand recognition that still resonates with elite recruits despite recent down years

Program Foundation:

• Young roster with multiple NFL-caliber players already in place

• Three national titles, consistent top-10 recruiting classes

• The Swamp. One of the most intimidating home-field advantages in college football

This isn’t a rebuild. The right coach walks into 9–10 wins in Year 2.

What I’m Looking For

None of these are hard rules, but here’s the profile:

1) Offensive innovator: Not just an “offensive guy”, someone who gameplans around what the defense can’t handle and attacks it every week. I want a coach who wants to win by 50, not one trying to hold on and win by 1.

2) Established head coach: Preferably already at the P4 level. There are no obvious coordinators ready to make the leap this cycle (no Kirby Smart or Will Muschamp types).

3) Cultural fit: He needs to fit the brand at Florida. For better or worse, Spurrier shaped how many Florida fans watch football, even those born after he stopped coaching. Florida fans want a quick-witted, Fun ‘n’ Gun-loving offensive guy who doesn’t mind poking fun at other schools and doesn’t take it all too seriously.

Lane Kiffin (Ole Miss)

If you look at my criteria, one guy checks every box: Lane Kiffin. If you’d told me five years ago that Lane Kiffin would be the number one candidate for the UF job, I would’ve thought you were insane. But here we are.

What you’re getting: A proven offensive juggernaut builder and elite recruiter who wins in the SEC, manages NIL and the transfer portal aggressively, and brings instant national attention.

Data & Track Record

• Ole Miss results: Multiple 10-win seasons (2021, 2023, potentially 2025), consistently top-15 offenses, Top 20 in SP+ offense every year since 2020

• Quarterback success: Coached Matt Corral (3rd-round pick) and Jaxson Dart (1st-rounder) to elite statistical outputs

• Roster strategy: Among the first SEC coaches to master the transfer portal as a roster-building tool. Ole Miss’s 2024 roster included 20+ impact transfers

Why This Works

• Instant relevance: He’s a media magnet. Florida would immediately become must-watch TV, which boosts recruiting and NIL participation overnight

• Offensive identity: Explosive, aggressive play-calling that perfectly suits Florida’s talent-rich offensive pipeline

• NIL and portal mastery: He’s built rosters better than almost anyone. He’ll maximize Florida’s financial advantages

• SEC-proven: He’s beaten Alabama, Georgia, and LSU. He knows what it takes to win in this conference

The Risk: Kiffin’s “volatility” isn’t just his personality, it’s job-hopping. He left USC, Tennessee (infamously), FAU, and he could leave Ole Miss. There’s a real risk he views Florida as a 3–4 year stop before the NFL or another opportunity.

What It’ll Cost: Ole Miss pays him $9M annually with escalators. Florida needs to offer $11–12M to make it worth leaving, plus pay a significant buyout (likely $15M+). This is a $25M+ investment upfront.

The Verdict: High offensive ceiling, most SEC-ready splash hire available. But you’re betting on short-term success over long-term stability. Honestly? We’ll probably be back here in four years no matter who we hire. I’d rather it’s because Kiffin left for the NFL than because we had to fire another guy who couldn’t win.

Curt Cignetti (Indiana)

Cignetti is the reason we should’ve fired Billy last year. If we’d fired him before the Texas game last season instead of giving him that vote of confidence, we could’ve hired Cig away from Indiana at a relatively low cost. Now if we want him, it’s going to cost a small fortune.

What you’re getting: A proven winner who builds discipline and structure. He wins fast, develops quarterbacks, and gets more from his roster than expected.

Data & Track Record

• Immediate success everywhere:

  • James Madison: 10–0 start in 2023, Top 25 finish

  • Indiana: 8–0 start in 2024, program’s best mark in decades

• Program versatility: Succeeded at IUP, Elon, JMU, and Indiana. Adapts across resource levels and conference types

• QB development: Multiple efficient, low-turnover quarterbacks. Strong tactical organization

Why This Works

• Maximizes current roster: He’ll elevate blue-chip talent through precision rather than waiting on multiple recruiting cycles

• Culture-first stability: Brings professionalism and accountability, both things UF has lacked post-Mullen

• Tactical soundness: His offenses control tempo and protect the ball. His defenses match the plan

• Defensive competence: Indiana ranked Top 40 in defensive efficiency in 2024. Proof he builds both sides

The Risk: Cignetti’s success came outside the SEC grind. Indiana’s 2024 schedule strength ranked outside the Top 50. His disciplined, lower-variance approach hasn’t faced Georgia, LSU, and Texas week after week. And he hasn’t recruited against SEC coaches who’ve been doing this for years.

What It’ll Cost: Indiana just gave him an 8-year, $72M extension. Florida needs to offer $12M+ annually and absorb a massive buyout (likely $15M+). This is a $30M+ decision upfront.

The Verdict: Immediate credibility, highest floor of anyone on this list. Safest pick. But you’re betting his system scales to elite competition. At the end of the day, Cignetti just wins, “Google him”.

Jedd Fisch (Washington)

I really wish we had one more year to see how Washington looks next season. He’s got something brewing there after just two years, and I’d love one more year of evidence before pulling the trigger on hiring him.

What you’re getting: Florida alum with NFL and Power 5 experience. Exceptional quarterback developer and offensive strategist who gets Gator culture.

Data & Track Record

• Pro pedigree: Worked for the Patriots, Rams, and Seahawks. Multiple NFL offensive staffs under Belichick, McVay, and Carroll

• College success: Turned Arizona into a top-20 offense (2022), now running a strong program at Washington in Year 2

• QB growth: Developed Jayden de Laura and Michael Penix Jr. into elite collegiate passers. Penix finished 2nd in Heisman voting

Why This Works

• Deep Florida ties: UF alum, former Gator GA. Immediate credibility with boosters and local recruits. Already has relationships in-state

• NFL-ready system: Pro-style offense appeals to quarterbacks and skill players who want to prepare for the league

• Game-plan flexibility: Weekly adaptability. Attacks what you can’t do rather than forcing scheme fit

• Defensive hiring acumen: Brought in Steve Belichick at Washington. Knows you need both sides of the ball

The Risk: Fisch left Arizona after three years for Washington. Will he view Florida as a stepping stone to an even bigger job? He’s said in the past this is his “dream job,” so hopefully not, but it’s something to keep in mind. His offenses are innovative, but he’s still building his head coaching résumé. Washington is 6–5 in Year 1 of the Big Ten, solid but not spectacular.

What It’ll Cost: Washington pays him $7.5M annually. Florida could offer $9–10M to make it worth the move, with a reasonable buyout of $10–12M. More feasible than Cignetti financially.

The Verdict: Modernized offense, recruiting credibility in-state, NFL pedigree, tactical acumen, cultural fit. Most “Florida-ready” candidate on this list.

Alex Golesh (USF)

Here’s something interesting: Tennessee fans are terrified we’re going to hire Golesh. They know what he can do, they watched him build the nation’s #1 offense in 2022 before he left for USF. He checks the offensive boxes pretty clearly, but he’s coming from a G6 school, which will be a problem for some people. He isn’t my first choice, but he’s someone we should be able to get if we want him.

What you’re getting: Rising star who modernized offenses at Tennessee and quickly elevated USF. Creative mind who could instantly raise Florida’s scoring ceiling.

Data & Track Record

• Elite offensive results:

  • Tennessee OC (2022): Nation’s #1 offense in scoring (49.4 PPG) and total yards (539 YPG)

  • USF (2024–25): Bowl-eligible turnaround, Top 50 recruiting class—best in a decade

• Player development: Produces explosive wide receivers and efficient quarterbacks in uptempo systems. Hendon Hooker’s breakout year came under Golesh

Why This Works

• Offensive fireworks: Modern pace, spacing, and big-play design that recruits love. Florida’s offense would immediately become a national talking point

• Recruiting energy: Young, innovative, social-media savvy. Resonates with players in the NIL era. Already recruiting Florida’s top talent to USF

• QB appeal: His system guarantees exposure, production, and NFL tape. Would make Florida a top destination for transfer quarterbacks

• Defensive awareness: At USF, hired coordinators who understand complementary football. Won’t ignore defense

The Risk: Golesh has one year of head coaching experience. When things go wrong, he has no track record. The CEO responsibilities at an SEC program, boosters, media, recruiting infrastructure, there’s a massive gap between USF’s expectations and Florida’s. His floor is unknown.

What It’ll Cost: USF pays him $2.25M annually. Florida could get him for $7M, with minimal buyout ($3–5M). Cheapest hire on the list by far.

The Verdict: High-upside, offense-first rebuild with recruiting buzz. Swing-for-the-fences choice. But you’re betting on potential over proven results at this level.

Coaches I’d Love But Who Aren’t Leaving

These are guys I’d take immediately, but they have no incentive to leave. So they aren’t going to be the new coach, but I wanted to at least list them here.

• Lincoln Riley (USC): Still refining his defensive staff, but USC’s resources and West Coast isolation match his ambitions

• Marcus Freeman (Notre Dame): Program culture and alignment are ideal right now. Notre Dame gives him everything he needs

• Curt Cignetti (Indiana): After his extension, he probably belongs here too. But he’d be worth breaking the bank for

• Dan Lanning (Oregon): Despite the fact he isn’t going to leave, it would be funny for the last three Oregon coaches to all leave for the Big 3 Florida schools (Taggart to FSU, Mario to Miami, and Lanning to UF)

Names You’ll Hear But I’d Avoid

Eli Drinkwitz (Missouri)

The Case For: Missouri has been competitive in the SEC under Drinkwitz, averaging 8+ wins since 2021. Solid developer, disciplined teams.

Why I’d Pass: Too conservative schematically. His offensive creativity stalls against top-tier athletes. Missouri scored 10 points against Georgia in 2024 and 14 against Alabama. Florida needs someone who can win shootouts and exploit elite talent, not grind out 7-yard runs against inferior competition. His ceiling feels like “9 wins and a decent bowl”—fine for Missouri, insufficient for Florida.

Data Point: Missouri ranked 52nd in offensive SP+ in 2024 despite having multiple NFL-caliber skill players. That’s a coaching problem, not a talent problem.

James Franklin (Penn State)

The Case For: Elite recruiter. Penn State consistently finishes with Top 15 classes. Polished with the media, handles boosters well, teams always competitive.

Why I’d Pass: Great recruiter, mediocre tactician. Penn State is 1–10 against top-5 opponents under Franklin. They consistently lose the games that matter because he gets outcoached in critical moments. Florida doesn’t need another coach who recruits well but can’t adjust in the fourth quarter. We just had that with Napier.

Data Point: Penn State ranks 35th nationally in yards per play against ranked opponents since 2020. Not a talent issue—a coaching issue.

Summary

Florida’s next hire should blend tactical intelligence with offensive innovation.

The good news: Florida has options. The resources, talent, and recruiting advantages make this a destination job. The next coach isn’t inheriting a rebuild, they’re inheriting a roster capable of competing for the SEC in Year 2, not to mention a much more favorable schedule (as far as SEC schedules go) than the one Billy was handed.

Hire the right guy, and we’re in the playoff by 2026. Hire the wrong one, and we’re right back here in three years, writing the same damn post about the next search.

This is a standalone configuration guide for setting up reliable Lightning node monitoring using a modern Go-based monitoring tool. Unlike the complex web interfaces that tend to break (RTL crashes, ThunderHub throws 500 errors), this approach uses simple Telegram notifications that actually work.

This guide assumes you’ve already completed the main Lightning node setup from Phase 1, Phase 2, and Phase 3. If you haven’t, go do that first.

The Problem with Lightning Node Monitoring

Running a Lightning node means stuff happens: channels open, channels close, payments flow through, fees get earned, balances change, servers reboot. You want to know about the important stuff without constantly checking lncli getinfo.

After trying various monitoring solutions, the reality is that simple, reliable notifications beat fancy dashboards that don’t work. Telegram bots are reliable, free, and work from anywhere. No web servers to crash, no dependencies to break.

What You’ll Monitor

This setup will ping you for:

• Server reboots (uptime tracking)

• Lightning channels opening (pending and confirmed)

• Lightning channels closing (initiated and completed)

• Lightning forwards with fee earnings

• Invoice payments received

• Balance changes (on-chain, Lightning local/remote, total portfolio)

• Formatted amounts (automatically shows BTC/millions/thousands/sats)

No spam, just actionable events when they actually happen.

1. Setting Up Telegram Bot Notifications

Create Your Telegram Bot

1. Message @BotFather on Telegram

2. Send /newbot

3. Choose a name like “Lightning Node Bot”

4. Choose a username like “your_lightning_bot”

5. Save the bot token (looks like 123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ)

Get Your Chat ID

1. Message @userinfobot on Telegram

2. Note your Chat ID (looks like 123456789)

2. Install the Lightning Node Tools

Clone the Management Repository

The monitoring system is now part of a comprehensive Lightning node management toolkit:

# Clone the lightning-node-tools repository
git clone https://github.com/brewgator/lightning-node-tools.git
cd lightning-node-tools

Build and Install

# Build the monitoring tool
go build -o telegram-alerts cmd/telegram-alerts/main.go

# Make executable
chmod +x telegram-alerts

# Create monitoring directory for state files
mkdir -p ~/lightning-monitor

3. Configure the Monitor

Set Environment Variables

Create a configuration file or set environment variables:

# Create config file
cat > ~/.lightning-monitor-config << ‘EOF’
BOT_TOKEN=YOUR_BOT_TOKEN_HERE
CHAT_ID=YOUR_CHAT_ID_HERE
EOF

# Or export directly
export BOT_TOKEN=”YOUR_BOT_TOKEN_HERE”
export CHAT_ID=”YOUR_CHAT_ID_HERE”

Test the Setup

# Run manually to test
./telegram-alerts

# You should receive a startup message in Telegram with:
# - Current channel count
# - Balance summary (on-chain, Lightning local/remote, total)
# - System status

4. Deploy and Automate

Set Up Cron Job

# Add to crontab to run every 2 minutes
crontab -e

# Add this line:
*/2 * * * * /home/$(whoami)/lightning-node-tools/telegram-alerts

Or use the one-liner:

(crontab -l 2>/dev/null; echo “*/2 * * * * $(pwd)/telegram-alerts”) | crontab -

Verify Deployment

# Check cron was added
crontab -l

# Monitor for first few runs
tail -f /var/log/syslog | grep telegram-alerts

What You’ll See

Balance Change Notifications

The Go version includes smart balance tracking with formatted amounts:

📈 Lightning Local Balance increased
Change: 125.3K sats  
Current: 2.45M sats

📉 On-chain Balance decreased
Change: 0.01050000 BTC
Current: 0.15000000 BTC

⚠️ 📈 Total Portfolio Balance increased  
Change: 5.25M sats
Current: 0.25000000 BTC

Breakdown:
On-chain: 15.5M sats (+2.1M)
Lightning: 9.75M sats (+3.15M)

Channel Events

Channel Opened
New active channels: 1
Total active channels: 8

Forward Activity

Lightning Forwards
Recent forwards: 3
Fees earned: 156 sats

Advanced Features

Configurable Thresholds

The Go version includes smart thresholds to prevent notification spam:

• Balance Threshold: Only notifies for changes > 10k sats (configurable)

• Significant Threshold: Large changes (> 1M sats) get special attention with ⚠️

• Smart Formatting: Automatically chooses BTC/millions/thousands/sats display

Repository Benefits

By using the lightning-node-tools repository, you get:

• Regular Updates: New features and improvements via git pull

• Additional Tools: More Lightning management utilities as they’re developed

• Go Performance: Faster execution and better error handling than bash

• Structured Logging: Better debugging and monitoring capabilities

• Community Contributions: Improvements from other Lightning operators

Keeping Updated

Update the Tools

cd lightning-node-tools
git pull origin main
go build -o telegram-alerts cmd/telegram-alerts/main.go

Contributing

Found a bug or want a feature? The repository accepts contributions:

• Issues: Report bugs or request features on GitHub

• Pull Requests: Submit improvements and new monitoring capabilities

• Documentation: Help improve setup guides and usage examples

Why This Approach Works

After dealing with broken web interfaces and complex monitoring solutions, this approach prioritizes:

• Reliability: Go binaries don’t have dependency conflicts

• Performance: Faster execution than shell scripts

• Maintainability: Clean code structure for easy modifications

• Extensibility: Repository structure allows adding new tools easily

• Community: Shared improvements from other Lightning operators

Sometimes the most effective solution combines simplicity with modern tooling.

Troubleshooting

Script Not Running

# Check cron logs
grep telegram-alerts /var/log/syslog | tail -10

# Test manual execution
cd lightning-node-tools
./telegram-alerts

No Telegram Messages

# Test Telegram API directly
curl -s -X POST “https://api.telegram.org/bot$BOT_TOKEN/sendMessage” \
    -d chat_id=”$CHAT_ID” \
    -d text=”Test message”

LND Connection Issues

# Verify LND is accessible
lncli getinfo
lncli channelbalance
lncli walletbalance

Repository Link

Lightning Node Tools: https://github.com/brewgator/lightning-node-tools

This repository will continue to expand with additional Lightning node management utilities, monitoring enhancements, and operational tools as they’re developed.

This monitoring setup complements your existing Lightning node infrastructure by providing reliable event notifications with modern tooling and community-driven improvements.

The Republic Was Basically Space Congress

The Senate was a 24-hour filibuster simulator where thousands argued while wars burned. Ordinary citizens waited months for hyperlane repairs and watched pirates get richer. Meanwhile, every committee seemed focused on minutiae like asteroid mining rights or proper etiquette for interplanetary ambassadors.

So when Palpatine promised “stability and security,” people didn’t hear tyranny, they heard competence. And for a galaxy exhausted by procedural chaos, that competence looked like salvation. The “emergency powers” he granted himself? They were just paperwork he didn’t have time to shuffle through. Efficiency rarely looks gentle, but it is effective.

The Jedi: Unelected Wizards With a God Complex

The Jedi are always framed as noble. In reality, they were a galaxy-wide cult with a dress code. They snatched toddlers, shaved their heads, and trained them to decapitate anyone who felt emotions. They treated politics like a spectator sport, debating morality from their high towers while systems fell into chaos.

When the Senate finally questioned them, the Jedi didn’t compromise, they staged a coup. Palpatine handled it the traditional way: paperwork. (Technically, Order 66.) It was decisive, yes, but consider the alternatives: endless debate, public hearings, and another decade of Jedi moral grandstanding. Sometimes efficiency isn’t pretty and sometimes it comes with laser swords.

The Empire: Peace, Prosperity, and the Occasional Superweapon

The Empire brought something the Republic hadn’t managed in centuries: order. Crime dropped, bureaucracy thinned, and even the star destroyers ran on time. The Death Star? Call it what it was: a jobs program with unfortunate side effects. Engineers, contractors, and technicians across multiple sectors found steady work.

Alderaan’s destruction was tragic, yes, but context matters. Reports suggest the planet harbored insurgents and stockpiled weapons. In press releases, “tragic” usually translates to “necessary.” The Empire understood that deterrence can be uncomfortable, but it keeps the galaxy’s larger system running.

Even smaller measures, like stormtrooper recruitment drives or rationing programs, improved daily life for many ordinary citizens. The Empire wasn’t just about fear; it was about functioning infrastructure in a galaxy that had spent centuries arguing over lunch schedules.

The Rebels: Freeloaders With Blasters

The Rebellion brands itself as grassroots, but look at the roster: princess, senator, rich smuggler. They weren’t fighting oppression; they were fighting taxes. And the “New Republic” they built? Collapsed faster than a stormtrooper on Endor.

Every time the Rebels scored a moral victory, they left devastation behind. Blown-up installations, dead civilians, disrupted trade: the very chaos they claimed to oppose. And yet, in cinematic marketing, they remained scrappy heroes. It’s a reminder that perception matters more than results, especially when you’re photogenic and have a good soundtrack.

The Real Lesson

Everyone calls the Empire authoritarian. Maybe it was just decisive. A little less “freedom,” a little more “stop parking your X-wing on my moisture farm.” It wasn’t perfect, but it delivered peace and matching uniforms.

Consider how few empires in fiction, or history, actually balanced competence with spectacle. The Empire did it while maintaining a color palette. The tragedy of Star Wars isn’t that the Empire fell; it’s that nobody learned the comfort of letting one guy in a cloak handle everything. The Empire didn’t fail. People did.

Order Through Absurdity

It’s easy to laugh at stormtroopers, absurdly massive space stations, or a Sith Lord who can choke someone across a room. But that absurdity is part of the Empire’s genius. By leaning into the theatrical, the regime distracts from the daily grind of bureaucracy and governance. Citizens may grumble about uniforms, but they rarely complain about their hyperlane schedules or taxes being processed on time.

There’s a lesson here: sometimes, authoritarian systems work because they make inefficiency unthinkable. In a galaxy where pirates, committees, and rebel insurgents were constant problems, a little absurdity was the only way to get anything done.

A Final Thought

If you’ve made it this far and you’re drafting a rebuttal about “freedom” and “checks and balances,” good news, you got the point. Authoritarians rarely start out looking like villains. They look like problem-solvers. They talk about law and order. They promise to drain the Senate swamp, build the biggest space station anyone’s ever seen, and make the galaxy great again.

And that’s when the Death Star plans usually get approved.

Phase 1 got Bitcoin Core running. Phase 2 hardened the security and added LND. Now Phase 3 is where your node actually stretches its legs, funding it, connecting to the Lightning Network, and finally moving sats. This is the glow-up moment where you graduate from “I run a node” to “I’m an actual Lightning participant.”

Get ready, this is where mistakes can cost real money. But also, this is where it starts to feel like magic. ⚡

1. Funding Your Lightning Node

You can’t ride without gas in the tank. Time to put some actual Bitcoin into LND.

Getting Bitcoin On-Chain

# Generate a funding address
lncli newaddress p2wkh

# Check wallet balance after funding
lncli walletbalance

Note: Don’t accidentally copy/paste your address into the wrong group chat. Your friends will definitely send memes instead of sats.

Funding Strategy

• Start conservative: Think of this like dipping your toe in the pool, 0.001–0.01 BTC is plenty.

• Understand costs: Lightning is cheap, but opening or closing channels costs on-chain fees.

• Reserve funds: Don’t YOLO your entire stash into channels, you’ll need on-chain for emergencies.

• Security reminder: This is mainnet. If you fat-finger something, it’s not Monopoly money.

Wallet Management

# Check on-chain transactions
lncli listchaintxns

# Monitor confirmations
bitcoin-cli gettransaction TXID

Pro tip: Watching confirmations is like watching paint dry, except each coat costs $5–$50 depending on mempool congestion.

2. Understanding Lightning Network Topology

Okay, time for some mental gymnastics. Lightning isn’t just “Bitcoin but fast”, it’s a mesh of channels and liquidity that makes Visa look like dial-up.

Network Discovery

• How Lightning works: Instead of broadcasting everything on-chain, you open payment channels. Think bar tabs, but cryptographic.

• Routing basics: Payments hop from node to node like a baton in a relay race. Sometimes you win, sometimes you drop the baton.

• Liquidity concepts: Outbound = you can send. Inbound = you can receive. Both matter.

Research Tools

• 1ML.com: A kind of “Top 40 Hits” chart for Lightning nodes.

• Amboss.space: Node analytics for the data nerds among us.

• Lightning Network Explorer: Eye candy (see the graph in all its chaotic glory).

Peer Selection Strategy

• Well-connected nodes: Don’t connect to your buddy’s Raspberry Pi with 0 channels.

• Geographic diversity: Spread the love, don’t centralize.

• Different operators: Avoid putting all your eggs in one mega-node basket.

• Reputation matters: Like dating, except instead of ghosting you, they might just drop your channels.

3. Connecting to Peers

This is the “friend request” stage. You can connect to anyone, but the cool kids have better routing.

The Connection Process

# Basic peer connection
lncli connect PUBKEY@HOST:PORT

# Examples of reliable nodes
lncli connect 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735  # Bitrefill
lncli connect 0279c22ed7a068d10dc1a38ae66d2d6461e269226c60258c021b1ddcdfe4b00bc4@ln1.satoshis.place:9735  # Satoshis.place

Pro tip: Connecting is like sliding into someone’s DMs. They don’t owe you anything, but now you’re in the same room.

Peer Management

# List current peers
lncli listpeers

# Disconnect if needed
lncli disconnect PUBKEY

Connection vs Channel

Big difference: connections are free (like chatting), channels cost actual Bitcoin (like buying drinks).

4. Opening Your First Channels

Now we’re talking. Channels are where the magic happens, but also where you start burning sats on fees.

Channel Economics

• Minimum amounts: Some nodes won’t even talk to you unless you bring 400k sats or more.

• Fee considerations: Every channel is an on-chain transaction, so don’t open or close frivolously.

• Capacity planning: Be honest, are you here to route payments, or just to buy coffee over Lightning?

Opening Channels

# Basic channel opening
lncli openchannel PUBKEY AMOUNT_IN_SATOSHIS

# Your successful example
lncli openchannel 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f 400000

# Check channel status
lncli listchannels
lncli pendingchannels

Channel Management

# Monitor channel state
lncli listchannels

# Check channel balance distribution
lncli channelbalance

# Close channels if needed
lncli closechannel CHANNEL_POINT

Closing a channel too early is like rage-quitting a game, you can do it, but it’ll cost you.

5. Making Lightning Payments

Finally, the fun part, actually sending sats.

Invoice-Based Payments (Standard)

# Pay a Lightning invoice
lncli payinvoice BOLT11_INVOICE

That first successful Lightning payment? Chef’s kiss. Worth all the setup headaches.

Creating Invoices

# Generate invoice for receiving payments
lncli addinvoice --memo "Test payment" --amt 10000 --expiry 3600

# List received payments
lncli listinvoices

Payment Tracking

# View payment history
lncli listpayments

# Check forwarding statistics (if routing)
lncli fwdinghistory

If you’re routing payments: congrats, you’re basically a mini-bank now (without the lobby fountain).

6. Backup and Recovery Operations

This is where you pretend you’re paranoid, but in reality you’re just being smart.

Critical Backup Tasks

# Daily channel backups (automate this!)
lncli exportchanbackup --all --output_file ~/backups/channels-$(date +%Y%m%d).backup

# Verify backups
lncli verifychanbackup --multi_file ~/backups/channels-$(date +%Y%m%d).backup

If you’re not backing up, you’re one power outage away from crying into your keyboard.

Recovery Planning

• Seed phrase security: Treat it like your house keys, except losing it is worse.

• Channel backup testing: Test on testnet, not mainnet (ask me how I know).

• Force closure procedures: When in doubt, close it out.

• Emergency contacts: Have a Lightning friend who can sanity-check your panic.

7. Hybrid Tor + Clearnet Configuration

Expand your node's connectivity to reach both clearnet and privacy-focused .onion nodes

Some Lightning nodes are only accessible via Tor (.onion addresses). Adding Tor support to your node enables connections to privacy-focused nodes while maintaining clearnet connectivity for maximum routing opportunities.

1. Install and Configure Tor

# Install Tor
sudo apt update && sudo apt install tor

# Add your user to the debian-tor group
sudo usermod -a -G debian-tor $(whoami)

# Edit Tor configuration
sudo nano /etc/tor/torrc

Add these lines to /etc/tor/torrc:

# Enable control port for LND
ControlPort 9051

# Use password authentication (more reliable than cookies)
HashedControlPassword YOUR_GENERATED_HASH_HERE

# Create hidden service for your node
HiddenServiceDir /var/lib/tor/lightning/
HiddenServiceVersion 3
HiddenServicePort 9735 127.0.0.1:9735

Generate the password hash:

# Generate a hashed password (replace with your own secure password)
tor --hash-password "your_secure_password_here"

Use the output hash in the torrc file above.

2. Set Up Hidden Service Directory

# Create the directory manually and set proper permissions
sudo mkdir -p /var/lib/tor/lightning/
sudo chown debian-tor:debian-tor /var/lib/tor/lightning/
sudo chmod 700 /var/lib/tor/lightning/

# Start and enable Tor
sudo systemctl enable tor
sudo systemctl start tor

# Verify hidden service was created
sudo cat /var/lib/tor/lightning/hostname

3. Update LND Configuration

Add these Tor settings to your existing ~/.lnd/lnd.conf:

[Application Options]
listen=0.0.0.0:9735
rpclisten=127.0.0.1:10009
restlisten=127.0.0.1:8080
alias=MyLNDNode
color=#3399FF

# Tor configuration
tor.active=true
tor.control=localhost:9051
tor.socks=localhost:9050
tor.dns=soa.nodes.lightning.directory
tor.v3=true
tor.password=your_secure_password_here

# Your existing configuration continues below...

4. Update Firewall and Restart

# Allow Tor SOCKS proxy from localhost
sudo ufw allow from 127.0.0.1 to any port 9050
sudo ufw allow from 127.0.0.1 to any port 9051

# Restart services
sudo systemctl restart tor
sudo systemctl restart lnd.service

5. Verify Hybrid Connectivity

# Check that your node now advertises its .onion address
lncli getinfo | grep -A 5 '"uris"'

# Should show something like:
# "033c4b...@your_onion_address.onion:9735"

# Test clearnet connections still work
lncli connect 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735

# Test Tor connections work
lncli connect PUBKEY@ONION_ADDRESS.onion:9735

Troubleshooting Notes

If your node's URIs remain empty after setup:

• Cookie authentication issues: Switch to password authentication as shown above (more reliable)

• Permission problems: Ensure the hidden service directory has correct ownership

• Service timing: Allow 10-15 seconds after restarting LND for the .onion address to appear

Your node now supports both clearnet and Tor connections, giving you access to the full Lightning network while maintaining privacy options for sensitive connections.

Managing Your Lightning Node

Each of these sections could be its own dedicated post, I'm hitting the broad strokes here and may link to more detailed walkthroughs later.

Channel Liquidity Management

This is the part most people skip until they can’t pay or receive. Don’t be that person.

Understanding Liquidity

• Outbound liquidity: Your ammo for sending.

• Inbound liquidity: Your open door for receiving.

• Balanced channels: Spoiler, 50/50 isn’t always the sweet spot.

Rebalancing Strategies

# Check current channel states
lncli listchannels | jq '.channels[] | {remote_pubkey, local_balance, remote_balance, capacity}'

Manual tricks:

• Circular payments to yourself (yes, you’re literally paying yourself fees).

• Loop Out or Loop In (fancy submarine swaps).

• Submarine swaps (because normal swaps weren’t cool enough).

Liquidity Tools

• Lightning Loop: Move liquidity around like a pro.

• Pool: Rent or sell liquidity, because apparently that’s a business now.

• Rebalance-lnd: Let a script do the boring math for you.

Node Monitoring and Health

Think of this like checking your vitals. Don’t wait until the patient is flatlining.

Daily Operations - Health Check Script

# Create comprehensive monitoring script
cat > ~/monitor-node.sh << 'EOF'
#!/bin/bash
echo "=== Node Status $(date) ==="
echo "Bitcoin Core:"
bitcoin-cli getblockchaininfo | grep -E "(blocks|headers|verificationprogress)"
echo "LND:"
lncli getinfo | grep -E "(synced_to_chain|synced_to_graph|num_active_channels|num_peers)"
echo "Channel Balances:"
lncli channelbalance
echo "Wallet Balance:"  
lncli walletbalance
echo "Recent Channel Activity:"
lncli listchannels | jq -r '.channels[] | "\(.chan_id): \(.local_balance)/\(.capacity) (\(.remote_pubkey[0:16])...)"'
EOF

chmod +x ~/monitor-node.sh

Run this script daily and you’ll feel like a sysadmin wizard.

Log Monitoring and Rotation

# Check LND logs for issues
tail -f ~/.lnd/logs/bitcoin/mainnet/lnd.log

Warning: reading logs can turn into a weird form of meditation.

Advanced Operations

For when you want to graduate from “casual user” to “Lightning tinkerer with too much free time.”

Routing Node Considerations

• Fee optimization: Too high, no one routes through you. Too low, you’re charity.

• Channel selection: You want quality connections, not just quantity.

• Liquidity advertising: Yes, you can actually market your liquidity. Late-stage capitalism is wild.

API Integration

# REST API examples
curl -X GET https://localhost:8080/v1/getinfo --insecure

Yes, you can script all of this, because typing commands manually forever is for masochists.

Troubleshooting Common Issues

Spoiler, things will break.

Channel Problems

• Force closures: Like hitting the eject button. Costly, but sometimes necessary.

• Stuck payments: Usually means your route is cursed. Try again later.

• Peer connectivity: Some nodes are basically flaky friends. Don’t rely on them.

Node Sync Issues

# Check sync status
lncli getinfo | grep synced

If it says “false”, welcome to the waiting room.

Performance Optimization

• Database maintenance: Compact those LND files like you’re cleaning out your garage.

• Memory management: Don’t cheap out on hardware.

• Network connectivity: A Lightning node on hotel Wi-Fi is a crime.

Security Considerations in Operations

The part where you realize you’re holding hot money in hot wallets.

Operational Security

• Hot wallet limits: Don’t put all your Bitcoin in Lightning.

• Channel partner vetting: Would you lend them cash IRL? Same logic applies.

• Force closure risks: Always have some spare on-chain funds ready.

Monitoring for Attacks

• Watchtower integration: Your bouncer when you’re offline.

• Breach detection: Because yes, people will try to cheat you.

• Access logging: Know who’s been poking at your box.

Economic Considerations

Running a node won’t make you rich, but it might pay for coffee.

Cost-Benefit Analysis

• Channel opening costs: Think of it as cover charges.

• Routing revenue: Pocket change, unless you’re Kraken.

• Opportunity costs: Bitcoin locked in channels can’t moon elsewhere.

Fee Strategy

# Set channel fees
lncli updatechanpolicy --base_fee_msat 1000 --fee_rate 0.000001 --chan_point CHANNEL_POINT

Set fees too high and you’re ignored, too low and you’re subsidizing strangers’ coffee.

Integration and Applications

Time to actually use this thing.

Merchant Integration

• BTCPay Server: Spin up your own crypto Stripe.

• LNbits: A mini-bank in your pocket.

• Custom integrations: If you can code, Lightning wants to be everywhere.

Personal Use Cases

• Mobile wallets: Zeus, Zap, Phoenix, all your friends are here.

• Web interfaces: RTL, ThunderHub, because CLI isn’t for everyone.

• Automation: Tip bots, paywalls, random side projects.

Community and Network Participation

Congrats, you’ve gone from lurker to active participant.

Contributing to the Network

• Running a routing node: Be part of the plumbing.

• Opening channels to new nodes: Help decentralization.

• Sharing knowledge: Flex your hard-won scars to help others.

Staying Informed

• Lightning development: New features drop often, don’t sleep.

• Network statistics: Know the health of the beast.

• Community engagement: Twitter, Nostr, Slack, whatever your poison.

Conclusion: From Node Operator to Lightning Native

By the end of Phase 3, you’re no longer just “that guy running a node in the corner.” You’re moving real sats, managing liquidity, and maybe even routing for others. You’ve graduated into Lightning-native territory.

Key Milestones:

• Funded and secured your Lightning wallet

• Opened channels with reliable peers

• Sent and received sats over Lightning

• Put monitoring and backups in place

• Learned enough to break and fix your own setup

What’s Next:

• Dive into swaps, liquidity markets, and advanced automation

• Experiment with Lightning-powered apps

• Build something cool that takes sats

You’re not just observing the future of payments anymore, you’re running part of it. ⚡

Resources and References

• LND Documentation: docs.lightning.engineering

• Lightning Network Explorer: 1ml.com, amboss.space

• Community: Lightning Network Slack, Bitcoin Stack Exchange

• Tools: RTL, ThunderHub, Lightning Loop, Lightning Pool

• Previous Phases: Phase 1 - Phase 2

This completes the trilogy: Phase 1 (Bitcoin Core), Phase 2 (Security & LND Setup), Phase 3 (Lightning Operations). You now have a fully sovereign, secure, and operational Lightning node. Don’t just hodl, route, send, and actually use it.

Four weeks in, Florida sits at the bye week with more questions than answers. The record doesn’t tell the full story, the way this team has played does. This isn’t about talent. It isn’t about injuries. It’s about leadership. And right now, Florida doesn’t have any.

Before the season, I said the Gators had enough athletes to compete if they could just avoid self-inflicted wounds. Instead, the first month has been one long highlight reel of penalties, busted play calls, and coaching blunders. The defense has teeth, the roster has depth, but the guy holding the headset? He’s sinking the whole thing.

Let’s walk through it.

Week 1: LIU

Opening against LIU was always going to be a “don’t get hurt, don’t embarrass yourself” type of game. The Gators didn’t embarrass themselves, they steamrolled. A 50-plus point shutout, Florida’s first in a decade. That’s not nothing.

DJ looked rusty, which you could chalk up to shaking off an offseason where he barely seemed involved. The offense? Predictable, but against LIU it didn’t matter. Run, run, easy pass, rinse and repeat.

The real headline was discipline. Zero penalties. Not one. Was it discipline? Was it luck? Spoiler alert: it was luck.

Still, 1-0 is 1-0, and no one complains about a blowout to open the season.

Week 2: USF

This is the game that will be remembered, and not in a good way. Embarrassing doesn’t even cover it.

Florida managed to hit the holy trinity of losing: constant penalties, refs adding fuel to the fire, and coaching malpractice at every turn. The last few minutes felt like a masterclass in how to mismanage a clock. On top of that, players spitting on opponents? Completely unacceptable. And then the offense (if you can even call it that). Middle school stuff. Run-run-screen, punt.

This was Billy Ball distilled: methodical incompetence. I already thought Napier wasn’t the guy, but this game was the exclamation point. At this point, the only scenario where you keep him is if he wins out and takes home a national title. And let’s be real, there’s a 0.0% chance of that happening.

I was ready to move on before this game. After it? I don’t see how he survives the year.

Week 3: LSU

If USF was the warning siren, LSU was the full-on alarm bell. Same movie, different opponent.

The offense was a mess. Endless jet sweeps and screens that fooled no one. Third-and-long calls so conservative LSU’s defense barely had to move. When your quarterback is left forcing throws into triple coverage because the scheme gives him nothing, that’s not a “unexperienced mistake” problem, it’s coaching malpractice.

Yes, Lagway threw five picks. Brutal. But what else is he supposed to do when the only route past the sticks is a lonely receiver running into a crowd? He pressed, because he had to. The staff left him out to dry.

Meanwhile, the defense got stuck playing 40 minutes of football because the offense couldn’t stay on the field. By the fourth quarter, they were cooked. LSU didn’t have to outplay Florida — they just had to wait for the Gators to implode.

Week 4: UM

Finally, a flash of what Florida could be with even average leadership. The defense bullied Miami. Carson Beck and his “unstoppable” offense looked ordinary all night. The front four owned the line, the secondary held their ground, and UM never got comfortable.

But then there was the offense. 0-for-13 on third down. Zero. That’s not bad luck, that’s design. Every drive stalled the same way: conservative calls, no creativity, no plan to attack downfield. You can’t move the chains if your scheme refuses to try.

The defense gave Florida chance after chance. The offense wasted every single one.

The Updated Outlook

So where does that leave us? Four weeks in, the verdict is clear: the players are good enough. The coach isn’t.

The USF loss will hang around Napier’s neck forever. LSU and UM proved what we already knew, this is not a talent gap. It’s not a rebuild. It’s a coaching problem. A fixable one, if Florida is willing to pull the trigger. Right now, though, Billy Napier is still pacing the sideline, headset in hand, calling bubble screens into oblivion. Dead man walking.

The projections don’t lie. ESPN’s FPI has Florida around 3.45 totals wins this season, with the most likely coming against Mississippi State (60%), Kentucky (48%), and FSU (43%). That is unacceptable. A program with this much talent should never be staring at bowl eligibility as its ceiling.

As for DJ, he looks like a guy who skipped a summer of practice, but the flashes are still there. If he sticks around for the inevitable coaching change, the next staff inherits a quarterback worth building around. The defense is ready. The roster is ready. All that’s missing is someone competent enough to steer the ship.

The season, in terms of championships, is already gone. But the bigger storyline is playing out: Florida is finally running out of excuses. And by the time the next bye week rolls around, the only real question might be whether Napier is still around to make it there.

Step 1: Install LND

There are basically two main options for running a Lightning node: LND and Core Lightning. I went with LND here, but the steps for Core Lightning aren’t wildly different. I may circle back and do a CL walk-through later. For now, let’s roll with LND.

Download, extract, and install LND:

wget https://github.com/lightningnetwork/lnd/releases/download/v0.17.0-beta/lnd-linux-amd64-v0.17.0-beta.tar.gz
wget https://github.com/lightningnetwork/lnd/releases/download/v0.17.0-beta/manifest-v0.17.0-beta.txt

# Verify download
sha256sum --check manifest-v0.17.0-beta.txt --ignore-missing

# Extract and install
tar -xzf lnd-linux-amd64-v0.17.0-beta.tar.gz
sudo install -m 0755 -o root -g root -t /usr/local/bin lnd-linux-amd64-v0.17.0-beta/*

Step 2: Configure LND

Set up the config file here. Make sure to use the same RPC password you generated when you installed Bitcoin Core (see Phase 1).

This is also your chance to give your node a fun alias and color. Totally cosmetic, but it shows up in explorers and mapping tools. (Yes, this is the “pick your gamer tag” moment.)

We’ll get into advanced settings later, but if you’re curious, the LND docs linked at the bottom go much deeper.

~/.lnd/lnd.conf:

[Application Options]
listen=0.0.0.0:9735
rpclisten=127.0.0.1:10009
restlisten=127.0.0.1:8080
alias=MyLNDNode
color=#3399FF

[Bitcoin]
bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

[Bitcoind]
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=bitcoinrpc
bitcoind.rpcpass=YOUR_RPC_PASSWORD_FROM_BITCOIN_CONF
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

[autopilot]
autopilot.active=false

[wtclient]
wtclient.active=true

Step 3: Fire It Up

Let’s run this bad boy and see what happens.

lnd --configfile=~/.lnd/lnd.conf

In another terminal, create a wallet for your Lightning node (if you have an existing wallet, this is when you’d restore it):

lncli create  # Follow prompts

⚠️ Mainnet sanity check before funding anything:

1. Bitcoin Core must be fully synced

2. Write down your 24-word seed offline

3. Start with small amounts while learning

4. Remember: Lightning ≠ free lunch. Mismanagement = lost sats

Immediately back up your wallet seed and channels:

# Create channel backup
lncli exportchanbackup --all --output_file ~/backups/channels-$(date +%Y%m%d).backup

# Set up automatic backups
mkdir -p ~/backups
echo "0 2 * * * lncli exportchanbackup --all --output_file ~/backups/channels-\$(date +\%Y\%m\%d).backup" | crontab -

Check LND status:

lncli getinfo

# Should show mainnet and synced_to_chain: true

If you want auto-unlock on startup (convenient, but less secure):

# Create password file (secure it properly)
echo "YOUR_WALLET_PASSWORD" > ~/.lnd/wallet_password
chmod 600 ~/.lnd/wallet_password

Step 4: Lightning Basics

Here are some commands you’ll run a lot. We’ll use them later when opening channels and sending sats, but for now, just know the toolkit:

lncli getinfo
lncli newaddress p2wkh
lncli connect PUBKEY@HOST:PORT
lncli openchannel PUBKEY AMOUNT
lncli sendpayment --pay_req=BOLT11_INVOICE

Step 5: Systemd Services

Now that we’ve been manually starting everything, let’s make life easier with systemd services.

bitcoind service

/etc/systemd/system/bitcoind.service:

[Unit]
Description=Bitcoin Daemon
After=network.target

[Service]
ExecStart=/usr/local/bin/bitcoind -conf=/home/bitcoin/.bitcoin/bitcoin.conf -datadir=/home/bitcoin/.bitcoin
ExecStop=/usr/local/bin/bitcoin-cli -conf=/home/bitcoin/.bitcoin/bitcoin.conf stop
Restart=on-failure
User=bitcoin
Group=bitcoin
Type=simple
TimeoutSec=300

[Install]
WantedBy=multi-user.target

(This is where auto-unlock for the LND wallet comes in. Otherwise, every restart = manual unlock.)

lnd service

/etc/systemd/system/lnd.service:

[Unit]
Description=LND Lightning Daemon
After=bitcoind.service
Requires=bitcoind.service

[Service]
ExecStart=/usr/local/bin/lnd --configfile=/home/bitcoin/.lnd/lnd.conf
ExecStop=/usr/local/bin/lncli stop
Restart=on-failure
User=bitcoin
Group=bitcoin
Type=simple
TimeoutSec=300
LimitNOFILE=128000

[Install]
WantedBy=multi-user.target

Enable on boot:

sudo systemctl daemon-reload
sudo systemctl enable bitcoind.service
sudo systemctl enable lnd.service

Step 6: Remote Access with Tailscale

Services are up and auto-restarting. But right now, you can only access your node via direct login or LAN SSH. That’s not very global-payments-future, is it?

Instead of opening ports to the world (risky) or fiddling with Tor (doable but clunky), I went with Tailscale. It builds a private mesh network between your devices, so you can securely connect from anywhere—phone, laptop, whatever.

curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up

Now you can securely hop into your node from anywhere. ✈️⚡

Step 7: Security Audit

Quick opsec check:

sudo netstat -tlnp | grep -E "(8332|9735|10009|8080|28332|28333)"

• ✅ Bitcoin RPC (8332) → localhost only

• ⚠️ LND gRPC (10009) → make sure it’s not wide open

• ⚠️ LND REST (8080) → same check

• ✅ ZMQ ports → localhost only

• ✅ Lightning P2P (9735) → public, as expected

Check UFW status:

sudo ufw status verbose

🚨 If UFW is inactive, all LND ports are exposed. That’s… bad.

Step 8: Lock It Down

Firewall

# Enable UFW
sudo ufw enable

# Allow SSH (adjust port if you changed it)
sudo ufw allow 22/tcp

# Allow Tailscale
sudo ufw allow in on tailscale0

# Allow Lightning P2P (if you want incoming connections)
sudo ufw allow 9735/tcp

# Allow Bitcoin P2P (if you want to serve other nodes)
sudo ufw allow 8333/tcp

# Block everything else
sudo ufw default deny incoming
sudo ufw default allow outgoing

File Permissions

chmod 600 ~/.bitcoin/bitcoin.conf
chmod 600 ~/.lnd/lnd.conf
chmod -R 700 ~/.lnd/data/

Fail2ban

sudo apt update && sudo apt install fail2ban

Verify everything:

sudo systemctl status bitcoind.service lnd.service --no-pager
bitcoin-cli getblockchaininfo
lncli getinfo

Why It Matters

• Firewall keeps randos out

• Permissions protect configs + macaroons

• Fail2ban blocks brute-forcers

• Tailscale = private remote access, no sketchy open ports

Final scorecard:

• 🔒 Network Security = LOW RISK

• 👤 User Management = LOW RISK

• 💰 Financial Risk = MEDIUM (because sats are always real money)

Advanced: Hardening Services

ProtectSystem=full
ProtectHome=true
NoNewPrivileges=true
PrivateTmp=true
CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_NET_ADMIN

Pros:

• Limits blast radius if compromised

• Locks services down to minimal environments

• Makes privilege escalation harder

Cons:

• May break upgrades or debugging

• Can block logging or Bitcoin connectivity if misconfigured

Your Bitcoin Lightning Node is Now Production-Ready! ⚡

You can safely:

1. Fund your Lightning wallet with real Bitcoin

2. Open channels and route payments

3. Access remotely via Tailscale

4. Monitor your node knowing it’s secured

Next Steps

At this point, your node is fully set up, secure, and running as a proper Lightning participant. Phase 3 will cover funding the node, testing payments, and managing channels, turning it into a living, breathing Lightning machine.

Resources

• Bitcoin Core Docs

• LND Documentation

• Ubuntu Server Docs

• Tailscale Docs

• My upcoming write-up: Phase 3 — Funding & Channels

This is Phase 2 of my “DIY Node Admin” series. If you’ve followed along, congrats—you now have a fully functional, hardened Bitcoin + Lightning node. Phase 3 will show how to actually use it, safely.

Family road trips are pitched as wholesome, memory-making adventures. You imagine the kids singing along to songs, everyone laughing, maybe even spotting a few landmarks together. The brochures in your head make it sound charming.

Reality? It is basically the Olympics (minus the medals, sponsorships, and cheering crowds). Instead, you get cracker crumbs, complaints, and the faint smell of feet that will never leave your upholstery.

The Training (That Never Happened)

Olympians spend years preparing for their event. They have coaches, nutritionists, and carefully mapped training plans. Parents? We get tossed into the arena with zero warm-up and one child who insists they need to bring seventeen stuffed animals, two blankets, and a shoebox of “important rocks.”

Packing the car is your first workout. It is a full-body CrossFit routine disguised as “loading up.” You squat with suitcases, deadlift coolers, and lunge awkwardly with car seats. You burn 600 calories just trying to wedge the stroller in next to the snacks. And no matter how many Pinterest lists you consult, you will forget something (usually your phone charger, always your patience).

The Opening Ceremony: Leaving the Driveway

The Olympic Games begin with fireworks, music, and pageantry. A family road trip begins with someone crying before you even hit the street.

You have got snacks packed, water bottles filled, and a carefully curated playlist ready to go. Then, right as you buckle everyone in:

• One kid suddenly needs to pee.

• Another announces they are starving.

• Someone insists you forgot their toy (you did not, it is literally in their lap).

By the time you actually pull out of the driveway, you have burned through half your energy reserves, three percent of your sanity, and the trip has not even started.

The Events

Like any Olympic sport, road trips have events (several of them):

• Snack Toss: Delivering snacks from the front seat to the back without swerving off the road. Bonus points if the pouch of applesauce lands upright.

• Referee Duty: Settling backseat disputes using only your rearview mirror and a “do not make me pull over” voice.

• Bathroom Sprint: Despite asking five times before leaving, every child’s bladder decides to operate on a 30-minute timer. You become an expert in locating rest stops, gas stations, and “that one sketchy diner” in the middle of nowhere.

• Car Seat Wrestling: The strength competition. Wrestling a squirming toddler into their car seat while they go full noodle-mode should earn you a spot in the Olympic Hall of Fame.

• “Are We There Yet?” Endurance Challenge: This begins approximately 14 minutes into the trip and continues at intervals of every 7–10 minutes until arrival. No known coping strategy exists.

• Playlist Decathlon: Managing to cycle between nursery rhymes, the K Pop Demon Hunter Soundtrack, and whatever 2000s R&B playlist keeps you sane without sparking a mutiny.

If you are lucky, there is also the Nap Time Relay. The rules: one kid falls asleep, but if another makes noise and wakes them, you lose.

The Judges (a.k.a. the Kids)

Real Olympians are scored by trained professionals. Parents, however, are judged by their kids, who are brutally honest and constantly dissatisfied.

• If the snack options are wrong: booed off the stage.

• If the Wi-Fi hotspot drops during a cartoon: automatic zero points.

• If the wrong stuffed animal is handed over: immediate meltdown and loss of medal eligibility.

There is no pleasing the judges. Even when everything is perfect, a child will find a reason to complain. (“These fries taste too potato-y.”)

The Hidden Events (for Parents Only)

Road trips also come with events no one talks about:

• Trash Bag Marathon: Collecting 492 snack wrappers, juice boxes, and mystery crumbs, only to discover you forgot the actual trash bags.

• Balance Beam of Conversation: Trying to talk to your spouse without little ears repeating everything loudly at the next gas station.

• Mental Gymnastics: Convincing yourself this trip is “fun” even while plotting how to sell the minivan afterward.

The Post-Game Wrap-Up

At long last, you arrive. The kids are refreshed, hyper, and somehow hungry again. Meanwhile, the car looks like a landfill, your back aches from sitting, and you are questioning why you did not just stay home and stream a travel documentary instead.

Every surface inside the car is sticky. No one knows why. You will spend the next six months discovering fossilized chicken nuggets in cup holders and mysterious slime welded to the carpet.

The kicker? The kids do not even remember the drive. They will remember the hotel pool, the ice cream stop, or the giant dinosaur statue you pulled over to see. All that Olympic-level effort? Already forgotten.

The Closing Ceremony

If medals were awarded, parents would deserve them:

• Gold: For surviving without tears (yours, not theirs).

• Silver: For only yelling once.

• Bronze: For making it without the car smelling like a locker room soaked in fruit snacks.

And yet, here is the twist. Despite the chaos, the crumbs, and the fact that you will never get Goldfish powder out of your seats, you will do it again. Because five years from now, you will not remember the bathroom sprints or the backseat fights. You will remember the laughing, the goofy car games, the off-key singing, and the weird inside jokes that came out of nowhere.

Road trips with kids are exhausting, ridiculous, and sometimes catastrophic. But they are also the memories that last (which is why parents keep showing up for the event).

Now if only someone would design an actual medal ceremony at the end. I would take podium photos holding a Capri Sun and a bag of pretzels any day.

Let’s be honest: if you’re reading this, you probably fall into one of two camps.

1. You’ve already written Bitcoin off as “magic internet money for nerds and criminals.”

2. You’re curious, but not convinced it has any real-world use.

If that’s you, then pull up a chair, grab a coffee (or margarita), and let me make the case for why Bitcoin isn’t just worth paying attention to, it’s worth investing in.

We’re going to cover the big-ticket items: Bitcoin as a hedge against inflation, as money outside of the fragile fiat system, as a technology that’s faster and more portable than anything your bank offers, and why adoption is growing globally at a breakneck pace.

And just so this doesn’t feel like a dry economics lecture, I’ll throw in a story about how my own bank managed to radicalize me against the fiat system while I was on vacation at a Nickelodeon resort in Mexico. (Yes, SpongeBob was there. No, he couldn’t help me move my money.)

Inflation: The Hidden Thief

Let’s start with the big, boring elephant in the room: inflation.

For most of modern history, Americans didn’t think too much about inflation. Then 2021 to 2023 hit. Suddenly, inflation in the U.S. surged to levels not seen since the early 1980s, peaking at 9.1% in June 2022 (U.S. Bureau of Labor Statistics). Grocery bills soared, housing costs skyrocketed, and people felt like their paychecks were shrinking before their eyes.

Globally, it’s often worse. Argentina’s inflation rate hit 276% in early 2025. Turkey’s sits above 70%. And in places like Lebanon, Venezuela, and Zimbabwe, inflation is so bad that the local currency is practically Monopoly money.

Here’s the kicker: central banks create this problem. They print money whenever they want. During the pandemic, the U.S. Federal Reserve expanded its balance sheet by more than $4 trillion in two years. And surprise, when you increase the supply of money without increasing goods and services, your dollars buy less.

Bitcoin flips the script. It has a hard cap of 21 million coins. No politician, banker, or bureaucrat can “stimulate the economy” by pressing CTRL+P on the money printer. The rules are set in code, and everyone knows them.

Owning Bitcoin isn’t about getting rich quick. It’s about not getting silently robbed by inflation.

My Bank Radicalized Me (Thanks, Nickelodeon)

Now, let me tell you how I went from “mildly curious about Bitcoin” to “fully convinced that the fiat system is broken.”

Picture this: I’m on vacation at the Nickelodeon resort in Mexico with my family. Think slime buckets, SpongeBob, endless kid chaos (and me sipping a margarita trying to relax).

While I’m there, I get an email finalizing the deposit I need to send to start construction on my house back home. No problem, right? I log into my bank, send the transfer, and go back to my drink. Easy.

Except it wasn’t.

A few hours later, I get a call from the bank: “Your transfer has been frozen. You’ll need to verify it in person.”

In person. As in: “We see you’re in another country, but tough luck, show up at a branch back home with your ID or your money stays locked.”

Not only did they deny the transfer, they froze the funds entirely. Meaning I couldn’t use that money for anything else either. It was like my money went into purgatory because I dared to use it.

I explained I was on vacation. They didn’t care. So I had to wait until I got home a week later, then take off time from work (because of course banks close at 5 p.m.), march into a branch, and basically plead my case.

Two forms of ID. An hour of questioning. Treated like I was committing fraud against… myself. Then they hit me with the kicker: “It’ll take up to 10 business days for us to review and release the funds.”

Ten. Business. Days.

Meanwhile, my builder was twiddling his thumbs waiting to start construction. By the time the bank “approved” me to use my own money, the whole process had delayed my project by about a month.

Bitcoin? That transaction would’ve been finalized in 10 minutes. No permission slips. No bank tellers. No SpongeBob lifeguarding my finances.

That was the moment I realized: the system isn’t designed to serve you. It’s designed to control you. Bitcoin fixes this.

Portability: The Money You Can Carry in Your Head

Imagine trying to carry $100,000 across a border. With cash, you risk seizure. With gold, you need a security team. With a bank account, good luck if your country freezes capital outflows.

With Bitcoin, you can carry your wealth in your brain. Literally. Memorize a 12-word recovery phrase, and you could walk through any airport security checkpoint in the world with millions of dollars secured in your head.

This is why Bitcoin adoption has exploded in countries with unstable currencies. A recent report from Chainalysis found that countries like Nigeria, Vietnam, and Ukraine rank among the top in global crypto adoption, driven largely by people looking for a way out of broken financial systems.

When your local currency melts faster than ice cream in Cancun, portability isn’t a luxury, it’s survival.

Speed and Efficiency

Let’s compare:

• Wire Transfer (Domestic): 1–3 business days. Fees vary. Bank hours apply.

• Wire Transfer (International): 3–7 business days. Intermediary banks take a cut. Exchange rates apply.

• Bitcoin: 10 minutes average. 24/7. Global. Final settlement.

And the kicker: in 2022, the Lightning Network (a Bitcoin scaling layer) processed over 5 million payments per month, many of them settling instantly for less than a penny in fees. Compare that to Visa or Mastercard, which skim 2–3% off every transaction. Bitcoin makes your Starbucks payment faster and cheaper than the plastic in your wallet.

Energy: The Favorite Criticism

You’ve probably heard the line: “But Bitcoin wastes so much energy!”

Here’s the reality: Bitcoin mining uses about 120–140 terawatt hours per year (Cambridge Bitcoin Electricity Consumption Index), roughly equivalent to the electricity consumption of Argentina. Sounds scary until you realize:

• Global air conditioning uses 2,000+ TWh annually.

• Christmas lights in the U.S. alone consume more electricity than some small countries.

• The traditional banking system consumes 2–3 times more energy than Bitcoin when you account for data centers, ATMs, branches, and armored trucks (Galaxy Digital Research).

The difference? Bitcoin is open, decentralized, and trending greener. Roughly 59% of Bitcoin’s mining energy now comes from renewable sources (Bitcoin Mining Council, 2023 Q4).

So yes, it uses energy. But compared to the alternatives, it’s remarkably efficient.

Adoption: This Isn’t Fringe Anymore

Here’s where it gets interesting:

• As of 2025, about 106 million people worldwide own Bitcoin (Crypto.com Research).

• More than 30,000 Bitcoin ATMs exist globally.

• El Salvador made Bitcoin legal tender in 2021, and now more than 75% of its population has used a Bitcoin wallet.

• Major corporations like Tesla, MicroStrategy, and Block (Square) hold billions in Bitcoin on their balance sheets.

• BlackRock, the largest asset manager in the world, now offers a Bitcoin ETF.

In other words: this isn’t your weird cousin’s side hustle anymore. This is mainstream finance catching up.

Closing the Case

Let’s wrap this up:

• Inflation eats your savings. Bitcoin doesn’t.

• Banks act like your money isn’t yours. Bitcoin puts you in control.

• Moving fiat is slow and expensive. Bitcoin is fast and borderless.

• Portability makes it the ultimate global asset.

• Adoption is growing faster than most people realize.

At the end of the day, Bitcoin isn’t just an investment. It’s a lifeboat. And if the last few years have taught us anything, it’s that you don’t wait until the ship is sinking to look for one.

Disclosure: This is not financial advice. Do your own research before investing. But also, seriously, don’t let SpongeBob guard your money.