![\"\"](\"https://cdn-images-1.medium.com/max/1024/1*lhnb8_1Fxy8aSsBtAMPZHw.png\")
The NEAR Foundation announced today that the Protocol Work Group will launch testing for Phase 2 of Sharding this week, marking a major milestone in the network’s development roadmap. Phase 2 introduces fundamental upgrades to NEAR’s core protocol architecture, enabling even greater scalability and decentralization for the network. The fourth edition of Stake Wars, an incentivized community testing initiative, will kick off on February 1.
NEAR’s vision of chain abstraction to facilitate broad adoption of decentralized apps requires an extremely scalable blockchain layer. From the start, NEAR has been designed to scale with demand towards mainstream adoption. A primary benefit of the new sharding implementation will be an up-to-10x speed improvement to NEAR’s already-fast transaction throughput. Sharding is NEAR’s unique approach to scaling, which partitions the blockchain into multiple parallel “shards.” Combined with NEAR already having the lowest transaction fees in Web3, this sharding upgrade positions NEAR at the forefront of Web3 in terms of both performance and scalability. Phase 2 greatly improves the network’s capacity for end user volume and is an important landmark on the road to global-scale usage of Web3.
“NEAR continues to make progress on bringing Chain Abstraction infrastructure that can scale to a billion users and beyond,” said Illia Polosukhin, Co-Founder of NEAR Protocol and CEO of NEAR Foundation. “The scalability improvements from stateless validation can unlock even better user experiences for more end-user applications, whether multichain DeFi-style dapps or those aimed at mainstream users.”
Phase 2 introduces the most significant changes to the NEAR Protocol since its Mainnet launch in 2020. The biggest of these is the implementation of stateless validation: an innovative approach to state change, or the process of updating the status of all the data posted to the blockchain. Now, NEAR validators no longer have to maintain the state of a shard locally and can retrieve all the information they need to validate state changes, or “state witness,” from the network.
With stateless validation, NEAR can finally achieve the truest form of sharding, where shards can function mostly independently at the consensus level to improve decentralization and throughput while preserving the highest security guarantees. An added benefit is that the hardware requirements to run most validator nodes are dramatically reduced (a smaller number of “chunk proposer” validators with specialized hardware will validate blocks with state held in memory). This also paves the way for greater decentralization of the network by lowering the barrier to entry to become a validator.
“We’re very excited about the potential for future proofing the NEAR protocol design with stateless validation,” said Bowen Wang, Director of Protocol at Pagoda. “From a research perspective, we expect that as zero-knowledge tech matures, more protocols will adopt a similar approach, where a smaller set of expensive machines execute transactions and produce proofs, while a bigger validator set validates the proofs. This will enable more unified security across networks and defragment Web3, advancing a key aspect of the chain abstraction vision.”
Phase 2 is a shift in direction from the original Nightshade sharding architecture NEAR launched with in 2020, bypassing some fundamental roadblocks in that protocol design around the implementation of challenges in the initial idea of Phase 2, while also unlocking additional benefits. Other network improvements in Phase 2 include in-memory trie, wherein validator nodes can load the entire state into RAM for maximized performance. This will greatly improve transaction throughput thanks to minimizing storage access.
![\"\"](\"https://cdn-images-1.medium.com/max/1024/0*94K7waHE1GRIEFov\")
NEAR users should not experience any downtime with the transition to Phase 2 and no special action is required from validators, apart from adjusting hardware specs. Through dozens of protocol upgrades since Mainnet launch, including three major upgrades, the core NEAR protocol has had 100% uptime with zero disruption for developers and end users.
On Thursday, February 1, Stake Wars IV: Attack of the Transactions will launch to incentivize battle testing of the new sharding architecture. Planned to run through March 31, the latest edition of Stake Wars invites community members to test features and generate traffic. For more information about participating and deeper technical detail about Phase 2, visit the Stake Wars page on GithubWe have become aware of a privacy bug in the -privatebroadcast feature, newly\nintroduced in Bitcoin Core 31.0, that may cause the originator’s IP address to be\nrevealed to the receiving peer under certain network conditions. A fix is\nforthcoming and will be released with 31.1. Users of -privatebroadcast are\nadvised to apply one of the workarounds below until 31.1 is released.
This bug affects users where all the following are true:
\n\n-privatebroadcast is set.sendrawtransaction RPC.\nWallet RPCs (sendtoaddress, sendall, etc.) do not use private\nbroadcast and are not affected.-onlynet\nrestriction excludes them, and no -proxy=... value applies to them.-v2transport=0.When private broadcast selects an IPv4 or IPv6 peer that advertises\nsupport for v2 (BIP324) transport, the initial connection is routed\nthrough the Tor proxy as expected. If the v2 handshake fails on that\nconnection, Bitcoin Core retries it as v1. The v1 retry is not routed\nthrough the Tor proxy and instead connects directly to the peer over\nIPv4 or IPv6, exposing the originator’s IP address to the recipient.
\n\nInitial v1 connections (to peers that do not advertise v2) are\ncorrectly routed through the Tor proxy and are not affected. The\nbug is specific to the v1 reconnection that follows a failed v2\nhandshake. Connections to onion and I2P peers are also unaffected,\nbecause they remain routed through their respective proxies on any v1\nretry and therefore never expose a clearnet IP address.
\n\nThis breaks the privacy guarantee stated in the 31.0 release notes:\n“Their IP address (and thus geolocation) is never known to the recipients”.
\n\nA v2 handshake is unlikely to fail for a peer that actually supports v2\ntransport. The bug is most likely to be triggered by a malicious\npeer deliberately closing the v2 handshake to force a v1 retry.
\n\nUntil they can upgrade to 31.1, users of -privatebroadcast should apply one\nof the following:
Disable the feature. Set -privatebroadcast=0.
Disable v2 transport. Set -v2transport=0. This causes all of the\nnode’s connections to use the unencrypted v1 protocol, which has the downside\nthat it becomes easier to fingerprint and censor on clearnet.
Route IPv4/IPv6 outbound through Tor. Set\n-proxy=127.0.0.1:9050 (replace 9050 with your Tor SOCKS\nport if different). This routes all outbound IPv4/IPv6 P2P\ntraffic through Tor exit nodes, which has the downside of making the node\neasier to Sybil attack.
Credit to Eugene Siegel for discovering the bug.
\n\n\nPrivate Broadcast May Reveal Sender IP Address in Bitcoin Core 31.0 was originally published by Bitcoin Core at Bitcoin Core on June 06, 2026.
", "source_name": "Bitcoin Core", "source_url": "https://bitcoincore.org/en/2026/06/06/privatebroadcast-ip-leak/", "image_url": null, "published_at": "2026-06-06T04:00:00", "sentiment": "neutral", "sentiment_score": 55, "source_trust_score": 95, "event_weight": 100, "events": [ { "type": "SECURITY_EVENT", "weight": 100, "priority": "CRITICAL" } ], "breaking_candidate": true, "importance_score": 94, "market_move_score": 100, "market_move_label": "high", "coins": [ "BTC" ], "coin_relevance": [ { "coin": "BTC", "relevance_score": 100 } ] }, { "id": 422, "title": "Solana Ecosystem Roundup: May 2026", "slug": "solana-ecosystem-roundup-may-2026", "summary": "Solana Ecosystem Roundup May 2026: RWA ATH at $2.8B+, 97% tokenized equities share, $16.4B stablecoin supply, and record ETF inflows.", "source_name": "Solana", "source_url": "https://solana.com/news/solana-ecosystem-roundup-may-2026", "image_url": null, "published_at": "2026-06-05T03:15:00", "sentiment": "bullish", "sentiment_score": 80, "source_trust_score": 95, "event_weight": 95, "events": [ { "type": "ETF_EVENT", "weight": 95, "priority": "CRITICAL" } ], "breaking_candidate": true, "importance_score": 94, "market_move_score": 100, "market_move_label": "high", "coins": [ "SOL" ], "coin_relevance": [ { "coin": "SOL", "relevance_score": 100 } ] }, { "id": 339, "title": "Clear Signing: Making Transaction Approvals Safer on Ethereum", "slug": "clear-signing-making-transaction-approvals-safer-on-ethereum", "summary": "An Ethereum Working Group consisting of wallet developers, security firms and the Ethereum Foundation’s Trillion Dollar Security Initiative today launched an open standard designed to end blind signing — a structural flaw that has contributed to billions in user losses, including the Bybit hack. Ethereum Foundation’s Trillion Dollar Security Initiative...", "source_name": "Ethereum Foundation", "source_url": "https://blog.ethereum.org/en/2026/05/12/clear-signing-announcement", "image_url": null, "published_at": "2026-05-12T00:00:00", "sentiment": "neutral", "sentiment_score": 55, "source_trust_score": 95, "event_weight": 100, "events": [ { "type": "SECURITY_EVENT", "weight": 100, "priority": "CRITICAL" } ], "breaking_candidate": true, "importance_score": 94, "market_move_score": 100, "market_move_label": "high", "coins": [ "ETH" ], "coin_relevance": [ { "coin": "ETH", "relevance_score": 100 } ] }, { "id": 682, "title": "Introducing Forklift: Network Forking and Smart Contract Testing for Aptos", "slug": "introducing-forklift-network-forking-and-smart-contract-testing-for-aptos", "summary": "![\"\"](\"https://cdn-images-1.medium.com/max/1024/1*msDLUAB3jm4HJO6TMQv3sw.png\")
Testing Move smart contracts on Aptos has always been tricky, as there were no easy ways to simulate transaction-based workflows with isolation and repeatability, let alone fork real network state for realistic testing. Until now.
Today, we’re releasing Forklift, a Move smart contract testing and scripting framework for Aptos. Written in TypeScript, it provides a unified interface: the Harness class, which works across local simulation, network forking, and live network execution.
If you’re coming from Ethereum, think of Forklift as Hardhat/Foundry for Aptos.
Before Forklift, if you wanted to simulate how your contract interacts with a real deployed protocol, say, a DEX or lending platform, your options were limited:
Forklift eliminates these tradeoffs. You can now:
This is the workflow Move developers have been missing.
Forklift provides a unified Harness class that works across three execution modes:
![\"\"](\"https://cdn-images-1.medium.com/max/1024/1*kSsUfXqyS6JA4xCbFDvtDQ.png\")
What makes the Harness powerful is that your code stays the same across all modes. Define your workflow once, swap the harness to change environments:
function deployAndInteract(harness: Harness) {
const result = harness.deployCodeObject({
sender: "alice",
packageDir: "./move/my_contract",
packageAddressName: "my_contract",
});
harness.runMoveFunction({
sender: "alice",
functionId: `${result.Result.deployed_object_address}::my_module::initialize`,
args: [],
});
}
// Same workflow, different environments
deployAndInteract(Harness.createLocal()); // Fast iteration
deployAndInteract(Harness.createNetworkFork("mainnet", apiKey)); // Verify against real state
deployAndInteract(Harness.createLive("mainnet")); // Execute for realOne capability that really stands out is network forking. With a single line of code, you can fork mainnet (or other networks) and simulate transactions against real chain state.
import { Harness } from "@aptos-labs/forklift";
// Fork mainnet - real state, zero consequences
const harness = Harness.createNetworkFork("mainnet", apiKey);
// Your transactions run against real deployed contracts
harness.runMoveFunction({
sender: "alice",
functionId: "0x123...::my_protocol::swap",
args: [...],
});
// All changes stay local - mainnet is untouchedWant to test how your DeFi protocol interacts with existing liquidity pools? Fork mainnet and find out. Need to dry-run a contract upgrade against real user state? Fork it first. Investigating a potential vulnerability? Fork it and reproduce the exploit safely in isolation.
State is fetched on demand as a local VM executes your transactions. Your modifications stay completely local, and the network is never affected.
npm install --save-dev @aptos-labs/forklift
Prerequisites: Node.js v18+ and Aptos CLI v7.14.1+
Check out the Forklift repository for full documentation and API reference. Also, take a look at the TipJar tutorial for a complete walkthrough from writing a contract to deploying on a real network.
Forklift is built on top of TL;DR 2025 was the year of the engine tune-up. Velociraptr and Baby Raptr tightened blocktimes and stability under load. Zaptos reduced time-to-settlement; Block-STM v2 increases parallel execution headroom. ACTs and encrypted mempools reduce state and intent leakage, setting the network up for an endgame 2026 stack (Archon, Event-Driven Transactions, Namespaces, etc.) Modern financial markets are built to respond in real-time. Prices update near instantly, orders clear at trillion-scale, state advances hundreds of times per second and market integrity is enforced with strict control on information flow. Most activity is automated and algo-driven, with markets responding to events autonomously. This is the baseline. If a network wants to act as the definitive global trading infrastructure, bringing equities, derivatives, FX, and every other asset & event on-chain, it has to at least match these properties. In 2025, the Aptos Labs research team shipped a set of proposed upgrades that moved the network meaningfully closer to that bar. The work maps cleanly to four questions: This article walks through the 2025 breakthroughs through those lenses: latencies, execution and finality, market integrity, and intent plus automation. We look at latency along two dimensions: how often state progresses, and how well that speed holds when activity spikes. Two upgrades anchor this. Velociraptr reduces the time between blocks to under 50 ms on mainnet. It pipelines proposal and voting, allowing new blocks to be proposed optimistically while the previous one is still converging. For perp DEXs like Decibel on Aptos, this means prices, orders, and positions progress at a pace much closer to how modern electronic markets behave. Baby Raptr ensures that this cadence holds under load. Baby Raptr is the first production step toward Raptr, Aptos’s prefix-consensus direction for BFT. Earlier designs incurred extra round trips as blocks grew larger, because transaction batches had to be fully certified before consensus could advance at full speed. Baby Raptr removes this. Leaders propose batch digests optimistically, and validators fetch and verify data as part of the voting path, so the system does not switch into a slower mode when blocks become large. We try to answer two questions here: How quickly are the transactions applied (execution)? How quickly are the new states safe to rely on (finality)? Zaptos reduces time-to-settlement. Instead of waiting for a block to be ordered and only then running execution and storage, Zaptos overlaps these steps under consensus. In the common case, by the time the network has agreed on the block, the transactions are already executed and committed. For users of applications like Decibel, this compresses the gap between “I submitted a trade” to “my position updated and I can move on”. Block-STM v2 (which will be proposed for governance soon) will signal a new era for dynamic parallel execution on Aptos, with specialized throughput improvements on DeFi apps on chain. Market integrity is downstream of how well the network prevents information leakage: what is your intent or what are you planning to do, and how much you hold or have moved. Encrypted mempools protect user intent from toxic exploitation. In most chains, transactions sit in the mempool fully visible before execution, allowing validators to react to them. Encrypted mempools change that. Instead of broadcasting pending transactions to the entire network, users can submit them encrypted and revealed automatically once ordering is locked in. This reduces orderflow leakage and the basic mechanics behind front-running and sandwiching. All is information recorded on chain and transparent as usual. Aptos Confidential Transactions (ACTs) protect amounts and balances on-chain. ACTs encrypt transaction amounts and token balances so they are confidential to the general public, while still supporting selective disclosure for authorized auditors when needed. This is completely optional, enabled by the token issuer and not the default setting. 2025 closed a set of core gaps. 2026 is about turning those gains into a full trading stack: faster confirmations, more execution headroom, native automation, and stronger integrity guarantees. We’d like to share our view on the relationship between Bitcoin Core development and transaction relay\npolicy on the network. Bitcoin is a network that is defined by its users, who have ultimate freedom in choosing what\nsoftware they use (fully-validating or not) and implementing whatever policies they desire. Bitcoin\nCore contributors are not in a position to mandate what those are. One way this is reflected is by\nour long-running practice of avoiding auto-updating in the software. This means that no entity can\nunilaterally push out changes to Bitcoin Core users: changes must be made by users choosing to\nadopt new software releases themselves, or if they so desire, different software. Being free to run\nany software is the network’s primary safeguard against coercion. As Bitcoin Core developers we also consider it our responsibility to make our software work as\nefficiently and reliably as possible for its purpose, namely validating and relaying blocks and\ntransactions in the Bitcoin peer-to-peer network, so that Bitcoin succeeds as a decentralized digital\ncurrency. With regards to transaction relay, this may include adding policies for denial of service (DoS)\nprotection and fee assessment, but not blocking relay of transactions that have sustained economic\ndemand and reliably make it into blocks. The goals of transaction relay include: Knowingly refusing to relay transactions that miners would include in blocks anyway forces users into\nalternate communication channels, undermining the above goals. It is the case that transaction acceptance rules have been used effectively in the past to\ndiscourage the development of use cases that used block space inefficiently while doing so was very\ncheap. However this can only be effective while both users and miners are satisfied with whatever\nalternatives exist. When that is no longer the case, and an economically viable use case develops\nthat would conflict with policy rules, users and miners can directly collaborate to avoid any\nexternal attempt to impose restrictions on their activities. In fact, the ability to do precisely\nthat is an important aspect of Bitcoin’s censorship resistance, and other node software with\npreferential peering has also shown that circumventing filters of the vast majority of the nodes\nis relatively easy. Given that, we believe it is better for Bitcoin node software to aim to have a\nrealistic idea of what will end up in the next block, rather than attempting to intervene between\nconsenting transaction creators and miners in order to discourage activity that is largely harmless\nat a technical level. This is not endorsing or condoning non-financial data usage, but accepting\nthat as a censorship-resistant system, Bitcoin can and will be used for use cases not everyone\nagrees on. While we recognize that this view isn’t held universally by all users and developers, it is our\nsincere belief that it is in the best interest of Bitcoin and its users, and we hope our users agree.\nWe will continue to apply our best judgment as developers in aligning transaction acceptance rules\nwith Bitcoin’s long-term health and miners’ rational self-interest, including specific\ntechnical reasons such as upgrade safety, efficient block building, and node DoS attacks. Signed, (List of contributors who support this letter) Bitcoin Core development and transaction relay policy was originally published by Bitcoin Core at Bitcoin Core on June 06, 2025. NEAR Foundation announces today that NEAT, a rollup protocol designed for scaling AI applications on NEAR, has received 1 million $NEAR token staking delegation from NEAR Foundation. All NEAR token rewards from the delegation will be redistributed to $NEAT stakers, producing approximately 120–200% APY. This funding is part of NEAR Foundation’s efforts to support AI and blockchain projects on NEAR, and to promote use cases of AI integration with blockchain technology more broadly. NEAT, as the first rollup scaling protocol to receive official support from the NEAR Foundation, will utilize these funds to attract a wider user base to its ecosystem. NEAT is a rollup scaling solution built on the NEAR inscription standard, specifically designed to facilitate AI and machine-learning applications on NEAR. NEAT offers an innovative approach for rollups to be built on NEAR. With off-chain indexer nodes for execution and NEAR L1 as the data availability layer, NEAT eliminates the need for rollups to deploy smart contracts or run verification logic on the L1. This streamlined process drastically reduces transaction costs for rollups, making NEAT particularly well suited for computationally intensive applications such as AI and gaming. Additionally, NEAR Catalog, powered by NEAT, is currently developing an advanced indexer that aims to provide projects and applications in the NEAR ecosystem with cost-effective and flexible indexing and querying capabilities. NEAT Token and Benefits The $NEAT token exists in two forms, NRC-20 and NEP-141, with a total supply of 42 million tokens. $NEAT tokens offers the following benefits: 1. Stakers of $NEAT-NEP141 will receive the staking rewards generated from the 1 million $NEAR tokens provided by the Foundation. A portion of these staking rewards will also be allocated to support the exploration of AI integration with NEAT. 2. $NEAT-NEP141 stakers will receive a share of the fees generated from wrap/unwrap operations (currently set at 1% fee rate) and a portion of the fees from the NRC-20 marketplace. 3. After the decentralized indexer is operational, a portion of the indexing fees will be distributed to $NEAT-NEP141 stakers. 4. Holders of $NEAT-NRC20 tokens will be eligible to receive airdrops of newly minted NRC-20 tokens. 5. $NEAT serves as a utility token within the NEAT ecosystem, enabling services/assets payments, DeFi integration, AI governance, and more. The Road Ahead: Revolutionizing AI with Decentralized Indexing NEAT is building the first fully customizable decentralized indexer network, which allows any project to easily store data on the NEAR blockchain, deploy custom indexing logic on a decentralized set of indexer nodes, and achieve verifiable execution through zero-knowledge proofs. This approach aims to address potential failure points and attack vectors associated with centralized indexers. One of the most exciting use cases for decentralized indexing is in the field of artificial intelligence. With NRC-20 and NEAT Indexers, it becomes possible to store AI data, parameters, algorithms, models, and outputs as on-chain inscriptions and integrate them with off-chain execution through zero-knowledge proofs. For instance, one can imagine creating fully open-source AI-powered games, where users participate in shaping the game’s narrative, and the history is permanently stored on-chain through inscriptions. AI agents’ models, parameters, and decisions can be represented as inscribed NFTs, and their training and model parameters can be stored on-chain. This combination of blockchain transparency and off-chain computational efficiency allows AI to be truly accessible and open to everyone, contributing to the development of a genuinely open network. NEAR Foundation Partners with NEAT Protocol to Accelerate the Growth of AI Applications with 1… was originally published in NEAR Protocol on Medium, where people are continuing the conversation by highlighting and responding to this story. The Hong Kong Web3 Festival, co-hosted by Wanxiang Blockchain Labs and HashKey Group, concluded with resounding success. Over four exciting days, the festival brought together more than 50,000 attendees, featured 300 global speakers, showcased 100 exhibitors, and offered nearly 200 engaging side events. The event not only highlighted the dynamic growth of the Web3 industry but also positioned the fusion of Web3 and AI as the hottest topic of the year. Chain Abstraction: Unlocking Mass Adoption’s Path to Success NEAR’s presence at the festival was nothing short of remarkable, solidifying its position as more than just a layer 1 protocol. Amos Zhang, Founder of Metaweb and Early Contributor to NEAR Protocol, introduced NEAR and its visionary founders, Illia Polosukhin and Alexander Skidanov. He highlighted the importance of chain abstraction in simplifying the user experience and fostering industry-wide collaboration, setting the stage for a seamless and prosperous Web3 future. Why AI Needs Web3 Illia Polosukhin, NEAR’s co-founder and CEO delivered a keynote presentation on “Why AI Needs Web3” at the Hong Kong Web3 Festival. He highlighted the powerful combination of Web3 and AI. Illia pointed out the existing challenges with closed-source AI models, including the lack of transparency in data generation methods. He recognized the need for open-source models but acknowledged obstacles such as data protection regulations and insufficient financial incentives. He proposed that AI language models should directly engage with users, leveraging cryptography and on-chain reputation systems to address these challenges and foster the development of competitive models within Web3. For a recap of the keynote presentation, please read this blog post: NEAR Protocol Co-Founder Illia Polosukhin Delivers Keynote at 2024 Hong Kong Web3 Festival on Why… Meeting the Vibrant NEAR Community NEAR has a strong presence in the Chinese community. At the NEAR booth, attendees were immersed in an electrifying experience, where we presented an array of engaging activities including NFT and Swag giveaways supported by NEAR China, Black Dragon, LiNEAR Protocol, Shard Dog, and Sender Wallet. The NEAR China team and ecosystem representatives captivated visitors with a comprehensive introduction to NEAR, exciting updates, and an unforgettable encounter that left everyone craving more. NEAR’s Impact in the Hong Kong Web3 Landscape During the Hong Kong Web3 Festival, NEAR and MetaWeb were invited to speak at various side events and panels hosted by renowned industry players such as AWS Cloud, Google Cloud, Hashkey, and Gate.io to share insightful possibilities of AI and Web3, as well as the trends of layer 1 blockchains. This participation reflects the growing momentum and enthusiasm surrounding NEAR, particularly in the field of web3 technologies and artificial intelligence. NEAR’s presence at the Hong Kong Web3 festival was remarkable, emphasizing the importance of chain abstraction and the potential of Web3 and AI integration. NEAR’s impact in the Chinese community also showcased its influence in the Web3 landscape. The momentum will continue at Token2049. The future is NEAR. For more information and updates on the event, follow NEAR China on Twitter and NEAR social platforms. NEAR @ Hong Kong Web3 Festival Wrap Up: NEAR’s Impact in Web3 and AI was originally published in NEAR Protocol on Medium, where people are continuing the conversation by highlighting and responding to this story. An exploit drained about $2.4 million in ADA from 374 addresses over three days through a flaw in SecondFi's wallet-generation software. SecondFi says it has completed forensic investigations, taken a final balance snapshot and is preparing to return assets. Remi's compliance-native interbank clearing and settlement network enables real-time settlement with balance-sheet treatment for participating financial institutions, simplifying and expanding global payments Main Takeaways After Bitcoin Core 0.14.0 and before Bitcoin Core 29.0, validating a specially-crafted block may\ncause the node to access previously freed memory. During validation, necessary data required for checking inputs for each transaction is\npre-calculated and cached. For specially crafted invalid blocks, it was possible for this data to be\ndestroyed while it was still being accessed by a background validation thread. An attacker capable\nof mining a block with sufficient proof-of-work could have exploited this to crash victim nodes.\nBecause of the nature of use-after-free bugs, it is possible that the crash could have been used for\nremote code execution, though constraints on the input (block) data make this unlikely. This issue is considered High severity. By default, script validation for new blocks is dispatched to background threads via a vector of\n The script checks lifetime is enforced by an RAII class, This is not an issue when the block is valid, as Cory Fields (MIT DCI) discovered this vulnerability and responsibly disclosed it in a detailed\nreport containing a proof of concept for reproduction and a proposed mitigation. CVE-2024-52911 - Script Interpreter Remote Crash was originally published by Bitcoin Core at Bitcoin Core on May 05, 2026. Disclosure of the details of a bug on 32-bit systems which may, in a rare edge case, cause the node\nto crash when receiving a pathological block. This bug would be extremely hard to exploit. A fix was\nreleased on October 10th 2025 in Bitcoin Core v30.0. This issue is considered Low severity. Before writing a block to disk, Bitcoin Core checks that its size is within a normal range. This\ncheck would overflow on 32-bit systems for blocks over 1GB, and make the node crash when writing it\nto disk. Such a block cannot be sent using the This issue was indirectly prevented by capping the maximum value of the Pieter Wuille discovered this bug and disclosed it responsibly. Antoine Poinsot proposed and implemented a covert mitigation. CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems was originally published by Bitcoin Core at Bitcoin Core on October 24, 2025.![\"\"](\"https://cdn-images-1.medium.com/max/1012/1*T5B9rkamo9eiOffJ8VMWqQ.jpeg\")
Latencies
![\"\"](\"https://cdn-images-1.medium.com/max/660/1*Dg_rdJ0EKidDTDOvW0xhQA.jpeg\")
Execution and Finality
Market integrity
Anticipated 2026 Aptos Improvement Proposals
\n
\n\n\n
\n\n NEAR Foundation Partners with NEAT Protocol to Accelerate the Growth of AI Applications with 1 million $NEAR Delegation
![\"\"](\"https://cdn-images-1.medium.com/max/1024/1*GiW4fxbKjVMqbc_B5CmOJA.png\")
![\"](\"https://s3-images.ctmedia.io/media/article-covers/hi-spotlight-for-crypto-recovery.jpg\")
",
"source_name": "Sui Foundation",
"source_url": "https://blog.sui.io/built-on-sui-remi-brings-regulated-stablecoin-payments-into-banks/",
"image_url": "https://storage.ghost.io/c/d7/e3/d7e30b85-64c2-4e5c-8e37-6b4a3e2f0142/content/images/2026/06/Blog-Header_0602_Sui-and-OpenAssets-Forge-New-RWA-Paths--1-.png",
"published_at": "2026-06-16T13:03:09",
"sentiment": "neutral",
"sentiment_score": 55,
"source_trust_score": 95,
"event_weight": 95,
"events": [
{
"type": "REGULATORY_EVENT",
"weight": 95,
"priority": "CRITICAL"
}
],
"breaking_candidate": true,
"importance_score": 92,
"market_move_score": 100,
"market_move_label": "high",
"coins": [
"SUI"
],
"coin_relevance": [
{
"coin": "SUI",
"relevance_score": 100
}
]
},
{
"id": 867,
"title": "Bybit to support Toncoin (TON) rebrand and ticker change to Gram (GRAM)",
"slug": "bybit-to-support-toncoin-ton-rebrand-and-ticker-change-to-gram-gram",
"summary": "Bybit to support Toncoin (TON) rebrand and ticker change",
"source_name": "Bybit Delistings",
"source_url": "https://announcements.bybit.com/en-US/article/bybit-to-support-toncoin-ton-rebrand-and-ticker-change-to-gram-gram--blt617f4bf48950ab77/",
"image_url": null,
"published_at": "2026-06-10T14:49:57",
"sentiment": "neutral",
"sentiment_score": 40,
"source_trust_score": 100,
"event_weight": 95,
"events": [
{
"type": "DELISTING",
"weight": 95,
"priority": "CRITICAL"
}
],
"breaking_candidate": true,
"importance_score": 92,
"market_move_score": 100,
"market_move_label": "high",
"coins": [
"TON"
],
"coin_relevance": [
{
"coin": "TON",
"relevance_score": 100
}
]
},
{
"id": 157,
"title": "ETH falls to 13-month low on Zcash bug, Bitcoin below $60K: Is $1.4K next?",
"slug": "eth-falls-to-13-month-low-on-zcash-bug-bitcoin-below-60k-is-14k-next",
"summary": "ETH price crashed below $1,600 as a vulnerability in Zcash emerged and Bitcoin sold off below $60,000 for the first time in months.",
"source_name": "CoinTelegraph Ethereum",
"source_url": "https://cointelegraph.com/markets/eth-falls-to-13-month-low-on-zcash-bug-news-and-bitcoin-drop-to-sub-60k-is-14k-next?utm_source=rss&utm_medium=rss&utm_campaign=rss",
"image_url": "https://s3-images.ctmedia.io/media/article-covers/article-covers-259027-ethereum-foundation-napravila-v-stejking-ese-46-64-mln-v-efire.jpg",
"published_at": "2026-06-05T21:18:29",
"sentiment": "neutral",
"sentiment_score": 55,
"source_trust_score": 90,
"event_weight": 100,
"events": [
{
"type": "SECURITY_EVENT",
"weight": 100,
"priority": "CRITICAL"
}
],
"breaking_candidate": true,
"importance_score": 92,
"market_move_score": 100,
"market_move_label": "high",
"coins": [
"ETH",
"BTC"
],
"coin_relevance": [
{
"coin": "ETH",
"relevance_score": 100
},
{
"coin": "BTC",
"relevance_score": 100
}
]
},
{
"id": 484,
"title": "CVE-2024-52911 - Script Interpreter Remote Crash",
"slug": "cve-2024-52911---script-interpreter-remote-crash",
"summary": "Details
\n\nCScriptCheck functors. Each CScriptCheck holds a pointer to a PrecomputedTransactionData object\nwhich stores some data needed by each input in the transaction. Because it stores a pointer and not\nthe data itself, care must be taken to ensure that the PrecomputedTransactionData outlives the\nCScriptCheck.CCheckQueueControl. However, the control\nis intantiated before the precomputed transaction data. Because local objects in C++ are\ndestructed in reverse order of construction,\nthis means the vector of PrecomputedTransactionData is destroyed before the\nCCheckQueueControl.CCheckQueueControl::Wait() will be called before\nthe function returns and the PrecomputedTransactionData gets destroyed. However, in case of an\nearly return (when a separate check fails) a background script thread may read the precomputed\ntransaction data after it was destroyed. An attacker could exploit this to crash victim nodes at the\nexpense of a valid PoW at tip.Attribution
\n\nTimeline
\n\n\n
\n\n\n Details
\n\nBLOCK message, but could in theory be sent as a\ncompact block if the victim node has a non-default large mempool which already contains 1GB of\ntransactions. This would require the victim to have set their -maxmempool option to a value\ngreater than 3GB, while 32-bit systems may have at most 4GiB of memory.-maxmempool setting on\n32-bit systems.Attribution
\n\nTimeline
\n\n\n
\n\n\n
![\"\"](\"https://cdn-images-1.medium.com/max/1024/0*_0gZRg2pxOL3CYlQ\")
![\"\"](\"https://cdn-images-1.medium.com/max/1024/0*Cnl-o_QxkjOEhUFj\")
![\"\"](\"https://cdn-images-1.medium.com/max/1024/0*uAr6izx5XZjKTIZz\")
![\"\"](\"https://cdn-images-1.medium.com/max/1024/0*yWkyrnqByosaJycp\")