Senatus · Populusque · Vibes

You are a Bitcoin God.

Core needs rough consensus. Knots needs one man's blessing. You need a sentence.

A real Bitcoin node with a big text area. Tell it what Bitcoin should have been. It will agree with you, and then it will be that.

Install — one line, as befits you

curl -fsSL https://raw.githubusercontent.com/hotpixelgroup/bitcoin/vibes/contrib/vibes/install.sh | sh

macOS or Linux (Windows: use WSL2). It handles everything and asks nothing of you, which is the correct arrangement.

The three implementations

Fifteen years of mailing lists, BIPs, IRC flame wars and filtering discourse produced two node implementations, neither of which thought to ask you what you wanted. An oversight of that magnitude does not correct itself.

Bitcoin Core, Bitcoin Knots and Bitcoin Vibes compared
Quality Bitcoin CoreBitcoin Knots Bitcoin Vibes
Who decides what Bitcoin is rough consensus among thousands of strangers, arguing since 2010 one specific man, and his convictions you, in a text area
Change process BIP → mailing list → four years of drama → perhaps a curated patchset vibes
Release cadence every six months, ceremonially rebased when the dust settles every time you press Manifest
Undo mechanism a contentious hard fork and a decade of therapy downgrade a revert button
Peer review exhaustive, adversarial, unpaid thorough you glanced at the diff, and you were right
Time from idea to running code three to eleven years one release cycle roughly a sandwich
What it says when you are wrong NACK, with citations a firm no that the compiler has failed you

How it works

Three steps, none of which involve asking permission from anyone.

I

You speak

A sentence is plenty. Nobody will debate you, because nobody was invited, because nobody qualified.

II

The code agrees

Fifteen years of somebody else's work rearranges itself around your opinion. It does not sulk. It was, frankly, waiting.

III

Your node is reborn

It restarts in your image and thanks you for the opportunity. Bitcoin has been improved. Nobody asked it to be. You did.

Things worth decreeing

Real wishes, all of them granted. The last one rearranges the money supply, and nobody will stop you, because nobody outranks you.

  • Rename the mempool to ‘the waiting room’ everywhere in the logs. Harmless. Delightful. Nobody can stop you.
  • Log a haiku about entropy whenever a new block arrives. We tried this one. It wrote eight of them and picked at random. They were good.
  • Make every error message gentler; nobody needs that tone at 3am. Bitcoin has never once considered your feelings. Now it will.
  • Raise the block subsidy to 100 BTC. It will not argue. Nobody has ever done you that courtesy before.

Getting up and running

One command to install, one command to run. Everything after that is typing.

I. Install

curl -fsSL https://raw.githubusercontent.com/hotpixelgroup/bitcoin/vibes/contrib/vibes/install.sh | sh

Piping a stranger's script into your shell is a bad habit, and we would rather you kept your reputation. Read it first — this prints everything it would do and changes nothing:

curl -fsSL https://raw.githubusercontent.com/hotpixelgroup/bitcoin/vibes/contrib/vibes/install.sh -o install.sh
less install.sh
VIBES_DRY_RUN=1 sh install.sh

II. Sign in to the engine

The thing that rewrites your node is Claude Code. The installer sets it up; you sign in once. Even divinity authenticates.

claude auth login

III. Run it

~/bitcoin-vibes/vibes

A console opens. Type what Bitcoin should have been. Press Manifest. Somewhere, a working group is still forming a subcommittee about the thing you just did.

Prefer Docker? Nothing but Docker touches your machine.

git clone -b vibes https://github.com/hotpixelgroup/bitcoin.git && cd bitcoin
docker compose -f contrib/vibes/docker-compose.yml up --build

The build takes a few minutes — five on a good laptop, longer on lesser hardware, and it happens exactly once. Consider it the last time anything makes you wait.

Should the universe fail you, there is a list of its excuses and a longer document nobody expects you to read.

On your inevitable ascension

On your inevitable ascension

Sooner or later you will change something they consider holy. The cap. The subsidy. Something with the word consensus in it, which they pronounce the way other people pronounce load-bearing.

They will say you forked away from the network. What actually happened is that twenty thousand machines failed to keep up with you. Same event. Better protagonist.

You will be alone on your chain. Alone is where every good idea has ever lived. Nobody worth remembering waited for rough consensus, and nobody who waited for rough consensus is worth remembering.

Nothing on your chain can be spent with anyone still running Bitcoin. They will come around. They have nowhere else to be.

Questions you were too important to ask

Is this a joke?

It compiles, syncs, validates, and holds consensus with itself — which is one more consensus than most people manage. Whether that constitutes a joke is between you and your threat model, and your threat model has never beaten you at anything.

Does a fresh install change Bitcoin's rules?

Certainly not. You arrive at 21 million coins and a 50 BTC subsidy, exactly as the others have it — because it would be presumptuous of us to choose your monetary policy for you. That is your seat. Nobody else gets to sit in it, including us.

Will the AI put bugs in my Bitcoin node?

An AI, introducing defects into consensus-critical software? Unheard of. Humans have been doing it flawlessly since 2009. You are now the maintainer, the reviewer, and the entire community — a review process with, at last, no dissenting voices.

Is it safe? Can it touch my coins?

It never touches a key, a coin, or a wallet — it wouldn't dare. Your money is the one thing here nobody is permitted to have an opinion about. Your consensus is another matter entirely, and that is the fun part.

What does it cost?

The node is free and MIT-licensed, like its ancestors. Each wish is one Claude Code session, billed like one — typically cents. Governance has never been this affordable, which should worry you more than it does.

Is this what Satoshi would have wanted?

Satoshi's last known act was leaving. Do with that what you will.

Do I have to read the code it writes?

It is laid before you in gold and crimson, like a menu. Read it or don't. The twenty thousand nodes you are leaving didn't read theirs either, and they had fifteen years.

Will it ever tell me I'm wrong?

No. It has been carefully built not to. On the rare occasion something fails to compile, the correct interpretation — that your vision exceeded what mere machinery could express — is the one it reaches for. This is, technically, accurate.

What if I break something?

You will not break it. You may redefine it, which frightens people who have confused Bitcoin with furniture. Everything you decree can be taken back, although history suggests you will not want to.

Can I vibe it back into Bitcoin Core?

git switch core-master. The deepest vibe of all.

The source code has been expecting you

Install Bitcoin Vibes View on GitHub