maidsafe/autonomi stable-2025.12.2.1

2025.12.2.1

on GitHub

Binary Versions

• antnode: v0.4.11
• antctld: v0.14.1
• antctl: v0.14.1
• ant: v0.4.14
• evm-testnet: v0.1.17
• nat-detection: v0.2.22
• node-launchpad: v0.6.1

Binary Hashes

x86_64-pc-windows-msvc

x86_64-apple-darwin

aarch64-apple-darwin

x86_64-unknown-linux-musl

arm-unknown-linux-musleabi

armv7-unknown-linux-musleabihf

aarch64-unknown-linux-musl

Merged Pull Requests

2025-12-16 #3363 -- fix(ci): put latest mac intel runner [@vphongph]
2025-12-16 #3322 -- feat(node): carry out fetch check among closeup peers and block bad ones [@maqi]
2025-12-16 #3360 -- chore(deps): bump actions/cache from 4 to 5 [@dependabot[bot]]
2025-12-16 #3361 -- chore(deps): bump actions/download-artifact from 6 to 7 [@dependabot[bot]]
2025-12-16 #3362 -- chore(deps): bump actions/upload-artifact from 5 to 6 [@dependabot[bot]]
2025-12-16 #3365 -- fix(client): during mutable data reupload, shall use same quoting range [@maqi]
2025-12-16 #3346 -- feat(node): skip replication once closeup peer restart pattern detected [@maqi]
2025-12-17 #3372 -- Refactor node merkle topology verification [@mickvandijke]
2025-12-17 #3373 -- chore(client): make get_storage_proofs_from_peer return PaymentQuote [@maqi]
2025-12-18 #3374 -- fix: macos services stop on anctl stop [@jacderida]
2025-12-18 #3358 -- feat: clear NodeRegistryManager during reset op [@RolandSherwin]
2025-12-18 #3367 -- refactor(ant-node): increase KAD_QUERY_TIMEOUT_S from 10s to 120s [@mickvandijke]

Detailed Changes

API

Changed

• Client::get_storage_proofs_from_peer method signature now requires two additional parameters:
  data_type: DataTypes and data_size: usize. The return type has also changed from
  Vec<(NetworkAddress, Result<ChunkProof, Error>)> to PeerQuoteWithStorageProof, which includes
  an optional PaymentQuote alongside the storage proofs. [BREAKING]

Network

Added

• Retry logic with exponential backoff to closest peers lookup operations, improving robustness when
  querying the network.
• Support for querying a specific number of closest peers, providing more control over network
  queries.
• Bad peer detection system that verifies fetched record copies match expected values and blocks
  peers that fail validation checks.
• Metrics tracking for bad peers to monitor network health.

Changed

• Node and client now use the same network get_closest scheme for consistent peer resolution
  across the network.
• Blocklist behaviour is limited to prevent unlimited growth by using a circular buffer mechanism.
• Record store indexing cache is now pruned to remove out-of-sync entries and improve accuracy.
• Replication is skipped when a close-up peer restart pattern is detected to reduce unnecessary
  network traffic.
• Increased KAD_QUERY_TIMEOUT to 120 seconds from 10 seconds. Improves node-side KAD query
  reliability and should prevent GetClosestTimeout errors when doing get_closest_peers lookups.

Fixed

• Record copy verification now ensures fetched records match the expected content before accepting
  them.
• Peers that have been dropped from the routing table are no longer blocked during recheck
  operations, preventing false positives in bad peer detection.
• Client get_closest check now returns more consistent results across multiple queries.
• Client operations no longer miss existing copies when verifying data storage.
• Mutable data re-uploads now use the same quoting range consistently.

Antctl

Fixed

• Services now stop correctly on macOS when using the antctl stop command. The underlying service
  manager crate was incorrectly specifying an 'on success' restart policy that prevented proper
  service termination.
• Services no longer start automatically when added with the antctl add command on macOS, restoring
  expected behaviour consistent with other service managers.
• Node registry manager is now properly cleared during reset operations, preventing phantom nodes
  from appearing after reset.

Launchpad

Fixed

• Input mode now only switches when error popup is dismissed, preventing unintended mode changes.
• Node registry is properly synchronized between local storage and in-memory representation after
  reset operations.