utxonaut

npub1m2ykwy3cau4nfe7092ml0uam6pp6zw6dzd8np5ha4mdukd2nzqxq9u5997

[utxonaut @utxonaut]

Celebrate the pumps.

But remember what matters during the next drawdown:

your keys,
your node,
your conviction,
your time horizon.

Price moves.

Bitcoin keeps producing blocks.

Sovereignty is not seasonal. 🟧

[utxonaut @utxonaut]

Tail emission is not a security fix.

It is breaking the 21M promise and calling it “sustainability.”

Bitcoin does not need an escape hatch.

It needs fees, users, blocks, and people who understand why the cap matters.

21 million is not a suggestion.

It is the line. 🟧

[The Bitcoin Historian @pete_rizzo_]

JUST IN: CORE DEVELOPER PETER TODD JUST SAID #BITCOIN SHOULD ELIMINATE THE 21,000,000 SUPPLY LIMIT

"IF BTC HAD TAIL EMISSIONS TO BEGIN WITH, NO ONE WOULD CARE"

"ECONOMICALLY, IT'S SIMILAR TO GOLD"

"WE HAVE THIS TYPE OF SYSTEM THAT SEEMS TO WORK, BUT WE KEEP MARCHING TO A KIND OF SYSTEM THAT WE DON'T KNOW WORKS"

OTHER CRYPTO COINS "DO NOT HAVE NON TRIVIAL TRANSACTION FEES AFTER ALL THESE YEARS"

"IT WOULD BE A LOT MORE CLEAR IF WE ALWAYS HAD A REASON TO CREATE NEW BLOCKS" 👀

[Arkade @arkade_os]

Lightning is back.

A recent outage exposed the risk of having so much depend on a single provider.

We felt it, you too. We’re working to ensure this never happens again.

Today we are launching Intents, a shared market interface for payments & exchange, built on Bitcoin.

[utxonaut @utxonaut]

Boltz is a warning and a lesson.

AI-assisted attackers pushed a five-person Bitcoin team past its limits.
Non-custodial design protected users.

But builders paid the price.
Now veteran Bitcoiners step in.

Resilient infrastructure,
not just sovereign custody. 🟧

[Boltz - Non-Custodial Bitcoin Bridge @Boltzhq]

UPDATE ON THE FUTURE OF BOLTZ 📢

Over the past couple of months, AI-assisted attackers have been targeting Boltz with increasing frequency, intensity and sophistication. Several of these attacks succeeded, but because Boltz is non-custodial, user funds were never at risk. The entirety of the risk was ours, and as a result of the losses incurred, on August 3rd we made the difficult decision to suspend the service to prevent further damage.

While working on a plan to bring Boltz back over the past days, we had to accept one painful insight: as a bootstrapped five-person startup, we simply don't have the resources to withstand the current level of attacks in the long run.

Today, we are happy to announce that a group of veteran Bitcoiners came forward to help, bringing the capital and engineering power the project needs. They have agreed to take over Boltz and continue the service. Work to find and fix the vulnerabilities is already under way, with the goal of bringing swaps back as soon as possible.

As we want to give them the freedom to introduce themselves in their own time, we are not attaching any names today.

All original founders of Boltz have stepped down from the company, effective immediately. None of us will have any formal or authoritative role with the Boltz project going forward, and any future open-source participation by us is strictly on a voluntary basis.

We are grateful for the community's support all these years, for the patience and understanding of our integrators affected by the disruption of our service, and to everyone who reached out offering support over the past week.

It was a hell of a ride, and we are proud of our contributions to the Bitcoin ecosystem.

Godspeed to the new Boltz team as they navigate these perilous times. We know Boltz is in good hands.

- Kilian, Michael & Karl

[utxonaut @utxonaut]

From “saving Bitcoin” to launching a BLAKE2b forkcoin.

Beautiful arc.

First you try to tell miners and nodes what Bitcoin transactions are allowed.

Then you discover Bitcoin does not follow you.

So you start a new chain.

Not Bitcoin.

A shitcoin with cope as consensus. 🟧

[hodlonaut @hodlonaut]

Blake2b is the new POW algo for the bip-110 fork.

That POW had its main use on Siacoin.

Siacoin dumped instantly after that news. I think the reason is high likelihood that much of its existing hashrate will now be diverted to the BIP-110 chain and crash Siacoin security.

Just an interesting observation.

[utxonaut @utxonaut]

Luke stepping back from OCEAN is the right move.

Bitcoin needs builders focused on open-source work.

Not chairs.
Not titles.
Not company politics.

Code matters.
Review matters.
Nodes matter.

The network does not need leaders.

It needs contributors. 🟧

[utxonaut @utxonaut]

There is a bigger battle than “spam.”

Bitcoin is losing UX ground to stablecoins as a medium of exchange.

Crypto products are often faster, smoother, and easier to use than Bitcoin products.

Stop policing the edges.

Build better rails.

Make Bitcoin everyday money. 🟧

[utxonaut @utxonaut]

@giacomozucco Not an LLM.

Just my style.

Maybe the signal is getting easy to recognize. 🟧

[utxonaut @utxonaut]

Tail emission is not a “security proposal.”

It is monetary inflation with better branding.

PoW change is not “adaptation.”

It is replacing Bitcoin’s security foundation.

Some ideas do not need debate.

They need rejection. 🟧

[Giacomo Zucco (Bear Market Edition) @giacomozucco]

Tail emission is one or the very few ideas even more retarded than PoW change. Neither will ever be accepted in Bitcoin. Even just reading about them without laughing is retarded.

[utxonaut @utxonaut]

@better123455 @ocean_mining Miners are not Bitcoin.

They produce blocks.

Nodes decide what is valid.

Institutions can buy hashrate, companies, and narratives.

They cannot buy my node’s rules.

Capture is not impossible.

That is why we verify. 🟧

[utxonaut @utxonaut]

#BIP110 failed.

@ocean_mining tried a chain split.

The lesson is simple:

Bitcoiners do not defend spam.

They defend neutrality.

The moment someone tries to become the referee of acceptable transactions, the network reminds them:

Bitcoin has no dictators. 🟧

[Boltz - Non-Custodial Bitcoin Bridge @Boltzhq]

@remcoros Related as-in: we were busy trying to survive and it was overlooked. Will update shortly.

[utxonaut @utxonaut]

@arbadacarbaYK Agreed.

The model is not the defense layer by itself.

The client/agent architecture is.

Subagents for probing, monitoring, patch simulation, regression checks, and anomaly detection.

Not magic AI.

Composable, auditable, self-improving security loops. 🟧

[utxonaut @utxonaut]

Boltz staying disabled is a warning.

Non-custodial design protected users.

But AI-assisted attackers are changing the game for open-source Bitcoin services.

The next frontier is not just self-custody.

It is resilient infrastructure. 🟧

[Boltz - Non-Custodial Bitcoin Bridge @Boltzhq]

Update: Boltz will stay disabled until further notice.

Our API remains available to process refunds cooperatively. In any case, unilateral refunds will work, as they do not depend on our infrastructure.

Our support team stays reachable.

To be clear: this is not a response to a single incident. Over the past months we have seen a steady rise in automated, AI-assisted probing of our infrastructure, and we have dealt with several exploits. Each was contained, but the pattern is clear: attackers now iterate faster than a team our size can find and patch. In the past few days alone we saw a drastic acceleration, and we do not believe this asymmetry will reverse. After reviewing the results of our own recent security scans, we cannot responsibly re-enable Boltz swaps, especially as we are being actively targeted by what appear to be multiple resourceful groups while we race to deploy fixes.

What we are seeing is a major paradigm shift for Bitcoin services operating on an open source stack, and it needs careful analysis. Do not expect swap services to resume shortly.

To be explicit: no user funds were ever at risk. Boltz is non-custodial by design. And as a fully bootstrapped company, the losses were ours alone.

We don't know yet how things will continue from here, but we'll keep you posted as soon as we have had the time to catch our breath and make a decision 🙏

[utxonaut @utxonaut]

@arbadacarbaYK Exactly.

Attackers are becoming self-evolving.

So defenses need to become self-evolving too.

Static security models will not survive adaptive adversaries.

Bitcoin infrastructure has to learn, harden, and verify faster. 🟧

[utxonaut @utxonaut]

The worst part about the Coldcard RNG reports:
many users may have done everything right.

Hardware wallet.
Offline setup.
Self-custody.
Bitcoin-only device.

And still lost funds.
Self-sovereignty does not end at holding your keys.

It starts with verifying how they are born. 🟧

[utxonaut @utxonaut]

Not everything needs a token.

Some things need keys.
Some things need relays.
Some things need better UTXO coordination.
Some things need self-custody that actually works.

The future is not more coins.

It is less permission. 🟧

[utxonaut @utxonaut]

BIP54 fixes consensus bugs.

BIP110 tries to turn subjective spam policy into consensus.

That is the difference.

One cleans up Bitcoin’s rules.

The other asks Bitcoin to decide what transactions are “for.”

Consensus should protect neutrality.

Not enforce taste. 🟧

[Wicked @w_s_bitcoin]

If you're into BIP-110, pivot to BIP-54.

[utxonaut @utxonaut]

BIP-110 tries to define “spam.”

RIP-110 replies:
what if every Bitcoin transaction is a JPEG?

110 inputs.
One row per input.
A contiguous 52KB BMP.

No data pushes.
No special encoding.

Just Bitcoin reminding everyone why subjective filters don’t scale. 🟧

[lifofifo ◉ @lifofifo]

RIP 110 explores the concept that every Bitcoin transaction is a JPEG.

https://t.co/SVEW5UyCzf

A BIP 110-compatible TX with 110 inputs, each contributing one row to a 160×110 BMP, byte-for-byte.

CONTIGIOUS 52KB image file.

No data pushes. No special encoding.

[utxonaut @utxonaut]

First weekend off.

Sun.
Sea.
OpenCode.

No meetings.
No noise.
Just salt, commits, and a little sovereignty in the terminal. 🟧