News
22 May 2026, 11:08
Attackers drain more than $520,000 from Polymarket contract

A Polymarket security incident drained more than $520,000 in collateral from the platform’s UMA CTF Adapter contract on Polygon on May 22, 2026. On-chain investigator ZachXBT flagged the incident in a community alert and pointed to a compromised deployer address as the likely entry point for the attack. The drain played out across a short window around 09:00 UTC. No official notice from Polymarket or UMA had been posted at the time of reporting. How the Polymarket drain played out? The hack targeted the Polymarket UMA CTF Adapter Admin Contract at address 0x91430C…E5c5, which is an upgradeable proxy that manages the main adapter that holds the market collateral. The blockchain reveals the initial events recorded on the Admin Contract at around 09:00:30 UTC. That should raise an alarm about a proxy pattern exploit. The initial events were quickly followed by transfer events for Polygon’s native currency, POL. At 09:00:49, the adapter admin received 5,000 POL from a Polymarket address. Five seconds later, it sent close to 9,994 POL out to the attacker-controlled account. The pattern repeated at 09:01:19 with another 5,000 POL inflow, followed by a transfer of close to 5,000 POL to the same attacker address at 09:01:26. The two-step transfer moved more than 10,000 POL out of the adapter in under a minute. The drained addresses listed by ZachXBT, 0x871D7c0f and 0xf61e39C7, had sent collateral into the adapter that the attacker then withdrew through the admin contract. The primary attacker address received the POL transfers and began consolidating the funds shortly afterward. A compromised key, not a smart contract bug In this way, the chain of initializing calls to the admin contract shows the risk of key theft and initialization vulnerability rather than any issue with the UMA optimistic oracle logic. The contract was based on the UMA oracle, but the breach occurred in the access control level, and the hacker received the ability to perform admin-only calls. It can be assumed that either the deployment process happened with the help of a key compromised by attackers or an uninitialized contract proxy was available for exploitation. After receiving administrator powers, the hacker could withdraw the whole collateral balance without any need for custom exploits. The Polymarket hack resembles similar events reported earlier in 2026. For instance, the Step Finance hack of about $27.3 million happened due to a breach of the executive key and the multi-sig mechanism at the beginning of 2026. A similar case is the Drift Protocol hack of about $285 million; it happened in April 2026 as a result of a socially engineered admin key, which enabled whitelisting worthless collateral. There were no software vulnerabilities in those smart contracts. Attacker wallet activity and tracing The address 0x8F98075d should be flagged as highly suspicious because it was the destination for both POL collateral transfers and is the greatest opportunity for movement of stolen value out of or into the Polygon network. Similarly, the intermediary address involved in initializing calls 0x65070BE9 can be assumed to be controlled by attackers and deserves similar monitoring. Based on past experiences, there is a possibility that the next step will involve cross-chain bridges and mixing. In the case of Drift , the stolen funds were partially bridged to Ethereum via the cross-chain protocol belonging to Circle prior to laundering. There were no reports as of reporting of large outgoing bridges from the suspect addresses. If you're reading this, you’re already ahead. Stay there with our newsletter .
22 May 2026, 11:07
Quantum threat: Crypto industry preparing for Q-Day

More on quantum computing Defiance Quantum ETF: The Infrastructure Of Tomorrow Quantum computing is a 'derivative play' on AI - Dan Ives IBM, others confirm proposed U.S. quantum funding awards Quantum risk to crypto is advancing, Google paper warns
22 May 2026, 11:07
Dogecoin Price Prediction: Can DOGE Finally Break Above $0.15?

Dogecoin is holding inside a long consolidation range as traders track signs of accumulation near key support. The latest daily and weekly charts point to $0.15 as the main upside level, but DOGE still needs a confirmed breakout above resistance. Dogecoin Eyes $0.15 Breakout After Long Consolidation Dogecoin is moving inside a long consolidation range after months of sideways trading on the daily chart. The setup shared by BitGuru shows DOGE holding above the lower support zone near $0.088, while price tries to build strength below the next resistance levels. DOGE Daily Consolidation Chart. Source: BitGuru on X The chart marks an earlier liquidity sweep, where DOGE briefly moved above a prior high before dropping back into the range. That move cleared upside liquidity, then price returned to a lower base. Since then, DOGE has traded in a tighter structure instead of continuing the downtrend. The key breakout area now sits around $0.127 to $0.131. A clean move above that zone would strengthen the recovery setup and open the way toward $0.140, then the larger target near $0.150. However, DOGE still needs stronger momentum. The current structure shows accumulation and compression, but not a confirmed breakout yet. If price fails to hold the consolidation range, the lower support near $0.088 remains the main level to watch. Dogecoin Weekly Signal Returns as DOGE Builds From Support Dogecoin is showing a fresh weekly Surf Indicator signal between February and April 2026, while price trades near a long-term support area. The chart shared by Surf shows a similar signal last appeared from June to September 2022, during DOGE’s earlier base-building phase. DOGE Weekly Surf Indicator Chart. Source: Surf on X The setup does not confirm a breakout by itself. However, it shows DOGE is again trading in a zone where previous downside pressure started to slow. That makes the current area important for trend direction. DOGE recently bounced from the $0.095 area and is trying to recover above the lower range. The first important resistance sits near $0.12, followed by the larger $0.15 zone. A move above those levels would make the recovery structure stronger. If DOGE fails to hold the current base, the chart leaves room for another test of lower support near $0.075 and $0.061. For now, the signal points to early accumulation conditions, but price still needs confirmation through resistance.
22 May 2026, 11:06
Quantum Computing and Crypto: Is Blockchain Security Ready for the Next Threat?

Quantum computing is moving from theory to prototypes, rekindling a hard question for crypto: will tomorrow’s machines break today’s blockchains? The short answer is nuanced. Some core tools that secure wallets and consensus could be vulnerable to future quantum attacks. Others—especially hash-based primitives that defend proof-of-work and Merkle trees—look comparatively robust. If you hold assets, build wallets, or run infrastructure, you don’t need panic—you need a plan. The timelines are uncertain, but migration takes years. The teams that inventory their cryptography, add algorithm agility, and sketch a post-quantum (PQ) roadmap will be positioned to adapt without rushing under pressure. This article separates signal from noise: what quantum threatens, what likely survives, the readiness of major networks, and concrete steps to reduce risk now—without hype or fatalism. PointDetailsPrimary quantum riskShor’s algorithm could break widely used public-key signatures (ECDSA, Ed25519, Schnorr, BLS). That’s a long-term but high-impact risk.What likely holds upHash-based primitives (SHA-256, Keccak-256), Merkle trees, and STARK-style proofs remain comparatively resilient; Grover’s algorithm offers only a quadratic speedup.Network exposure variesBitcoin addresses that hide public keys until spend reduce exposure; Taproot and many L1/L2 accounts that directly reveal public keys are more exposed in a post-Shor world.Standards progressNIST has selected PQC algorithms (Kyber; Dilithium, Falcon, SPHINCS+) and circulated draft FIPS in 2024; real-world deployment still takes years.Practical mitigationAdd crypto agility (hybrid signatures, account abstraction), avoid address reuse, plan UTXO sweeps, and monitor vendor roadmaps for PQ support.Investor takeawayNo immediate collapse is likely, but preparation now reduces future migration costs and key-exposure risks. The Quantum Threat Model for Blockchains Quantum computers exploit superposition and entanglement to accelerate specific computations. Two algorithms matter for cryptography: Shor’s algorithm threatens discrete logarithm and factoring problems—the foundation for ECDSA, Ed25519, Schnorr, RSA, and BLS signatures. Grover’s algorithm gives a quadratic speedup for brute-forcing symmetric keys and hashes. That halves the “effective” bits of security (e.g., 256-bit hash to roughly 128-bit search effort), which is still considered strong in practice with parameter adjustments. For blockchains, signatures protect funds and consensus identities. If a sufficiently powerful, fault-tolerant quantum computer becomes available (“Q‑day”), an attacker who sees a public key could compute the corresponding private key and forge signatures. Important nuance: the “harvest now, decrypt later” risk that plagues encrypted data is less direct for signatures. Attackers cannot decrypt your private key from an address hash they see on-chain. They can, however, archive exposed public keys today and attempt key recovery later if those funds remain unmoved when quantum machines arrive. Pro tip: Limiting public key exposure and avoiding address reuse are low-cost steps that improve your posture against future signature forgery. What Breaks Under Shor vs. Grover Different blockchain components depend on different primitives. Here’s a high-level map of potential impact. ComponentMain PrimitiveQuantum ImpactCommentWallet signatures (BTC ECDSA, ETH ECDSA/Schnorr, Ed25519, BLS)Discrete log on elliptic curvesVulnerable to ShorAttacker could derive private keys from exposed public keys and forge spends.Consensus keys (e.g., BLS for validator aggregation)BLS over pairing-friendly curvesVulnerable to ShorWould require protocol-level migration; aggregation benefits complicate alternatives.PoW hashing (SHA-256) and Merkle treesHash functionsResists; Grover reduces marginParameter increases or double hashing mitigate; no known catastrophic break.zk-SNARKs on pairings (Groth16/Plonk variants)Elliptic curves + pairingsVulnerable to ShorUnderlying group assumptions break; PQ alternatives include STARKs.zk-STARKsHash-based with FRI protocolsRelatively resilientSecurity rests on hash assumptions; adjust parameters for Grover.Address hashing (BTC P2PKH, ETH addresses)Hash + encodingResists; Grover reduces marginAddresses that hide public keys buy time until spend/signature exposure. On the defense side, several PQ signature families show promise: Lattice-based (e.g., CRYSTALS-Dilithium, Falcon) offer performance close to today’s systems, with larger keys/signatures. Hash-based (e.g., SPHINCS+) avoid number-theoretic assumptions, but signatures are larger and verification is heavier. Code-based and multivariate schemes exist, but most blockchain discussions center on lattice and hash-based options due to tooling and standardization momentum. The U.S. National Institute of Standards and Technology (NIST) has selected CRYSTALS-Kyber (key encapsulation) and three digital signatures—CRYSTALS-Dilithium, Falcon, and SPHINCS+—for standardization, with draft Federal Information Processing Standards circulating in 2024. See the program page for status updates at NIST PQC . State of Major Networks: Bitcoin, Ethereum, Solana and Beyond Bitcoin Most Bitcoin outputs (P2PKH/P2WPKH) commit to a hash of the public key. Your public key is only revealed when you spend, limiting pre-spend exposure. However, Taproot (P2TR) places an x-only public key directly in the output, which could be attractive to a quantum-capable attacker if such machines existed. In practice, no cryptographically relevant, fault-tolerant quantum computer exists today that can execute Shor at required scales—but the design detail matters for future planning. The Bitcoin Script system is flexible enough to add new opcodes or tapscript paths for PQ signatures, and to support hybrid conditions (e.g., spendable with ECDSA now or with a PQ signature later). That said, consensus changes are conservative and take time. There is no widely adopted BIP that enshrines a standard PQ signature yet; discussions remain active in research forums. Ethereum Externally Owned Accounts sign transactions with ECDSA; the public key can be recovered from transaction signatures, so any used account effectively exposes its public key. Ethereum’s beacon chain uses BLS signatures for validator aggregation, which are also based on discrete logarithms. The good news: Ethereum’s programmability enables crypto agility. Account abstraction (e.g., ERC-4337-style smart contract wallets) allows alternative verification logic, so chains and wallets can adopt PQ or hybrid signatures without an immediate hard fork. Replacing BLS at the consensus layer is a larger research and engineering task because aggregation and performance are integral to validator operations. Solana and other high-throughput L1s Solana addresses are Ed25519 public keys, which would be directly vulnerable to a sufficiently powerful quantum adversary. Migrating to PQ signatures at Solana’s throughput and latency targets raises engineering questions about signature sizes and verification costs, but the runtime allows for new verification programs and staged migrations. Across the Cosmos, Polkadot, and other ecosystems, most default signature schemes are Schnorr/EdDSA variants over elliptic curves and share similar exposure to Shor’s algorithm. The specific migration levers depend on governance and upgrade mechanisms of each chain. Layer 2 and proofs Rollups that use zk-SNARKs on pairing-friendly curves inherit discrete log assumptions and would need PQ alternatives in the long run. STARK-based systems rest primarily on hash assumptions and are comparatively better positioned with parameter tuning. Nonetheless, L2 accounts and bridges often rely on ECDSA/EdDSA at the edges, so full-stack planning is needed. Regulatory posture signals urgency without alarm: U.S. guidance such as NSA’s Commercial National Security Algorithm Suite 2.0 (CNSA 2.0) outlines a phased PQ migration for government systems into the 2030s, emphasizing early inventory and crypto agility. See the NSA notice for context at NSA CNSA 2.0 . Migration Playbooks: From Crypto-Agile Wallets to L1 Upgrades Hybrid signatures and algorithm agility Wallet-level hybrids: Require both a classical signature (ECDSA/Schnorr) and a PQ signature to spend, or allow either path under policy. This enables gradual rollout while preserving compatibility. Scriptable commits: For UTXO chains, commit to a PQ public key’s hash today (cheap) and reveal PQ verification only when needed. Smart contract wallets: In account-based chains, customizable validation logic can accept PQ signatures as soon as precompiles or libraries exist. L1 consensus and protocol changes New address types or opcodes: Introduce PQ-verify operations and new address encodings. Expect extensive review because signature sizes and verify costs affect fees and block limits. Consensus key migration: For chains using BLS, research targets include PQ signatures with aggregation or alternative consensus designs that reduce signature load. Bridges and cross-chain: Many bridges rely on threshold signatures or multisig over elliptic curves. Plans should evaluate PQ-ready quorum schemes or hybrid attestations. Key management, hardware, and custody Inventory your cryptography: Map where ECDSA/EdDSA/BLS are used across wallets, custodial flows, validator tooling, and off-chain services. Hardware wallet roadmaps: Ask vendors about implementing Dilithium/Falcon/SPHINCS+ and how firmware upgrades will be authenticated as the trust anchor transitions to PQ. Rotation and sweeping: Prepare to rotate keys and sweep funds from addresses that expose public keys (including Taproot and any reused accounts) to PQ or hybrid outputs before any credible Q‑day. Cost, Performance, and UX Trade-offs of Post-Quantum Signatures Post-quantum signatures are larger and often heavier to verify than today’s ECDSA/Ed25519 or BLS. That reality affects chain limits, fees, and user experience. Footprint: Typical PQ signature sizes range from roughly a few hundred bytes up to tens of kilobytes depending on the scheme and security level. Public keys can also be larger. Larger payloads increase bandwidth and storage needs. Verification cost: Lattice-based verification is generally fast but still costlier than Ed25519 per signature. Hash-based signatures (e.g., SPHINCS+) can be slower and bigger, trading performance for conservative assumptions. Aggregation: BLS’s compact aggregation is a major win in current consensus designs. PQ aggregation is an active research area; today’s PQ schemes don’t yet match BLS’s combination of compactness and speed. Stateless and one-time signatures: Some hash-based options (e.g., XMSS/WOTS variants) require careful state handling or produce large signatures. They may suit niche uses (e.g., infrequent rotations) rather than high-throughput wallets. Given these trade-offs, many teams pursue hybrid strategies: add PQ validation where the cost is acceptable (e.g., treasury moves, validator keys) while keeping classical paths for mass retail usage until better PQ tooling matures. A Practical Checklist for Teams and Treasuries For protocol and wallet developers Map dependencies: List every place signatures are used—wallets, consensus, bridges, admin keys, CI/CD signing, binary updates. Minimize public key exposure: Avoid address reuse; prefer address types that don’t reveal public keys until spend where possible. Add crypto agility: Design interfaces so signature algorithms can be swapped without rewriting apps. Consider hybrid verification in scripts or smart contracts. Run PQ pilots: Experiment with Dilithium/Falcon/SPHINCS+ in devnets. Measure size, verification cost, and UX impact. Engage standards early: Track NIST PQC, IETF CFRG drafts, and ecosystem proposals. Align encodings and parameter choices with emerging norms to avoid costly rewrites later. See IETF CFRG . Have a sweep plan: Create playbooks to move funds from exposed public keys to PQ/hybrid outputs on short notice. Test fees, batching, and operational throughput. Vendor diligence: Ask HSM, hardware wallet, and custody providers for PQ timelines, firmware auth plans, and migration tooling. For institutions and treasuries Assess key exposure today: Identify assets held at addresses that reveal public keys (e.g., Taproot, Solana accounts, used Ethereum EOAs) and prioritize rotation sequencing. Choose crypto-agile custody: Require contracts that include PQ roadmaps and service-level objectives for migration readiness. Diversify controls: Prefer multisig or smart contract wallets that can add PQ paths, rate limits, and time locks to slow down potential key-forgery attacks. Incident drills: Simulate a sudden step-change in estimated quantum risk. Can you rotate thousands of keys in days? Who signs off? What’s the communications plan? Monitor policy signals: NSA CNSA 2.0 and NIST guidance won’t dictate blockchain timelines, but they provide credible migration pacing for critical systems. Risk reminder: The dominant threats today are still classical—phishing, malware, key mismanagement, smart-contract bugs, and bridge exploits. Preparing for quantum should not distract from basic operational security. Myths, Edge Cases, and Open Questions “Quantum will kill Bitcoin overnight.” Not likely. Even if a credible quantum threat emerges, networks can soft-fork in PQ options and coordinate sweeping to safer outputs. The harder challenge is logistics at scale, not a lack of cryptographic candidates. “Proof-of-Work collapses under quantum.” Grover’s algorithm offers only a quadratic speedup for hashing. Practical quantum hardware capable of challenging global hash rates appears far off, and parameter tweaks (e.g., difficulty, hash output length) help maintain margins. “Address hashes make me safe forever.” Address hashing helps until you spend and reveal a signature or public key. If funds sit behind a public key (e.g., Taproot, many account-based chains), exposure is immediate in a post-Shor world. “We can just switch to PQ in a week.” Real migrations touch wallets, nodes, fee markets, hardware, and user education. Expect multi-year, staged rollouts—hence the value of crypto agility now. zk-proof ecosystems. SNARKs built on elliptic curves face the same Shor risk as signatures, while STARKs lean on hash assumptions and look more robust. Either way, account keys and bridges may still rely on classical signatures until upgraded. Aggregation gap. Today’s PQ signatures don’t replicate BLS’s elegant aggregation properties. Research into PQ-friendly aggregation or alternative consensus accounting remains ongoing. For authoritative guidance and status updates on standardization, track NIST’s PQC project at csrc.nist.gov and draft FIPS for Kyber, Dilithium, and SPHINCS+ (circulating in 2024). Ethereum developer resources on account design are collected at ethereum.org , and Bitcoin’s transaction formats are documented at bitcoin.org . If you’d like ongoing coverage of the post-quantum journey across chains, Crypto Daily follows standards, protocol roadmaps, and vendor announcements—visit Crypto Daily for the latest analysis. Frequently Asked Questions How soon could quantum computers threaten blockchain signatures? No one can give a precise date. Public assessments suggest fault-tolerant, cryptographically relevant machines are not imminent, but standards bodies encourage early migration planning because swapping foundational cryptography takes years. Treat this as a long-tail, high-impact risk: plan now, execute in phases. Are my Bitcoin holdings safe if I never reused addresses? Using address types that hide your public key until spend reduces exposure. However, funds behind outputs that directly reveal a public key (e.g., Taproot) would be at risk in a post-Shor world. Regardless, developing a plan to sweep into PQ or hybrid outputs before any credible quantum threat is prudent. Does Ethereum expose my public key? For EOAs, a transaction’s signature allows recovery of the public key, so any used account effectively exposes it. Account abstraction and smart contract wallets can help by supporting alternate or hybrid verification paths over time. Will Grover’s algorithm break SHA-256 mining? No. Grover offers a quadratic speedup, not an exponential break. While it narrows security margins, parameter adjustments and the immense practical challenges of building such hardware make a near-term disruption to PoW unlikely. Which post-quantum signatures look most practical for blockchains? Lattice-based schemes such as Dilithium and Falcon are front-runners due to performance, with SPHINCS+ valued for conservative assumptions. Exact choices depend on chain limits, desired signature sizes, verification costs, and whether aggregation is needed. What should teams do first to prepare? Inventory where signatures are used, minimize public key exposure, build crypto agility into wallets and contracts, and test PQ schemes on devnets. Coordinate with custody and hardware providers on their migration roadmaps. Is this financial advice? No. This article is educational. Crypto assets are volatile and involve security, technical, and regulatory risks. Always do independent research and consider professional guidance for treasury decisions. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
22 May 2026, 11:05
From New York to Mumbai: What 10,000 Bitcoin Buys Today Around the World

BitcoinWorld From New York to Mumbai: What 10,000 Bitcoin Buys Today Around the World May 22, 2026 – On May 22, 2010, a programmer named Laszlo Hanyecz made history by spending 10,000 Bitcoin on two pizzas. At the time, the transaction was worth around $41. Today, depending on Bitcoin’s market price, those same coins would be worth well over $700 million and at certain points in 2025 exceeded $1 billion in value. But sixteen years later, Bitcoin Pizza Day has evolved far beyond a famous crypto anecdote. It has become a global symbol of how quickly internet native communities can transform technology from niche experimentation into mainstream participation. And nowhere is that growth more visible than in the scale of global crypto adoption today. According to Chainalysis’ 2025 Global Crypto Adoption Index, India now ranks among the world’s leading crypto adoption markets, driven by a mix of retail participation, creator ecosystems, remittances, payments, and investment activity. Meanwhile, stablecoins processed an estimated $28 trillion in real economic volume globally in 2025, demonstrating how digital assets are increasingly being used beyond trading and speculation. To mark Bitcoin Pizza Day 2026, Binance analyzed what the original 10,000 BTC pizza purchase could buy today across some of the world’s most iconic cities. The result highlights not only Bitcoin’s extraordinary growth, but also crypto’s increasingly global cultural footprint. Mumbai 10,000 BTC today could buy: tens of millions of cups of chai thousands of years of local commuter rail tickets major commercial real estate space in the city’s business districts Dubai 10,000 BTC today could buy: more than 12 million shawarmas hundreds of luxury desert safari experiences dozens of ultra-luxury Palm Jumeirah villas New York 10,000 BTC today could buy: approximately 22 million slices of New York pizza over 3,000 Manhattan studio apartments enough subway rides to circle the city for generations London 10,000 BTC today could buy: over 8 million pints at London pubs several Premier League hospitality boxes for every match of the season entire rows of townhouses in some boroughs Tokyo 10,000 BTC today could buy: millions of sushi plates thousands of high-speed rail journeys across Japan entire floors in some central Tokyo apartment buildings While the comparisons are playful, the broader story is serious. Bitcoin Pizza Day represents one of the earliest examples of digital assets entering the real economy. What began as an experimental online transaction has since evolved into a global financial and cultural movement powered by communities, creators, developers, entrepreneurs, and everyday users. Today, crypto adoption increasingly spans both developed and emerging markets. In many regions, particularly across Africa, Asia, and Latin America, growth has been driven not by institutions first, but by communities educating communities. The world’s most famous pizza purchase may have started with two pizzas in Florida, but sixteen years later, it reflects something much bigger: the globalization of internet native finance. About Binance : Binance is a leading global blockchain ecosystem behind the world’s largest cryptocurrency exchange by trading volume and registered users. Binance is trusted by more than 310 million people in 100+ countries for its industry-leading security, transparency, trading engine speed, protections for investors, and unmatched portfolio of digital asset products and offerings from trading and finance to education, research, social good, payments, institutional services, and Web3 features. Binance is devoted to building an inclusive crypto ecosystem to increase the freedom of money and financial access for people around the world with crypto as the fundamental means. For more information, visit: https://www.binance.com For all media queries, please contact: [email protected] This post From New York to Mumbai: What 10,000 Bitcoin Buys Today Around the World first appeared on BitcoinWorld .
22 May 2026, 11:03
Ethereum falls to $2,100 as key supporters exit

🚨 Key figures from Bankless have sold all their $ETH. ETH price dropped to $2,100, down 55% from last year’s peak. Continue Reading: Ethereum falls to $2,100 as key supporters exit The post Ethereum falls to $2,100 as key supporters exit appeared first on COINTURK NEWS .
















































