Concordium Smart Contracts VS Code extension updates to version 3.0.1

The Concordium Smart Contracts extension for Visual Studio Code jumped to version 3.0.1, adding native Apple Silicon (ARM64) binaries for cargo‑concordium and updating the bundled tooling to cargo‑concordium 4.0.0 and @concordium/ccd‑js‑gen 1.2.1 [1].

New tooling and platform support

The latest release swaps the previous x86_64 build for an ARM64 binary on macOS, meaning developers using Apple Silicon can compile and test Concordium contracts without Rosetta translation [1]. The bundled cargo‑concordium tool jumps from version 3.2.0 (in 2.2.0) to 4.0.0, and the JavaScript/TypeScript client generator upgrades to @concordium/ccd‑js‑gen 1.2.1, providing more recent language features and bug fixes [1].

Core commands and settings

The extension continues to expose VS Code commands for initializing a contract project, building, testing, and generating TypeScript/JavaScript clients [1]. Users can still override the bundled executables with custom paths via settings such as concordium-smart-contracts.custom-executable and concordium-smart-contracts.custom-ccd-js-gen-executable, allowing integration with locally‑installed cargo‑concordium or ccd‑js‑gen versions [1].

Compatibility with Concordium’s contract engine

Concordium’s on‑chain smart‑contract engine supports two versions: legacy v0 and the newer v1, which uses a trie‑based state for efficient partial updates [2]. While the extension itself does not enforce a contract version, the bundled cargo‑concordium 4.0.0 aligns with the v1 engine, enabling developers to target the more capable contract model [2][1].

What to watch

• Future releases – watch for version 3.1.0, which may add support for additional platforms or further upgrades to cargo‑concordium.
• Contract version adoption – monitor the proportion of new contracts using v1 versus v0 on‑chain, as the tooling shift encourages migration to the more efficient trie‑based model.
• Custom executable paths – developers may configure alternative cargo‑concordium binaries; any breaking changes in those binaries could affect build or test workflows.

The extension’s ARM64 support removes a major friction point for macOS developers, signaling Concordium’s commitment to keeping its developer ecosystem current with evolving hardware trends. The next step will be how quickly the community adopts the newer v1 contract model using these updated tools.