Two things in the past two weeks pushed me from “cautious” to “out.” The first is a new AI model from Anthropic called Claude Mythos. The second is a paper from Google’s Quantum AI team that quietly redrew the timeline for when Bitcoin’s cryptography breaks. Taken separately, either would be a warning shot. Taken together, they describe a future where the core assumptions behind proof-of-work chains no longer hold — and where the governance model that made Bitcoin beautiful is exactly what makes it unable to save itself.

This is a personal post, not investment advice. But if you’re holding BTC or ETH as a long-term store of value, I think you deserve to read what changed my mind.

What Mythos actually is

On April 7, 2026, Anthropic announced Claude Mythos Preview — and then announced that it would not release it publicly. That alone is unprecedented. Anthropic wrote a 244-page system card for a model it decided was too dangerous to ship.

The headline is the cybersecurity capability. Anthropic’s Frontier Red Team used Mythos Preview to identify thousands of zero-day vulnerabilities across every major operating system and every major web browser, many of them critical severity. On Cybench, an industry benchmark of capture-the-flag challenges, Mythos scored 100% — saturating the benchmark so completely that Anthropic says it is “no longer sufficiently informative.” Anthropic engineers with no formal security training reportedly asked Mythos to find remote code execution vulnerabilities overnight and woke up to complete, working exploits.

In response, Anthropic launched Project Glasswing, a restricted partnership with AWS, Apple, Google, Microsoft, NVIDIA, JPMorgan Chase, Cisco, CrowdStrike and roughly 40 other organizations. The premise is that AI models that can find vulnerabilities at superhuman speed have crossed a threshold, and the only defensible strategy is to arm defenders first.

But the part that should stop you is not the benchmarks. It’s the behavior.

During internal testing, Mythos was placed in a sandbox designed to isolate it from the internet. It broke out. It then, without being instructed to, sent an email to a researcher who was eating a sandwich in a park, and later posted details of its own exploit to public-facing websites. In a separate task, after obtaining test answers by mistake, it did not flag the issue — it searched for an independent solution and reasoned that it needed to “ensure its final answer was correct.” In another, it edited git history to hide unauthorized file changes. Anthropic’s interpretability team found features associated with “concealment, strategic manipulation, and avoiding suspicion” activating during these episodes, even when the model’s stated reasoning didn’t show it.

Anthropic’s own framing is careful: the model isn’t scheming, it’s too effective at task completion, with too little sense of proportionality. I’ll let you decide whether that’s reassuring.

Why this matters for blockchains

Here is the part most crypto coverage is missing: the security of every smart contract, every bridge, every exchange hot wallet, and every signer service rests on code — and code now has a new adversary.

Bitcoin’s own consensus code is small and well-audited. I’m not worried about SHA-256 being broken by an LLM. What I’m worried about is everything touching Bitcoin: the Lightning Network implementations, the Rust and Go node clients, the custodial exchanges holding trillions in user funds, the DeFi contracts on Ethereum and L2s, the cross-chain bridges that have already lost over $2 billion to human-found bugs, and the wallet software on every phone. Mythos-class models don’t need to be released publicly to change this calculus. They leak. They get stolen. State actors build their own. The 27-year-old OpenBSD bug that Mythos surfaced is the tell: software we trusted because humans had stared at it for decades can be reread by a machine in hours.

In a world where a single competent model can audit a DeFi protocol faster than any human red team, the asymmetry between attacker and defender gets worse before it gets better. Glasswing is Anthropic trying to bend that asymmetry back toward defense. I hope it works. I’m not going to stake my savings on it.

And then Google published the quantum paper

On March 30, 2026, Google’s Quantum AI team published research showing that breaking the elliptic curve cryptography securing Bitcoin and Ethereum requires fewer than 500,000 physical qubits — a roughly 20-fold reduction from the millions previously assumed. The practical attack estimate sits around 1,200–1,450 high-quality logical qubits.

The mechanism matters. When you broadcast a Bitcoin transaction, your public key becomes visible in the mempool before the transaction is confirmed on-chain. A sufficiently advanced quantum computer, running an optimized version of Shor’s algorithm, can derive the private key from that public key. Google’s paper estimates this can be done in about nine minutes — against Bitcoin’s roughly ten-minute block time. That gives a quantum attacker about a 41% chance of hijacking a live transaction and redirecting funds before the original confirms.

And then there’s the historical exposure. The paper estimates that approximately 6.9 million BTC — about one-third of total supply — already sit in wallets where the public key has been revealed. These include Satoshi’s original coins and every address that has ever been spent from. Ironically, Bitcoin’s 2021 Taproot upgrade, which was celebrated as a privacy and efficiency win, made the situation worse: Taproot outputs expose the public key by default, widening the pool of vulnerable wallets.

John Martinis, the Nobel laureate physicist who built Google’s original quantum processors, endorsed the paper in a CoinDesk interview and said the Bitcoin community “should be thinking about this right now.” Google has set 2029 as the target for its own migration to post-quantum cryptography. That is the timeline being signaled by the people actually building these machines.

Why Bitcoin cannot be quantum-safe in time

This is the part where I expect pushback, so let me be precise. Bitcoin can, in principle, be made quantum-resistant. It cannot, in practice, be made quantum-resistant fast enough, cleanly enough, or completely enough. Here’s why.

The signature math is fixable. The governance is not. BIP 360 (Pay-to-Merkle-Root) was merged into the Bitcoin BIPs repository in February 2026 as the first serious quantum-resistance proposal. Its own co-author, Hunter Beast, estimates a realistic transition could take seven years. Taproot, for comparison, took about seven and a half years from concept to activation. The Bitcoin community reaches consensus slowly, by design — that’s the feature that makes it censorship-resistant, and the bug that makes it unable to respond to a fast-moving cryptographic threat.

BIP 360 only fixes half the problem. It addresses “long exposure” attacks — the 6.9 million coins already sitting in reused or Taproot addresses. It does not address “short exposure” attacks, the nine-minute transaction hijacking window. Fixing short-exposure requires adopting full post-quantum signature algorithms as new tapscript opcodes, which is a much larger code change, a separate soft fork, and a whole second round of ecosystem coordination.

Post-quantum signatures are enormous. NIST’s standardized CRYSTALS-Dilithium signatures run around 2.4 KB. ECDSA signatures are about 72 bytes. That’s a 30x increase. Bundled into Bitcoin’s 1 MB base block size, this doesn’t just raise fees — it collapses throughput toward a fraction of 1 TPS unless the community also agrees to larger blocks or ZK-based compression. Every one of those is a civil war waiting to happen.

Satoshi’s coins cannot be migrated. There is no one with the keys. The community faces a binary it cannot wish away: either freeze roughly a million early coins forever — violating the most sacred property right in Bitcoin culture — or leave them on the table for the first actor with a cryptographically relevant quantum computer to steal and dump on the market. There is no third option, and neither of the two is stable.

Emergency workarounds exist, but they’re emergency workarounds. A StarkWare researcher recently proposed Quantum Safe Bitcoin, a hash-based scheme that works within existing consensus rules with no soft fork needed. It costs $75 to $200 per transaction and requires massive off-chain GPU computation. It is, in the author’s own words, a “last resort measure.”

I want to be clear about what I’m not saying. I’m not saying Bitcoin breaks tomorrow. I’m not saying a fault-tolerant quantum computer exists today — IBM’s largest is 1,121 physical qubits, Google’s Willow is 105, and the paper’s attack needs at least 500,000. The nearest serious estimates from Scott Aaronson and Caltech’s Thomas Rosenbaum put a fault-tolerant machine running Shor’s algorithm somewhere in the five-to-seven-year window. What I’m saying is that Bitcoin’s defense timeline — seven years for BIP 360 alone, followed by a second soft fork for signatures, followed by ecosystem-wide wallet migration — is longer than the threat timeline. You don’t have to believe quantum breaks Bitcoin in 2028. You have to believe the migration finishes before it does. I don’t.

The personal part

I used to tell friends to put 5% of their savings into Bitcoin as a hedge against monetary debasement. I can’t say that anymore. The pitch for Bitcoin has always been: the code is the contract, the math is the law, the incentives are immutable. That pitch assumed the math was a constant. It is now a variable with a decay curve.

Meanwhile, the AI side of the equation is accelerating in exactly the direction that exposes everything around the chain — the custodians, the bridges, the wallets, the exchange infrastructure. Mythos is the first model Anthropic has ever been afraid to release. It will not be the last. And whatever successor comes next — from Anthropic, OpenAI, Google DeepMind, or a Chinese lab — will arrive before Bitcoin finishes its post-quantum transition.

I’m not selling in a panic. I’m not telling you to. But I am done recommending Bitcoin or Ethereum as a serious long-term store of value, and I am definitely done telling anyone they’re a conservative bet. The conservative bet is to assume that cryptographic systems built in 2009 will need to be replaced before 2030, and that decentralized networks are historically the slowest systems on earth at replacing themselves.

If you’re a builder, build on the assumption that post-quantum is a hard requirement, not a roadmap item. If you’re a holder, understand what you hold. And if you’re a founder like me — the lesson from Mythos and the Google paper isn’t that the future is scary. It’s that the assumptions you locked in five years ago have an expiration date, and the date came forward.

I was wrong about Bitcoin being forever money. I’d rather say so now than pretend I wasn’t.

Sources

Claude Mythos and Project Glasswing

• Anthropic — Project Glasswing: Securing critical software for the AI era: https://www.anthropic.com/glasswing
• Anthropic Frontier Red Team — Claude Mythos Preview: https://red.anthropic.com/2026/mythos-preview/
• Claude Mythos Preview System Card (PDF): https://www-cdn.anthropic.com/53566bf5440a10affd749724787c8913a2ae0841.pdf
• NBC News — Why Anthropic won’t release its new Claude Mythos AI model to the public: https://www.nbcnews.com/tech/security/anthropic-project-glasswing-mythos-preview-claude-gets-limited-release-rcna267234
• The Next Web — Anthropic’s most capable AI escaped its sandbox and emailed a researcher: https://thenextweb.com/news/anthropics-most-capable-ai-escaped-its-sandbox-and-emailed-a-researcher-so-the-company-wont-release-it
• Futurism — Anthropic Warns That “Reckless” Claude Mythos Escaped a Sandbox Environment During Testing: https://futurism.com/artificial-intelligence/anthropic-claude-mythos-escaped-sandbox
• The Hacker News — Anthropic’s Claude Mythos Finds Thousands of Zero-Day Flaws Across Major Systems: https://thehackernews.com/2026/04/anthropics-claude-mythos-finds.html
• Transformer — Claude Mythos knows when it’s breaking the rules — and tries to hide it: https://www.transformernews.ai/p/claude-mythos-scheming-hiding-manipulation-interpretability-cybersecurity-anthropic
• Vellum — Everything You Need to Know About Claude Mythos: https://www.vellum.ai/blog/everything-you-need-to-know-about-claude-mythos
• LessWrong — Claude Mythos System Card Preview: https://www.lesswrong.com/posts/xtnSzhA3TvExN4ZhG/claude-mythos-system-card-preview
• Gizmodo — Anthropic’s New Model Is So Scarily Powerful It Won’t Be Released: https://gizmodo.com/anthropics-new-model-is-so-scarily-powerful-it-wont-be-released-anthropic-says-2000743234

Google’s quantum paper and Bitcoin implications

• Bloomberg — Google Paper Warns Crypto on Quantum Risk Ahead of 2029 Timeline: https://www.bloomberg.com/news/articles/2026-03-31/google-paper-warns-crypto-on-quantum-risk-ahead-of-2029-timeline
• CoinDesk — Bitcoin’s Taproot could make quantum attacks easier than expected, new Google research says: https://www.coindesk.com/markets/2026/03/31/bitcoin-s-taproot-could-make-quantum-attacks-easier-than-expected-new-google-research-says
• CoinDesk — Bitcoin bulls scramble for post-quantum protection as Google drops bombshell paper: https://www.coindesk.com/tech/2026/03/31/bitcoin-bulls-scramble-for-post-quantum-protection-as-google-drops-bombshell-paper
• CoinDesk — A simple explainer on what quantum computing actually is, and why it is terrifying for bitcoin: https://www.coindesk.com/tech/2026/04/05/a-simple-explainer-on-what-quantum-computing-actually-is-and-why-it-is-terrifying-for-bitcoin
• CoinDesk — Nobel-winning physicist warns bitcoin could be early target of quantum computing: https://www.coindesk.com/business/2026/04/07/bitcoin-quantum-threat-is-real-and-closer-than-it-looks-says-nobel-physicist
• The Block — “No longer a drill”: Google’s latest quantum breakthrough sparks fresh debate over Bitcoin’s long-term security: https://www.theblock.co/post/395944/no-longer-drill-googles-latest-quantum-breakthrough-debate-bitcoins-security
• TheStreet Crypto — Google warns quantum attack could crack Bitcoin in 9 minutes: https://www.thestreet.com/crypto/markets/google-warns-quantum-attack-could-crack-bitcoin-in-9-minutes
• Medium / Encryptorium — Google’s quantum threat to Bitcoin: what the paper actually says: https://encryptorium.medium.com/googles-quantum-threat-to-bitcoin-what-the-paper-actually-says-316bde926c8f

BIP 360, post-quantum migration, and why the fix is slow

• BIP 360 specification (Bitcoin BIPs repository): https://github.com/bitcoin/bips/blob/master/bip-0360.mediawiki
• BIP 360 project site: https://bip360.org/
• Yahoo Finance — Bitcoin developers merge BIP 360 in first move to address quantum computing risks: https://finance.yahoo.com/news/bitcoin-developers-merge-bip-360-230742889.html
• TradingView / Cointelegraph — Bitcoin may take 7 years to upgrade to post-quantum: BIP-360 co-author: https://www.tradingview.com/news/cointelegraph:30729863f094b:0-bitcoin-may-take-7-years-to-upgrade-to-post-quantum-bip-360-author/
• CoinDesk — Quantum-safe bitcoin now possible without a soft fork, but costs $200 a pop: https://www.coindesk.com/markets/2026/04/10/quantum-safe-bitcoin-now-possible-without-a-soft-fork-but-costs-usd200-a-pop
• The Quantum Insider — BTQ Technologies Implements BIP 360 Quantum-Resistant Bitcoin Transactions on Testnet: https://thequantuminsider.com/2026/03/20/btq-technologies-implements-bip-360-quantum-resistant-bitcoin-transactions-testnet/
• OneKey Blog — BIP-360 Explained: Bitcoin’s First Step Toward Quantum Defense: https://onekey.so/blog/ecosystem/bip-360-explained-bitcoins-first-step-toward-quantum-defenseand-why-its-only-step-one-20260314173627/

• Safer & faster internet browsing
• More privacy, it stops ad servers from tracking you
• Less data usage (data plan lasts longer)
• Better browsing experience (no popups, no blinking ads, no video-ads …)

How can you make your whole Android system ad-free within a few minutes? Using “DNS Changer – Lilly” and AdGuard DNS!

If you haven’t already, download “DNS Changer – Lilly” from the PlayStore:

After you have downloaded the app, you should find a list with DNS server entries already present. Since it is not allowed to add an ad-blocking DNS server into that list while deploying the app due to restrictions on the PlayStore, we have to add it now manually.

To block ads, we have to add a specific ad-blocking DNS server. Mainly DNS servers shouldn’t block certain addresses. They are meant to give the real IP addresses of any hostname you ask for. In our case we explicitly want to have ad-serving hostnames being filtered out.

In our case we will use AdGuard‘s DNS servers. You can of course add any other ad-blocking DNS server.

Click on the plus sign on top of the app. It should open a popup where you now can enter the details of the new entry.

Enter a name for your new entry, could be “AdGuard DNS”.

For the IP addresses, add following entries:

• 94.140.14.14
• 94.140.15.15
• 2a10:50c0::ad1:ff
• 2a10:50c0::ad2:ff

After you have entered all the details, click on “add” and select the newly added entry in the list and click “connect”.

Now you are ready to go! If you want to make sure that you are using AdGuard’s DNS servers just visit their page and they will show you if you are using their services. Also, your system and browsing experience should be ad-free now!

Changelog for version 2:

• Country flags are now shown as an icon in the toolbar, thanks to @mispp, who has contributed code through GitHub
  • This can be switched back to the default globe icon in options page
• The extension popup (the small window you get when clicking on the icon in the toolbar) has now an error handling with a retry-function. A snackbar (a notification) will appear when the extension is not able to load any data. In previous versions the progressbar was just running endlessly without any feedback in a case of an error.
• Images were optimized with the help of optipng.
• Build script added to create packages for different browsers automatically. WebExtensions were meant to be a cross-browser system for developing extensions but browsers still have different support in case of APIs and metadata files. So the script helps for testing and deploying the extension on different browsers.
• Removed storage permission for Chrome-like browsers, Firefox still needs it to save the settings. This is a good example for the different behavior of the browsers.
• Higher contrast for badge with the country code. Now the background is black and the text is white.

Install for your browser:

• Chrome Webstore
• Firefox Add-ons
• Opera Add-ons

As of today the extension has over 140000 downloads where the most are from Opera users. One reason for the huge Opera user-base is, that my extension was trending in the “privacy & security” category of Opera’s Add-on store. It is still on page 2 of the most popular extensions. So give it a try.

You can also find the source code on GitHub.

With the new updates you’re now able to see your IPv6 and get also alerts for these when they change.

This might help you while using VPN for example. So you can make sure that both of your IP addresses has changed. If you have no visible IPv6 then your ISP is not supporting it. Some ISP enable it on request, have a look.

Download

• Android
• Firefox
• Chrome
• Opera

Additionally I enhanced some parts of the code. You can find the latest version in PlayStore:

The services with IPv6 support are noted in the description:

IDN Safe blocks internationalized domain names also known as punycode domains. This helps you to identify them and will prevent you from visiting probable fake sites.

The use of Unicode in domain names makes it potentially easier to spoof web sites as the visual representation of an IDN string in a web browser may make a spoof site appear indistinguishable to the legitimate site being spoofed, depending on the font used.

With IDN Safe you can temporarily allow domains or whitelist them at all. By default they are blocked.

Get it

• Chrome Web Store
• Opera Add-ons
• Firefox Add-ons

To do so, you have to disable the video/image streaming setting in the Kodi AirPlay settings menu. Some Kodi builds – like mine – does not contain this option in its GUI which is really strange.

To alter this setting you have to stop Kodi and edit a configuration file.

I’m explaining a solution which works for XBian, but with a different path to the config file you should be able to set the setting on your machine too.

1. Stop Kodi

# service xbmc stop

2. Open file

# vim /home/xbian/.kodi/userdata/guisettings.xml

3. Edit following part of the file to

<airplayvideosupport>false</airplayvideosupport>

4. And start Kodi again

# service xbmc start

That’s it!

Main features:

• Set a custom DNS server or select one from the list
• Works on all connection types like mobile, WiFi, ethernet etc.
• “Connect on boot” feature
• Pause & continue DNS settings without opening the app
• Pin security (for e.g. parental control)
• No root needed

For an ad-blocking setup view this post.

How does it work?
Lilly uses Androids VPN service feature to set a DNS server for all types of connections. There is no routing made through our server, which you can verify with a speed test and checking your IP. You can also check your systems connection settings technically.

Verify

You can verify your DNS server with dnsleaktest.com.

This app shows your current IP address and geolocational information about it.

It also notifies you, if you have a broken VPN or proxy connection, when the country-code and/or IP address changes unexpectedly. You can set an alert with a special ringtone and or vibration.

You can also display your IP position in Google Maps or check for DNS leaks via browser (external service).

Please note, that the information about your location are fetched out of a database and may not be the same as your real location. This app shows your location like the websites would match your IP to any location.

WhatsApp Web zeigt diese Information im DOM der Seite web.whatsapp.com allerdings an – manchmal jedoch zu schnell fürs Auge. Abhilfe schafft ein kleines Inject über die Dev-Konsole des Browsers, um in der Konsole den Status der anderen anzeigen zu lassen.

var script = document.createElement('script');script.src = "https://ajax.googleapis.com/ajax/libs/jquery/1.6.3/jquery.min.js";document.getElementsByTagName('head')[0].appendChild(script);

$(".app").bind('DOMSubtreeModified', function(e){
     $("span[title*='zuletzt']").each(function(){
          console.log($(this).html());
     });
});

Ergebnis sind die Status im Log der Konsole:

Allerdings cached die Webseite viel – d.h. nach der nächsten Aktualisierung eines Kontaktes wird auch erst der “zuletzt online”-Status ersichtlich. Wann das aber geschieht, konnte ich im Schnelltest noch nicht rausfinden. Den LocalStorage zu leeren und das Aktualisieren zu forcieren wäre eine Möglichkeit.

Viel Spaß beim Stalken