# Monad Foundry Toolkit

**URL:** <https://forum.monad.xyz/t/monad-foundry-toolkit/412>\
**Category:** Announcements\
**Tags:** toolings\
**Created:** [March 27, 2026, 5:17am UTC](https://forum.monad.xyz/t/monad-foundry-toolkit/412 "2026-03-27T05:17:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![haythemsellami](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haythemsellami](https://forum.monad.xyz/u/haythemsellami)\
**Post date:** [March 27, 2026, 5:17am UTC](https://forum.monad.xyz/t/monad-foundry-toolkit/412/1 "2026-03-27T05:17:19Z")

</div>

# Monad Foundry v1.5.0-monad.0.3.0

This release introduces `MonadNine` as the default Monad execution hardfork and brings MIP-3, MIP-4 and MIP-5 support through upgrades to `monad-revm 0.3.0` and `alloy-monad-evm 0.3.0` .

It also makes Monad hardfork selection a first-class Foundry feature through the new `monad_hardfork` option in `foundry.toml`, and both the standard `anvil --monad --hardfork` flag, and `vm.setEvmVersion()` cheatcode.

Update by running `foundryup --network monad`.

Full release note and changelog: [https://github.com/category-labs/foundry/releases/tag/v1.5.0-monad.0.3.0](https://github.com/category-labs/foundry/releases/tag/v1.5.0-monad.0.3.0)

---

<div class="post-metadata">

**Author:** ![haythemsellami](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haythemsellami](https://forum.monad.xyz/u/haythemsellami)\
**Post date:** [July 11, 2026, 1:04am UTC](https://forum.monad.xyz/t/monad-foundry-toolkit/412/2 "2026-07-11T01:04:34Z")

</div>

# Monad Foundry v1.7.1-monad-v1.0.0

This release does not introduce new Monad VM functionality compared with the previous  
[`v1.5.0-monad.0.3.0`](https://github.com/category-labs/foundry/releases/tag/v1.5.0-monad.0.3.0)  
release.

The main change is an internal port of the existing Monad integration onto the new generic  
network and EVM architecture introduced by upstream Foundry v1.7.0. This architecture makes  
Foundry’s Forge, Cast, Anvil, Chisel, cheatcode, script, and EVM execution paths generic across  
different networks.

> Existing Monad `foundryup` installations using the legacy `1.5.0` version must reinstall the  
> launcher once:
> 
> ```sh
> curl -L https://foundry.category.xyz | bash
> 
> ```
> 
> The legacy updater only understands `major.minor.patch` versions and cannot self-update to the  
> new `1.5.0-monad-v1.0.0` version scheme. After this one-time reinstall, future launcher updates  
> can use `foundryup --update` again.

More details in [Release v1.7.1-monad-v1.0.0 · category-labs/foundry · GitHub](https://github.com/category-labs/foundry/releases/tag/v1.7.1-monad-v1.0.0)