The early Church had a scaling problem. Acts 6 tells us that as the number of disciples grew, complaints arose because some widows were being overlooked in the daily distribution of food. The mission had not failed. Growth had simply created operational pressure. The apostles responded by organizing responsibility differently, saying, “It would not be right for us to neglect the ministry of the word of God in order to wait on tables.” The tables mattered deeply, but not every responsibility needed to sit on the same layer.
That is a surprisingly helpful way to think about Bitcoin and the Lightning Network. Bitcoin’s base layer is extraordinarily good at what it was designed to do: verify ownership, prevent double spending, enforce scarcity, and settle value without requiring a central financial institution. But as we discussed in Part Two, blockspace is intentionally scarce. If every cup of coffee, streaming payment, tip, donation, and $5 transaction had to compete for permanent settlement directly on Bitcoin’s blockchain, the system would eventually become unnecessarily expensive and cumbersome for everyday commerce.
Lightning is an attempt to solve that problem without rewriting Bitcoin’s foundation.
The simplest way to understand Lightning is to imagine two people opening a tab. Instead of writing every individual payment permanently into Bitcoin’s ledger, they create a payment channel by committing bitcoin in an onchain transaction. Once that channel is open, they can update the balance between themselves again and again without publishing every update to the blockchain. Ten payments can occur, or a thousand, while the base layer does not need to record every movement. When the channel is eventually closed, the final balance can settle back onto Bitcoin.
The clever part is that you do not need a direct channel with every person you want to pay. Lightning can route payments through a network of connected channels. If I have a channel that eventually connects through several participants to you, the network can find a path and move the payment across it. The intermediate participants do not need to know the entire relationship between sender and receiver, and they cannot simply rewrite who owns the money. What emerges is a payment network built above Bitcoin rather than a replacement for Bitcoin.
That distinction matters.
The base layer is designed for final settlement and strong verification. Lightning is designed for speed, smaller payments, and repeated activity. The base layer says, in effect, this is the authoritative record. Lightning says, we do not need to engrave every cup of coffee into stone before someone can drink it. Both layers matter, but they solve different problems.
This is not entirely foreign to the way financial systems already work. When you swipe a credit card, final settlement between financial institutions does not necessarily occur at the instant the cashier hands you the receipt. Layers of authorization, clearing, and settlement sit behind an interface that feels immediate. Lightning uses a very different architecture, but the larger idea is familiar: everyday commerce can move quickly above a slower, more deliberate settlement foundation.
Benjamin Franklin might have appreciated the architecture. He helped organize colonial postal systems because a growing nation needed more than laws and institutions. It also needed networks capable of moving information efficiently across distance. A Constitution sitting safely in Philadelphia would not have delivered a letter from Boston to Virginia. Foundational structures create order, while practical networks allow ordinary life to move across them.
Lightning brings that distinction into the household.
Imagine paying a small merchant nearly instantly in bitcoin. Imagine sending a modest amount to a family member overseas without treating the payment like an international banking project. A reader could support a creator with a few satoshis, a church could receive small digital donations, or recurring payments could eventually become easier through technologies which are designed to create reusable payment requests rather than requiring a completely new invoice for every transaction.
But Lightning is not magic, and convenience should never become theology.
Payment channels require liquidity, meaning bitcoin has to be positioned within the network in a way that allows payments to flow in the desired direction. A channel can have plenty of bitcoin and still be unable to receive a large payment if the balance is sitting on the wrong side. Routing can occasionally fail. Wallet design matters. Some Lightning wallets manage everything for the user and hold the bitcoin on the user’s behalf, while others provide greater self-custody and therefore require greater responsibility.
That tradeoff belongs squarely inside the Kingdom Bitcoin conversation.
Freedom is not measured solely by how quickly money moves. Stewardship asks who controls it, where the trust sits, what risks have been accepted, and whether the person using the system understands enough to make a wise choice. Lightning can make Bitcoin dramatically more useful for everyday payments, but speed does not absolve us from understanding custody or responsibility.
Acts 6 ultimately teaches something larger than organizational efficiency. The apostles recognized that a growing mission needed structure capable of carrying growth without weakening the foundation that gave the mission meaning. They did not declare that caring for widows was beneath them. They created an architecture where both responsibilities could be honored.
Bitcoin faces a similar architectural challenge. The foundation must remain difficult to corrupt, but everyday commerce cannot require every small payment to demand permanent base-layer settlement. Lightning allows more activity to happen above that foundation while still anchoring ultimately to Bitcoin beneath it.
A sound foundation does not need to do everything. It needs to remain sound enough for everything built upon it. And once money begins moving faster across those higher layers, another question quickly becomes unavoidable.
How much of our financial life should everyone else be able to see?
Kingdom Principle 👑
A strong foundation does not have to perform every function itself. It must faithfully support what is built above it.
God repeatedly brings order through structure. Scripture shows responsibilities being delegated, work being distributed, and different people carrying different assignments without diminishing the importance of the whole. Wisdom recognizes that trying to force every function through one layer can eventually weaken the very foundation we were trying to protect.
Bitcoin’s base layer and Lightning offer a useful technological example. One prioritizes final settlement and durable verification. The other enables faster movement above it. Stewardship begins by understanding which layer is doing what, where responsibility lives, and what tradeoffs accompany convenience.
Prayer 🙏
Heavenly Father, thank You for giving humanity the creativity to build tools that can serve people across distance, borders, and circumstances. Give us wisdom to build on strong foundations without confusing speed with strength or convenience with truth. Help us understand the systems we use and never allow technological sophistication to become an excuse for spiritual shallowness.
May the Holy Spirit guide how we build, spend, give, save, and serve. Keep Jesus Christ as the true foundation beneath everything we do, and teach us to use technology in ways that strengthen households, expand generosity, preserve freedom, and honor the responsibilities You have entrusted to us. In Jesus’ name, Amen. 🙏📖⚡₿☕🏠🕊️👑