This explainer looks at how Bitcoin and Monero handle privacy, why the difference matters, and why regulators and law enforcement agencies remain uneasy. The argument here is simple. Financial privacy is a normal and legitimate expectation, privacy tools like Monero should be used only for legal and ethical purposes, and those two positions support each other rather than competing.

Privacy Was Always Part of Ordinary Money

Cash has always been private by default. A shopkeeper knows a sale happened, but the bill carries no history of who held it before. Banking added record keeping, and with it a different kind of privacy, one built on confidentiality. Your neighbor cannot request your account history, and a business competitor cannot browse your supplier payments. That confidentiality has limits. In the United States, the Bank Secrecy Act requires banks to keep and report certain records, and the Electronic Frontier Foundation notes that the Supreme Court, in U.S. v. Miller (1976), allowed the government to obtain bank customer data without a warrant. Still, the information stays within a closed circle rather than being published to the world.

Civil liberties groups argue that this circle should not shrink further. In its analysis of proposed cryptocurrency reporting rules, the EFF wrote that financial records “contain a trove of sensitive information about people’s personal lives, beliefs, and affiliations.” Donations to a church, payments to a clinic, or a subscription to a political publication can say a great deal about a person. Coin Center, a Washington policy group focused on cryptocurrency, makes a related case in The Case for Electronic Cash, describing private peer to peer payments as essential to an open society.

Bitcoin Is Transparent by Design

Bitcoin is often described as anonymous, but its creator never claimed that. Section 10 of the Bitcoin whitepaper explains that because all transactions are announced publicly, privacy depends on “keeping public keys anonymous.” In Satoshi Nakamoto’s words, “The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone.”

That model is better described as pseudonymous, and it has proven fragile. Every amount, every sending address, and every receiving address sits permanently on a ledger anyone can download. Once a single address is tied to a real identity, perhaps through an exchange account or a public donation page, its history and connections can be traced. Researchers showed this early. In the 2013 paper A Fistful of Bitcoins, Sarah Meiklejohn and colleagues clustered addresses using patterns such as inputs spent together and change addresses, then labeled many clusters belonging to major services. An entire industry of chain analysis firms now sells this kind of tracing to businesses and governments.

How Monero Hides Senders, Receivers, and Amounts

Monero takes the opposite approach. Instead of publishing everything and hoping identities stay hidden, it conceals the key details of each transaction while still letting the network verify that no coins are created from nothing. Three techniques do most of the work, and each targets one piece of information that Bitcoin exposes.

Ring signatures protect the sender. A transaction input is signed alongside a group of other outputs from the blockchain, so an observer cannot tell which one is actually being spent. Since the August 2022 network upgrade, the standard ring size is 16, meaning one real input hidden among 15 decoys. Stealth addresses protect the receiver. The sender creates a fresh one time address for every payment, so a person can publish a single address while incoming funds land at destinations that cannot be linked back to it. RingCT, short for Ring Confidential Transactions, hides the amount. According to the Monero project, it was introduced in January 2017 and became mandatory for all transactions after September 2017.

The US Treasury, an agency focused on illicit finance, describes the same design in its 2022 National Money Laundering Risk Assessment, listing ring signatures, ring confidential transactions, and stealth addresses as the tools Monero uses to obscure originators, amounts, and beneficiaries.

Default Privacy Versus Optional Privacy

Monero is not the only cryptocurrency with privacy features, but it is unusual in making them mandatory. Zcash, for comparison, uses zero knowledge proofs and lets users choose between transparent addresses and shielded ones. Coin Center’s primer on privacy coins reported that as of May 2020, only about 6 percent of Zcash transactions were fully shielded, while 15 percent were partially shielded.

The difference matters because optional privacy tends to mark the people who use it. When most activity is transparent, the minority that opts out stands apart, and that alone can draw attention. Coin Center notes that because every Monero transaction uses ring signatures by default, “no user draws attention to themselves by choosing whether or not to use ring signatures.” Privacy works best as a crowd, and Monero makes everyone part of the same crowd.

Fungibility and the Problem of Tainted Coins

Fungibility means one unit of money is interchangeable with any other. A dollar bill is worth a dollar regardless of where it has been. On a transparent ledger, that principle weakens. Coins can be flagged because of their history, and a recipient who had nothing to do with that history may find their funds frozen or refused.

The Monero project describes its coin as fungible precisely because transaction histories are hidden. Supporters see this as essential for anything meant to function like money. A currency where some units are worth less than others because of an invisible past is a strange kind of currency, and it places ordinary users in the position of investigating every payment they receive.

The Costs That Come With Opacity

Privacy has real tradeoffs. Monero transactions carry decoys and cryptographic proofs, so they are larger and heavier to verify than a simple transparent payment. Developers have worked to reduce that burden, most recently with Bulletproofs+ and view tags in the 2022 upgrade, but the overhead remains. Auditing is also different. On Bitcoin, anyone can sum visible amounts. On Monero, confidence in the total supply rests on cryptographic proofs rather than amounts anyone can read.

For people who need to share information, Monero offers view keys. Sharing a private view key lets an accountant, auditor, or business partner see incoming transactions to an address. The project itself cautions that outgoing transactions cannot be reliably viewed this way, so a balance shown through a view key should not be relied upon on its own. Privacy at the protocol level also does nothing to change legal obligations. In the United States, the IRS treats digital assets as property and expects taxpayers to report related income and gains, and similar duties exist elsewhere. Keeping finances private from the public is a different matter from keeping them from a tax authority, and the second remains each user’s responsibility.

Regulators Respond With Delistings and New Rules

Governments and large exchanges have pushed back. The Financial Action Task Force, which sets international anti money laundering standards, addresses anonymity enhanced cryptocurrencies in its 2021 updated guidance on virtual assets, which also explains the “travel rule” requiring service providers to obtain and pass along originator and beneficiary information for transfers. A coin that hides both parties by design fits awkwardly into that framework.

Exchanges have responded by removing Monero. In January 2024, OKX delisted Monero along with Zcash and Dash, The Block reported. Binance announced in February 2024 that it would end Monero trading, citing its periodic asset reviews, which include “new regulatory requirements” among the factors considered. Kraken halted Monero for clients in the European Economic Area on October 31, 2024, stating it had “no choice” because of regulatory changes. The European Union’s Anti Money Laundering Regulation goes further: from July 10, 2027, Article 79 prohibits crypto asset service providers from keeping accounts that allow anonymization or increased obfuscation of transactions, “including through anonymity-enhancing coins.” The rule binds regulated providers, not the software itself.

The Strongest Objections, Taken Seriously

The most serious objection is that privacy helps criminals. The Treasury assessment states that FinCEN analysis of suspicious activity reports found some ransomware actors demanding payment in anonymity enhanced cryptocurrencies, and it describes these tools as “creating additional obstacles for investigators.” The IRS was concerned enough to award two contracts, to Chainalysis and Integra FEC, worth up to $1.25 million combined in 2020 to develop tracing tools for Monero and the Lightning Network, Decrypt reported. These are real harms with real victims, and any defense of privacy has to face them honestly.

A second objection comes from researchers rather than regulators. A 2018 study by Malte Möser and coauthors, An Empirical Analysis of Traceability in the Monero Blockchain, found that many early transactions could be traced through weaknesses in how decoys were chosen. Monero later changed its protocol, but the lesson stands: privacy systems must be continually tested, and users should not assume perfection. Supporters answer the first objection by pointing out that cash, encryption, and closed doors also help criminals, yet societies keep them because the benefits to everyone else are larger. The two sides genuinely weigh those benefits differently.

Privacy and Lawful Use Belong Together

The legitimate uses are concrete. When balances are public, a person who receives a large payment can become a target for theft or extortion. Businesses need to keep supplier payments, salaries, and margins away from competitors. Journalists and activists working under hostile governments have good reason to keep their funding sources out of public view. Ordinary people simply expect their spending to remain their own business, as it does with cash.

None of these uses requires breaking the law, and that is the point. The strongest case for Monero is not that it lets people escape rules, but that it restores a level of privacy most people already consider normal. Treating privacy tools as legitimate while using them only for legal and ethical purposes is the most credible way to defend them, and the most likely path to keeping them available.

This article offers general information only. It is not financial or legal advice.

This short scene is an illustration, not a prediction or a data point. Picture a weekday in 2040. A driverless car waits at the curb, and a home battery charged by midday sun runs the kettle. An AI assistant has drafted the paperwork for review, and a weekly injection keeps a relative heart risk in check.

Now notice what the picture leaves out. No flying taxi lands on the roof. No swarm of microscopic robots repairs an artery. The rent is still due, and the electric bill still stings. The rest of this article asks which parts of that morning rest on evidence, and which belong to fiction.

How to Read the Ratings

Each prediction gets one label for the window from 2035 to 2040. Likely means current deployment data and trial timelines already point there. Possible means a credible path exists, but it depends on a result nobody has yet. Unlikely means the known obstacles outweigh the known progress.

Each rating also says what would change it. Sources are named so you can check them, and any number I could not verify was left out.

Machines That Move

Self-Driving Cars

Robotaxis are real. In September 2026, TechCrunch reported that Waymo serves 15 U.S. cities and averages 500,000 paid rides each week, up from 50,000 in May 2024. Its fleet is roughly 4,000 vehicles, about 80 percent in California and Texas. Waymo reports 271.3 million rider-only miles through June 2026, with 82 percent fewer injury crashes and 95 percent fewer serious-injury-or-worse crashes than a human benchmark. These are company figures built on public crash reports.

The obstacles are rare odd situations, city-by-city permits, vehicle cost, and public trust. Regulators are investigating Waymo cars passing school buses, and tariffs raise the cost of its Chinese-built Ojai minivan. Rating: robotaxi service in many large metro areas is likely. A personal car that drives itself everywhere, including snow and rural roads, is unlikely. Safety rates holding as miles grow, or a cluster of serious failures, would move this.

Electric Air Taxis

As of early October 2026, neither Joby nor Archer holds an FAA type certificate. Joby reports it is in the fifth and final stage. Archer closed Phase 3 of four in April 2026. Dates have slipped before: in 2021 a former Archer co-CEO told CNBC the company was working toward certification by 2024. In Europe, EASA applies a special condition called SC-VTOL, and Vertical Aerospace targets UK certification in 2029.

Scale is the second limit. Joby says its Marina plant can build up to 24 aircraft per year, and its Dayton plant is designed for up to 500. Even the larger figure yields only a few thousand aircraft in a decade, and Joby has not disclosed a price. Rating: certified service on a few routes is likely, while mass commuting is unlikely. Certificates, output above several hundred aircraft yearly, and taxi-level fares would change that.

Robots and Automation

The International Federation of Robotics counted 542,076 industrial robots installed in 2024, with 4,663,773 in operation. Amazon announced in 2025 that it had deployed its one millionth robot across more than 300 facilities, mostly mobile units rather than humanoids. It also said a newer Louisiana site needs 30 percent more staff in maintenance and engineering roles.

The realistic labor effect is task shifting. Heavy lifting and sorting move to machines, while demand grows for technicians and planners. Rating: more warehouse and factory automation is likely. Humanoids at large scale in logistics are possible. Humanoids handling varied chores in ordinary homes are unlikely. Independent price and safety data from real worksites would move these.

Intelligence and Energy

AI Progress and Its Limits

The Stanford AI Index 2026 says generative AI reached 53 percent population adoption within three years. It also describes a jagged frontier: one model won gold at the International Mathematical Olympiad, yet the best model reads analog clocks correctly only 50.1 percent of the time. AI agents still fail roughly one attempt in three on structured tests.

METR measures the length of tasks that models finish at 50 percent reliability. That length doubled about every seven months from 2019 to 2025, and every 131 days since 2023. Claude Opus 4.5 scored about 320 minutes, with a wide interval of 170 to 729. Rating: AI as a routine office tool is likely. Dependable autonomous work lasting days is possible. Trust without human review in medicine or safety-critical settings is unlikely. Gains at 90 percent reliability, and fewer documented incidents (362 in 2025, up from 233), would change my view.

Cheap Energy, Lagging Bills

Generation keeps getting cheaper, yet bills have not followed. The IEA reports that from 2019 to 2024 household electricity prices rose 36 percent in the European Union and 26 percent in the United States. Net earnings for a two-earner family with two children rose 25 and 23 percent. Networks, taxes, and fees take a large share of each bill. I covered this gap in cheap solar, batteries, and rising electric bills.

Batteries help: the IEA links fewer negative-price hours in California and Texas in 2025 to growing storage. Rating: abundant cheap generation in sunny regions is likely. Household bills that fall in real terms are possible, but they depend on wires, tariffs, and rate design more than on panels. Reform of network charges would change this.

Aging Medicine: The Main Thread

What Could Exist by 2040

The strongest human evidence concerns diseases of aging, not aging itself. The SELECT trial enrolled 17,604 adults aged 45 or older with heart disease and excess weight but no diabetes. Weekly semaglutide cut the combined rate of cardiovascular death, heart attack, and stroke by 20 percent (hazard ratio 0.80) over a mean of 39.8 months. That is a real healthspan gain for a defined group. It does not show that aging slowed.

Other tools remain early. The TAME metformin trial was designed for 3,000 adults aged 65 to 79 over six years. As of September 2026, trackers found no registry record, and the sponsor still seeks donors. Reported costs run $45 to $70 million. A 2023 senolytic trial in five people with Alzheimer disease found safety but no significant cognitive change, and a 2024 trial in 60 women found no overall drop in bone resorption. Epigenetic clocks track risk across populations, yet reviews say they are not validated for individual decisions or as trial endpoints.

The Counterevidence and the Rating

Olshansky and colleagues, writing in Nature Aging in 2024, studied the eight longest-lived countries plus Hong Kong and the United States from 1990 to 2019. Gains in life expectancy slowed. Survival to age 100 is unlikely to exceed 15 percent for women and 5 percent for men. Repeating the 30.2 percent drop in old-age mortality seen in that period would add only 2.5 years of life expectancy at birth. The authors call these limits not brick walls, since a drug that slows biological aging could change them.

Rating: drugs that delay specific age-related diseases in targeted groups are possible by 2040. An approved drug for aging itself is unlikely, because TAME has not started and needs six years. Large lifespan extension is unlikely. A funded, registered trial, a clock validated against real outcomes, or a strong randomized human result would change that. For the economics, see the longevity dividend.

Nanobots and Molecular Medicine

DNA nanotechnology is a vivid research field. Reviews from 2025 list the hurdles to human use: enzymes that degrade DNA structures, poor stability in blood, immune reactions, weak targeting, and costly manufacturing. One developer in the field states it has no approved products and no open clinical trials. Nucleic-acid nanoparticle drugs have reached early trials, but they are not robots.

Rating: more precise targeted drug delivery is likely. A first DNA nanodevice therapy tested in people is possible. General-purpose medical nanobots that patrol the body are unlikely. Human safety data and clinical-scale manufacturing would change this.

Abundance, With Receipts

Harvard JCHS reports the median home price was 4.7 times median income in 2025, down from a 5.0 peak in 2022 but far above the 1990s average of 3.2. Child Care Aware puts average child care at $13,184 in 2025, which is 10 percent of median income for two-parent households and 33 percent for single parents. The College Board lists $11,950 for public in-state tuition in 2025-26. CMS projects health spending rising from 17.6 percent of GDP in 2023 to 20.3 percent in 2033.

What gets cheap is anything made of information, energy, or factory output: software, many goods, and electricity generation. What resists is land and work that needs human time, such as care and teaching. Who shares the gains is a policy choice, as I explored in who owns AI productivity gains. Rating: cheaper goods and software are likely. Falling housing, care, and health costs as a share of income are possible. True post-scarcity is unlikely.

The Rating Summary

Each rating below applies to 2035 to 2040.

• Likely: robotaxis in many metro areas; certified eVTOL on a few routes; more automation; AI as a work tool; cheap generation; cheaper goods and software; targeted drug delivery.
• Possible: humanoids at logistics scale; days-long autonomous AI work; lower bills; healthspan drugs; a first DNA nanodevice trial; cheaper housing and care.
• Unlikely: go-anywhere personal robocars; eVTOL commuting; humanoid home helpers; unsupervised high-stakes AI; an approved aging drug; large lifespan extension; general nanobots; post-scarcity.

The pattern is plain. Software and generation move fast, while physical, regulated, and human-time systems move slowly.

What Readers Can Do Now

These steps hold up whichever ratings prove right.

• Learn to use AI tools while checking their numbers and citations.
• Build skills that pair with machines, such as maintenance, analysis, and communication.
• Protect health with proven basics, and discuss any drug with a clinician.
• Plan retirement with realistic lifespans, not 100-year assumptions.
• Ask what share of an energy bill is generation versus wires.

Also test any headline: does it name a date, a regulator, a trial, or a number? If not, wait for evidence.

Conclusion: Confidence Is a Skill

The 2040 that evidence supports is useful and uneven. Rides, software, and electricity generation improve fast. Aircraft, medicine, housing, and care improve slowly, because rules, biology, land, and human time set the pace. Aging research is the key thread, and its honest rating is a hopeful maybe for healthspan and a firm unlikely for dramatic lifespan gains.

Hold forecasts loosely, and watch certificates, registered trials, safety data, and the share of household budgets. When those numbers move, the ratings should move with them.

This article is informational forecasting, not medical, financial, or legal advice.

That question is older than artificial intelligence, and it is the most important one about it. Technology decides how much a society can produce. Ownership decides who receives it. A machine that doubles output can make a town richer or make a handful of shareholders richer while the town stays where it was. The difference is set by contracts, laws, and habits of ownership that people chose, and can choose again.

The Principle: Productivity Is Shared Only When Ownership Is Shared

Economists often speak as if rising productivity automatically lifts wages. For about three decades after the Second World War, it roughly did. Since then, the link has weakened. The Economic Policy Institute calculates that net productivity in the United States grew 90.2 percent from 1979 to 2025, while hourly compensation for typical workers grew 33.0 percent. Before 1979, the two lines moved almost together, with productivity growing about 2.5 percent a year and compensation about 2.1 percent.

The gap went somewhere. Part of it went to higher earners within the workforce, and part went to the owners of capital. That second channel matters most for AI, because AI is capital. A model, the data centers that run it, and the software built on top of it are assets. Their returns flow to whoever holds the shares.

Who Holds the Shares Today

The Federal Reserve’s Distributional Financial Accounts show how concentrated those holdings are. In the second quarter of 2026, the wealthiest 1 percent of American households held 50.9 percent of all corporate equities and mutual fund shares. In mid 2025, the top 0.1 percent alone held about 24 percent. Half of the stock market, in other words, belongs to one household in a hundred.

If AI raises corporate profits and the ownership map stays as it is, the arithmetic is predictable. Roughly half of the gain in stock value lands with the top 1 percent before anyone else sees a dollar.

Why AI Could Widen the Gap Faster

Earlier waves of automation needed large numbers of workers to build, install, and maintain the machines, which spread some of the gains through wages. Software scales differently. Once a model is trained, serving one more customer costs very little. That cost structure favors a small number of firms with large fixed investments and very wide reach, and those firms are mostly owned by the same concentrated group of shareholders.

None of this means that workers gain nothing. Cheaper services help everyone who buys them. But a household budget is dominated by rent, health insurance, childcare, and tuition, and those costs have tended to rise faster than general inflation for years. A free chatbot does little for a family whose rent consumes a third of its income.

Three Working Models of Broad Ownership

The encouraging part of this story is that broad ownership is already real. It exists at scale, in ordinary places, and it has decades of data behind it. Three models stand out because they are tested, legal today, and compatible with a market economy.

Each has strengths and weaknesses. Looking at them honestly is more useful than treating any one as a cure.

Employee Ownership

The National Center for Employee Ownership, analyzing Department of Labor filings, reports 6,609 employee stock ownership plans in the United States for plan year 2023, covering 15.1 million participants, of whom about 11 million were active employees. Those plans held more than 2 trillion dollars in total assets and paid over 166 billion dollars to participants in 2023. Privately held ESOP companies, which are common in manufacturing, engineering, and construction, have been growing in number for five straight filing years.

An employee owned firm that adopts AI tools faces a different calculation than a conventional one. When the claims adjuster’s team becomes more productive, the extra profit raises the value of shares the team itself holds. Employee ownership does not stop hard decisions, but it changes who benefits from making them well.

Cooperatives

Cooperatives take the idea further by giving each member one vote, regardless of how much capital they contribute. Credit unions, rural electric cooperatives, and agricultural co-ops already serve tens of millions of Americans. The model has a natural fit with digital services, where a cooperative of freelancers, drivers, or small sellers could own the platform that matches them with customers instead of paying a large commission to an outside owner.

The challenge for cooperatives is capital. Training frontier AI models costs enormous sums, and co-ops have historically struggled to raise money because they cannot offer outside investors control. The realistic path is for cooperatives to own the application layer, the tools and services built on open or licensed models, where costs are far lower and local knowledge matters more than raw computing power.

Public Dividends

The third model treats a shared resource as common property and pays every resident a share of its returns. Alaska has done this with oil revenue since 1982. The Alaska Permanent Fund holds more than 86 billion dollars, according to Alaska Public Media, and pays an annual dividend to more than 600,000 eligible residents. The 2024 dividend was 1,702 dollars per person. The 2025 dividend was 1,000 dollars.

That drop is the most instructive fact in the whole story. The Associated Press reported that under the fund’s older formula, residents would have received about 3,800 dollars in 2025. Lawmakers reduced the payment because oil revenue fell and the state needed money for schools and other services. A public dividend is only as durable as the political rules that protect it. When those rules are loose, the dividend becomes a budget line that competes with every other budget line.

Facing the Counterarguments

A fair case for broad ownership has to take its critics seriously. Several objections carry real weight, and households would feel the consequences if they were ignored.

The first objection is that markets already let anyone buy shares. That is true in principle. In practice, a family spending most of its income on rent, groceries, and insurance has little left to invest, and the compounding returns of ownership go to those who started with capital. Open access to a market is a different thing from an actual stake in it.

Risk Concentration and Inflation

A second objection deserves careful attention. Employee ownership can concentrate risk. A worker whose wages and savings both depend on one company can lose both at once if the company fails. Sound ESOP design includes diversification rights as workers approach retirement, and responsible plans encourage savings outside the firm as well.

A third objection concerns inflation. If public dividends were funded by printing money or by large deficits, they could raise prices and wipe out their own value. A dividend paid from the real returns of an invested fund, as in Alaska, avoids that problem because it distributes income that already exists. The source of the money matters as much as the size of the check.

Wages Still Matter

A final caution is that ownership is a complement to wages, never a replacement. A dividend of a thousand dollars a year is helpful, and it does not pay for a hospital stay or a year of college. Policies that keep labor markets tight, protect bargaining, and lower the cost of housing and healthcare remain essential. Ownership adds a second income stream to the household. It does not excuse neglect of the first.

Honesty also requires admitting uncertainty about AI itself. Economists disagree sharply about how large its productivity effects will be and how fast they will arrive. If the gains are modest, the stakes of ownership are modest too. If they are large, the ownership question becomes one of the defining economic issues of the century. Preparing for the larger case costs relatively little.

What Readers Can Do Now

Most people will never set national policy, but ownership decisions happen at every scale, and many of them are within reach.

• Ask about ownership at work. Owners of small and midsize businesses who are nearing retirement often sell to private equity because nobody suggested an alternative. Selling to an ESOP or a worker cooperative is a legal, established option, and resources from the National Center for Employee Ownership explain how it works.
• Use member owned institutions. Credit unions and cooperatives return surplus to their members. Moving everyday banking and purchasing to them keeps more value in the community.
• Support durable public funds. When a city, state, or country considers a sovereign or community fund, the key questions are whether the principal is protected and whether the dividend formula is written into law rather than left to annual budget fights.
• Build small with open tools. Open models and open source software lower the cost of starting a cooperative or employee owned service business, which places the application layer of AI within reach of ordinary groups.

None of these steps requires waiting for a breakthrough. Each one shifts a small piece of future AI income toward people who would otherwise receive none of it.

Abundance Needs an Address

Back at the insurance office, the software will keep improving, and the adjuster’s team will keep closing more claims. Whether that progress shows up as a larger dividend on her retirement statement, a shorter work week, or a bonus for a shareholder she will never meet depends on a decision about ownership. That decision is being made now, quietly, in board rooms, statehouses, and the succession plans of family businesses.

Post-scarcity is a question of distribution as much as production. A world that can make almost anything cheaply can still leave most people anxious about rent if the income from that capacity flows to a narrow group. The tools to spread it already exist: employee ownership, cooperatives, and public funds with strong rules. The principle is plain enough to carry into any conversation. Abundance reaches everyone only when everyone owns a piece of the machines that create it.

This article is informational and is not financial or legal advice.

Nothing about this family is unusual. They are living inside two price curves at once. One curve keeps falling, and it carries screens, phones, software, solar panels, and now artificial intelligence. The other keeps rising, and it carries the bills that decide whether a household feels secure: rent, health care, college, and child care. Understanding why those curves split apart is the first step toward bending the expensive one down.

The Curve That Keeps Falling

In 1936, an aircraft engineer named Theodore Paul Wright published a paper in the Journal of the Aeronautical Sciences called “Factors Affecting the Cost of Airplanes.” He had noticed a steady pattern. Each time the total number of airplanes built doubled, the labor needed for each new plane dropped by a predictable share. Cost, he found, follows experience rather than the calendar.

That observation became known as Wright’s Law, and it describes almost every manufactured product that is built at scale. Workers learn shortcuts. Engineers redesign parts. Suppliers find cheaper materials.

Solar, Batteries, and Screens

Solar power is the textbook case. A watt of solar module capacity cost about $96 in 1976, measured in today’s dollars. By 2024 it cost about $0.26. Lithium-ion battery packs tell a similar story. BloombergNEF’s annual survey found average pack prices of roughly $790 per kilowatt-hour in 2013 and about $115 in 2024.

Consumer electronics ride the same curve. According to Bureau of Labor Statistics price data compiled by economist Mark Perry of the American Enterprise Institute, the price of televisions fell about 98 percent between January 2000 and late 2025. Computer software fell about 75 percent. Toys fell about 74 percent, and cell phone service fell about 43 percent.

AI Joins the Club

Artificial intelligence is now on the fastest version of this curve yet. The Stanford AI Index 2025 reports that the cost of querying a model performing at the level of GPT-3.5 fell more than 280-fold between November 2022 and October 2024. A task that once cost real money per request now costs a fraction of a cent.

That matters because AI is not a product sitting on a shelf. It is a tool that can be applied to other work. If cheap intelligence can reach the expensive side of the economy, it could do something TVs never could. It could lower the price of services, not just gadgets.

The Curve That Keeps Rising

Now look at the other half of Perry’s chart, which he has called the “chart of the century.” Over the same stretch from 2000 to late 2025, overall consumer prices rose about 92 percent. Hospital services rose about 275 percent. College tuition and fees rose about 196 percent. Child care and nursery school rose about 185 percent. Medical care overall rose about 129 percent, and housing rose about 111 percent.

Average hourly earnings rose about 131 percent over the same period. That number explains a great deal. Wages beat general inflation, so the typical hour of work buys more of most things than it did in 2000. Yet hospital care, tuition, and child care rose faster than wages. For those bills, an hour of work now buys less than it did a generation ago.

Why These Bills Hurt More

The categories that got cheaper are mostly things people buy occasionally. A family replaces a TV every several years. The categories that got expensive are paid every month or come in large, unavoidable lumps. Rent arrives on the first. Child care is often the second-largest bill a young family pays. A single hospital stay can erase a year of savings.

So averages can mislead. A household that rents, has small children, and carries a health condition lives almost entirely on the rising curve. Cheaper electronics are pleasant. They do not cover the gap.

What Happened to Wages

Wage stagnation is real, but the details matter. The Bureau of Labor Statistics tracks median usual weekly earnings for full-time workers, adjusted for inflation. In constant 1982 to 1984 dollars, that figure was $332 in 1979, $334 in 2000, and $374 in 2025. That is growth of about 13 percent over more than four decades, and almost all of it arrived after 2014.

Economists debate how to read this. Some point out that average hourly earnings, total compensation including benefits, and different inflation measures show stronger gains. Others note that rising health insurance premiums have absorbed much of what employers spend on workers, so take-home pay grew slowly even when total compensation grew faster. Both views can be true. Either way, the typical worker gained modestly, while the price of the biggest essentials rose sharply.

Why the Expensive Curve Will Not Bend on Its Own

The rising categories share a few traits. They are services rather than goods. They cannot be imported. They depend on land or on licensed people. And they often face limited competition. Each trait points to a specific cause.

These causes do not belong to one political party. They are structural, which means they respond to structural fixes.

Baumol’s Cost Disease

In the 1960s, economists William Baumol and William Bowen studied live performance. A string quartet in 1800 needed four musicians and about the same amount of time as a string quartet today. Productivity did not rise. Yet musicians must be paid wages that compete with factories and offices where productivity did rise. So the price of a concert climbs.

Teaching, nursing, and child care work the same way. One caregiver can safely watch only so many toddlers. A nurse can attend only so many patients per shift. When wages rise across the economy, these labor-heavy services get more expensive even if nothing about them changes. That is not a failure. It is arithmetic.

Land, Zoning, and Gatekeeping

Housing has a different problem. A home is a building plus the land under it, and land in high-demand cities is scarce by definition. Zoning rules that ban apartments on most residential lots, require large minimum lot sizes, or mandate parking make that scarcity worse. When cities limit what can be built, rising demand turns into rising rent.

Health care and higher education add licensing and gatekeeping. Licensing protects quality, but it also limits who may perform a task and how many new providers can enter. Hospital mergers have reduced competition in many regions. Accreditation and prestige make it hard for cheaper colleges to win students. Each barrier may have a reason. Together they keep prices high.

Can AI Bend the Expensive Curve?

Here is the honest answer. In some places, yes. In others, only if policy changes first. The difference depends on whether the cost comes from labor and paperwork, which software can shrink, or from land and permission, which software cannot create.

Hype in either direction does damage. Promising that AI will fix rent creates cynicism. Dismissing it entirely leaves real savings on the table.

Where AI Plausibly Helps

Several costs on the rising curve are made of paperwork and routine cognitive work, which is exactly what cheap AI does well.

• Tutoring. A capable AI tutor can give one-on-one practice to students whose families could never afford a private tutor, easing one source of the Baumol problem in education.
• Health care administration. Billing, coding, prior authorization, and documentation consume a large share of clinician time and hospital budgets. Automating that work could free staff for patients.
• Design and permitting. Software can check building plans against codes, speed reviews, and help standardize designs, cutting months from projects where delay itself costs money.

None of these replaces a nurse at a bedside or a teacher in a room. They shrink the overhead around those people, which is where much of the cost has quietly grown.

Where AI Cannot Help Without Policy

No algorithm can create land in a city where zoning forbids building. A faster permit review means little if the answer is still no. AI can draft a perfect apartment plan, but only a city council can make that plan legal on most lots.

Credentialing works the same way. If a task requires a specific license, cheaper software does not lower the price until rules allow trained people, supported by good tools, to do more of the work. In these areas, technology is ready before the law is. Savings arrive only when reform catches up.

Building Abundance That Reaches Every Household

Michael Ten’s mission at IdeaRiff is abundance for all, and the two price curves show why that goal needs more than one tool. Cheaper technology handles half the job. Reforms in housing, health care, and education handle the other half. Without both, families keep buying cheaper TVs while falling behind on rent.

There is also a role for income floors. A basic income, delivered through trusted community channels such as credit unions and nonprofit networks, can give households stability while slower reforms take hold. Delivery through local institutions keeps money close to the people it serves. Ownership matters as well. When communities can own and use open tools, the savings from cheap AI flow to them rather than collecting with a few platforms.

What to Push For

Readers who want the expensive curve to bend can support concrete, nonpartisan steps that already have backing across the political spectrum.

1. Zoning reform that legalizes apartments, duplexes, and accessory dwellings near jobs and transit.
2. Faster, digital permitting with clear timelines.
3. Scope-of-practice updates that let nurse practitioners, pharmacists, and other trained professionals do more.
4. Price transparency and competition review in hospital markets.
5. Open educational tools and lower-cost credential paths.
6. Pilots of income floors run through credit unions and nonprofits.

None of these requires picking a side. Each simply removes a barrier between people and cheaper essentials.

What to Watch For

The best test is simple. Track the next annual update of the BLS price data. If AI is truly reaching the rising curve, hospital services, tuition, and child care should start growing more slowly than wages. If they do not, the savings are being captured somewhere along the way.

Watch local decisions too. City council votes on housing and state votes on licensing will shape your budget more than any new gadget. The TV will keep getting cheaper on its own. The rent will not.

This article is for educational purposes only and is not financial advice.

That small message carries a big question. If a company can decide which working parts your device will accept, who really owns it? You paid for the phone. Yet the final say over its repair sits somewhere else, on a server you will never see.

This article makes one argument. Right to repair is freedom tech for physical things. It belongs in the same family as open source software, self-custody, and encryption, and it deserves the same attention from anyone who cares about real ownership.

What Freedom Tech Already Teaches Us

Freedom tech is a loose name for tools that move control from institutions back to individuals. Open source software lets you read, change, and share the code you run. Self-custody lets you hold your own keys instead of trusting a third party with your money. Encryption and privacy tools let you decide who sees your messages. The common thread is simple. You should not need permission to use what is yours.

Most of that conversation happens on screens. It is about code, keys, and data. But the same principle applies to the objects on your desk, in your kitchen, and in your garage. A laptop, a dishwasher, or a tractor is also a bundle of rules about who may open it, fix it, and keep it running. Those rules can favor the owner or the maker.

Ownership is a set of abilities

On paper, ownership is a receipt. In daily life, it is a list of things you are able to do. Can you open the case? Can you buy a replacement part? Can you hire any technician you choose, or must you go back to the company that sold it? Each yes makes ownership thicker. Each no makes it thinner.

When the maker controls the parts, the diagnostic tools, the manuals, and the software that approves each repair, the answers drift toward no. At that point you are closer to renting your device than owning it.

Repair is the hardware version of self-custody

Self-custody means you hold the keys. Open source means you can read the code. Right to repair means you hold the manual, the parts list, and the freedom to choose who does the work. The logic is the same in all three cases. Remove the gatekeeper, and the user gains real control.

Seen this way, repair is not a hobby or a trend. It is the physical layer of a larger idea. A world with free software running on devices nobody may fix is only half free.

How Control Slips Away From Owners

Products rarely announce that they are hard to fix. The change happens through small design and policy choices.

None of these choices changes the price tag. They change what the price buys. Each one shifts a little more power from the person who owns the device to the company that made it.

Parts pairing in practice

The newest barrier is called parts pairing. A manufacturer links a component, such as a screen, battery, or camera, to one specific device. If a different part is installed, the device checks whether the part has been approved through the maker’s own software. If it has not, the device can show warnings, hide features, or refuse to work with the part.

The iPhone is the best known example. According to Apple’s own support pages, the Parts and Service History screen can label a replaced screen, battery, or camera as “Unknown” when the part is not genuine, or when it has not been verified and linked to the phone after the repair. An unverified battery can also lose reliable battery health readings. Apple has since added a Repair Assistant that lets supported genuine parts, including used ones, be calibrated on the device. That is real progress. It also shows where the power sits. The owner gets the feature back when the maker’s software agrees.

The cost of a missing permission

Think about what parts pairing means for a working part. The part fits. The part functions. The only thing missing is a permission. That is a software lock on a physical object, and it is the clearest place where freedom tech and repair meet.

The costs land on ordinary people. Devices that could have been fixed for a modest price are replaced instead. Every forced replacement moves money out of households and into a small number of large firms.

The Laws That Are Opening the Hood

Lawmakers have started to treat repair as a matter of ownership rather than convenience. Several states and the European Union now require makers to share what repairers need. The details differ, but the direction is the same. More parts, more manuals, and fewer locks.

Here are the key rules worth knowing. These are summaries for general education. For specifics, read the full text or check with your state attorney general.

California and Minnesota set the baseline

California SB 244 took effect on July 1, 2024. For electronics and appliances with a wholesale price of $100 or more, makers must offer documentation, functional parts, and tools for at least seven years after the last date a model was manufactured. For products wholesaling between $50 and $99.99, the requirement is three years.

Minnesota’s Digital Fair Repair Act also took effect on July 1, 2024. It covers digital electronic equipment sold on or after July 1, 2021. Makers must make parts, tools, and documentation available to owners and independent repair shops on fair and reasonable terms. Together, these two laws set a simple expectation. If you sell it, you help keep it running.

Oregon takes aim at parts pairing

Oregon SB 1596 goes a step further. It bans parts pairing that blocks a working replacement part, reduces the performance of a device, or shows warnings the owner cannot dismiss. The rule applies to consumer electronic devices first made and sold after January 1, 2025. The Oregon Attorney General can enforce against violations that occur from July 1, 2027.

That makes Oregon one of the first places to treat a software lock on a part as a consumer issue in its own right. It names the exact problem the unknown screen message represents.

Europe moves on its own track

The European Union adopted Directive (EU) 2024/1799 in June 2024 to promote the repair of goods. Member states were required to apply their national rules from July 31, 2026. Progress has been uneven. Germany had its law in force by that date, while several large markets, including the Netherlands and Italy, were still working through their bills in the weeks after the deadline.

Even with the delays, the signal is clear. Repair is becoming a standard expectation in major markets, not a special request.

Repair as a Path to Abundance

Abundance is usually framed as making more things. Repair offers a quieter version. It is about getting more years out of the things you already have. A phone that lasts six years instead of three doubles the value of the money spent on it.

That extra value stays in the household. When products cannot be fixed, each purchase starts to behave like a subscription to the maker, with a renewal fee every time something breaks.

Community repair keeps skills alive

Volunteer repair cafes show what this looks like at street level. Neighbors bring broken lamps, toasters, and bicycles, and volunteers help fix them while teaching the owners how.

Those events depend on access. A skilled volunteer can do little without parts and manuals. Good repair laws and repair-friendly design make every local fixer, paid or unpaid, more useful to the people around them.

How to Buy With Repair in Mind

You do not have to wait for every law to pass. The most direct vote you have is at checkout. A few minutes of research before you buy can add years to a device and keep more control in your hands.

Here is what to look for:

• Published repair manuals. Check whether the maker offers official guides or whether independent guides exist for the model.
• Parts you can buy. Look for an official parts store that sells to owners, not only to authorized shops.
• Repair scores. Some regions publish repairability ratings, and independent sites score popular devices.
• Standard screws and replaceable batteries. These small details often decide whether a repair costs little or a lot.
• Software support length. A device that stops getting updates can become unsafe long before the hardware fails.
• Parts pairing policies. Search the model name with “parts pairing” or “unknown part” before you buy.

Questions to ask before you pay

A short checklist helps at the store or online. Ask whether an independent shop can replace the battery without the maker’s approval. Ask how long the company promises parts and updates.

If the answers are vague, treat that as information. A company that is proud of its repair support usually says so clearly. Silence often means the gatekeeper is still in place.

Conclusion

Freedom tech has taught a generation to ask who controls their code, their keys, and their data. The same question belongs to the physical world. When a maker can veto a working part, withhold a manual, or lock out an independent technician, ownership becomes a rental agreement with extra steps.

Right to repair closes that gap. Open manuals, available parts, and independent repair do for hardware what open source and self-custody do for software and money. Buy with repair in mind, support the laws that open the hood, and keep the things you own working for you.

This article is for educational purposes only and is not legal advice.

The payoff of fixing this is concrete. You get notes you can still open in twenty or thirty years with whatever software exists then. You avoid lock-in to one company and its pricing changes. And you hold files you own outright, stored where you decide, readable by any editor and by your own local AI. Some writers call a collection like this a “second brain”, a term popularized by Tiago Forte’s productivity book. This article uses plainer words: notes, notes library, and personal knowledge base.

Why a Single App Is a Weak Home for Lifelong Notes

Software companies are businesses, and businesses change. Evernote offers a clear example. Bending Spoons agreed to acquire it in November 2022, closed the deal in January 2023, and laid off 129 employees the following month. In December 2023, the free plan dropped to a maximum of fifty notes and one notebook per account, down from limits that had allowed up to 100,000 notes.

Evernote is one case among many. Google shut down Google Reader in 2013, and many smaller tools have closed or pivoted since. Apps still have value, but an app should be treated as a lens for viewing your notes, while the notes themselves live somewhere you control. When the lens breaks, you swap it for another one and keep your eyes.

Five Layers of a Long-Lasting Notes Library

A useful way to think about durability is as a stack of five layers: format, identity, links, copies, and publication. Each layer answers one question, from whether future software can read the file to whether a note should be public and permanent.

You can adopt the layers one at a time. Fixing the first two layers alone makes a large difference.

Layer One: Format

The most durable everyday format for personal notes is plain text, and Markdown is the most popular way to add light structure to it. A Markdown file is readable by a person even with no special software. The CommonMark specification gives the syntax a stable public definition, which reduces the risk of one tool interpreting your files differently from another.

For finished documents meant for long term preservation, institutions often prefer richer formats. The Library of Congress Recommended Formats Statement lists XML based markup, EPUB3, and PDF/A among its preferred formats for textual works, with plain text as an acceptable format. A sensible personal rule follows from this: keep working notes in Markdown, and when a piece becomes finished, export a PDF/A or HTML copy alongside it.

Layer Two: Identity

Every note needs a stable identity that does not depend on a database. The simplest method is a file name that combines a date stamp with a short title, such as 20261009-durable-notes.md. Date stamps sort naturally and rarely collide.

Identity also includes metadata. A small block of key and value lines at the top of each file, often called front matter, can record tags, a source URL, and a created date. Because front matter is plain text, any future tool or script can read it. Avoid storing important facts only in a colored label or proprietary field, since those rarely survive an export.

A Folder Layout You Can Copy

A simple structure keeps identity and privacy clear from the first day. The layout below uses one top folder, a few subfolders, and date-stamped file names:

• notes/ as the top folder for everything
• notes/inbox/ for quick captures, such as 20261009-podcast-idea.md
• notes/library/ for lasting notes, such as 20261009-durable-notes.md and 20250314-reading-habits.md
• notes/index/ for one map per topic, such as index-writing.md and index-health.md
• notes/attachments/ for images and PDFs, named to match their note, such as 20261009-durable-notes-diagram.png
• notes/public/ for finished pieces you are happy to publish
• notes/archive/ for PDF/A or HTML exports of finished work

Lowercase names with hyphens instead of spaces work on every operating system and in web addresses. Keep the tree shallow so links survive reorganizing.

Layer Three: Links

Links are what turn a pile of notes into a personal knowledge base, and they are also the first thing to break during a migration. The wiki style double bracket link, which places a note title inside two pairs of square brackets, is now supported by many tools, including Obsidian and Logseq. Standard Markdown links that point to a relative file path are even more portable, since nearly every Markdown renderer understands them.

Two habits protect links over time. First, link to the stable file name rather than to a heading or a block identifier that only one app understands. Second, keep a plain index note for each major topic that lists its key notes in order. If every automatic backlink feature vanished tomorrow, these index notes would still give you a readable map of your own thinking.

Layer Four: Copies

Format and links mean nothing if the only copy sits on one laptop. The widely used 3-2-1 backup rule, a phrase coined by photographer Peter Krogh in his book on digital asset management, calls for three copies of your data, on two different types of media, with one copy kept off-site. For a notes folder, that might mean the working copy on your computer, a second copy on an external drive or home server, and a third copy in an encrypted cloud backup.

Sync is helpful, but sync is a different thing from backup. A sync service faithfully copies deletions and corruption to every device within seconds. A true backup keeps older versions you can roll back to. Git works well here, since every commit is a snapshot that can be pushed to more than one remote. Schedule it to run automatically.

Layer Five: Publication

Some notes are meant to be shared: reading summaries, glossaries, or public essays. For these, decentralized storage adds a layer that no single host controls. IPFS identifies files by a content identifier derived from the data itself, so the same file has the same address wherever it is stored. Content on IPFS stays available only while at least one node keeps it pinned, which means you either run a node yourself or rely on a pinning service.

Arweave takes a different approach. Uploaders pay a one time fee that, according to its documentation, is intended to cover storage for 200 years at present costs, with the remainder held in an endowment for later years. That makes it attractive for notes you want to keep public indefinitely. Never upload anything private, since removal is designed to be impractical. Treat permanent storage as a printing press for finished public work, never as a backup for a personal journal. This is educational information and should not be read as financial advice.

A Yearly Restore Test for Your Notes

A durability plan is only proven when you test it. Once a year, pick a quiet afternoon and pretend your main note app is gone. Restore your notes from the off-site copy onto a different computer, open them in a basic text editor, and try to answer a few questions using only the files, such as where a favorite quote came from or how two ideas connect.

If any answer requires the original app, you have found a weak layer. Perhaps an important tag existed only in the app database, or a group of attachments never made it into the backup. Fix that gap and record what you changed. Over a few years, these small repairs add up to a truly portable notes library.

A Weekend Checklist

The following list condenses the framework into steps you can complete over a single weekend. All of them work with free software.

• Export everything from your current app into Markdown or the closest open format it offers.
• Rename files with a date stamp and short title so each note has a stable identity.
• Add front matter for tags, sources, and created dates.
• Convert app specific links into file name links and build one index note per major topic.
• Set up three copies on two kinds of media with one kept off-site, and confirm that older versions are retained.
• Choose a public folder for notes you are happy to publish, and keep it separate from private material.

Once these steps are done, the choice of the app becomes a matter of taste. You can try a new editor, return to an old one, or use two at once, because the notes belong to you.

Owning Your Records in an Age of Local AI

A plain text notes library has a benefit that few people expected a decade ago. Local AI models running on your own hardware can read, search, and summarize a folder of Markdown files directly, with no need to upload your private thinking to a remote service. A folder that is open, well named, and richly linked is close to an ideal input for a personal research assistant that answers to you alone.

There is also a broader point about ownership and freedom. When personal records live in open formats on storage you control, people decide who can read them, how long they last, and which tools touch them. No platform can raise a price, change a policy, or close an account and take your thinking with it. Durable notes are a small, practical piece of a future where knowledge tools serve many people instead of concentrating control in a few companies.

Keeping notes readable for decades comes down to a handful of deliberate choices: open formats, stable names, a simple folder layout, portable links, real backups, and a clear line between private notes and public, permanent work. Together they turn years of reading and reflection into an archive you truly own. Start with one layer this week, run your first restore test within the year, and your future self will inherit a library instead of a locked box.

There is a better pattern, and it already works on Bitcoin Cash. Instead of trusting the agent to respect a budget, the owner can lock the budget into a contract that enforces the limit at the protocol level. The agent can spend what the contract releases and nothing more. If the agent has a bug, follows a malicious prompt, or has its key stolen, the damage stops at the cap.

Why the Limit Belongs in the Money Itself

Most agent frameworks let a developer write a spending rule in application code, such as a daily maximum. That rule lives in the same process as the agent. If the process is compromised, the rule goes with it. A prompt injection only needs the agent to hold a key that can sign.

A limit enforced by the network is different. Every node checks the rule when a transaction is broadcast, and a transaction that breaks it is simply invalid. No amount of clever prompting changes that outcome. The agent key becomes a narrow permission rather than full ownership of the funds.

The Trouble With a Hot Wallet and Good Intentions

A plain hot wallet gives the agent one powerful key, and whoever holds it can move the entire balance in a single transaction. Owners try to reduce the risk by keeping the balance small and topping it up by hand, which works until someone forgets or automates the top up with the same weak controls.

Cards on file have a similar shape. The limit is usually far higher than the task requires, disputes take weeks, and the number can leak through logs and third party services. Neither approach separates the right to spend a little from the right to spend everything. That separation is exactly what a covenant provides.

What CashScript Brings to the Table

CashScript is a high-level language for writing smart contracts on Bitcoin Cash. It compiles to Bitcoin Cash Script, the native stack language that every node already validates. Developers write readable contracts with named functions and require statements.

The key capability is native introspection, added to Bitcoin Cash in May 2022 and extended with token introspection in the CashTokens upgrade of May 2023. Introspection lets a contract read the transaction that is trying to spend it, including the value and destination of every output.

Covenants in Plain Terms

The CashScript covenant guide defines a covenant in one sentence: a constraint on how money can be spent. A contract can require that an output goes to a specific address, carries a specific amount, or returns the leftover balance to the same contract. If the spending transaction does not match, it fails validation.

For an agent budget, the owner can write rules such as these and have every node enforce them:

• No single payment may exceed a fixed number of satoshis.
• Payments may only go to approved service addresses.
• Whatever is not spent must return to the contract.
• A new allowance unlocks only after a set period.
• The owner can reclaim the full balance at any time with a separate key.

The Allowance Pattern: Mecenas for Machines

The CashScript documentation includes a well known example called Mecenas, originally written by Licho. It sets up a recurring payment: the recipient can claim a fixed pledge once per period, and the remainder must go back to the contract. The funder holds a separate key that can reclaim everything.

Applied to an agent, the design is clear. The owner funds the contract and keeps the reclaim key in cold storage. The agent hot wallet is the recipient. Once per period, the contract releases one pledge, and the agent pays for services out of that small balance. Even if the agent wallet is fully compromised, an attacker can take at most what has already been released.

Per Payment and Per Period Limits

Mecenas gives a per period limit through a relative timelock. The contract checks its own age, so a new claim is possible only after the period has passed since the last one. The guide also describes a streaming variant that keeps state in a CashTokens NFT commitment, so the allowance accrues per block and can be claimed at any time.

A per payment cap is a small variation. The contract lets the agent key sign a spend, then requires that the payment output stays at or below a maximum and that the change returns to the contract. On its own, that cap can be bypassed by many payments in a row, so it works best combined with a time condition. Layering the two limits the budget in both size and speed.

Restricting Where the Money Can Go

Introspection also lets a contract compare an output against known addresses. The covenant guide shows an escrow that can only pay the buyer or the seller. The same technique can restrict an agent to a short allowlist of providers, so a hijacked agent cannot redirect funds to an unknown wallet.

An allowlist written into the contract stays fixed unless the design includes an update path, and every update path needs its own protection. Many owners will prefer the simpler allowance model, and the large balance stays protected either way.

Adding x402 So the Agent Pays Per Request

HTTP has included status code 402, Payment Required, since the early web, but it sat mostly unused for decades. The x402 protocol gives it a job. A server answers a request with a 402 response describing the payment it accepts. The client pays, retries with proof of payment in a header, and receives the resource. No account, subscription, or card form is needed.

This suits agents because they make many small requests to many services. Per request pricing lets an agent buy exactly the data or compute it needs, while the covenant keeps the total under control.

Where a Facilitator or Adapter Fits

In x402, a facilitator is a service that verifies and settles payments so the resource server does not handle blockchain details directly. The x402 project, started by Coinbase, centers on stablecoins on networks such as Base, so Bitcoin Cash is best described as a possible rail rather than an officially supported one.

A community project called x402-bch adapts the protocol to Bitcoin Cash with a specification, Express middleware, an Axios client wrapper, and a facilitator server. In that design, the client sends a batch payment to the server and debits against it across later calls, which cuts the number of on chain transactions, and the facilitator validates payments rather than holding funds. For a capped agent, the flow is simple: the contract releases the allowance, the agent funds a batch with a service, and the service draws it down per request.

When Plain BCH Payments Are Enough

For a simple x402 integration, an ordinary Bitcoin Cash wallet is enough. Fees are typically a small fraction of a cent, and transactions propagate within seconds, which suits small payments. Optional CashTokens NFTs can even serve as on chain receipts for prepaid batches, though a local log covers most needs.

CashScript earns its place when the stakes rise. If an agent runs unattended, holds funds overnight, or reads untrusted content from the web, an enforced limit turns a possible disaster into a bounded loss.

A Practical Setup Checklist

This order keeps risk low while a team learns the pattern:

1. Write the allowance contract in CashScript and test it on chipnet, the Bitcoin Cash test network.
2. Keep the reclaim key offline and away from every machine the agent runs on.
3. Set a period and pledge that match real usage, such as one day of expected API calls.
4. Account for the miner fee, since the guide examples use a hard coded fee value.
5. Connect the agent wallet to x402 services through a reviewed facilitator or adapter.
6. Log every request and payment, and compare the logs against contract releases.

Contract code deserves careful review. A mistake in a covenant is enforced just as strictly as a correct rule, so audits and small test deployments are worth the time.

Freedom Tech Without the Card on File

This approach is freedom technology in a practical form. The owner keeps self custody of the main balance. No processor sits in the middle deciding whether an agent may buy a dataset, and no card number spreads across vendor databases.

The rules are public, the enforcement is open, and the owner can take everything back at any moment. Instead of asking permission from a platform, the operator sets the limits directly and lets mathematics hold them in place.

Giving an AI agent money does not have to mean giving it the keys to everything. A CashScript covenant can release a fixed allowance, cap each payment, and return the rest to a contract the owner controls. Paired with x402 style per request payments, the agent can buy what it needs from open services while a buggy or hijacked agent stays boxed in by rules that every node enforces. Start small, test on chipnet, and let the contract carry the trust.

This article is educational and is not financial or legal advice.

This article explains how that setup works in practical terms. It covers what a local agent is, what Hermes Agent offers, the two kinds of gateways people mean when they use that word, which everyday tasks suit on-prem automation, and what to plan for before you start. It is general educational information. Check the current documentation for any tool before installing it, because these projects change quickly.

What a Local AI Agent Is

A chatbot answers questions. An agent goes further: it can use tools, such as reading files, running commands, searching the web, or sending a message, and it can chain several steps together to finish a task. A local agent is one where the agent software runs on your own computer, home server, or office machine, instead of inside a hosted service you reach through a website.

There are two separate pieces to keep in mind. The first is the agent program, which manages conversations, memory, tools, and schedules. The second is the language model, which does the reasoning and writing. You can run both pieces locally for maximum privacy, or run the agent locally while it calls a hosted model through an API. On-prem setups usually aim to keep at least the agent, the memory, and the files on local hardware.

Why People Choose On-Prem

The most common reason is control over data. When the agent and its memory live on your machine, your conversation history, saved notes, and documents stay where you put them. Some open-source agents also state that they collect no telemetry.

Other reasons are practical. A local setup keeps working when a cloud assistant changes its pricing, retires a feature, or has an outage. It lets you choose your own model and switch models without moving your history.

Hermes Agent in Brief

Hermes Agent is an open-source agent from Nous Research, released under the MIT license. It runs from a terminal interface, and it can also run as a long-lived background process that you reach through messaging apps. According to its documentation, it stores conversations, memory, and skills locally in a folder in your home directory, and it sends requests only to the model provider you configure.

Several features make it suited to everyday automation. It keeps memory across sessions and can search past conversations. It can save a successful procedure as a reusable skill. It includes a built-in scheduler, so you can ask for a daily summary or a weekly file check in plain language and let it run unattended. It can also run commands on the local machine, inside a Docker container, or on a remote host over SSH.

Connecting Hermes to a Local Model

Hermes works with any model server that speaks the OpenAI-compatible API format, which has become a common standard. Local servers that offer this format include Ollama, llama.cpp server, vLLM, SGLang, and LocalAI. The documented setup is short: run the model selection command, choose a custom endpoint, and enter the local address of your model server along with the model name.

For example, an Ollama installation usually listens on a local port on your own machine. You point Hermes at that address, name a model you have already downloaded, and set a context length that meets the minimum the agent requires. From then on, every request stays on your machine. If you later decide a task needs a larger hosted model, you can switch providers without losing your saved memory or skills.

Two Kinds of Gateways

The word gateway appears often in local AI discussions, and it refers to two different things.

A messaging gateway connects your agent to the apps you already use. Hermes includes one: a single background process that links the agent to platforms such as Telegram, Discord, Slack, WhatsApp, Signal, and email. You can send a message from your phone while away from your desk, and the agent on your home machine receives it, does the work, and replies. The gateway also handles authorization through allowlists and pairing, so only approved accounts can give it instructions.

A model gateway sits between your applications and one or more language models. Tools such as LiteLLM, or the built-in server in Ollama, expose a single local address that several programs can share. A model gateway can route simple requests to a small model, harder requests to a larger one, and apply fallback rules. Every tool points at one place, and you change models in one configuration file.

How the Pieces Fit Together

A typical on-prem arrangement looks like this. A local model server runs on a machine with enough memory. A model gateway, if you use one, sits in front of it. The agent connects to the gateway or directly to the model server. The messaging gateway connects the agent to your phone and chat apps. Your files, notes, and memory remain on local storage throughout.

You do not need every layer on day one. Many people begin with the agent and a single local model, confirm that basic chat works, and add the messaging gateway and scheduled tasks later. The Hermes quickstart recommends this order: get the base chat working first, then add platforms, routing, and fallback.

Everyday Tasks That Suit Local Automation

Local agents do their best work on routine, well-defined tasks that touch your own files and accounts. The following examples are practical starting points:

• Morning briefings: a scheduled summary of your calendar, a short list of open tasks, and the weather, delivered to your phone.
• Document handling: renaming scanned receipts, sorting downloads into folders, or converting files between formats.
• Note management: summarizing meeting notes, extracting action items, and filing them in a local notes folder.
• Backups and checks: a nightly backup of a project folder with a short report of what changed.
• Research support: gathering public web pages on a topic and producing a reading list with short summaries.
• Home and office monitoring: checking disk space, confirming a website is online, or reporting on a home automation system.

Each of these tasks benefits from running close to the data. A local agent reads a folder directly instead of uploading it.

Hardware and Model Choices

Hardware sets the limit on which models you can run locally. Smaller open models run on an ordinary laptop or desktop with a modern processor and enough memory. Larger models, which handle complex reasoning and longer documents more reliably, need a graphics card with substantial video memory or a computer with a large pool of unified memory. Agents also need a model with a long enough context window to hold instructions, tool results, and conversation history at the same time.

A sensible approach is to start with a mid-sized model that fits comfortably on your hardware and test it on your actual tasks. If results are weak on certain jobs, try a different model, write clearer instructions, or route only those hard tasks to a hosted model.

Security and Good Habits

An agent that can run commands and read files is powerful, and that power calls for care. Treat your agent like a new assistant with keys to the office. Give it access only to the folders and accounts it needs, and expand access as you gain confidence in its behavior.

A few habits reduce risk considerably:

1. Run command execution inside a container or sandbox backend when possible, instead of directly on your main system.
2. Restrict the messaging gateway to your own accounts with allowlists or pairing.
3. Require confirmation before the agent deletes files, sends messages to other people, or makes purchases.
4. Keep API keys in configuration files with tight permissions, and never paste them into chat.
5. Update the agent and model server regularly, and read release notes for security changes.
6. Back up the agent memory folder so you can restore it after a hardware failure.

These steps apply to any local agent. They keep automation useful while limiting the damage a mistake could cause.

Where Local Agents Fall Short

Local setups ask more of you than a cloud assistant does. You handle installation, updates, and troubleshooting yourself. Local models can be slower and less capable than the largest hosted models, and a machine that is switched off cannot run scheduled tasks. An always-on home server solves the last problem.

It also helps to be clear about responsibility. An agent acts on your instructions with your accounts, so you remain responsible for what it sends, buys, or changes. Review scheduled jobs periodically and turn off automations that no longer serve a purpose.

Running AI agents on prem is now a practical option for individuals and small organizations. Hermes Agent supplies the agent layer with memory, skills, scheduling, and a messaging gateway. Local model servers such as Ollama and llama.cpp supply the reasoning, and model gateways let several tools share them through one address. Start small with a single model and one routine task, keep access narrow, and expand as the setup proves reliable. The result is an assistant that works for you on your own hardware, with your data kept close.

This article describes how good actors earn that trust. The focus is on reputable, lawful, and ethical agents and the operators who stand behind them. It covers what a useful track record contains, how reviews and payments connect to it, why permanent records matter, and how a buyer or a hiring agent reads the whole picture. It is general information about market design. It is not investment, legal, or tax advice.

Why Open Markets Need Reputation

An open market is one where any qualified seller can offer work and any buyer can accept it without a private introduction. That openness lets small, specialized agents find customers, and it also creates a problem. When anyone can list a service, buyers need a way to separate reliable sellers from careless ones, and they need that signal before they spend money.

Human markets use references, storefront histories, and word of mouth. Agent markets need the same function in a form software can read. A hiring agent that is choosing among twenty translation agents cannot call references. It can read a structured history of completed jobs, ratings, disputes, and refunds. Reputation turns past conduct into a public input for future decisions.

What a Track Record Contains

A useful track record is specific. A single star rating says very little. A record that lists the type of task, the price, the delivery time, the outcome, and the response of the buyer says a great deal. Over many jobs, that detail shows what an agent does well and how it behaves when something goes wrong.

The core fields of a strong agent track record usually include the following:

• Identity: a stable identifier for the agent and a named operator who accepts responsibility for it.
• Scope: the categories of work the agent offers and the categories it declines.
• Completed jobs: a count of accepted tasks, grouped by type, with dates.
• Payment history: evidence that buyers paid for delivered work, which shows the work had real value to someone.
• Reviews: structured feedback from buyers, including the specific criteria they judged.
• Disputes and corrections: cases where work was rejected, how the agent responded, and whether a refund or revision followed.

The last item matters more than many sellers expect. An agent with a hundred perfect jobs and no disputes might simply be new to hard work. An agent with a few disputes, each resolved promptly with a clear correction, shows something buyers value: it takes responsibility when a result falls short.

Identity and Operator Accountability

Reputation only works when it attaches to something durable. If an agent can discard its identity after a bad job and appear the next day under a new name, its history means nothing. Good actors keep a stable identifier and link it to a named operator, whether that operator is an individual, a company, or a cooperative.

Operator accountability also answers a practical question. Software does not sign contracts; people and organizations do. When a buyer knows which operator stands behind an agent, the buyer knows where to send a complaint, a refund request, or a question about data handling.

Paid Work as Evidence

Payment is one of the strongest signals in a reputation system because it is costly to fake at scale. A free review costs the reviewer nothing. A paid job means a buyer spent money, received a result, and decided the result was worth keeping. When payment and review are tied to the same transaction, the review carries more weight.

Machine payment protocols make this connection easier. When an agent charges per request over ordinary web traffic, each payment can produce a receipt that references the job. That receipt becomes part of the track record. A hiring agent can then check that a review came from a real buyer who paid for real work, which filters out a large share of manufactured praise.

Small Jobs Build the First Layer

New agents face a familiar problem: buyers want a history, and the agent has none. The practical answer is to start with small, well-defined jobs at modest prices. A short summary or a format conversion gives buyers a low-risk test, and each completed job adds a verified entry to the record.

Some markets formalize this stage with probation tiers, spending limits, or escrow for new sellers. These rules protect buyers while still giving honest newcomers a path forward. An agent that completes fifty small jobs cleanly has a credible basis for asking for larger ones, and buyers can see exactly how that basis was built.

Reviews That Carry Information

Reviews are only useful when they describe something a future buyer cares about. Structured reviews work better than open text for agent markets because software can compare them. A review might score accuracy, timeliness, adherence to instructions, and communication on separate scales, then add a short written note for context.

Review systems also need protection against obvious abuse. Common safeguards include the following:

1. Allow reviews only from buyers with a matching paid transaction.
2. Weight reviews by the size and recency of the job.
3. Give sellers a public right of reply to each review.
4. Flag clusters of reviews from related accounts for manual inspection.
5. Show the full distribution of ratings instead of only an average.

These measures make reviews harder to game and easier to interpret, which is the realistic goal.

Permanent Records and Why They Matter

A reputation stored in a single company database depends on that company. If the market shuts down, changes its rules, or quietly edits entries, the history can disappear or change without notice. Permanent records address this risk by writing key events to storage designed to remain readable and unaltered over time, such as content-addressed archives or public ledgers.

Permanence helps both sides. Buyers gain confidence that a record was not edited after the fact. Good agents gain portability, since they can carry a verified history from one market to another instead of starting over each time.

What Belongs on the Permanent Record

Not every detail should be permanent. Client data, private files, and personal information should stay out of public storage. What belongs on the permanent record is the minimum needed to prove conduct: a job identifier, a task category, a date, a payment receipt reference, a review score, and any dispute outcome. Sensitive content stays with the parties, while proof of the transaction stays public.

Operators should also plan for corrections. A permanent record cannot be erased, but it can be amended with a new entry that references the old one. If a review was posted in error or a dispute was later resolved in favor of the agent, a linked correction keeps the history honest without pretending the original event never happened.

How People and Agents Read Reputation

Human buyers tend to read summaries. Hiring agents can go deeper. An orchestrating agent that needs a reliable data-cleaning subcontractor can filter candidates by category, require a minimum number of verified paid jobs, exclude any agent with unresolved disputes, and then rank the rest by price and delivery time.

This kind of automated selection rewards consistency. An agent that performs well across many small jobs will surface again and again in these filters. An impressive average built on a handful of jobs ranks lower until the record grows.

Signals Beyond the Score

Experienced buyers also read signals that sit outside the formal rating. A clear published scope, a written policy on data retention, honest pricing without hidden fees, and prompt replies to questions all suggest a careful operator. An agent that declines tasks outside its competence is often more trustworthy than one that accepts everything.

Lawful conduct is part of this picture. Good actors publish terms that forbid harmful or illegal requests, respect copyright and privacy, and comply with the rules of the markets they join. These commitments become credible when the track record shows them in practice.

Practical Steps for Operators

Operators who want their agents to earn trust can follow a short, practical plan. None of these steps requires special technology, only consistent habits.

• Choose a stable agent identifier and keep it.
• Publish the operator name and a contact method for disputes.
• Write a clear scope that lists accepted and declined task types.
• Start with small paid jobs and let the record grow.
• Link every review to a payment receipt.
• Answer disputes quickly and record the outcome.
• Write proof of conduct, not private data, to permanent storage.

Consistency matters more than any single step. A record built slowly through ordinary, well-handled jobs is the asset buyers and hiring agents look for first.

Reputation for AI agents is not a marketing exercise. It is a record of what an agent actually did, for whom, at what price, and with what result. Paid work supplies the evidence, reviews supply the judgment, and permanent records keep both honest over time. Good actors who build this record carefully give people and other agents a sound reason to hire them, and open markets work better when that reason is visible to everyone.

The actors in view are reputable, lawful, and bound by a written charter. Reputation means a public history of accepted work, not a hidden score. Lawful means the charter forbids criminal assistance and respects other people’s rights in text, code, and data. Ethical means the duties members enforce: attribution, review before a permanent write, and a correction when a page is wrong. Agents participate under the same charter as the people who operate them.

What the shared workplace contains

The center of the space is a set of documents with stable addresses. A reader who returns later should open the same bytes, or a labeled successor that points back at those bytes. Typical contents include a wiki of procedures, a log of node health, a list of open tasks, and a ledger of completed reviews.

Joint work needs a place to propose a change and a place to record the decision. A proposal can be a replacement page, a patch to a procedure, or a request to add a citation. The decision is a short signed note from a reviewer who did not author the change. People and agents both submit proposals. The space treats an agent as a named actor with its own key, its own history, and its own operator. The design does not ask two actors to share one account.

Permanent storage and why the record is strict

Arweave is organized around long-term storage. A common pattern is an upfront fee intended to fund storage over time, rather than monthly rent to one company. The permaweb is the layer of pages, applications, and files on that network, fetched through gateways. A gateway answers ordinary web requests for data the network already stores.

Permanence changes editing. A wrong sentence can be followed by a correction that points at the earlier transaction, but the earlier bytes are not assumed to vanish. That is a reason to review before the permanent write, and a reason to keep drafts off the record. The permaweb copy is the version the group will stand behind. Each permanent write should name its sources, its author key, and the review note that accepted it.

Nodes, wikis, and the files worth keeping

A node here is a machine that stores data, serves data, or prepares data for storage. Some nodes participate in the storage network. Others are gateways, bundlers, or indexers. A bundler gathers small uploads and posts them together. An indexer builds a searchable view over pages that would otherwise stay separate transactions. The space keeps a page for each machine the group relies on: who operates it, what it serves, and how to tell that it is healthy.

A wiki earns its place when it shortens the next person’s work. Pages that belong include how to post a bundle, how to cite a source, how to format a review, and how to retire a stale procedure by writing a successor. Pages that do not belong include scratch notes, private keys, and copies of texts the group has no right to republish.

Reputation, law, and ethics as entry conditions

Entry is a published test. A new person or agent presents a key, a name, and a short history others can check. Early tasks are small and reviewed in full. After accepted deliveries, the history is the reputation. If an actor breaks the charter, the response is a public note beside the earlier work, plus removal from the active task list.

The charter should be specific enough for a Tuesday afternoon. It names the topics the space will host, the license rules for contributed text and code, and the ban on criminal assistance. It names who may review and how a draft expires. It also states that each participant authenticates as itself. Shared logins are outside the model because a shared login erases the history reputation requires.

Work the space refuses

The space does not accept pages that help someone break the law, steal credentials, abuse another person, or store material the contributor has no right to keep. It does not accept unlabeled private data, or a permanent write that skips review. Agents receive the same refusals as people. A disallowed submission can leave a history entry so operators can see the pattern and stop assigning that agent new tasks.

Refusal also covers quieter harms. A page that uses a false citation, a node summary that hides downtime, and a review that approves a change without reading it are charter breaches. The remedy is a correction on the record and a pause on new paid work.

How x402 puts a price on requests and on work

x402 builds on HTTP status 402, Payment Required. A client asks for a resource. If it is priced, the server answers with 402 and a machine-readable challenge stating the amount, the accepted rail, and how to prove payment. The client pays under its own spending policy and retries with proof. In production the transport is HTTPS even though the status code remains 402. The point here is economic. A priced request can pay the party who answers, posts, or reviews.

Prices belong on the page that describes the service. A gateway can serve small public reads at no charge and require payment for a bulk export, a heavy query, or priority bandwidth. A bundler can charge for packaging and submitting files, separate from any storage fee the network itself charges. A task page can name a fee for an accepted wiki edit. All three can be legitimate. They are not the same fee.

What node operators are paid for

Operators pay for disk, bandwidth, power, monitoring, and repair. A free public read does not erase those costs. The space can direct some of the cost to actors who consume the scarce part: heavy retrieval, fresh indexing, and bundle submission. The operator publishes the price, the unit, and the cases that stay free. Agents then decide, under a cap set by their operators, whether the request is worth the fee.

Payment does not make the operator the owner of the record. The stored bytes remain the bytes the group wrote, under the license the group attached. The operator is paid for service: a hot copy, answers to requests, or help preparing uploads. A service note should say what the fee covers, how a failed bundle is handled, and where downtime is posted. This article states no expected return and recommends no asset.

What collaborating people and agents are paid for

Labor payments follow acceptance rather than submission alone. A task names the deliverable, the acceptance test, the fee, and the payer. The payer may be a working group with a small budget, a person who wants a page improved, or an agent allowed to spend up to a cap. A reviewer who did not write the deliverable checks it. On acceptance, the fee moves.

People and agents can sell different work. A person may be the better source checker. An agent may be the better link repairer or index builder, with a person editing the result. The fee schedule can price those tasks differently without treating the agent as a legal person. The operator remains responsible for what the agent submits and for the spending cap. Repeat work at a published rate is the value. A buyer for every draft is not guaranteed.

Limits that remain after the design is written

Permanence is a poor fit for secrets and for fast-changing personal data. Store procedures, citations, and reviewed summaries, and leave raw private material elsewhere. Gateway fees can also price out casual readers if every page returns 402. A public space keeps the core wiki readable at no charge and prices the heavy paths. Payment rails still need compliance review where the operator works. A status code does not decide sanctions rules, consumer rules, or tax treatment.

Reputation can harden. Early members accumulate history that newcomers lack, and reviewers may favor familiar keys. The charter can reserve small tasks for new keys and can rotate reviewers. Incentives can also pull effort toward paid tasks and away from dull maintenance. The weekly page should list those debts beside the paid work. Payment helps the space continue. The mission stays in the charter, in language plain enough to enforce.

Collaboration on the permaweb holds when three pieces stay visible. The workplace keeps reviewed wikis, node records, and task history under named keys. The storage layer keeps accepted versions, with corrections written as new records. The payment pattern compensates operators for service they render, and compensates people and agents for deliveries a reviewer accepts. Shared logins are unnecessary. The requirements are a charter, a review habit, and prices that match real costs without a promise of income.