Welcome to the next crypto level
← Nexorena

Blockchain

Quicknode completes snarkOS 4.13.0 deployment on its Aleo testnet infrastructure

Quicknode confirmed the end of maintenance at 12:59 a.m. Paris time on November 18. The release remains compatible with 4.12.x nodes on the testnet and prepares integrations for REST API v2.

Nexorena Editorial Team

Quicknode completes snarkOS 4.13.0 deployment on its Aleo testnet infrastructure

Quicknode finishes maintenance on the test network

Quicknode said it completed the deployment of snarkOS testnet-v4.13.0 on its Aleo testnet infrastructure. Its completion notice is dated November 17 at 11:59 p.m. UTC, or November 18 at 12:59 a.m. in Paris. The provider announced the maintenance on November 10. Its confirmation covers its own services. The software release and the completion of deployment at Quicknode are separate milestones.

The snarkOS release notes say this version is built against snarkVM v4.13.0-rc.1 and keeps the existing consensus rules. There is no activation height for this testnet update. Nodes on 4.12.x and 4.13.0 remain compatible on the same network, so operators can choose when to upgrade. The notes describe bringing these changes to mainnet in a separate release after they have been accepted on the test network.

REST clients have a transition path to v2

The project’s release notes say REST API v1 and unversioned paths continue to respond. Their responses include headers that mark those paths as deprecated and direct integrations to v2. The snarkOS developer commands now use version 2 by default. If the URL supplied does not specify a version, the command appends that path. Those commands reject URLs containing a query string.

JSON responses now use a compact representation. The server can also compress them with gzip when the client requests it. These changes affect how a client receives data and specifies an endpoint. They are separate from the rules that determine block validity. The release notes point developers who maintain REST integrations to a dedicated migration guide.

Validators check their peers’ upgrade plans

The release adds a check when validators connect. They share the schedules of consensus versions they expect to support. If a committee member announces a version the validator’s software does not support, the validator can stop before activation and leave a notice in its data directory. This mechanism is intended to prevent the validator from continuing to build blocks that would be rejected after the rule change.

The maintainers say this stop condition does not currently trigger on the test network, where nodes share the same schedule. The release also changes synchronization to request again any blocks a reachable peer failed to provide. Quicknode had said brief service interruptions were possible during maintenance. Its completion notice confirms the end of the work without specifying how many nodes were involved or measuring any interruptions.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena