A message can cross the world almost instantly while the money attached to it waits for a business day, a review, or an approval. A worker can finish a job and still wait on a reimbursement. A department can have an approved budget and still need permission to use it.
The frustration is not just the delay. It is the distance between being told that something belongs to you and being able to act on it.
We see a connection between financial friction and administrative friction. Whoever controls the account or approval process has considerable influence over what happens next. That does not make every safeguard a scheme. It does make control over access worth examining.
What a bank hold actually means
Check deposits illustrate the problem, but the mechanics matter. Funds availability is not the same as final collection. A bank can make a deposit available before it knows whether the check will be returned unpaid. Holds help manage that risk.
In the United States, Regulation CC limits many deposit holds and requires disclosures. Some checks qualify for next-day availability; other checks have longer schedules, with exceptions for situations such as large deposits, new accounts, or reasonable doubts about collectibility. Weeks of waiting are not the standard for every domestic check.
Banks earn income from the spread between interest earned on assets and interest paid on funding. That does not establish that every payment delay produces extra profit, or that profit is the reason for a particular hold. Regulation CC also generally requires interest on interest-bearing deposits to begin accruing no later than the business day the bank receives credit for the funds.
There is a simpler criticism that does not need an invented motive: the customer cannot necessarily use money when the customer wants to. The institution administers access, subject to law, its agreements, and its own risk decisions.
Faster banking does not remove the gatekeeper
It would be wrong to describe all conventional payments as slow. FedNow allows participating financial institutions to offer instant payments around the clock, every day of the year. Banking can move much faster than a paper-check workflow.
But speed and permission are different properties. An instant payment still runs through an institution that decides whether to offer the service and whether a customer or transaction qualifies. Faster infrastructure can improve the experience without changing who controls access.
That is the distinction worth watching. A faster queue is useful. It is not the same thing as no longer needing the queue.
When process becomes control
The same question applies inside large organizations. Billing requirements, procurement rules, grant conditions, and audit trails often serve legitimate purposes. They can protect patients, taxpayers, customers, and employees. Removing them indiscriminately would create real harm.
Yet each additional approval also gives someone another opportunity to stop the work. A budget can be allocated but difficult to spend. A reimbursement can be owed but remain inaccessible. A routine decision can pass through so many reviewers that no one is clearly responsible for the delay.
Our concern is what happens when the process becomes harder to challenge than the decision it was meant to improve. People start optimizing for approval rather than outcomes. Those doing the work bear the waiting cost, while those controlling the process may feel little pressure to shorten it.
This is an argument about incentives, not proof that every organization is deliberately tightening control. The useful test is concrete: which requirement prevents a real harm, who owns the decision, and can someone explain why the delay is necessary?
What Bitcoin changes
Bitcoin offers a different starting point. Under its current consensus rules, issuance is constrained by a schedule with a maximum supply of roughly 21 million bitcoin. A node verifies those rules instead of relying on an issuer to keep a supply promise.
With self-custody, spending authority comes from satisfying cryptographic conditions, usually by signing with private keys, rather than asking an account provider to release a balance. There is no central Bitcoin administrator that must approve each valid transaction.
That is not a guarantee of instant or unrestricted movement. On-chain inclusion depends on fees, network conditions, and miners. Confirmations accumulate over time; finality is probabilistic, not a fixed deadline. Exchanges and custodial wallets can still restrict withdrawals, and legal obligations do not disappear.
Lightning can complete payments in seconds using payment channels, but routing and liquidity matter. Payments can fail, and closing a channel can require on-chain transactions and waiting periods. Self-custody also shifts responsibility to the owner: lost keys, mistakes, and security failures can be costly and irreversible.
The difference is not that Bitcoin eliminates every constraint. It offers a way to hold and transfer value without putting a single account operator in charge of permission. That changes the relationship between the owner and the institution.
Software should reduce the burden, not perfect it
As reporting and compliance become more demanding, software becomes attractive because it can handle repetitive checks and documentation. That does not mean every occupation will become impossible for humans or that automation can replace human judgment.
There are two possible directions. We can use software to remove unnecessary steps and give people more time for useful work. Or we can use it to enforce an even denser rulebook, making an unreasonable process easier to scale.
The same choice appears when software agents transact. Conventional payment APIs can serve many automated workflows. Bitcoin and Lightning offer another option where small, frequent payments and reduced dependence on account permissions are useful. Neither rail makes an agent trustworthy. Spending limits, secure credentials, usable delivery, and accountability still matter.
For us, the opportunity is not to replace every human decision with a machine or every bank payment with bitcoin. It is to make ownership more meaningful and permission less burdensome. Faster settlement helps. Fewer unnecessary approvals help. Software that gives people back their time helps.
The question to ask of any system is straightforward: does it help the person doing the work, or mainly strengthen the position of the institution standing in the way?
Sources
Federal Reserve Board, A Guide to Regulation CC Compliance
https://www.federalreserve.gov/supervisionreg/guide-regulation-cc-compliance.htm
12 CFR 229.14, Payment of interest
https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-229/subpart-B/section-229.14
Federal Reserve Financial Services, About the FedNow Service
https://www.frbservices.org/financial-services/fednow-service/about-fednow-service/
Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System
https://bitcoin.org/bitcoin.pdf
Kraken, Lightning Network payments, routing and limitations
https://www.kraken.com/learn/lightning-network
Comments0
No comments yet. Start the conversation.