Binance co-founder Changpeng Zhao, widely known as CZ, has pushed back against growing concern that artificial intelligence-assisted hacking poses an outsized danger to crypto networks, argui
Binance co-founder Changpeng Zhao, widely known as CZ, has pushed back against growing concern that artificial intelligence-assisted hacking poses an outsized danger to crypto networks, arguing that the fears are overblown given that the internet and traditional banking operate on cryptographic foundations that are comparatively weaker than those underpinning most modern blockchains.
CZ's Case That AI Crypto Hacking Fears Are Overblown
What CZ is arguing
CZ's core position is that the threat model applied to crypto is inconsistently strict. He has argued that the broader digital economy, including the HTTP and TLS infrastructure of the public internet and the legacy encryption standards used in retail and interbank settlement systems, relies on security assumptions that are no more robust, and in many cases weaker, than the elliptic curve cryptography and hash functions that secure Bitcoin and comparable proof-of-work and proof-of-stake networks. For related coverage, see Best Crypto Casinos for Halloween 2026: Live Events, Spooky Slots, and Real Bonuses.
The argument follows a comparative logic: if AI-assisted adversaries were capable of breaking the cryptographic primitives protecting crypto wallets and on-chain transactions, those same capabilities would compromise online banking, payment card networks, and the authentication layers that protect e-commerce infrastructure first, since those systems carry larger aggregate value and have historically received less adversarial scrutiny from the research community. For related coverage, see Crypto.com, Novig Sue Missouri Over Sports Betting Rules.
What the statement does not prove
CZ's framing is a rebuttal to perception, not a technical audit. Pointing out that legacy banking infrastructure carries comparable or greater theoretical exposure does not mean crypto is immune to AI-augmented threats; it means the threat is not uniquely concentrated in crypto. The distinction matters for how users and protocols should calibrate their own risk assessment. For related coverage, see Bitcoin Could Find $30K Support Even Without ETFs, Says Ki Young Ju.
The claim also does not address application-layer vulnerabilities specific to DeFi: smart contract exploits, oracle manipulation, and governance attacks are not defeated by strong on-chain cryptography. As the Chainalysis-tracked Drift exploiter case illustrates, fund movement and protocol exploitation regularly involve social engineering, key mismanagement, or contract logic errors rather than breaking elliptic curve cryptography directly. For related coverage, see BULK Trade Review 2026: Wallet Connection, Trading Experience, and AURA Farming Strategy.
Why CZ Compares Crypto With Internet and Banking Security
The security comparison behind the claim
The comparison CZ draws is grounded in the structure of public-key cryptography. Bitcoin's secp256k1 curve and SHA-256 hashing, Ethereum's keccak-256 implementation, and the consensus-layer signature schemes used by major proof-of-stake validators are all built on mathematical problems, elliptic curve discrete logarithm and preimage resistance, that are not meaningfully easier for current or near-term AI systems to break than the RSA-2048 and AES-128 standards underpinning most internet and banking authentication flows.
Where CZ's comparison has the most traction is in quantum threat discourse. The NIST post-quantum standardization process, finalized in 2024, targets the same cryptographic primitives used across both crypto and conventional finance. If a sufficiently powerful quantum computer eventually threatened secp256k1, it would simultaneously threaten the TLS handshakes that protect every HTTPS banking session. CZ's point is that the framing of crypto as uniquely fragile misrepresents the shared nature of the underlying risk.
Why a comparison is not a guarantee of safety
The "banking uses the same thing" argument works as a relative statement but not as an absolute assurance. Traditional finance benefits from reversibility, regulatory backstops, and fraud recovery infrastructure that on-chain settlement does not provide. A successful attack on a crypto private key results in an irreversible loss; the same class of cryptographic failure in a banking context typically triggers fraud detection layers and potential chargebacks. The attack surface comparison is valid; the consequence comparison is not symmetric.
Protocol-level security also diverges sharply from key-custody security. The Bitcoin network's hash rate and Ethereum's validator set represent robust consensus-layer defenses, but the majority of theft from crypto users occurs at the custody layer: phishing attacks, compromised seed phrases, malicious browser extensions, and exchange-level breaches. AI tools have already lowered the cost of producing highly convincing phishing content and deepfake social engineering, which is a real and demonstrable increase in attack surface that does not require breaking any cryptographic primitive.
What the Debate Means for Crypto Security Expectations
TLDR KEYPOINTS
- CZ argues AI-driven crypto hacking fears are disproportionate because internet and banking infrastructure runs on comparable or weaker cryptographic foundations.
- The comparison is valid at the protocol cryptography layer but does not extend to application-layer risks specific to DeFi, such as smart contract exploits and custody failures.
- AI's near-term threat to crypto is concentrated in social engineering and phishing, not in breaking elliptic curve or hash primitives, which remain computationally infeasible to attack with current hardware.
Risk perception versus demonstrated incidents
The majority of documented large-scale crypto losses attributed to sophisticated attackers have involved compromised private keys, insider access, or smart contract logic errors rather than any form of cryptographic brute force. AI capabilities available today meaningfully accelerate the social engineering component of these attacks, producing more convincing spear-phishing emails and fake support interactions, but they do not change the underlying mathematical security of on-chain transaction signing.
This distinction is operationally important for DeFi protocols managing concentrated liquidity positions, governance multisigs, and protocol-owned treasury allocations. The threat model for a Gnosis Safe multisig holding protocol reserves is primarily about signer key hygiene and governance process integrity, not about the elliptic curve math that protects the signatures themselves. CZ's framing is correct at one layer of the stack and less relevant at the layers where most DeFi losses actually occur.
What readers should watch next
The more consequential near-term development in AI and crypto security is not a cryptographic break but the acceleration of autonomous attack tooling: AI agents that can identify and probe vulnerable smart contract deployments at scale, or that can automate the social engineering steps needed to compromise a protocol's governance or operational security. These vectors do not require defeating SHA-256; they require only that human operators remain in the loop of key management and governance decisions, which is precisely where DeFi protocols remain most exposed.
For users assessing portfolio exposure, the relevant question is not whether AI can crack Bitcoin's cryptography, which is not a credible near-term threat, but whether the protocols and custodians holding their assets have hardened their operational security against the phishing, impersonation, and automated vulnerability scanning that AI tooling has made significantly cheaper and faster to execute.
Additional source references: source document 1, source document 2.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
Read original article on defiliban.io