Don't Trust, Verify. No permission.

I run my own Bitcoin infrastructure and build software for people who do the same.

Not a company. Not a VC-backed startup. A sovereign operator who runs Bitcoin Knots with BIP-110 activated, mines with DATUM through Ocean on a personal setup called The Oracle 🔮, and ships practical tools so node operators can inspect mempools, block templates, and chain spam without trusting third parties.

If you run your own node, you should be able to see what your node sees. That's the work.

Terminal dashboard (TUI) for sovereign Bitcoin Knots operators.

Built in Python. Talks to your node via bitcoin-cli. No external APIs. No trust required.

What it does:

• Mempool analysis and real block template inspection (full GBT)
• BIP-110 spam detection — witness data scoring, miner tagging, navigable block tables
• DATUM mining panel — gateway status, workers, hashrate, shares
• Ocean account stats — pool hashrate, TIDES, earnings, blocks found
• Live metrics — mempool and peer charts

Philosophy baked in: Don't Trust, Verify.

git clone https://github.com/MarcanoFilms/oraculovision.git
cd oraculovision
python -m venv .venv && source .venv/bin/activate
pip install -e .
oraculovision

More sovereignty-focused tools are in active development — including a self-hosted mempool explorer with BIP-110-aware spam metrics (The Oracle Mempool). Watch this profile for releases.

Bitcoin is peer-to-peer electronic cash. Not a general-purpose data storage network. Not a token issuance platform. Not a JPEG registry. Money.

I run Bitcoin Knots because it gives operators real policy control. Knots ships practical mempool and relay policies that Core has been slow to adopt — including the tools needed to reject arbitrary data before it pollutes your UTXO set and bloats blocks your node must validate forever.

Node software is not neutral infrastructure. It encodes values. I choose the implementation that protects my sovereignty as an operator.

BIP-110 is a pragmatic measure to protect node sovereignty and keep the network verifiable by regular users.

When miners include inscriptions, Ordinals, Runes, and other arbitrary witness data on L1, they externalize storage costs onto every full node on Earth — forever. That is not a fee market. That is a subsidy from node operators to data hoarders.

BIP-110 draws a line: transactions with excessive witness data get rejected at the mempool policy layer. Nodes stay lean. Verification stays accessible. Decentralization survives.

I support BIP-110 not because I want to police what people do off-chain, but because L1 must remain verifiable by people running hardware they can actually afford.

• Arbitrary data and spam embedded in Bitcoin blocks
• Treating L1 as free permanent storage for non-monetary payloads
• "Just increase block size" as a substitute for actual scaling (Lightning, custody minimization, efficient protocols)
• Any workflow that asks you to trust instead of verify

Verify everything. No permission.

Run your node. Read your mempool. Inspect your block templates. Reject what you reject. Mine if you can. Build tools if you code. Nobody needs to approve your participation in this network.

Technical questions about oraculovision or sovereign node operation → open an issue on the repo or reach out on X.

Español: README.es.md

_{🦉 The Oracle sees what your node sees. ⚡ Verify everything. 🔮 No permission.}