Chore/merge develop to aac client breaking

.github/workflows/image-build-source.yml

@@ -8,7 +8,7 @@ on:
 
 ## Define which docker arch to build for
 env:
-  docker_platforms: "linux/amd64"
+  docker_platforms: "linux/amd64,linux/arm64"
   docker-org: blockstack
 
 concurrency:
@@ -69,7 +69,6 @@ jobs:
             STACKS_NODE_VERSION=${{ env.GITHUB_SHA_SHORT }}
             GIT_BRANCH=${{ env.GITHUB_REF_SHORT }}
             GIT_COMMIT=${{ env.GITHUB_SHA_SHORT }}
-            TARGET_CPU=x86-64-v3
           push: ${{ env.DOCKER_PUSH }}
 
       ## Generate docker image attestation(s)

CHANGELOG.md

@@ -5,12 +5,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to the versioning scheme outlined in the [README.md](README.md).
 
-## Unreleased
+## [Unreleased]
+
+### Added
+
+- Added support for new Clarity 4 builtin, `secp256r1-verify?` (not activated until epoch 3.3)
+
+### Added
+
+- New `block_proposal_validation_timeout_secs` configuration option in the connection options section, allowing to set the maximum duration a node will spend validating a proposed block.
 
 ### Changed
 
 - Renamed Clarity 4's new `block-time` to `stacks-block-time`
 - Improve cost-tracking for type-checking function arguments in epoch 3.3 (see [#6425](https://github.com/stacks-network/stacks-core/issues/6425))
+- Replaced `libsecp256k1` with `k256` and `p256` from RustCrypto and removed separate Wasm implementations.
 
 ## [3.2.0.0.2]
 

clarity-types/src/errors/mod.rs

@@ -44,7 +44,7 @@ pub struct IncomparableError<T> {
 
 /// Errors that can occur during the runtime execution of Clarity contracts in the virtual machine.
 /// These encompass type-checking failures, interpreter issues, runtime errors, and premature returns.
-/// Unlike static analysis errors in `ClarityError::StaticCheck(CheckError)` or `ClarityError::Parse(ParseError)`,
+/// Unlike static analysis errors in `ClarityError::StaticCheck(StaticCheckError)` or `ClarityError::Parse(ParseError)`,
 /// which are caught before execution during type-checking or parsing, these errors occur during dynamic
 /// evaluation and may involve conditions not detectable statically, such as dynamically constructed expressions
 /// (e.g., based on VRF seeds or runtime data).