billete de banco desintegrandose

Programmable Money: The Quiet Future Nobody Voted For

By floc1960 | joanramo | 13 Jan 2026


We don’t wake up one day and lose freedom.

 

We trade it away in small upgrades:

 

faster payments,

less friction,

“more convenience,”

“less cash,”

“more security.”

And then, one day, we realize something uncomfortable:

 

When money becomes programmable, money becomes a set of permissions.

 

This is not a sci‑fi idea. It’s a design choice being discussed around the world under a simple name: CBDC — Central Bank Digital Currency.

 

A CBDC is basically digital cash issued by a central bank, not a private bank, not a fintech app, and not a crypto protocol. Even the U.S. Federal Reserve describes it as “a digital form of central bank money… widely available to the general public.” They also say they haven’t decided to issue one and would need authorizing law to proceed (Federal Reserve FAQ).

 

So why talk about it now?

 

Because the direction is clear: many countries are exploring, piloting, or launching versions of state-backed digital money. According to the Atlantic Council’s tracker (last updated July 2025), 137 countries and currency unions are exploring a CBDC, and 49 are in pilot stage (Atlantic Council CBDC Tracker).

 

But the real question isn’t “Will CBDCs exist?”

 

The real question is:

 

What happens when money can be programmed?

Cash is “dumb.” You can’t tell a €20 bill where it’s allowed to go. You can’t add rules to a coin.

 

Digital money can be different.

 

Some designs make it possible to:

set limits on how much a wallet can hold,

restrict where funds can be spent,

define time conditions (like vouchers that expire),

enforce policy through payments instead of debate.

Even mainstream discussions acknowledge that programmability can introduce rules and constraints—like an expiry date or limits on how funds can be used (Thales on CBDCs & programmability).

 

And this isn’t just theory. China’s digital yuan pilot has been discussed as an example where digital money/vouchers can include spending incentives and time constraints. The broader point is simple:

 

If money can be programmed, someone has to write the program.

 

“But that would never be used against ordinary people.”

Maybe. Maybe not.

 

The problem is not what a system promises on day one.

 

The problem is what the system allows on day 700, when:

 

there’s a crisis,

inflation is high,

energy is scarce,

or social tension is boiling.

Then the temptation appears:

 

“We’ll just add one more rule.”

 

And one more.

 

And one more.

 

Until money stops feeling like money and starts feeling like a leash made of code.

 

Privacy isn’t a luxury. It’s the human default.

Cash has something digital systems struggle to replicate:

 

privacy by nature.

 

Even if a CBDC is “intermediated” (run through banks or payment providers), it still raises the question:

Who sees what? Who stores it? Who can be compelled to hand it over?

 

The Federal Reserve explicitly acknowledges that any CBDC design would need to balance privacy with compliance and law enforcement needs (Federal Reserve FAQ). That’s honest. It also means privacy is not guaranteed by default.

 

My sober take

I’m not saying CBDCs are evil. I’m saying they are powerful.

 

And the more powerful a tool is, the more carefully it should be limited.

 

The political debate often sounds like:

 

“CBDC = efficiency”

“CBDC = innovation”

“CBDC = inclusion”

But the human question is simpler:

 

Do we want a future where our money is ours… or where our money is granted?

 

A question for you

If programmable money becomes normal, what do you fear more?

 

Censorship by finance (wallets blocked, categories restricted)

Invisible nudges (expiry dates, incentives, “approved” spending)

Total transparency (every transaction becoming a permanent footprint)

Or do you think the risks are exaggerated?

 

Write it in the comments. I read them all.

 

Sources

Federal Reserve CBDC FAQs: federalreserve.gov

Global CBDC status & pilots: Atlantic Council CBDC Tracker

Discussion of CBDC programmability constraints (expiry, restricted use): Thales article

 

A few words from the author

If you made it this far, thank you from the bottom of my heart for your time. Writing is, for me, a way to give a voice to what many of us feel but sometimes struggle to put into words. If this article gave you something valuable, please consider leaving a small tip as a recognition of the work behind it; every cent is an encouragement for me to keep writing.

Also, feel free to check out the other articles on my blog. You will find reflections on life, society, and the human condition that I hope will resonate with you as well. Thank you for being part of this journey!

How do you rate this article?

10


floc1960
floc1960

Escritor y articulista de opinión. Bienvenidos a mi búnker de pensamiento y letras. Podéis encontrar todas mis obras y artículos en mi web oficial: https://joanramonwriter.org Sine Labore Non Emerita. 🏛️🛡️✨


joanramo
joanramo

RouteLLM Routing to GPT-4.1 Mini Claro, Joan. Aquí tienes un resumen para la descripción de tu blog en Publish0x, que abarca temas de actualidad, con o sin relación con Bitcoin: En este blog encontrarás análisis y reflexiones sobre temas de actualidad que impactan nuestra sociedad y economía, desde las últimas tendencias en criptomonedas como Bitcoin hasta cuestiones políticas, sociales y tecnológicas. Un espacio para entender mejor el mundo que nos rodea, con un enfoque crítico y abierto a diversas pers

Publish0x

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.