🌟 Meet Blockscout CEO, Eva Zhang. With her expertise in fintech & cloud, Blockscout open-source explorers will be an intelligent AI-driven platform that: › Delivers actionable insights › Scales with enterprises › Empowers developers worldwide A new dawn begins 🌅

Check Blockscout 🙏 we just integrated detailed ENS info into our Pro API docs.blockscout.com/api-refe…

Pick the right tool to build your chain's explorer. If it runs on EVM, Autoscout can index it. Launch any testnet, mainnet, L2, or custom network in 5 minutes from one self-serve launchpad. 👇 autoscout.blockscout.com

🚨 Attackers are exploiting a flaw in wallet generation to drain addresses created as far back as 2018, even if completely dormant. Unexplained missing funds? Treat your recovery phrase as compromised. Move remaining assets to a new wallet and recovery phrase. Check all chains!

Blockscout Frontend v2.8.0 has arrived!🛠️✨ 🆕Key Features: → Avalanche ICTT support: users index, bridged tokens tab, stats layout → Async CSV export (built on v11 backend) → WebSocket live updates on homepage → ERC-7984 confidential token support

EVM chain explorer fragmentation is out of hand. For Mainnet, it's eth.blockscout.com. But for Optimism, it's explorer.optimism.io Stop hunting URLs! Search on Blockscout Multichain to get data across 90 networks instantly: explorer.blockscout.com/

More support for Ethereum Security QF Round projects! Thanks to @blockscout, every project in the round is eligible for a free one-month upgrade to one of Blockscout's developer plans. 🔹 Top 10 projects: Business API Plan (3B Credits/month @ 50 RPS) 🔹 Projects 11-134: Pro Plan (500M Credits/month @ 30 RPS) Eligible projects will receive an email from Giveth with instructions on how to claim their upgrade. Huge thanks to Blockscout for supporting the teams helping keep Ethereum secure. 🛡️

The nice thing about FHE is that its not a black box. You can actually track every computation onchain just like you would for regular EVM transactions. Blockscount has been an incredible partner and has been pushing great tools for people to see what really happens behind a confidential transaction.

We are rallying the entire ecosystem. Every touchpoint across the token lifecycle will require confidential token support. Integrations from key pillars of crypto infrastructure will catalyze utility, adoption, and growth of the ecosystem.

🛡️ PRIVACY WITHOUT SACRIFICING TRANSPARENCY? $ZAMA JUST PROVED IT. 🚨 BLOCKSCOUT JUST SHOWED THE WORLD HOW #FHE REALLY WORKS 🚨 ⸻ One of the biggest criticisms of privacy in crypto has always been: “If transactions are private, how can they be audited?” Blockscout and Zama just gave the answer. 🔐 Your balances stay encrypted. 🔐 Your transaction amounts stay confidential. 🔐 Validators never see your sensitive data. BUT… ✅ Every #FHE computation is visible. ✅ Every operation is traceable. ✅ Every computational cost is auditable. ✅ The entire execution path can be verified on-chain. This isn’t a black box. Blockscout now lets anyone inspect the actual #FHE operations happening behind confidential transactions. You can literally see: • Encryption operations • Arithmetic operations • Validation checks • Control logic • HCU computational costs All while the underlying financial data remains private. That’s the breakthrough. Privacy and transparency are no longer opposites. They’re working together. This is what programmable privacy looks like. This is why institutions, stablecoins, RWAs, AI agents, and next-generation DeFi are paying attention. And this is exactly why the partnership between Zama, T-REX, and eventually ecosystems like #Shibarium ’s $TREAT privacy layer is so important. The future isn’t public everything. The future is: 👁️ Auditable computation 🔒 Confidential data ⚡ Verifiable execution Welcome to the FHE era. $ZAMA $TREAT $SHIB $BONE $ETH #FHE #Zama #Privacy #ConfidentialTokens #RWAs #TREX #Shibarium #Blockchain #DeFi #Crypto

Have you explored the "FHE operations" tab on Blockscout yet? 🛡️ Let’s break down a live transaction to see how we maintain total on-chain transparency while keeping your sensitive data completely private. 👇 eth.blockscout.com/tx/0xd2d5…

Huge thank you to everyone who supported Blockscout in the Giveth Ethereum Security Quadratic Funding Round. Your support helps us keep building open source explorer infrastructure for Ethereum and the wider EVM ecosystem.

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.

A Safe Delay Module used in @gnosispay was exploited, allowing unauthorized txs from affected accounts. Withdraw funds from your Gnosis Card/Safe if possible (esp. EURe & GNO). Team says they'll cover losses for affected users.

The Ethereum-Cosmos bridge @gravity_bridge was exploited for ~$5.4M. The contract tagged as Gravity: eth.blockscout.com/address/0… You can: 1. Navigate to the Token transfers tab. 2. Click the Filter button and select Outgoing transfers. 3. Hover over the hacker's wallet address (0x7B...a1F9) to see the assets being transferred to them. The stolen tokens includes: → USDC: $4.3M → WETH: $552k → USDT: $434k → PAYG: $64k Looking at the hacker address, they likely don't trust stablecoins. They swapped the $USDC into $ETH to dodge a potential freeze. Swaps went out in big batches, from ~$500k down to $1.7k, all routed through @KyberNetwork. Example: eth.blockscout.com/tx/0xb87a… (500k USDC → ETH) After swapping to ETH, they split the funds across multiple wallets. ~$4.1M in ETH now sits dormant in the hacker's staging wallet 0x4d3ca32e…7A47, mostly untouched and likely waiting for an off-ramp via non-KYC CEXs or mixers. The smaller slice was peeled into worker wallets and split across multiple hops to blur the trail and hinder tracing. Root Cause: According to @QuillAudits_AI, Gravity Bridge contract works as intended. The exploit happened off-chain: the validators' signing pipeline was likely poisoned, so they unknowingly signed a malicious validator set update. Combined with the fact that the contract has no timelock, guardian, or circuit breaker, the drain was instant and irreversible once the signatures validated.

AI is a real threat vector, but it is also one of the most powerful defensive tools we have, if used with rigor and expert human judgment. Our researchers use AI daily to catch more issues and edge cases. The answer to AI risk is not retreat from DeFi. It is better security.

From rigorous security attributes to a complete visual overhaul, here are some things we delivered over April 🧵👇

Per instance API keys will be deprecated on July 1, 2026. Upgrade to Blockscout Pro API, one account, multichain access across 100 chains, better performance, and predictable scaling. Start free or scale with industry leading paid tiers. dev.blockscout.com/

$1 per Merit on Arbitrum Sepolia testnet 🤯 Trade @blockscout Merits on @CheckpointEX How to join: → Get USDC: faucet.circle.com/ → Buy/sell chBMRT: checkpoint.exchange/market/b… Have fun with the speculation! 🔮