Testnet v1.1.0

Release candidate notes for v1.1.0

snarkVM Consensus Changes

The most consequential change in this release is that a consensus update is going to take place, introducing two features requested by many members of the Aleo community:

• Use timestamp-based block_reward and coinbase_reward algorithms (instead of height-based) for more accurate rewards emission. ARC42 - AleoNet/snarkVM#2569
• Reduced mapping base cost from 10,000 to 1,500 microcredits for GET operations based on benchmarked runtime performance, optimizing chain economics while maintaining safety margins. AleoNet/snarkVM#2564

The consensus changes will occur at the following blocks:

• Canary - Block 2,900,000
• Testnet - Block 2,950,000
• Mainnet - Block 2,800,000

ATTENTION: Validators that do not upgrade in time will be at risk of forking and require manual intervention. Clients that do not upgrade will be at risk of halting until an upgrade occurs.

Other important changes

• The CDN has been created and updated for all of the Aleo networks. snarkOS#3348.
• The --seed flag was removed from the snarkos account sign command, because it exposes users to unsafe behavior. snarkOS#3382.
• Deprecated REST endpoints were removed. snarkOS#3347.
• A new REST endpoint to GET mapping values was added. snarkOS#3365.
• Fixes the --rest-rps flag to parse the given rate limit as you would expect it to. snarkOS#3405.
• Adding private key file support for secure program execution. snarkOS#3429.
• Fixed JSON serialization of u128 elements. snarkVM#2559.
• Limit parallel processing of transmissions in clients to prevent OOM crashes. snarkOS#3358.
• Periodically process transmissions in the mempool. snarkOS#3421.
• Mitigate network spam by banning misbehaving IPs. snarkOS#3422.

Full Changeset

Many more documentation, performance and stability improvements were made. For a full overview of the merged changes, we invite you to dive into the following intermediary canary releases:

• Canary release week 24.43 - v1.1.1 in #3419
• Canary release week 24.44 - v1.1.2 in #3426
• Canary release week 24.45 - v1.1.3 in #3431
• Canary release week 24.46 - v1.1.4 in #3436

New Contributors

• @bendyarm made their first contribution in #3373
• @JakkuSakura made their first contribution in #3337
• @fulltimemike made their first contribution in #3405

Full Changelog: testnet-v1.0.0...testnet-v1.1.0

v2.2.7

chore(snarkos): bump version for new release

v2.2.6

chore(snarkos): bump version for new release

v2.2.5

chore(snarkos): bump version for new release

v2.2.4

chore(snarkos): bump version for new release

v2.2.3

chore(snarkos): bump version for new release

v2.2.2

chore(snarkos): bump version for new release

v2.2.1

chore(snarkos): bump version for new release

v2.1.7

Changelog

With this update, to pass in a private key via the command line (CLI), please now use:

--private-key {PRIVATE_KEY}

It is now advised to use a file, whose path can be defined with:

--private-key-file {PRIVATE_KEY_PATH}

The path must lead to a file that contains just the private key in string format (i.e. APrivateKey1...).

v2.1.6

chore(snarkos): bump version for new release