# Prebuilt Aztec Toolchains per Release

**URL:** https://forum.aztec.network/t/prebuilt-aztec-toolchains-per-release/7735
**Category:** Aztec
**Tags:** specs
**Created:** [April 22, 2025, 12:32pm UTC](https://forum.aztec.network/t/prebuilt-aztec-toolchains-per-release/7735 "2025-04-22T12:32:07Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![hsy822](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.aztec.network/hsy822/32/2431_2.png) [@hsy822](https://forum.aztec.network/u/hsy822)
#### Post date: [April 22, 2025, 12:32pm UTC](https://forum.aztec.network/t/prebuilt-aztec-toolchains-per-release/7735/1 "2025-04-22T12:32:07Z")

</div>

Currently, verifying contracts across multiple Aztec versions using the official releases or Docker requires building `nargo`, `bb`, and `avm-transpiler` from source for each version. This build process often takes more than five minutes per version, which adds unnecessary friction for developers who need to support multiple protocol versions or perform verification across different environments.

To improve the developer experience and reduce this overhead, I would like to suggest providing **prebuilt toolchain archives** as part of each official release. For example:

```bash
toolchain-v0.85.0-alpha-testnet.2-amd64-linux.tar.gz  
toolchain-v0.85.0-alpha-testnet.2-arm64-darwin.tar.gz

/nargo  
/bb  
/avm-transpiler  
/compile_then_postprocess.sh

```

This would ensure consistency across environments, simplify local setup, and help developers avoid rebuilding the same toolchain repeatedly.

Thank you for considering this. I believe it would be a big step forward for accessibility and trust in the Aztec development workflow.