Four protocol-level changes from the last 48 hours: two mainnet upgrades shipped, one Bitcoin governance test approaching a hard deadline, and one oracle security failure on an L1. NEAR Protocol: On July 10, the NEAR mainnet activated v2.13.0, shipping three distinct infrastructure changes simultaneously. The upgrade added post-quantum signature support using the NIST-finalized ML-DSA-65 algorithm at the validator layer. It also enabled automatic shard splitting, letting the network dynamically redistribute load across shards as congestion builds rather than requiring manual parameter changes through governance. The third change deploys NEP-611, a new gas key system that lets applications sponsor user transaction fees, which removes the requirement for end users to hold NEAR to transact. Stellar: On July 10, Stellar mainnet shipped Protocol 27, named Zipper. The upgrade introduces smart contract credentials and developer identity verification delegation. Credentials allow smart contracts to hold and verify attestations about accounts or addresses directly onchain, making Stellar's contract layer usable for compliance-sensitive workflows without relying on off-chain identity infrastructure. The timing is notable: DTCC selected Stellar as the public-chain layer for its tokenized securities pilot, which is scheduled to begin limited production trades this month. Bitcoin BIP-110: As of July 12, miner signaling for BIP-110 remains below 1% with an early August deadline approaching. BIP-110 would impose a one-year restriction on OP_RETURN outputs and other non-financial data-carrying transaction methods. The proposal uses a user-activated soft fork mechanism requiring 55% miner signaling, significantly below the traditional 95% threshold. Michael Saylor and Adam Back have both publicly opposed the measure. With sub-1% support across the mining pool at the deadline horizon, BIP-110 is tracking toward a small minority fork rather than a network-wide rule change, but the UASF path keeps the outcome formally open until the block-height trigger. Bonzo Lend / Hedera: On or around July 12, Bonzo Lend lost approximately $9.05 million after an attacker exploited a verification flaw in a third-party Supra oracle contract deployed on the Hedera network. The protocol lost 77% of its total value locked. The attack vector was the oracle contract itself, not the lending protocol logic, placing the failure at the price-feed and verification layer rather than in Bonzo's core contract. Hedera is an account-model DLT used primarily for enterprise settlement use cases, and Supra is a third-party oracle provider. The failure adds another data point to the pattern SlowMist identified in its H1 2026 mid-year report: infrastructure and cross-chain systems are absorbing a disproportionate share of losses relative to smart contract code vulnerabilities.