Skip to main content
The Modular Execution Environment (MEE) supports multiple versions of its contract suite. Each version introduces new capabilities around smart accounts, validator configuration, and composability.
This guide helps SDK developers understand and select the appropriate version for their use case.

​
Versions Table

The table below outlines all supported MEE versions and their core capabilities. Use this to determine the best version for your project based on EVM support, composability, and ERC-7702 compatibility.

​
Version Breakdown

!!

​
Experimental and unaudited

Unlocks cross-chain orchestration for Safe accounts

Key Features:
  • Safe accounts can now be used as master accounts in Fusion flow as well as EOAs.
    • Flow is the same as for EOA’s, just instead of one master EOA signature, the proper multisig is required to initiate a SuperTxn
    • Safe accounts should be deployed at the same address on all the chains involved in the SuperTxn (source and destination chains)
Recommended for projects on early stages looking to attract the large Safe multisig accounts userbase.

​
Recommendation

Use 2.2.3 for new accounts. It is the only version built on Nexus 1.3.3, and version ordering does not indicate which suite to use: 2.3.0 sorts above it but is a release candidate on Nexus 1.3.1. Earlier versions remain available so that accounts already created on them stay derivable and upgradeable. They are not a starting point for new integrations.

​
How to Find Your Current Nexus Version

Not sure which Nexus version your smart account is using? Follow these simple steps to find out:
1

Locate your smart account address

Locate your existing Nexus smart account address on the specific blockchain you’re working with.
2

Open the block explorer

Open the block explorer for that chain (e.g., Etherscan, Polygonscan) and paste the smart account address into the search bar.
3

Navigate to the Contracts tab

Navigate to the Contracts tab on the explorer page.
4

Verify the proxy contract if needed

If the contract is a proxy and the proxy contract isn’t verified yet, you’ll need to verify it first. (If “Read as proxy” option isn’t available, this usually means verification is needed.)
5

Call the getImplementation function

Once verified, go to the Read as proxy section and call the getImplementation function. This will return the address of the actual implementation contract your smart account is using.
6

Compare with official addresses

Compare this implementation contract address against the addresses listed on our Contracts and Audits page. This will help you identify exactly which MEE version you are using.
If you need further assistance, feel free to join our Discord community and ask for help!
Keeping track of your Nexus version is key for smooth upgrades and compatibility checks.

​
Not Sure Which Version to Choose?

If you’re still confused about which MEE version fits your needs, or if you’re unsure about your current version for migration, don’t worry! Join our Discord community to ask questions and get real-time support from the team and other developers. We’re here to help you choose the best path forward!