The Ethereum Foundation has published ratings for 62 Hegotá proposals after collecting 397 assessments from about 60 protocol specialists across nine teams. The Ethereum Foundation said in a Sept. 7 post on X that its Protocol Cluster had released two…
BNB Chain developers have announced the Lorentz hard fork activation schedule for mainnet, with the upgrade set for block height 42,100,000.
The update includes BEP-341 transaction priority changes designed to reduce gas costs by 20% for network users. Validators and node operators will need to upgrade their software before the trigger height, which makes this both a technical update and a coordination event.
That is how hard forks work when they go smoothly.
Users may only notice cheaper or smoother transactions later. Validators notice the deadline first.
For more details, visit the official Blog platform.
TL;DR
BNB Chain has announced the Lorentz hard fork schedule.
The upgrade is set for mainnet block height 42,100,000.
Validators and node operators need to upgrade before activation.
Why Hard Forks Matter
A hard fork changes network rules.
That makes coordination essential. If validators and node operators are not ready, a chain can face disruption, split behavior, or degraded performance. Most planned hard forks are routine, but they still need careful execution.
For BNB Chain, Lorentz is a mainnet upgrade with a specific block-height trigger.
That gives operators a clear deadline. It also gives developers and users a timeline for when the new rules are expected to come into effect.
BEP-341 Is About Transaction Priority
The upgrade includes BEP-341 transaction priority updates.
The goal is to improve how transactions are handled and reduce costs for users. Lower gas costs can matter a lot on a chain like BNB Chain, where retail activity, trading, gaming, payments, and DeFi transactions can all be fee-sensitive.
A 20% gas reduction claim is meaningful, but it needs to be tied to the upgrade’s stated scope.
That does not necessarily mean every user will see exactly the same savings in every transaction. Network conditions, app design, and transaction type can all affect real-world costs.
BNB Chain Still Competes On Accessibility
BNB Chain has always leaned into accessibility.
Low fees, fast settlement, broad exchange familiarity, and a large retail base have been part of its appeal. In a market where Solana, Base, Polygon, Arbitrum, Sui, and others are all fighting for activity, fee improvements matter.
Users can be fickle.
If a chain is cheap and smooth, they stay. If it becomes expensive or unreliable, they move.
That is why technical upgrades have direct competitive importance.
Validators Carry The First Responsibility
For the Lorentz hard fork to activate cleanly, validators and node operators need to upgrade in time.
That is the less glamorous side of blockchain operations. Users often treat chains like apps, but under the hood, networks depend on operators keeping software current and following upgrade instructions.
A scheduled hard fork is a test of coordination.
If enough operators are prepared, the chain moves forward. If not, the rollout can become messy.
The Ecosystem Signal
The Lorentz schedule shows BNB Chain continuing to tune its mainnet infrastructure.
This is not a BNB price forecast. It is not a promise that activity will surge overnight. But it is a real network update with practical implications for users and developers.
Lower costs and better transaction handling can improve the experience.
Now the chain needs validators to complete the upgrade and users to see the benefits in practice.
This article draws on BNB Chain materials relating to the Lorentz hard fork activation schedule.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Blog. at Blog
Solana validator adoption of the v1.18 client has reached 85% of consensus stake, marking an important infrastructure milestone for the network.
This is one of those updates that will not excite casual traders as much as a meme coin rally. But for the health of the chain, it matters.
Validator software upgrades are how networks improve performance, reliability, and execution over time. In Solana’s case, the v1.18 release is tied to improvements around transaction scheduling, block propagation, and reduced state contention during periods of heavy demand.
That matters because Solana’s whole pitch depends on staying fast when activity gets intense.
For more details, visit the official Github platform.
TL;DR
Solana validator client v1.18 has reached 85% consensus stake adoption.
The release includes improvements around transaction scheduling and network performance.
The upgrade does not change SOL tokenomics.
Why Validator Adoption Matters
A blockchain upgrade is only meaningful if validators actually run it.
Developers can release new software, but the network depends on validator adoption. If too little stake upgrades, new features or performance changes may not become broadly effective. If enough stake upgrades, the network can move forward with more confidence.
That is why the 85% mark matters.
It shows that a large share of Solana’s consensus weight has moved to the newer client version. Not every validator has necessarily upgraded, but the network has reached a meaningful adoption threshold.
For a high-throughput chain, that is a big operational signal.
Solana Needs Performance To Stay Its Brand
Solana is judged differently from many chains.
Ethereum is judged on security, settlement depth, and ecosystem breadth. Bitcoin is judged on monetary strength and resilience. Solana is judged heavily on performance.
Fast blocks, cheap transactions, and high-volume activity are central to the network’s identity.
That means software upgrades are not background noise. They are part of the product. If Solana wants to support DeFi launches, memecoin trading bursts, NFT activity, payments, and consumer apps, the validator layer has to keep improving.
Transaction Scheduling Is A Real Bottleneck
High activity can create stress.
When lots of users and bots compete for blockspace, the network needs to order, process, and propagate transactions efficiently. Poor scheduling can lead to congestion, failed transactions, and a worse user experience.
Solana has dealt with those issues before.
So improvements to the transaction scheduler and state contention are worth watching. They are not glamorous, but they speak directly to whether the network can handle the kind of activity its supporters expect.
Not A Tokenomics Event
This update should not be confused with a supply change.
The v1.18 client adoption milestone does not alter SOL issuance, staking rewards, fee burns, inflation, or governance economics by itself. It is a software and infrastructure update.
That is still important.
A chain can have good tokenomics and poor performance, or strong performance and weak economics. This story is about the performance side.
The Network Signal
Solana’s v1.18 adoption shows the validator network moving through another infrastructure upgrade cycle.
For builders, that can mean more confidence in the chain’s ability to handle demanding apps. For users, it may eventually translate into smoother execution during busy periods. For traders, it is a reminder that Solana’s story is not only about price.
The network is still being tuned.
And for a chain that sells itself on speed, those boring-looking technical milestones are exactly the ones that count.
This article draws on Solana v1.18 release materials and validator adoption data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Github. at Github
BNB Smart Chain is preparing to activate its Pasteur hard fork on mainnet on August 25 at 02:30 UTC.
The upgrade introduces several network changes, including BEP-682 for bridge verification, BEP-695 for validator governance, and BEP-675 for block processing capacity. Node operators are required to update their software client to version 1.7.7 and remove the EnableBAL setting.
The timing matters.
At the time of the source materials, the upgrade was scheduled but not yet completed. It should not be described as already live until the activation has occurred.
TL;DR
BNB Smart Chain’s Pasteur hard fork is scheduled for August 25 at 02:30 UTC.
The upgrade includes BEP-682, BEP-695, and BEP-675.
Node operators need to update to client version 1.7.7.
Why Pasteur Matters
BNB Chain is one of the largest smart contract ecosystems by user activity.
That means hard forks are operationally important. Validators, node operators, exchanges, wallets, developers, and infrastructure providers need to coordinate around the upgrade to avoid service disruptions.
Pasteur introduces changes across bridge verification, validator governance, and block processing.
Those are not cosmetic upgrades. They touch infrastructure areas that affect security, performance, and network operations.
Bridge Verification Gets Attention
BEP-682 focuses on bridge verification.
Bridge security remains one of the biggest issues in crypto. Cross-chain infrastructure has historically been a major attack surface, and ecosystems have had to improve how they verify and secure bridge-related activity.
A proposal focused on bridge verification fits that broader trend.
BNB Chain is trying to strengthen the infrastructure around cross-chain movement, which is essential for a network with wide DeFi and exchange-connected usage.
Validator Governance Also Changes
BEP-695 introduces validator governance changes.
Validator governance determines how network operators participate in decisions and how the chain evolves operationally. Changes in this area can affect decentralization, upgrade coordination, and long-term network control.
For users, validator governance may feel distant.
But it shapes the network’s resilience. A chain with poor validator coordination can struggle during upgrades, security events, or performance stress.
That is why BEP-695 belongs in the upgrade conversation.
Block Processing Capacity Is The Performance Piece
BEP-675 targets block processing capacity.
This is the kind of change users may eventually feel through throughput, reliability, or network responsiveness. BNB Chain handles high transaction activity, so processing capacity remains a practical concern.
Performance upgrades can help the ecosystem support more applications, more users, and more transaction types.
But the impact should be judged after activation, not before.
Node Operators Have Work To Do
The operator instructions are clear.
Nodes need to update to version 1.7.7 and remove the EnableBAL setting. Upgrade coordination is one of the most important parts of a hard fork. If too many operators fail to update, networks can face instability or temporary disruption.
That is why scheduled hard forks are communicated in advance.
The market should watch whether activation proceeds smoothly on August 25.
What Comes Next
The next milestone is mainnet activation.
If Pasteur goes live without problems, BNB Chain will have completed another infrastructure upgrade across bridge, governance, and processing layers. If issues emerge, developers and validators may need to respond quickly.
For now, the story is preparation.
BNB Smart Chain has a scheduled hard fork, clear operator requirements, and several meaningful BEPs bundled into the upgrade.
TON validators have been instructed to update their node software and mytonctrl tooling ahead of a configuration vote tied to the network’s new collator architecture.
The validator preparation includes node commit 140320b and mytonctrl commit 7e90e26. The configuration switch vote was scheduled for August 21 at 08:00 UTC.
The important detail is status.
This is a preparation and voting-stage story. It should not be described as full collator activation if the vote and switch process have not completed.
Still, the update matters because collator architecture can affect how TON organizes block production and validator responsibilities as the network scales.
TL;DR
TON validators were told to update node software and mytonctrl.
The updates prepare for a collator-related configuration vote.
The process should not be described as completed activation unless the vote has finalized.
Why Validator Updates Matter
Validator coordination is critical for any blockchain upgrade.
If validators do not update software correctly, networks can face delays, inconsistent behavior, missed blocks, or operational confusion. That is why upgrade instructions often include precise commit versions and deadlines.
TON’s validator update is part of that process.
The network needs participants to prepare their infrastructure before a configuration switch can move forward safely.
For users, this kind of work is mostly invisible — unless something goes wrong.
What Collators Do
Collators are generally tied to collecting transactions, preparing candidate blocks, or supporting block production workflows depending on the network design.
For TON, introducing or activating collator architecture is part of improving how the network handles scale and coordination. The technical details matter most to validators and infrastructure operators, but the user-facing goal is smoother network performance.
This is the kind of upgrade that can strengthen a chain’s underlying machinery.
It may not create an immediate retail-facing feature, but it can improve how the network operates under load.
Vote Status Needs Care
The vote timing is central.
Validators were preparing for a configuration vote, not necessarily announcing that the upgrade had already gone live. Crypto upgrade coverage often jumps too quickly from “vote scheduled” to “activation complete.”
That can mislead users and node operators.
The clean read is that TON’s validator set was being asked to update software and participate in a configuration decision connected to collator activation.
Final status depends on the vote and subsequent network execution.
TON’s Scaling Ambitions Remain Active
TON has positioned itself as a high-throughput blockchain with a large consumer-distribution opportunity, especially because of its connection to Telegram’s ecosystem.
That ambition requires strong infrastructure.
Large-scale consumer blockchain usage is not only about wallets and apps. It requires validators, nodes, transaction processing, developer tools, and upgrade coordination that can support heavy demand.
Collator architecture fits into that broader scaling effort.
What Comes Next
The next step is confirmation of the vote result and any completed configuration switch.
If validators approve and the transition proceeds smoothly, TON can point to another infrastructure milestone. If the vote is delayed or implementation requires more work, the upgrade remains in progress.
For now, the story is clear enough.
TON validators are preparing their software for a collator-related vote, and the network’s infrastructure roadmap is moving forward.
The market should watch the final activation status before treating the upgrade as complete.
Arbitrum has activated its ArbOS 61 “Elara” upgrade, adding new tooling for Orbit chains, including an optional protocol-level compliance filtering feature for enterprise deployments.
The upgrade went live on August 20. Node operators are required to update to Nitro v3.11.3. Elara also expands the Stylus contract size limit from 24 KB to 96 KB, giving developers more room for larger smart contracts.
The compliance filter will likely attract the most attention.
But the key word is “optional.”
The feature is designed for private or enterprise Orbit chain operators. It should not be described as censorship on public Arbitrum One or Nova networks.
TL;DR
Arbitrum activated the ArbOS 61 “Elara” upgrade.
The upgrade adds optional compliance filters for Orbit chains.
Stylus contract size limits expand from 24 KB to 96 KB.
The ecosystem includes Arbitrum One, Nova, and a growing Orbit chain framework that lets teams launch custom chains using Arbitrum technology. That means upgrades increasingly affect not only public users, but also teams building specialized networks.
Elara fits that broader direction.
It adds capabilities aimed at developers and enterprise operators, while continuing to refine Arbitrum’s infrastructure stack.
For Orbit chains, customization is the pitch. Teams can design chains for specific use cases, compliance needs, performance goals, or application environments.
Compliance Filters Will Be Debated
The optional compliance filtering feature is likely to divide opinion.
Enterprise and regulated users may see it as necessary infrastructure. If a private Orbit chain is serving institutions, tokenized assets, or regulated workflows, operators may need tools to meet legal and compliance obligations.
Crypto purists may dislike the idea of filtering at the protocol level.
Both reactions are understandable.
The important point is scope. The feature is not described as a blanket change to public Arbitrum One activity. It is configuration-dependent and aimed at Orbit chain operators.
That distinction matters for users worried about censorship.
Stylus Contract Expansion Helps Developers
The Stylus contract size increase is also important.
Moving the limit from 24 KB to 96 KB gives developers more flexibility when building larger or more complex contracts. That can support richer applications and make migration easier for teams with heavier codebases.
Stylus is one of Arbitrum’s major developer-facing bets.
It allows smart contracts to be written in languages beyond Solidity, opening the door to Rust, C, and C++ developers. Expanding contract size helps make that environment more practical.
Orbit Is Becoming More Enterprise-Friendly
Elara shows Arbitrum leaning further into customizable infrastructure.
Enterprise adoption often requires controls that open public networks do not prioritize. That can include permissioning, compliance tooling, custom gas models, privacy considerations, and operational control.
Orbit chains are designed to serve those needs.
The challenge is maintaining a balance between enterprise flexibility and crypto’s open-network ethos.
Arbitrum’s approach appears to be letting custom chain operators choose features without forcing the same rules across the public ecosystem.
What Comes Next
The next test is adoption.
If more teams launch Orbit chains using Elara’s new capabilities, the upgrade could strengthen Arbitrum’s position in the rollup-as-a-service and enterprise L3 market. If the compliance tooling remains niche, the developer improvements may matter more than the regulatory features.
Either way, ArbOS 61 is a notable infrastructure upgrade.
It shows Arbitrum continuing to build beyond a single public rollup and toward a broader stack for custom Ethereum-aligned chains.
The Cardano Foundation has published a new Cardano Improvement Proposal draft called Dijkstra, outlining changes aimed at improving smart contract execution pathways and compute efficiency.
The proposal is still in draft form. It is not live on Cardano mainnet. It is not confirmed as an activated upgrade. That distinction matters because protocol proposals often move through several stages before they affect users.
Still, the Dijkstra draft is worth watching because it touches one of Cardano’s most important long-term questions: how the network improves developer experience and smart contract performance without compromising its design philosophy.
TL;DR
The Cardano Foundation has posted a Dijkstra CIP draft.
The proposal targets smart contract execution and compute efficiency.
It is still under discussion and should not be treated as live.
Why Dijkstra Matters
Smart contract performance is central to Cardano’s competitiveness.
The network has always taken a more research-heavy and deliberate approach than many rivals. That has helped Cardano build a strong community around formal methods and careful design, but it has also attracted criticism when development feels slower than faster-moving ecosystems.
A proposal targeting execution pathways is therefore important.
If Dijkstra can reduce compute friction or improve how smart contracts run, it could help developers build more efficient applications.
The practical impact will depend on the final design and implementation.
A CIP Is A Starting Point
Cardano Improvement Proposals are part of the network’s development process.
They give the community a way to discuss, refine, and evaluate changes before they become part of the live system. That makes the publication of a draft meaningful, but not final.
A draft can change. It can stall. It can be merged into a broader upgrade path. It can require more research or implementation work.
So the correct framing is that Dijkstra is now part of Cardano’s development conversation.
It is not already reshaping the network today.
Compute Efficiency Is A Developer Issue
Users may not care about execution pathways, but developers do.
If smart contracts consume too much compute or are difficult to optimize, applications become harder to build and scale. Better execution efficiency can support more complex DeFi products, better user experience, and lower operational friction.
That matters in a competitive smart-contract market.
Cardano is not only competing with Ethereum. It is also competing with Solana, Sui, Avalanche, BNB Chain, and other ecosystems trying to attract developers.
Every improvement to smart contract performance helps the network make its case.
Avoiding The Price Trap
The discovery trail included ADA price weakness, but the more important story is technical.
Protocol development should not be reduced to whether ADA is up or down on the day. Price may influence sentiment, but it does not define whether a CIP matters.
The Dijkstra draft deserves attention because it may affect Cardano’s application layer over time.
That is more durable than a short-term price move.
What Comes Next
The next step is community and developer review.
Cardano builders will need to evaluate whether the proposal achieves its goals, what trade-offs it introduces, and how it fits into the broader roadmap. If it advances, implementation and testing will become the next milestones.
For now, Dijkstra gives Cardano another technical upgrade path to watch.
It is early, but it signals continued work on making Cardano’s smart contract layer more efficient and competitive.
BNB Chain has introduced BEP-675, a draft proposal aimed at improving network throughput by reducing block re-execution in the validator process.
The proposal introduces blind signing for validator blocks, allowing builders to submit executed blocks directly. According to the proposal, the change can reduce validator execution time on the critical path from 125 milliseconds to 15 milliseconds, with testnet environments showing a potential doubling of throughput.
That sounds technical, but the goal is simple: make block production more efficient without relying only on higher gas limits or shorter block times.
The key caveat is that BEP-675 is not live on BNB Chain mainnet. It remains in Draft status under the Pasteur network hard fork timeline.
For more details, visit the official Github platform.
TL;DR
BEP-675 aims to reduce block re-execution in BNB Chain’s validator process.
The proposal could improve throughput in testnet environments.
It is still in Draft status and should not be described as live mainnet functionality.
Why Block Re-Execution Matters
In blockchain systems, small inefficiencies can become big bottlenecks.
If builders and validators are repeating some of the same execution work before a block is finalized, the network is spending time on duplicated effort. BEP-675 targets that issue by changing how executed blocks are submitted and verified.
The proposal’s core idea is to remove unnecessary execution from the critical path.
That could allow blocks to move faster through the production process, improving throughput without pushing every other parameter harder.
For users, the benefit would be less visible than a new app or token launch, but it could matter for network performance.
Not Every Scaling Upgrade Needs Bigger Blocks
Scaling debates often center on gas limits and block times.
Raise the gas limit, and more transactions can fit into a block. Shorten block times, and blocks arrive more often. Both can increase throughput, but they can also create new pressure on validators, nodes, propagation, and network stability.
BEP-675 takes a different angle.
It targets the workflow around block construction and validation. If the same amount of work can be processed more efficiently, the network may gain capacity without simply forcing larger or faster blocks.
That is the cleaner kind of scaling when it works.
Draft Status Keeps Expectations In Check
The most important limitation is status.
BEP-675 is a proposal. It is not something users should assume is active on mainnet today. It sits inside a hard fork timeline and still needs the usual implementation, testing, review, and activation path.
Crypto markets often treat proposals as finished upgrades.
That is risky. Drafts can change. Timelines can shift. Testnet performance may not translate perfectly to mainnet conditions.
The right read is that BNB Chain is working on a meaningful throughput improvement, not that throughput has already doubled for live users.
Why BNB Chain Needs Efficiency
BNB Chain has long competed on low-cost, high-throughput activity.
That attracts DeFi apps, trading venues, gaming projects, retail users, and high-frequency transaction patterns. But it also means the network needs to keep improving performance if demand rises.
Efficiency upgrades help maintain that competitive position.
They can also reduce pressure during periods of heavy activity, especially when retail trading and on-chain speculation spike.
A block-building improvement may not be flashy, but it can support the kind of user experience BNB Chain is built around.
What To Watch Next
The next steps are implementation and activation.
Developers, validators, and the broader ecosystem will need to evaluate whether BEP-675 performs as expected, whether it introduces new trade-offs, and when it can safely move beyond Draft status.
If successful, the proposal could give BNB Chain more throughput headroom without relying entirely on blunt parameter changes.
For now, BEP-675 is best understood as a technical scaling proposal with real potential, but not yet a live mainnet upgrade.
That is still important.
The networks that keep improving under the hood are the ones most likely to handle the next wave of demand.
This article is based on BNB Chain’s BEP-675 proposal materials.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Github. at Github
Avalanche staking value has reached about $204.77 million, while the Fuji testnet has activated the Helicon upgrade, giving AVAX watchers two separate network signals to track.
The validated notes show staked AVAX representing roughly 43% of circulating supply. The Helicon upgrade activated on Fuji testnet on July 30, 2026, while derivatives positioning remained active, with high open interest and long-to-short positioning.
The key caveat is that the $204 million figure refers to the total USD value of staked AVAX, not one whale buying $204 million worth of tokens.
That distinction matters because staking stories are often misread as accumulation headlines. This is really about network participation and upgrade progress.
For more details, visit the official Subnets platform.
TL;DR
Avalanche staking value reached roughly $204.77 million.
Staked AVAX represented about 43% of circulating supply.
The Helicon upgrade activated on Fuji testnet, not necessarily mainnet.
Staking Shows Network Commitment
Staking is one of the clearest ways to measure long-term network participation.
When users stake AVAX, they are helping secure the network and locking capital into the ecosystem. A high staked share can suggest stronger alignment between holders and network operation.
That does not automatically mean price goes up. But it can affect circulating liquidity, validator economics, and user confidence.
A 43% staked share is meaningful because it shows a large portion of supply is being used in network security rather than sitting entirely liquid.
Still, the value of staked AVAX changes with price. If AVAX price rises, the dollar value of staking rises. If price falls, the dollar value falls, even if token count stays the same.
That is why percentage of circulating supply is often more useful than the USD value alone.
Helicon On Fuji Is A Testing Step
The Helicon upgrade activating on Fuji testnet is another important detail.
Testnet activation means the upgrade is being tested in an environment designed to catch issues before broader production deployment. It is not the same as saying all mainnet users are already under the new upgrade.
That distinction keeps the story accurate.
Testnets matter because blockchain upgrades can have unexpected consequences. Validators, developers, infrastructure providers, and app teams need time to see how changes behave before mainnet deployment.
Fuji gives Avalanche a proving ground.
If the Helicon upgrade performs as expected, it can move the ecosystem closer to broader activation. If issues appear, they can be addressed before users are exposed.
Derivatives Add A Market Layer
The validated notes also point to active whale derivatives positioning, elevated open interest, and strong long-to-short data.
That suggests traders are paying attention to Avalanche around the staking and upgrade news.
But derivatives positioning can cut both ways. Heavy long positioning may show confidence, but it can also create liquidation risk if price moves against crowded traders. High open interest increases the potential for sharper moves because leverage can unwind quickly.
So the network data and market data should be read separately.
Staking and Helicon are ecosystem signals. Open interest and long-to-short ratios are trader-positioning signals. They can influence each other, but they are not the same thing.
Avalanche Is Still Building Through Infrastructure
Avalanche has been trying to differentiate itself through infrastructure, custom chains, institutional RWA activity, and developer tooling.
Staking levels and testnet upgrades support that larger story. A network does not stay competitive only by announcing partnerships. It has to keep improving performance, validator coordination, and developer experience.
Helicon’s testnet activation fits that quieter infrastructure track.
It may not attract as much attention as a token rally or a major grant announcement, but upgrades are how networks stay usable.
What To Watch Next
The next question is whether Helicon moves smoothly beyond testnet and whether staking participation remains stable.
If the upgrade path is clean and staking remains high, Avalanche can point to continued network health. If testnet issues appear or staking participation weakens, the market may become more cautious.
For now, the setup is constructive but not conclusive.
Avalanche has a large share of supply staked, a testnet upgrade underway, and active derivatives positioning. That gives traders and builders something to watch, but it does not justify turning the story into a simple price prediction.
The better read is that Avalanche’s infrastructure story is still moving, and the market is paying attention.
This article is based on Avalanche staking and Fuji testnet upgrade data for July 30–31.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Subnets. at Subnets
Login
