[Mainnet][TestNet] Adhoc Release 20240328

Commit not open sourced yet, please use the pre-built binary or docker image for your deployment.

Summary: Improves the API's performance on annotating on chain move values

Commit hash: ea0b8f0ba1050a7cefd18820ef84fbbdd9210513
Docker image tag: adhoc-20240328
Digest: sha256:3ebae73b78066d0d1e8a1c36dcf57ef85585a48f42b97588fab33f2edcbb1283

Validators: REQUIRED, upgrade by April 4th, 12:00 PM PST
Full Nodes: REQUIRED, upgrade by April 4th, 12:00 PM PST

[Mainnet][Testnet] Aptos Node Release v1.10.1

Release Hash: 4174fd615d442ccac6e5d77db00ba693d0d57108

Recommended CLI Version: aptos-cli-v3.1.0

Docker Image: aptos-node-v1.10.1

Validator Update: Required by 3/27 11:59pm PST

Full Node Update: Required by 3/29 11:59pm PST

Resolved Issues

Bug Fixes

• Resolved some corner cases for the upcoming AIP-67 - Native Consensus for JSON Web Key (JWK)
• Memory improvements to the upcoming AIP-47 - Aggregators V2
• Resolved rare consensus/mempool corner cases
• Cleaning up the logs by demoting non-important error logs to warns, for better visibility of real issues
• Fix validator transaction handling for Rosetta
• Improvements/fixes to BlockSTM error handling

Improvements

• Adding new payload type called “QuorumStoreInlineHybrid”. This is used for piggybacking a few batches inline into the payload along with batches that have proof of store. The goal is to reduce the end to end latency.
• Adding gas charging for module loading of dependent modules

Full Changelog: aptos-node-v1.10.0...aptos-node-v1.10.1

Aptos CLI Release v3.1.0

aptos-cli-v3.1.0

[CLI] Bump to 3.1.0 (#12627)

Aptos CLI Release v3.0.2

aptos-cli-v3.0.2

[CLI] Bump to 3.0.2 for release (#12478)

Aptos CLI Release v3.0.1

aptos-cli-v3.0.1

Make install dir if not present in aptos update revela (#12401)

Aptos CLI Release v3.0.0

aptos-cli-v3.0.0

Update target Revela version to 1.0.0 (#12398)

Aptos CLI Release v2.5.0

aptos-cli-v2.5.0

[CLI] Upgrade processor dep to d44b2d209f57872ac593299c34751a5531b513…

[Indexer][GRPC] Upgrade to node 1.10

Release GRPC compatible with node 1.10.

Changes to the protobuf include

• A new transaction type (validator transactions)
• Remove ModuleBundlePayload - It's not used anywhere anyway
• Add new authentication types - Keyless, and R1
• Add authenticator type to signature and deprecating the old signature field that was only bytes

[Mainnet][Testnet] Aptos Node Release v1.10.0

Please update by: 3/21 5:00PM Pacific

Release Hash: b24f6cd08f84b179e49090c7e51a501c535096ca

CLI Version this release is compatible with: v3.0.2+

Validator Update Required? Y

Fullnode Update Required? Y

Aptos Improvement Proposals (AIPs)

Check out all of our AIPs and discussions here on GitHub.

Breaking Changes

• [AIP-43] Parallelize Digital Assets (Token V2) minting: Allow much higher throughput for Token V2 NFT minting/burning of a single collection.
  • Ecosystem Impact: If you are running indexer/calling fullnodes API for TokenV2 - there is a change in minting and burning events being emitted, as well in which resources token data is stored. Onchain contracts are not affected.
  • Feature Flag: concurrent_token_v2
• [AIP-64] Validator transaction type: Introduces a framework for validators to publish quorum-certified on-chain config updates with low latency.
  • Ecosystem Impact: Indexers, Explorers, SDKs need to be able to handle a new transaction type ValidatorTransaction
• [AIP-66] Passkey Accounts: Allows the user to sign transactions and create an account associated with their passkey.
  • Ecosystem Impact: Indexers, Explorers, SDKs need to be able to handle a change to the AnySignature proto type, where the signature field was deprecated and converted to a oneof signature_variant enum (see PR #12016 for more details)
  • Feature Flag: web_authn_signature

New features and enhancements

• [AIP-47] Aggregators V2: Revamped the concept of Aggregators (which are efficient concurrent counters), allowing them to be concurrently used in control flow, and “snapshots” of their values to be stored in other fields, enabling AIP-43 above, and other things to come.
  • Feature Flags: aggregator_v2_api, aggregator_v2_delayed_fields , resource_groups_split_in_vm_change_set
• [AIP-54] Object Code Deployment: Introduces a method to deploy code to objects, allowing more modular and resource efficient development. This simplifies and reduces the amount of steps necessary to deploy to accounts/resource accounts.
  • Ecosystem Impact: New CLI commands
    • CLI commands have been generated to support this feature. See detail in AIP-54.
    • Users are now able to deploy code to objects via the CLI, just how they are able to publish code to addresses/resource accounts,
  • Feature Flag: object_code_deployment
• [AIP-61] Keyless accounts: Allows users to effectively create “keyless” blockchain accounts that are secured via the user’s existing Web 2 account (e.g., their Google account) and not via a secret key, which can be lost very easily.
  • Ecosystem Impact: SDK for keyless accounts impacting Dapp and wallet developers
• [AIP-65] Storage Fee for State Bytes Refundable: Updates the Storage Fee charging scheme so that: 1. the per item 1KB free quota is removed, every byte is charged on allocation; 2. an item larger than 1KB is no longer punished by being charged storage fee every time it gets modified and 3. storage fee charged for the bytes are now refundable on item deletion, in addition to the fee for the slot allocation. Creating state items of the size between 200bytes to 4KB will see slight cost increase although the charge is now fully refundable and >1KB items are no longer punished for being modified.
  • Feature Flag: refundable_bytes
• [AIP-66] Passkey Accounts: Allows the user to sign transactions and create an account associated with their passkey.
  • Ecosystem Impact: New method for account creation and transaction signing. No SDK available yet.
  • Feature Flag: web_authn_signature
• [AIP-67] Native consensus for JSON Web Keys(JWK): Creates a flow to replicate JWKs on chain for a given list of OpenID Connect (OIDC) providers.
  • Required: [AIP-64] Validator transaction type
  • Feature Flag: jwk_consensus
• [AIP-68] Reordering transactions in a block for fairness: Updates the Transaction Shuffler logic to add other aspects of fairness to how transactions are ordered in the block by extending AIP-27 to adjacent transactions (in the proposed order) that match two new categories - module and entry function, to give transactions from non-dominant modules / entry functions a better chance of survival when a potential block cut results from the block gas limit being.
• [AIP-69] Start replication of Google JWKs on chain: Starts the replication of Google JWKs on chain, using the native JWK consensus framework.
  • Required: [AIP-67] Native consensus for JSON Web Keys(JWK)
  • Ecosystem Impact: Operators need to ensure their nodes have access to the following Google APIs: https://accounts.google.com/.well-known/openid-configuration and the jwk_uri of the response JSON from the API above

Aptos Blockchain

General

• Rust was upgraded to use the 1.75.0 toolchain version.
• Improved backpressure to be able to handle slow and poorly gas-calibrated transactions as well, keeping latency predictable.

Networking

• Implemented latency-aware peer dialing, allowing PFNs to prioritize connections to low-latency peers.

State sync

• Improved the state sync execution pipeline by adopting 4 pipelined phases (instead of 3). This improves syncing throughput and performance under load.

Configuration

• As outlined in Static Identity for Fullnodes, a fullnode will generate a random network identity if a static identity isn’t configured. This generated identity is now saved to /opt/aptos/data/ephemeral_identity_key so it will be retained after any restarts.

  • Use this command to retrieve your generated peer ID:

  aptos key extract-peer --host 1.1.1.1:6180 \
      --private-network-key-file /opt/aptos/data/ephemeral_identity_key \
      --output-file /path/to/peer-info.yaml

Move

VM

• Added a cache to avoid re-verifying previously verified Move modules during loading.
• Improved performance with per-frame cache for paranoid mode
• Introduced a new native ValueImpl which the aggregator can use to define custom serialization/deserialization logic.
• Improved devs debugging through refactoring of errors and error forwarding

Gas

• Improved the gas-calibration code
• Added gas charge for type creation
• Added a new binary remote-gas-profiler to the aptos-debugger crate. The tool allows devs to generate a gas profiling report for a transaction on chain.

Resolved Issues

Bug Fixes

• Added new local cache to prevent unneeded operations during Move modules' bytecode verification.
• Enabled the max object nesting check, preventing running out of gas due to ownership cycles
  • Feature flag: MAX_OBJECT_NESTING_CHECK
• Fixed the race condition with the order of operations
• Fixed VM error resolver. Errors are now propagated from where they originated and are not ignored.

[Mainnet][Testnet] Aptos Node Release v1.9.7

What's Changed

• [Execution] Increase the default concurrency to 32 by @sitalkedia in #12211
• [consensus] fix the race condition with the order of operations by @zekun000 in #12251

Full Changelog: aptos-node-v1.9.5...aptos-node-v1.9.7

Upgrade requirement

• Validators: required, upgrade before 2/28 end of day
• Fullnodes: optional