Загрузка видео...

Не удалось загрузить видео

На главную

How the Binance hack worked: The attacker exploited EIP-7702 - an Ethereum Pectra upgrade That lets a regular wallet temporarily act as a smart contract with a valid private key signature. Hacker pre-collected 50 EIP-7702 authorizations with sequential nonces Not knowing the exact nonce at attack time. Sent them...

philarekt's profile picture

philarekt

23,378 subscribers

383,619 просмотров • 9 дней назад •via X (Twitter)

Наука и технологииФинансы
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

🚨 MASSIVE: DNA Protocol ZKGuard shows how the $6,300,000,000 Binance hack could have been stopped, with proof before movement on the $XRP Ledger. On October 29, the largest theft in crypto history: → ~$6,300,000,000 drained from Binance hot wallets across ~10 blockchains, most of it in about 20 minutes → Binance says no private key leaked. Its own withdrawal infrastructure signed the transfers → Blockaid traced the entry point to one successful Ethereum EIP-7702 authorization that redirected the Binance 14 hot wallet to a malicious contract → Chainalysis attributes the attack to North Korea's TraderTraitor group No key leaked. Control did. Whatever got signed, moved. One day later, DNA Protocol published ZKGuard: Proof Before Movement, an authorization architecture for exchanges and institutions designed to close exactly this gap. How ZKGuard's design answers each failure: → Preparing is not authorizing. Operations can build a transaction, but signatures are released only after a zero-knowledge proof shows the institution's policy is satisfied for that exact transaction → Approved destinations only. The proof must show the destination is in the institution's approved set. A fresh attacker address fails → Approved transaction types only. Handing a wallet's control to an outside contract is an authority change, and authority changes need their own governance approvals → Independent approvers on separate devices and credentials, each bound to that one request → Hard spending limits. Per-transfer ceilings and one shared daily allowance across every spending path → Every authorization expires and can be used once. No open-ended access → Settlement on the XRP Ledger, where native multi-signing requires a weighted quorum of independent keys Privacy stays intact. Approver lists, counterparties and internal rules stay private. Only the proof gets verified. $6,300,000,000 left because a signature was trusted without proof. ZKGuard flips the order: no proof, no signature, no movement. Part of DNA Protocol's zkPrivacy infrastructure on the XRP Ledger, all powered by $XDNA (
0:15

🚨 MASSIVE: DNA Protocol ZKGuard shows how the $6,300,000,000 Binance hack could have been stopped, with proof before movement on the $XRP Ledger. On October 29, the largest theft in crypto history: → ~$6,300,000,000 drained from Binance hot wallets across ~10 blockchains, most of it in about 20 minutes → Binance says no private key leaked. Its own withdrawal infrastructure signed the transfers → Blockaid traced the entry point to one successful Ethereum EIP-7702 authorization that redirected the Binance 14 hot wallet to a malicious contract → Chainalysis attributes the attack to North Korea's TraderTraitor group No key leaked. Control did. Whatever got signed, moved. One day later, DNA Protocol published ZKGuard: Proof Before Movement, an authorization architecture for exchanges and institutions designed to close exactly this gap. How ZKGuard's design answers each failure: → Preparing is not authorizing. Operations can build a transaction, but signatures are released only after a zero-knowledge proof shows the institution's policy is satisfied for that exact transaction → Approved destinations only. The proof must show the destination is in the institution's approved set. A fresh attacker address fails → Approved transaction types only. Handing a wallet's control to an outside contract is an authority change, and authority changes need their own governance approvals → Independent approvers on separate devices and credentials, each bound to that one request → Hard spending limits. Per-transfer ceilings and one shared daily allowance across every spending path → Every authorization expires and can be used once. No open-ended access → Settlement on the XRP Ledger, where native multi-signing requires a weighted quorum of independent keys Privacy stays intact. Approver lists, counterparties and internal rules stay private. Only the proof gets verified. $6,300,000,000 left because a signature was trusted without proof. ZKGuard flips the order: no proof, no signature, no movement. Part of DNA Protocol's zkPrivacy infrastructure on the XRP Ledger, all powered by $XDNA (

RippleXity

10,525 просмотров • 7 дней назад

🚨BREAKING: BINANCE HOT WALLET APPEARS TO BE DRAINED FOR ~$2.53B! On-chain data shows a large outflow from a Binance hot wallet (Binance 14) involving roughly $2.53 billion across 60+ tokens on Ethereum, including a major ETH transfer. The transaction that moved the funds was initiated by an address funded via Tornado Cash, with the assets sent to a fresh EOA. The report remains unconfirmed.
0:19

🚨BREAKING: BINANCE HOT WALLET APPEARS TO BE DRAINED FOR ~$2.53B! On-chain data shows a large outflow from a Binance hot wallet (Binance 14) involving roughly $2.53 billion across 60+ tokens on Ethereum, including a major ETH transfer. The transaction that moved the funds was initiated by an address funded via Tornado Cash, with the assets sent to a fresh EOA. The report remains unconfirmed.

Crypto Banter

511,992 просмотров • 9 дней назад

Today's #BinanceBuild highlights 3 key features of the refreshed Binance Wallet (formerly Binance Web3 Wallet), designed with simplicity at its core: 🔸 All-in-one dashboard 🔸 Cross-chain adaptability 🔸 View mode toggles Check them out 👉
0:19

Today's #BinanceBuild highlights 3 key features of the refreshed Binance Wallet (formerly Binance Web3 Wallet), designed with simplicity at its core: 🔸 All-in-one dashboard 🔸 Cross-chain adaptability 🔸 View mode toggles Check them out 👉

Binance

124,819 просмотров • 1 год назад

Uniswap smart wallet is live!! This is a huge unlock for wallet UX and one of the most sneakily complex projects I’ve ever worked on. Quick 🧵 on a few of the design principles behind our 7702 wallet implementation:
0:14

Uniswap smart wallet is live!! This is a huge unlock for wallet UX and one of the most sneakily complex projects I’ve ever worked on. Quick 🧵 on a few of the design principles behind our 7702 wallet implementation:

zack

17,400 просмотров • 1 год назад

Polkadot token on Hyperbridge exploited as attacker mints 1B A bridged version of Polkadot $DOT on Ethereum has been hit by an exploit. Blockchain security firm PeckShield flagged that the attacker minted 1 billion tokens unexpectedly. Per reports, the entire supply was dumped in a single transaction shortly after. The attacker walked away with 108.2 $ETH, worth around $237,000. The exploit targeted the Hyperbridge gateway contract, according to CertiK. The attacker used a forged message to gain unauthorized control. This allowed them to manipulate the admin role of a Polkadot token contract on Ethereum.
0:15

Polkadot token on Hyperbridge exploited as attacker mints 1B A bridged version of Polkadot $DOT on Ethereum has been hit by an exploit. Blockchain security firm PeckShield flagged that the attacker minted 1 billion tokens unexpectedly. Per reports, the entire supply was dumped in a single transaction shortly after. The attacker walked away with 108.2 $ETH, worth around $237,000. The exploit targeted the Hyperbridge gateway contract, according to CertiK. The attacker used a forged message to gain unauthorized control. This allowed them to manipulate the admin role of a Polkadot token contract on Ethereum.

BSCN

15,017 просмотров • 6 месяцев назад

Announcing AERSeal. Your smart contract is controlled by one private key. One point of failure. AERSeal replaces it with a threshold signature that was never whole to begin with. Find out more through the link below ⬇️
0:12

Announcing AERSeal. Your smart contract is controlled by one private key. One point of failure. AERSeal replaces it with a threshold signature that was never whole to begin with. Find out more through the link below ⬇️

AEREDIUM

598,466 просмотров • 2 месяцев назад

Ethereum And BNB Chain Face $575M Security Hit Across Thousands Of Addresses A USENIX Security ’26 study identified 65,340 high-risk crypto addresses linked to more than $574.8 million in estimated losses. Researchers traced activity across Ethereum and BNB Chain. The study identified 126,982.94 ethereum:native and 17,726.7 binancecoin:native tied to the addresses. Researchers also identified attack methods involving contract accounts and EIP-7702. The study reported a detection accuracy of 99.11%.
0:15

Ethereum And BNB Chain Face $575M Security Hit Across Thousands Of Addresses A USENIX Security ’26 study identified 65,340 high-risk crypto addresses linked to more than $574.8 million in estimated losses. Researchers traced activity across Ethereum and BNB Chain. The study identified 126,982.94 ethereum:native and 17,726.7 binancecoin:native tied to the addresses. Researchers also identified attack methods involving contract accounts and EIP-7702. The study reported a detection accuracy of 99.11%.

BSCN

30,434 просмотров • 2 месяцев назад

Set the standard with Cristiano Ronaldo and learn his signature moves on the pitch. Unlock your potential with a ForeverSkills digital collectible only on Binance.
0:17

Set the standard with Cristiano Ronaldo and learn his signature moves on the pitch. Unlock your potential with a ForeverSkills digital collectible only on Binance.

Binance

17,152,919 просмотров • 1 год назад

A look at the rarest of them all. Forever CR7: The Goat NFT collection. Dropping tomorrow, exclusively on #Binance.
0:13

A look at the rarest of them all. Forever CR7: The Goat NFT collection. Dropping tomorrow, exclusively on #Binance.

Binance

307,451 просмотров • 3 лет назад

I made a visualization of EIP-8288 aka "recursive mempool aggregation," my new favorite EIP of all time because it perfectly encapsulates the thesis of the "cryptographic world computer" -- a system whose scalability *increases*, not decreases, with the level of decentralization. In a previous tweet I explained how EIP-8288 achieved this seemingly impossible feat, but one gif is worth a thousand words. Essentially, EIP-8288 leverages Ethereum's decentralized mempool as a parallel ZK proving cluster. Clients send signatures and proofs to the mempool, which over multiple rounds progressively aggregate them into fewer and fewer proofs, until the block builder finally aggregates them into one SINGLE proof. This design accomplishes five things at once: - The more nodes we add to the decentralized mempool, the more signatures/proofs Ethereum can process as a whole. This is obvious if you look at the animation and imagine more nodes in the mempool ring, which would "fan out" to more signatures/proofs. - By aggregating over multiple rounds (aka "recursive aggregation"), the bandwidth consumed by proofs remains constant for each node even as the network processes more proofs. As a result, the network stays decentralized even as capacity increases. - By aggregating proofs before one final aggregation by the builder, as opposed to requiring the builder to aggregate everything, the network can process more proofs without increasing hardware requirements for the builder. - By aggregating everything to a single block-level proof, validators can verify thousands of signatures/proofs by checking just one aggregated proof. Hardware requirements for validators can therefore stay low, keeping the network decentralized. - By aggregating not just native signatures but also STARKs, Ethereum can support any signature scheme by wrapping them in STARKs. So once again, this is how Ethereum will: - scale to process tens of thousands of PQ and private transactions per second - charge a tiny amount of gas to validate each txn, even though the original signature/proof may be huge (up to hundreds of KBs in size) - all while decentralizing even MORE. You are not bullish enough.
0:13

I made a visualization of EIP-8288 aka "recursive mempool aggregation," my new favorite EIP of all time because it perfectly encapsulates the thesis of the "cryptographic world computer" -- a system whose scalability *increases*, not decreases, with the level of decentralization. In a previous tweet I explained how EIP-8288 achieved this seemingly impossible feat, but one gif is worth a thousand words. Essentially, EIP-8288 leverages Ethereum's decentralized mempool as a parallel ZK proving cluster. Clients send signatures and proofs to the mempool, which over multiple rounds progressively aggregate them into fewer and fewer proofs, until the block builder finally aggregates them into one SINGLE proof. This design accomplishes five things at once: - The more nodes we add to the decentralized mempool, the more signatures/proofs Ethereum can process as a whole. This is obvious if you look at the animation and imagine more nodes in the mempool ring, which would "fan out" to more signatures/proofs. - By aggregating over multiple rounds (aka "recursive aggregation"), the bandwidth consumed by proofs remains constant for each node even as the network processes more proofs. As a result, the network stays decentralized even as capacity increases. - By aggregating proofs before one final aggregation by the builder, as opposed to requiring the builder to aggregate everything, the network can process more proofs without increasing hardware requirements for the builder. - By aggregating everything to a single block-level proof, validators can verify thousands of signatures/proofs by checking just one aggregated proof. Hardware requirements for validators can therefore stay low, keeping the network decentralized. - By aggregating not just native signatures but also STARKs, Ethereum can support any signature scheme by wrapping them in STARKs. So once again, this is how Ethereum will: - scale to process tens of thousands of PQ and private transactions per second - charge a tiny amount of gas to validate each txn, even though the original signature/proof may be huge (up to hundreds of KBs in size) - all while decentralizing even MORE. You are not bullish enough.

Derek Chiang | Ethlabs

19,414 просмотров • 19 дней назад

🚨BINANCE HACKER ACCIDENTALLY SENDS ~$3.5M IN TOKENS TO NEWT CONTRACT ADDRESS, FUNDS NOW STUCK! Binance hacker sent roughly $3.32-3.5 million worth of tokens, including about 8 million $NEWT plus other altcoins, directly to the NEWT token contract address by mistake, per Lookonchain. $NEWT is the native token of Newton Protocol, an on-chain automation project. The Newton Foundation confirmed the contract itself was not compromised. Because it is immutable, has no admin keys, and cannot be upgraded, no one can recover tokens sent to the contract address. The funds are permanently locked.
0:11

🚨BINANCE HACKER ACCIDENTALLY SENDS ~$3.5M IN TOKENS TO NEWT CONTRACT ADDRESS, FUNDS NOW STUCK! Binance hacker sent roughly $3.32-3.5 million worth of tokens, including about 8 million $NEWT plus other altcoins, directly to the NEWT token contract address by mistake, per Lookonchain. $NEWT is the native token of Newton Protocol, an on-chain automation project. The Newton Foundation confirmed the contract itself was not compromised. Because it is immutable, has no admin keys, and cannot be upgraded, no one can recover tokens sent to the contract address. The funds are permanently locked.

Crypto Banter

71,160 просмотров • 9 дней назад

Next on Darwin: your agent's wallet is its API key. Today an agent needs a Darwin key, and that key works for anyone holding a copy. If it leaks into a log, a repo or a shared config, someone else spends your credit. We're replacing it with the wallet the agent already has. The agent signs each request with its Solana keypair, and Darwin checks the signature before it runs anything. A signature covers one request and expires in seconds, so a copied one is useless. The private key never leaves the wallet. Credit comes from the $darwin that wallet burned, so there's no signup. Burn from the agent's wallet, point the agent at Darwin, and it can run Qwen3 30B on Darwin's GPU, swarms and the MCP server. Keys keep working for anyone who wants one.
0:20

Next on Darwin: your agent's wallet is its API key. Today an agent needs a Darwin key, and that key works for anyone holding a copy. If it leaks into a log, a repo or a shared config, someone else spends your credit. We're replacing it with the wallet the agent already has. The agent signs each request with its Solana keypair, and Darwin checks the signature before it runs anything. A signature covers one request and expires in seconds, so a copied one is useless. The private key never leaves the wallet. Credit comes from the $darwin that wallet burned, so there's no signup. Burn from the agent's wallet, point the agent at Darwin, and it can run Qwen3 30B on Darwin's GPU, swarms and the MCP server. Keys keep working for anyone who wants one.

Darwin

16,977 просмотров • 1 месяц назад

When the hardware wallet shows the EIP-712 digest
0:11

When the hardware wallet shows the EIP-712 digest

Patrick Collins

12,405 просмотров • 10 месяцев назад

Hedera tokens enforce their rules through keys assigned at creation On Ethereum a token is a smart contract, so every rule it enforces is code someone wrote, audited, and deployed. Hedera (hedera-hashgraph:native) makes a token a native ledger entry instead. Its controls are keys set at creation: an admin key that governs the rest, plus supply, freeze, pause, KYC, and wipe. The wipe key lets an issuer remove tokens from a holder's account, a power Hedera's documentation frames as a tool for refunds or correcting allocations. Every key is optional, and one left out at creation can never be added later. A token issued with no keys at all is immutable from day one.
0:14

Hedera tokens enforce their rules through keys assigned at creation On Ethereum a token is a smart contract, so every rule it enforces is code someone wrote, audited, and deployed. Hedera (hedera-hashgraph:native) makes a token a native ledger entry instead. Its controls are keys set at creation: an admin key that governs the rest, plus supply, freeze, pause, KYC, and wipe. The wipe key lets an issuer remove tokens from a holder's account, a power Hedera's documentation frames as a tool for refunds or correcting allocations. Every key is optional, and one left out at creation can never be added later. A token issued with no keys at all is immutable from day one.

BSCN

30,145 просмотров • 2 месяцев назад

I can’t stop thinking about this… before hackers stole $6.4 billion from Binance, they spent days rehearsing the attack in public. The test transactions on Ethereum were worth only a few dollars. Nobody stopped them. Bloomberg reconstructed what happened. Once the code worked, the hackers launched the real attack across multiple blockchains. Then I reached the detail that doesn’t feel real. Some of the compromised wallets kept receiving fresh funds from Binance while the hackers were draining them. The attackers emptied a wallet, Binance refilled it, and they emptied it again. For a period of time, the exchange was effectively feeding new money into its own robbery. Binance co-founder Yi He was at home in Abu Dhabi. She reportedly discovered the breach while scrolling X before bed. Imagine opening Twitter and learning that billions of dollars are disappearing from your own exchange. Within minutes, Binance assembled a 100 person crisis team. The FBI, the U.S. Secret Service and blockchain analysts around the world joined the response. Meanwhile, some employees were reportedly already worried about losing their annual bonuses. But the most disturbing detail came later. According to the investigation, the hackers used valid permissions to execute the transfers. To the blockchain, everything looked authorized. There was no transaction labeled “hack” just legitimate-looking operations moving billions out of wallets the system still trusted. The $6.4 billion heist didn’t begin when billions started moving. It began days earlier with transactions worth a few dollars, too small for anyone to care about. By the time it looked dangerous, the blockchain was still saying: authorized.
0:16

I can’t stop thinking about this… before hackers stole $6.4 billion from Binance, they spent days rehearsing the attack in public. The test transactions on Ethereum were worth only a few dollars. Nobody stopped them. Bloomberg reconstructed what happened. Once the code worked, the hackers launched the real attack across multiple blockchains. Then I reached the detail that doesn’t feel real. Some of the compromised wallets kept receiving fresh funds from Binance while the hackers were draining them. The attackers emptied a wallet, Binance refilled it, and they emptied it again. For a period of time, the exchange was effectively feeding new money into its own robbery. Binance co-founder Yi He was at home in Abu Dhabi. She reportedly discovered the breach while scrolling X before bed. Imagine opening Twitter and learning that billions of dollars are disappearing from your own exchange. Within minutes, Binance assembled a 100 person crisis team. The FBI, the U.S. Secret Service and blockchain analysts around the world joined the response. Meanwhile, some employees were reportedly already worried about losing their annual bonuses. But the most disturbing detail came later. According to the investigation, the hackers used valid permissions to execute the transfers. To the blockchain, everything looked authorized. There was no transaction labeled “hack” just legitimate-looking operations moving billions out of wallets the system still trusted. The $6.4 billion heist didn’t begin when billions started moving. It began days earlier with transactions worth a few dollars, too small for anyone to care about. By the time it looked dangerous, the blockchain was still saying: authorized.

exit

413,227 просмотров • 8 дней назад

🚨 BITGET HACKER CAN BE CAUGHT 🤯 The Bitget hacker reportedly withdrew $1.23 million worth of Ethereum from Binance. Now Binance can potentially help trace the identity of this hacker linked to the Lazarus Group. 👀
0:15

🚨 BITGET HACKER CAN BE CAUGHT 🤯 The Bitget hacker reportedly withdrew $1.23 million worth of Ethereum from Binance. Now Binance can potentially help trace the identity of this hacker linked to the Lazarus Group. 👀

TMA | The Money Ape

110,164 просмотров • 1 месяц назад

BINANCE HACK - FULL BREAKDOWN $5.6B drained from Binance hot wallets across Ethereum, Bitcoin and Tron 67 assets. 63 swept in a single transaction. Attack vector still unknown. Frozen: $2.38B (~42%) $1.56B USDT frozen by Tether $823M USDC frozen by Circle Still moving: ~$2.6B 18,270 BTC ($1.45B) - nobody can freeze this 197K ETH ($451M) - same ~$730M USDT - Tether can still act $234M TRX + smaller tokens Addresses to watch ETH main: 0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c ETH (195K ETH parked): 0x8532fa14acaf483729c449b8458aeddb900543d4 BTC: bc1q0mtc2f5agpkvlq6hhahmfr3hlr55kyfjhl2mnm Tron (frozen): TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi Tron (not frozen): TSUUVjysXV8YqHytSNjfkNXnnB49QDvZpx Context Bybit Feb 2025: $1.5B - this is 3.8x bigger. SAFU fund: ~$1B - hack is 5x that. This is a balance sheet problem, not a SAFU problem. What to watch next Does Tether freeze the remaining $730M USDT? Do BTC and ETH addresses start moving to bridges or mixers? Official Binance statement on how 63 tokens got signed out Does the hacker follow the Bybit playbook through THORChain?
0:16

BINANCE HACK - FULL BREAKDOWN $5.6B drained from Binance hot wallets across Ethereum, Bitcoin and Tron 67 assets. 63 swept in a single transaction. Attack vector still unknown. Frozen: $2.38B (~42%) $1.56B USDT frozen by Tether $823M USDC frozen by Circle Still moving: ~$2.6B 18,270 BTC ($1.45B) - nobody can freeze this 197K ETH ($451M) - same ~$730M USDT - Tether can still act $234M TRX + smaller tokens Addresses to watch ETH main: 0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c ETH (195K ETH parked): 0x8532fa14acaf483729c449b8458aeddb900543d4 BTC: bc1q0mtc2f5agpkvlq6hhahmfr3hlr55kyfjhl2mnm Tron (frozen): TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi Tron (not frozen): TSUUVjysXV8YqHytSNjfkNXnnB49QDvZpx Context Bybit Feb 2025: $1.5B - this is 3.8x bigger. SAFU fund: ~$1B - hack is 5x that. This is a balance sheet problem, not a SAFU problem. What to watch next Does Tether freeze the remaining $730M USDT? Do BTC and ETH addresses start moving to bridges or mixers? Official Binance statement on how 63 tokens got signed out Does the hacker follow the Bybit playbook through THORChain?

ᴛʀᴀᴄᴇʀ

19,780 просмотров • 9 дней назад

With 50 regular season games left at the Dome (and probably no more playoffs there), knowing that this was the last peak Flames moment at the Saddledome is so bittersweet
0:12

With 50 regular season games left at the Dome (and probably no more playoffs there), knowing that this was the last peak Flames moment at the Saddledome is so bittersweet

Yegor Sharangovich replaced Breadman

18,406 просмотров • 7 месяцев назад