Latest blockchain news: July 2026

July left a clear signal: many of the sector's most relevant conversations are no longer only about new narratives, but about the infrastructure required to bring them into production.

This month, we saw products that bring staking into third-party experiences, tools that reduce friction for node operators, and network changes that require validators and technical teams to prepare in advance. The layers Ethereum needs to support institutional activity also continued to mature.

Here is our selection of the developments that stood out most.

At Stakely, we launched the Staking Widget, a solution that lets teams embed a non-custodial, customizable, ready-to-use staking experience directly into their own product.

The widget brings together the interface, staking logic, and transaction flows without requiring teams to build every layer from scratch. For a product already working with digital assets, it creates a way to add staking to the experience, keep the user relationship within its own environment, and reduce integration work. Our article on the Staking Widget explains the model in more detail.

We also made a free service of daily snapshots available to the GenLayer community. A snapshot lets an operator restore a node database from a recent state rather than synchronizing the entire network from scratch. It is not the most visible kind of improvement, but it is a practical one for teams deploying, recovering, or testing infrastructure. In a growing network, reducing that friction can make an operator's work considerably easier.

We also announced that Stakely is joining Alpen as an external operator. During Alpen Testnet III, we are participating in the verification of deposits and withdrawals that move BTC between Bitcoin and Alpen's execution environment. It is particularly sensitive infrastructure work, and reflects a growing part of what we do: participating from early stages in networks where availability, reliability, and technical correctness support high-value services.

Finally, July was particularly interesting for the conversation around Ethereum and institutions. In our analysis of Ethereum's institutional infrastructure phase, we explored how privacy, standards, custody, and operations are no longer separate topics. For an institution to use Ethereum in production, all of these layers need to work together.

This month, Solana progressed one of the prerequisites for its future consensus evolution with Alpenglow: on-chain BLS public-key registration by validators.

The Solana Foundation guide on BLS Pubkey and the Validator Admission Ticket presents this registration as the cryptographic requirement for the Validator Admission Ticket, or VAT. It is not the same as activating Alpenglow; it is a prior component that determines who will be able to participate in consensus once that mechanism is enabled.

The operational implication is straightforward. Validators that do not register a BLS pubkey before VAT activation will not be able to participate in consensus or receive the associated inflation rewards and block fees. The design also introduces an admission cap, so this should not be treated as just another client upgrade.

This is a useful reminder: network upgrades do not begin when a feature activates. For operators, they begin earlier, with monitoring, testing, and orderly infrastructure preparation.

Avalanche activated Helicon on Fuji on July 28, opening a testing phase before a future mainnet deployment.

The proposed changes include several with direct implications for validator operations: auto-renewal for a validator's own stake, a reduction in the minimum validation period from 14 days to 48 hours, a 90% uptime threshold, and reward-curve adjustments.

One nuance is important: auto-renewal applies to the validator's own stake, not to delegations. Still, the combined changes point to an interesting direction: reducing entry friction without relaxing availability requirements.

We are preparing a dedicated article on Helicon because it deserves a deeper look through the lens of staking and operations. For a Monthly Review, the takeaway is simpler: before mainnet is discussed, the priority is to see how these changes behave on testnet and what adjustments they require from operators.

Sui has also moved a less visible but essential piece for technical teams: its data stack.

The Sui Foundation has started the gradual retirement of JSON-RPC on its mainnet full nodes, directing developers and infrastructure providers toward gRPC, GraphQL, and the Archival Store. The process begins during the week of July 27, with full retirement planned for mid-October.

This is not a consensus change or a new application, but it affects how wallets, indexers, explorers, and other services query network data. For any team relying on Sui endpoints, it is a transition worth planning in advance: review dependencies, adapt integrations, and avoid allowing compatibility to become a last-minute incident.

July's common thread is clear: a staking experience needs a usable integration; a new network needs tools that help operate nodes; and protocol upgrades need teams that prepare before their activation date.

Infrastructure is not only what happens beneath an application. It is what determines whether an idea can move from demo to product, from testnet to mainnet, or from institutional interest to sustained operations.

We will continue following these developments throughout August, especially Helicon's progress on Avalanche and Solana's next steps toward Alpenglow.