❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayCryptocurrency

Cardano Opens Dijkstra Testnet While The Upgrade Itself Awaits Its Next Step

25 October 2026 at 09:00

Cardano developers now have a public environment for preparing the Dijkstra upgrade, but its name needs careful reading. The test network is available; the transition to Dijkstra’s new protocol rules is still a separate step.

TL;DR
  • Intersect’s October 24 update says the refreshed Dijkstra testnet became public on October 21.
  • It currently runs Conway protocol version 11 with node 11.1.3.
  • A later node prerelease and testnet governance action are needed for protocol version 12.

A live rehearsal environment comes before new rules

The sequence is set out in Intersect’s weekly report and the Cardano Operations Book. Pool operators can obtain configuration files, connect to the test network and use a faucet for test assets. The planned Dijkstra transition follows availability of the 11.2 prerelease and a hard-fork initiation action.

For developers, that staging creates a useful baseline. A wallet or indexer can establish that it handles the present environment correctly before it is asked to interpret changed transaction formats and protocol behavior. If everything changes at once, distinguishing an application bug from a network-upgrade problem becomes much harder.

The published node release provides the actual software reference. A version number in a roadmap should never substitute for checking which release a network configuration requires. Public test assets also have no relationship to the value of mainnet ADA.

NewsBTC has covered the same operational distinction during Ethereum’s Hoodi postponement: being ready for an earlier configuration does not guarantee readiness for the next one.

Readiness is broader than upgrading a pool

Stake pools are one part of the exercise. Exchanges need deposits and withdrawals to remain intelligible, wallets need accurate balances and signatures, and applications need their transactions to be accepted under the intended rules. A testnet gives those teams a shared place to expose mismatches before real assets depend on the answers.

It also changes what observers should measure. The number of announcements about an upgrade says little about whether independent teams have completed their checks. Useful evidence includes compatible releases, successful synchronization, working transaction submission and identified problems that have been fixed.

That is relevant to the adoption questions behind Cardano’s stablecoin activity. An application ecosystem needs reliable infrastructure as well as liquidity. Likewise, the concerns in NewsBTC’s Solana resilience coverage show why network performance is only one part of a usable platform.

The public Dijkstra environment is a tangible preparation milestone. It does not announce a mainnet activation date, establish that every proposed feature is already running, or guarantee a particular ADA price response. Its immediate value is more practical: the next round of compatibility work can happen on a network that other participants can inspect and join.

Written by the News Desk and edited by Samuel Rae.

Zcash Foundation Details Zebra Sync Fixes Ahead Of NU7 Release

22 October 2026 at 16:30

TL;DR: The Zcash Foundation says it merged fixes for Zebra nodes that stopped syncing near the chain tip. The October 21 update places the work ahead of a stable NU7 release and reminds operators of the older client’s approaching stop date.

Zcash’s preparation for NU7 includes a less glamorous but essential task: making sure nodes keep following the chain reliably.

In an engineering update published Wednesday, the Zcash Foundation described fixes for synchronization problems reported after Zebra 7.0.0-rc.0. Its team also confirmed the same underlying cause on a mainnet node.

The changes adjust how Zebra requests blocks from peers and handles failed downloads. At the time of the update, the work was merged into the development branch but had not appeared in a published release. The foundation described Zebra 7.0.0 as the likely next stable NU7 release.

Merged Code Still Has To Reach Operators

That release distinction matters. A fix being accepted into development does not mean an exchange, wallet provider or individual node is already running it.

Operators normally receive the benefit when an appropriate release is published and deployed. Services relying on their own nodes then need to establish that those nodes have caught up and continue to follow the network correctly.

The update also describes improvements to handling ZEC amounts through Zebra’s RPC types and a migration guide for services moving from zcashd’s interface. These are integration concerns that can affect the reliability of downstream systems even when they do not change what an ordinary transaction looks like.

An Approaching Operational Deadline

The foundation repeated that Zebra 6.4.x is designed to stop around November 2, making an upgrade to the NU7 release an operational requirement for affected mainnet users. The broader NU7 planning thread provides the surrounding upgrade schedule.

The October 21 report covers engineering work from October 6–19. It should be read as a dated account of readiness, not as proof that every item was already deployed across the network or that every subsequent release decision had been completed.

There is also no basis in this update for describing the synchronization issue as a theft of coins. The reported problem concerns node behavior and the work needed to deliver a stable client ahead of the upgrade.

Related Reading

This article was written by the News Desk and edited by Samuel Rae.

Solana Activates Alpenglow As Anza Targets Millisecond Finality

22 October 2026 at 12:30

TL;DR: Anza says Alpenglow activated on Solana mainnet-beta on October 21. The consensus change targets roughly 150-millisecond finality; further networking and post-quantum improvements remain planned work.

Solana has replaced the consensus protocol it used from launch, bringing a long-discussed change in transaction finality onto the live network.

Core engineering firm Anza announced the Alpenglow activation at slot 459,653,000, around 14:00 UTC on Wednesday. According to the company, validators retired TowerBFT during the transition without moving activity to a separate chain.

Finality Is The Point Of The Upgrade

Anza describes the design as reducing the path to finality from approximately 12.8 seconds to around 150 milliseconds. That is the developer’s stated performance target, not a network-wide latency measurement independently reproduced for this article.

Finality concerns when a transaction can be treated as irreversible under the network’s consensus rules. It is different from the moment a wallet displays a transaction or an application gives a user an initial confirmation.

That difference is particularly relevant to payments and trading. An interface can appear responsive before the recipient is willing to treat the transfer as settled. Shortening that second interval can reduce the period in which an exchange, merchant or application waits before acting on a payment.

It does not make every application instant. Wallet signing, internet connections, transaction inclusion and the application’s own checks still contribute to the time a user experiences. Nor does a lower finality target, by itself, establish higher transaction throughput.

More Changes Remain On The Roadmap

Anza lists Rotor, geographically aware leader rotation and the post-quantum research design Quantumglow as further developments, with no committed release dates in the announcement.

Their inclusion should not blur the scope of Wednesday’s event. Alpenglow’s activation is the completed milestone being reported; the additional work describes where the engineering team wants to take the system next.

For applications built on Solana, the practical question now is how the new consensus behaves under real traffic and varying network conditions. Operational evidence will determine how closely users’ settlement experience matches the design’s headline speed.

Related Reading

This article was written by the News Desk and edited by Samuel Rae.

❌
❌