treadorBE

[Mr. Pool @MrPool_QQ]

🔻 YOUR WIFI ROUTER OPERATES ON 2.4 GHz. YOUR MICROWAVE OVEN OPERATES ON 2.45 GHz. THE DIFFERENCE IS 0.05. ONE HAS A METAL CAGE AROUND IT. THE OTHER SITS OPEN IN YOUR BEDROOM 24 HOURS A DAY.

This is not a coincidence. It is a frequency selection made deliberately — and the document explaining why was removed from the FCC's public archive in 2014.

In 2003, the WHO commissioned a 6-year study across 4 countries on long-term low-level microwave exposure from wireless devices. Reference: WHO/EMF-2009/RC-7. Completed 2009. Never published.

A former research coordinator — 11 years at WHO Geneva:

"Continuous 2.4GHz exposure at standard router output — 100 milliwatts — produces measurable cellular stress markers within 14 days. At 90 days, we observed a 31% increase in cortisol baseline during sleep hours. At 180 days, blood-brain barrier permeability increased by 18%. The findings were unambiguous. Publication was blocked at the director level. We were told the economic implications were 'not manageable.'"

31% more stress hormone while you sleep. 18% more permeable blood-brain barrier — meaning toxins that should never reach your brain tissue now pass through freely. From a device you never turn off.

Your router does not sleep. At 3 AM it transmits at full power — beacon frames 10 times per second — maintaining connections you are not using. You are irradiated while unconscious for a purpose that serves the network, not you.

The microwave has a Faraday cage because 2.45GHz cooks tissue. Your router at 2.4GHz has no cage. The frequency interaction with cellular water is identical. One heats fast. The other heats slowly. Over years. Every night.

The fix is simple: buy a $4 outlet timer. Set your router to shut off at 11PM and turn on at 6AM. 7 hours of zero exposure every night. Within 2 weeks you will notice deeper sleep, fewer headaches, and less morning fog. This is not a theory. This is what happens when you remove a 2.4GHz source from a sleeping body.

Your insomnia is not anxiety. Your morning headaches are not dehydration. Your brain fog is not age. It is a microwave transmitter running at head-level while you are unconscious.

CODE: WHO-EMF-2009-RC7 / 2.4GHZ-BBB-18 / CORTISOL-31 / BEACON-10PS / TIMER-FIX

⟁
A microwave has a cage because the frequency is dangerous. Your router uses the same frequency with no cage. The only difference is speed. One cooks you in minutes. The other takes years. Turn it off tonight. Share this.

[Nicolas Hulscher, MPH @NicHulscher]

STUDY: Nattokinase DISSOLVES 84% of amyloid microclots within 2 hours in vitro — a pathology found in 100% of COVID vaccinated individuals tested.

This natural enzyme helps break down BOTH the trigger (spike protein) AND the pathological result (amyloid microclots).

[Justin Drake @drakefjustin]

Today a crazy quantum story just got wilder.

On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures.

But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first!

As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise.

Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours.

Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure.

Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice!

The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :)

Part 2: neutral atoms and qday

The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers.

Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low.

Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts.

My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom".

Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions.

So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030.

Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years.

Part 3: post-quantum cryptography

There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation.

These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer.

The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security.

Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.

[bandidolegal 🎗️ 🇳🇱 Ongevaccineerd @banditolegal]

De helft van al het drinkwater in Nederland wordt door datacenters verbruikt, de helft.
Dit blijkt uit een brief die minister Harbers naar de Tweede Kamer heeft gestuurd.

[NewRulesGeopolitics @NewRulesGeo]

🚨🇨🇳 PENTAGON'S WORST NIGHTMARE: CHINA'S UNJAMMABLE AI DRONE SWARMS

China just dropped HG-STR — the AI algorithm letting drone swarms autonomously detect, coordinate and annihilate targets even when jammed into total comms blackout and near-zero visibility.

🔸 HETEROGENEOUS GRAPH BRAIN: Tags every object by class (friendly UAV, search zone, enemy target) — unlike the West’s outdated “everything is data” swarms.

🔸 6.6 MILLISECONDS DECISIONS: Memory module stores last-known positions so swarms keep fighting autonomously when links die.

🔸 PREDICTIVE HUNTING: Estimates hidden enemy locations from terrain, patterns and prior intel — no ground control needed.

🔸 DOMINANT SIM RESULTS: 100% target hit probability in testing, showcasing China's edge in next-gen swarm intelligence

Do you think U.S. can catch up China in drone AI technology?

[Son Luong @sluongng]

Codex just found a “workaround” of not having sudo on my pc…

[Lukas Ziegler @lukas_m_ziegler]

3D Tissue Braiding for robot hands! 🧬

@AllonicRobotics created a 3D tissue braiding machine.

The machine is weaving high-strength fibers around a minimal rigid skeleton, exactly how human connective tissue wraps around bone.

There are no screws, no cables, and no fiddly joints. A continuous automated process creates tendons, soft tissue, and compliant structure all at once.

Digital design to physical part in minutes. Cost drops dramatically, so that end-effectors could eventually be swapped like disposable gloves.

Dexterous manipulation has been one of the last great unsolved problems in humanoid robotics.

Hands are expensive, slow to iterate, and hard to scale. 3D Tissue Braiding attacks every single one of those constraints simultaneously.

They also raised $7.2M in the largest Pre-Seed round in Hungarian history. 🇭🇺

This feels like the moment robotic bodies get their own 3D printing revolution.

@benedektasi let's go! 😮‍💨

~~

♻️ Join the weekly robotics newsletter, and never miss any news → https://t.co/GoA3ZuwoPB

[Joe Tippens @JoeTippen]

🚨🚨 83-year-old woman with stage 4 breast cancer that had metastasized to the liver, spine, and bones...
Generally, a death sentence.
For eight months, she took a daily dose of 222 mg of fenbendazole, which normalized her liver enzymes. The tumor marker dropped from 316 to 36...
No abnormal metabolic activity indicating cancer was detected...
Dr. John Campbell.
💊 FENBENDAZOLE – 12 Known Anticancer Actions:
1. Microtubule disruption: prevents cancer cells from dividing.
2. Inhibits glucose uptake: deprives cancer cells of energy.
3. Activates the p53 tumor suppressor gene, which helps eliminate damaged cells.
4. Triggers apoptosis (cell death), especially in lung, colon, and prostate cancer.
5. Inhibits metastasis: prevents cancer from spreading.
6. Increases oxidative stress in cancer cells, making them more vulnerable.
7. Immune modulator: may help the immune system attack tumors.
8. Blocks angiogenesis: prevents tumors from generating a blood supply.
9. Depletes glutathione in tumors, weakening their defenses.
10. Suppresses the AKT signaling pathway, involved in cell survival.
11. Restores normal cell cycle regulation: prevents uncontrolled growth.
12. Synergistic with other natural agents (e.g., CBD, curcumin, vitamin. Like, share and follow me for more updates..
. Thanks

[“Sudden And Unexpected” @toobaffled]

Every Vaccine Batch Had a Different Formula?

According to this analysis of 12,000+ lot numbers cross-referenced with VAERS data, some batches caused dramatically more adverse events than others .. up to thousands of percent higher.

The researchers claim it wasn’t random manufacturing inconsistency… but a clear pattern.

Whether you believe it was deliberate or not, the huge variation between lots is hard to ignore.

[HOSTIS @hostis_black]

Google is building a registry that ties every piece of Android software to a government ID, and your phone will soon refuse to run anything that is not on it.

Starting September 2026, an app will not install on a certified Android phone unless its maker has handed Google a government photo ID, paid a fee, registered a payment profile, and signed over the keys to their own code. And not just apps from the Play Store. Every app. The one a friend builds you. The one a stranger across the world wrote and gave away. The one you wrote yourself, for your own phone, in your own home.

Your hardware will check it against Google's list, and if the name is not on file, the door stays shut.

Android was the open one. For fifteen years that was the entire pitch, the one phone where you owned the device and chose the software and no one stood at the gate. That is what is ending.

The phone goes from a thing that runs what you tell it to a thing that runs what Google has approved, and approval now means a legal name in a database.

A malware author will buy a stolen identity for $40 and ship his poison the same as ever. He always has. The registry does not touch him. What it touches is the developer who cannot put his real name on his work. The one building a secure messenger for people a government wants dead. The one shipping a tool that embarrasses the powerful. The one who writes under a handle because the alternative is a knock at the door.

The purpose, in Google's own words, is to "remove the cover of anonymity."

The mask is the oldest tool the free press ever held. The pamphlet with no printer's name. The essay signed with a fake one. Every government that ever feared what its people might read started by demanding to know who set the type. Google has volunteered to be the one who keeps the list.

If you want to install software from a maker who refused the registry, you can, after you enable developer mode, swear to your phone that no one is forcing you to do this, restart the device, wait a full twenty-four hours, and authenticate again. A day-long cooling-off period and a coercion check, to put a program you chose on a phone you own.

It is the permission slip with enough friction that most people stop trying, which was always the point.

F-Droid, the free software catalogue that has handed out unsigned, unregistered, no-name software for over fifteen years, called it existential and refused to comply.

67 organizations told Google to kill the plan. Google moved the date for no one.

So learn the way out now, while the door is still open. The stores that answer to no registry. The phones that were never on Google's list. The skill of putting what you choose onto the machine you own, before that skill becomes a thing you have to wait a day and swear an oath to use.

A phone that asks permission before it runs your software was never your phone. It was theirs, parked in your pocket, billed to your name.

Take it back while taking it back is still allowed.

[Maryanne Demasi, PhD @MaryanneDemasi]

🎥 The Cholesterol Code - a review
What makes @realDaveFeldman such a compelling figure is that he approached the problem like an engineer rather than a doctor. He started dismantling the system piece by piece to understand how it actually worked.
@wideeyetv @Metabolic_Mind @matthewbaszucki @DavidBaszucki @newstart_2024 @ProfTimNoakes @ifixhearts

[treadorBE @treadorBE]

@SoulzBTC TRADING

[treadorBE @treadorBE]

@Danny_Crypton Me

[Joe Tippens @JoeTippen]

Cancer's old story: endless mutations, endless chemo.

Two leading doctors — Thomas Seyfried & Dr. Zakaria MD — are rewriting it: Cancer is metabolic & immune failure at the core.

Their preliminary research has led them to revelations on anti-parasitics, ketosis, and chemo's effect on wiping out the immune system. Thread 🧵
1. Professor Thomas Seyfried (Boston College) — world-renowned cancer biologist — saw cancer as mitochondrial metabolic disease.

Damaged respiration forces glucose/glutamine fermentation (Warburg effect).

His research shows that cancer cells rely on fermentation for energy, specifically from glucose and the amino acid glutamine, due to damaged mitochondria.

Seyfried advocates for metabolic therapies, including calorie restriction, ketogenic diets, and targeted drugs.

2. That led him to another revelation: anti-parasitics like fenbendazole disrupt glutamine pathways (glutaminolysis).

Professor Thomas Seyfried: "Mebendazole, Febendazole did a dive on it and I said, why do Parasite medications work against cancer cells, and it turns out that the parasites use mitochondrial substrate level phosphorylation in the tissue .. and mebendazol fenbendazol kill these parasites. So I tried it on the cancer cell and sure as hell, it targets the mitochondrial substrate and glycolysis"

As he points out, not only does Nutritional Ketosis support mitochondrial biogenesis in healthy cells — increasing efficiency, lowering oxidative stress, he points out the state of Ketosis might help other alternative drugs like anti parasitics work better.

3. Dr. Zakaria MD also had his awakening.

Chemo wipes out the cells important for cancer defense — NK cells, T cells, the immune frontline.

Dr Zakaria MD
@ZakariaMDv3
- "When you get chemotherapy it wipes out your NK and T Cells which are the only thing that protects your body against cancer”.

4. The Cells that Matter. to fight Cancer.

Whilst we sleep, the immune system keeps working.

Here's a Natural Killer (NK) taking out a cancer cell.

And this is the cell Dr. Zakaria MD was lazer focused on.....the same cell stimulated by a "breakthrough" the NIH was sitting on, which Dr. Zakaria (@ZakariaMDv3 ) was working towards making work in the clinical setting

5. His "profound realisation" is linked to why he worked toward steering the system away from more toxic treatments.

In trying to shift the industry toward immunotherapy, he recently pointed out to
@ZakariaMDv3
the NIH were sitting on a cancer breakthrough for over a decade.

But they did nothing with. Its name? IL-15.

IL-15 was designated by the NIH as the most important molecule to fight cancer, but they couldn't make it work.

Dr. Zakaria MD : "The NIH tried to develop this for 10 years." "The NIH and NCI designated this IL15 as the most important molecule to cure cancer, and they failed to develop it, because they couldn't make it last long or figure out how to actually just target directly the NK cells."

He emphatically emphasises - "We did that", when the NIH couldn't.

6. Seyfried Proved what fuels cancer needed to thrive, which led to his awakening to anti-parasitics' glutaminolysis blocking ability.

The mitochondrial upregulation stimulated by Nutritional Ketosis is used as the foundational support.

Dr. Zakaria MD (
@ZakariaMDv3
) awakened to chemo's immune destruction and focused on the role of NK Cells.

Both expose cancer's metabolic & immune vulnerabilities, showing potentially synergistic pathways. Preliminary animal & early clinical data show promise (Not medical advice).

Two brilliant minds — Seyfried & Dr. Zakaria MD— attacking cancer from different ends of the same problem: dysfunctional mitochondria & weakened immunity.

These Doctors are trying to move the entire system away from outdated thinking.

[VECERT Analyzer @VECERTRadar]

🚨 CRYPTO SECURITY ALERT: THE END OF FACIAL VERIFICATION (KYC) 🚨

🌐 The launch of JINKUSU CAM—a cybercriminal tool—has been detected. It is a powerful AI suite designed specifically to BREACH the security protocols of the world's largest exchanges (Binance, Coinbase, Kraken, OKX).

👤 Developer/Threat Actor: jinkusu.

🛠️ Tool Type: Real-time media manipulation software (Live Deepfake).

🎯 Objective: To bypass KYC (Know Your Customer) protocols on financial platforms, cryptocurrency exchanges, and mobile banking applications.

📦 TECHNICAL FEATURES (ATTACK VECTORS):

The software utilizes cutting-edge AI technologies to deceive verification systems:

🎭 Real-time Face Swap: GPU-accelerated face replacement (CUDA/DirectML) using InsightFace for fluid gesture transfer.

🗣️ Voice Changer: Real-time voice modulation with pitch adjustments and preset profiles (Anonymous, Radio, Robot) to evade voice biometrics.

🎥 Virtual Camera: Output compatible with OBS Virtual Camera, allowing the manipulated video feed to be injected into Zoom, Teams, Chrome, and verification apps.

📱 Emulator Support: Designed to function within Android emulators, enabling attacks against mobile applications that require "live" selfies.

✨ AI Enhancement: Utilizes GFPGAN and 478-point facial meshes (MediaPipe) to ensure the fabricated face mimics human expressions with extreme precision.

⚠️ ASSOCIATED RISKS (CRITICAL):

🏦 Mass Banking Fraud: Enables criminals to use stolen photos (such as those from previous data leaks in France or Mexico) to create a "living" persona that speaks and moves convincingly before a bank's camera.

🎭 Synthetic Identity Theft: Facilitates the creation of highly convincing fake identities for money laundering activities and romance scams (pig butchering). 🔓 KYC Compromise: Bypasses the "Liveness Detection" checks that many applications consider secure.

#Cybersecurity #Deepfake #KYC #Bypass #JinkusuCam #AI #IdentityTheft #Fintech #InfoSec #CyberAlert

[Wall Street Apes @WallStreetApes]

Man makes a visual demonstration of how American bread is actually made

Many Americans know our bread is toxic by now but they don’t really understand what the process of making it actually looks like and how bad it really is

This is eye opening

[Tom Kratman @TKratman]

From Martin Iles, reposted:

Having lived in the USA for nearly two years, I've realised something.

The USA and the remainder of the Western world are no longer aligned.

We all laugh and mock when the Americans say, "Freedom!" because we truly think we're as free as they are.

Wrong. We're not. Not even close. The laws, the mindset, and the behaviour, is totally different in this regard.

Most of all, the governments are totally different. The USA's convictions around core freedoms are on a scale we do not share.

Meanwhile, Donald Trump wins the popular vote, the electoral college, the House, and the Senate... a man who, in every other Western country, is held in open derision, if not contempt.

For these and other reasons, we are not the same.

Yet the West, including Australia, fully expect to rely on the USA for our very survival.

If the world turns bad (which will happen - only a question of time), then the whole West, without America, is toast.

So, you may ask - if we're not very aligned ideologically, then it must be that we bring something to the party militarily?

Well, no... actually... we don't matter that much militarily.

The USA has about 470 ships in its navy, including 11 aircraft carriers, 69 submarines, 75 destroyers... plus 110 new ships in the pipeline.

Australia has about 30, including 3 destroyers, 7 frigates and 7 outdated submarines. The UK does a little better, with about 60.

Meanwhile, the US has over 14,000 military aircraft. A staggering number.

Australia has 252 military aircraft. The UK has 556.

The US army has just shy of 1,000,000 uniformed personnel in its military. Australia has about 45,000.
The USA spends 3.4% ($968 billion) of its GDP on defence. Australia spends 2% ($36.4 billion). The US spends as much as the next 15 largest military-spending countries (including China) combined.

The USA has a fighting culture. The men shoot things (a lot) and hunt things, the veterans get favoured in everything from parking spots to boarding planes. A uniformed young man is thanked in the street a dozen times a day.

"Oh, the Americans and their guns!" we say, in our smug way. Yes, they have a warrior culture. We do not. We don't have to, because we're a leech on theirs.

How many young British men are willing to fight for their country? Now ask the same regarding young American men. The difference is about as wide as it could be.

Militarily, we don't offer squat.

Meanwhile, look at the way Australia works against America's interests by loving on China. China made us rich and we stay close. This is a Marxist regime with expansionist aims.

Again, you have to spend time in the USA to realise just how vast a gulf there is between us on China.

Europe, too. They let China have their way everywhere from Germany to Greenland, all the while importing Islam and sending their own people to court for saying hurty words.

Somehow, we have landed the deal of a lifetime with the USA that says, "when the baddies come, you'll save us ok?" Because we can't save ourselves.

And we live in peace. But we keep gnawing away at freedoms, keep enabling China, and get flabby and disinterested about our military because Uncle Sam's got it.

And, let's be honest, Americans are widely looked down on. To add insult to injury, we don't think that highly of our protectors.

So, the USA is finally saying "enough." I am here, I can tell you what the vibe is, and that's it. Trump is doing what people want in this regard. They're over it.

And we come across all shocked and hard done by. We behave like people with no self-insight at all.

Yes, the global alliance system is all over the place now. From America's perspective, it's about time.

And I must say, though I be a proud Australian, I am forced to agree. Something has to change.

[A Midwestern Doctor @MidwesternDoc]

For over a century, they've known vaccines cause sudden infant deaths—yet each time proof emerged, the CDC fought tooth and nail to hide it.

Here, I reveal all the buried evidence vaccines kill infants and the hospital data which explains how it happens.
https://t.co/HTM9dFmbmE

[Eric van de Beek 🇳🇱 @beek38]

Ben je een Duitse man van 17 tot 45 jaar? Dan mag je het land niet verlaten voor langer dan drie maanden, tenzij Defensie je daar toestemming voor geeft.

Deze wet is er stiekem doorheen geloodst. Binnenkort ook in NL? #Wereldoorlog3
https://t.co/I2FTKAp4wa

[𝕋𝕖𝕞𝕞𝕪🦇🔊 @Only1temmy]

i can't stop thinking about the drift protocol hack.

not because of the $280m. we've seen big numbers before. i can't stop thinking about how it happened. and what it says about everything we're building.

on april 1st, while people were posting jokes, an attacker drained $280 million from drift protocol in minutes. the team had to literally tweet "this is not an april fools joke."

but this didn't start on april 1st. it started on march 23rd.

that's when the attacker created four durable nonce accounts. two tied to drift's own security council multisig members. two controlled by the attacker. quietly. no alarms. no flags.

on march 27th, drift migrated their security council due to a routine member change. by march 30th, the attacker had already compromised a signer on the new multisig too.

then on april 1st, they executed.

a test transaction first. then one minute later, two pre-signed transactions fired four slots apart. admin takeover. withdrawal limits removed. a malicious asset introduced. every vault drained. jlp. sol. btc. usdc. over 15 tokens gone.

the entire thing took minutes.

this wasn't a bug. this wasn't a smart contract exploit. this wasn't a flash loan or an oracle manipulation. drift's own report confirms it (you can check @DriftProtocol's latest to confirm). no compromised seed phrases. no code vulnerability.

this was social engineering.

the attacker got 2 out of 5 multisig signers to approve transactions they didn't fully understand. used durable nonces to pre-sign them. then waited. patiently. for over a week.

two signatures out of five. that was the security standing between users and $280 million.

two out of five.

i keep coming back to that number because this is the part that should make everyone uncomfortable. not the hack itself. the architecture that made it possible.

we've seen this before. we've seen this so many times.

bybit. $1.4 billion. the attacker compromised the signing infrastructure and tricked signers into authorizing malicious transactions. same concept. social engineering. not code.

ronin bridge. $625 million. compromised validator keys. same story.

cetus protocol. $223 million. different method but same result. hundreds of millions gone.

in 2025 alone, $3.4 billion was stolen in crypto. and the pattern is almost always the same. not brilliant code exploits. not zero-day vulnerabilities. someone was tricked. a key was exposed. a human made a mistake.

only 19% of hacked protocols even used multi-sig wallets. and the ones that did, like drift, got beaten anyway. because the weakest link was never the code. it was always the person holding the key.

now here's what makes me angry.

i've seen people dunking on solana over this. blaming svm. questioning the entire chain. the same thing happened after bybit when people started questioning evm and ethereum's security model.

this is not a solana problem. this is not an ethereum problem. this is not chain-specific at all.

drift's own report says it clearly. the programs and smart contracts worked exactly as designed. the chain did what it was supposed to do. a human was tricked into signing something they shouldn't have. that can happen on any chain. any protocol. any ecosystem.

pointing fingers at solana is a deflection. and it's net negative for the entire space because it distracts from the real conversation we need to have.

which brings me to circle.

nine days before the drift hack, circle froze 16 business wallets overnight. legitimate companies. crypto exchanges. forex platforms. payment processors. no criminal charges. a sealed civil lawsuit that nobody could even read. no advance warning. businesses woke up and couldn't process payments, couldn't settle trades, couldn't serve their customers.

zachxbt called it "potentially the single most incompetent freeze" he'd seen in over five years of investigations. one of the frozen wallets wasn't even a business. it was a dfinity bridge contract used by thousands of users who had nothing to do with the case.

then nine days later, $280 million is being drained from drift in real time. the attacker is converting stolen tokens through jupiter, bridging them to ethereum, moving funds through circle's own cross-chain transfer protocol.

and the freeze didn't come fast enough.

so circle can shut down 16 legitimate businesses overnight for a civil case. but a quarter billion being actively stolen through their own infrastructure? different speed.

i'm not saying circle is the villain here. i'm saying the system is broken in ways that should concern everyone.

now think about who's actually affected by drift.

it's not just traders. protocols are built on top of drift. neobanks integrate with defi infrastructure. real customers with no idea what a multisig even is woke up and saw they couldn't access their money. some platforms said user funds are safe. but nobody could withdraw.

your money is "safe" but you can't touch it. think about what that feels like for someone who just wanted a better savings rate.

i know what it feels like on a smaller scale. i lost $5,000 to social engineering. it's nothing compared to $280 million. but the feeling is the same. that moment when you realize the funds are gone and there's nothing you can do. it doesn't scale with the dollar amount. it's the same pit in your stomach whether it's $5k or $280m.

and here's the question i keep circling back to.

we say defi is the future. we say we're going to onboard the next billion users. we say this technology will replace traditional finance and bank the unbanked and give people financial sovereignty.

but how do we onboard millions of people into a system where a social engineering attack can drain a quarter billion dollars in minutes? where 2 out of 5 signatures is considered security for $280m? where the attacker sets up wallets two weeks early, runs a test transaction, and nobody notices? where circle can freeze legitimate businesses overnight but can't stop a live heist fast enough? where the same attack, the same playbook, the same human error keeps happening year after year after year?

ronin. bybit. cetus. now drift. same cause. different name. different chain. same result.

defi doesn't have a code problem. it has a people problem. and we keep solving for the code.

i haven't interacted with a protocol in a while. i like money. but i love safety more. and right now this space is asking me to choose between the two.

security can't keep being the last conversation. it can't keep being the thing we talk about after the hack and forget about before the next one. it has to be the first priority. not the last.

because right now we're not ready for the next billion users. we're barely keeping the ones we have safe.