Queda acentuada de Binance Coin (BNB)

On July 13, 2026, during WebX, the "Japan RWA, Stablecoin, and BNB Ecosystem Closed-Door Exchange" was held in Tokyo. Organized by ASIAN STAR and co-hosted by Hash Global, with BNB Chain as the blockchain ecosystem partner, the event brought together Japanese traditional financial institutions, listed companies, real asset holders, stablecoin issuers, and Web3 infrastructure teams. Discussions centered on tokenizing real-world assets (RWA), stablecoin settlement, global distribution, and institutionalized on-chain finance. Speakers highlighted Japan's high-quality assets, such as real estate and REITs, and emphasized that RWA success depends on compliance, governance, valuation, and investor protection—not just tokenization. The industry is shifting from defining RWA to achieving scale, where tokenized assets must enable real financial activities like collateralization and lending. BNB Chain was presented as providing global distribution, stablecoin ecosystems, and on-chain liquidity infrastructure. A key synergy framework was proposed: combining Japanese asset quality and compliance with dollar/yen stablecoins and BNB Chain's global network. While Japan's security token market has seen issuance, greater connection to global Web3 liquidity is needed. Panels agreed that liquidity stems from trusted underlying assets, clear regulation, licensed partners, and robust distribution—not from tokenization alone. Compliance enables institutional capital entry. Stablecoins were identified as a crucial settlement layer for connecting Japanese assets to global capital, requiring trust, licensing, and reliable fiat channels. For initial RWA pilots, key elements include licensed partners, compliance tools, custody, investor suitability checks, stablecoin settlement, and real global distribution plans. The event concluded with ASIAN STAR and Hash Global signing a strategic MOU to collaborate on a Japanese real estate fund project within the BNB Chain ecosystem, exploring compliant issuance, on-chain settlement, and liquidity. The discussion marks a step towards building institutional-grade financial infrastructure for Japanese assets in the global Web3 space.

Wanchain's Cardano-BNB Bridge was exploited due to a cryptographic vulnerability in its TreasuryCheck validator, known as non-injective signed-message encoding. This flaw allowed multiple withdrawal requests to generate the same encrypted message, enabling an attacker to reuse a legitimate signature to authorize fraudulent transactions. As a result, approximately 515 million NIGHT tokens, valued at $9 million, were drained from the bridge's treasury. The stolen tokens were subsequently laundered into ADA on the Cardano network. Wanchain has since halted the bridge and confirmed the incident was isolated, not affecting Midnight's network or Cardano's core blockchain. This exploit is part of a series of recent attacks on cross-chain protocols, though overall crypto losses have reportedly declined year-over-year.

BNB Chain has publicly disavowed any connection to the meme coin ASTEROID, alleging it was created by a former employee using unauthorized access. According to the company, while employed, the individual created a wallet address using an official test wallet for a tutorial and launched a test token (TST). After leaving the company, the ex-employee reportedly used the retained seed phrase to generate a new private key and, on August 1, used that same wallet address to deploy the ASTEROID token on the BNB Chain. The token's market cap briefly surged to $10 million within four hours of launch. BNB Chain clarified it did not create, authorize, or promote ASTEROID, and maintains no control over the token or its wallet. The company announced it has initiated legal proceedings against the former employee and is cooperating with relevant authorities on the matter.

BNB Chain has proposed BEP-675, a draft upgrade aimed at increasing network throughput by optimizing the block production process. The core change introduces blind signing, allowing builders to submit pre-executed blocks directly to validators. This is designed to eliminate redundant execution work, potentially reducing a validator's critical path execution time from 125ms to 15ms. Initial testnet results indicate a possible doubling of throughput. Unlike scaling via larger blocks or shorter block times, this proposal focuses on workflow efficiency. It's important to note BEP-675 is currently a draft under the Pasteur hard fork timeline and is not active on the mainnet. If successfully implemented, it would provide BNB Chain with more performance headroom to support its high-activity ecosystem.

BNB Chain has confirmed that the Pasteur hard fork for the BNB Smart Chain (BSC) mainnet will activate at 02:30 UTC on August 25, 2026. Node operators must upgrade to client version 1.7.7 by that time to avoid network disconnection. The hard fork, packaged under the BEP-673 meta-proposal, consolidates three other proposals: BEP-682, BEP-695, and BEP-675. BEP-682 aims to secure cross-chain bridges by fixing a vulnerability where validator signatures in asset transfers could be counted multiple times, allowing a threshold to be met with fewer genuine signatures. The update ensures duplicate signatures are removed before counting. BEP-695 addresses a flaw in staking and governance systems where a validator's old consensus key, after being rotated for maintenance, could retain its administrative privileges. The fix ensures retired keys immediately lose their authority and prevents validators from avoiding slashing through key rotation. BEP-675 aims to increase network throughput. It allows a block proposer to submit a pre-executed block, reducing the time validators spend re-executing transactions. Testnet results showed validator execution time dropped from 125ms to 15ms, and throughput increased by nearly 88% to 2,324 TPS, with average block gas usage rising significantly. Node operators must follow detailed upgrade procedures. Developers using the BEP-675 scheme may need to run a full node instead of a light client, as they are now responsible for creating fully executed blocks.