Movement Labs
Movement Labs is building a network of Move-based blockchains. Our flagship networks are M1 and M2.
Introduction
Movement Labs is bringing Move execution to new networks and environments. Our flagship products are M1 and M2. We are also building the Movement SDK, Movement CLI, Fractal, Hyperlane messaging infrastructure, and the Movement Shared Sequencer to provide paramount interoperability between our Move-based environments and other networks.
M1 is a community-first blockchain providing the highest possible TPS through Move, instant finality, native day-zero access to mass liquidity, and modular customizations. M1 will transition into becoming a decentralized shared sequencer for the Movement network towards mainnet launch.
M2 will be the first Move Layer-2 on Ethereum. It will support Sui Move, Aptos Move, and also our embedded EVM interpreter MEVM—empowering both Sui, Aptos, and EVM users to use the L2.
Why Move?
Move is a safe and secure programming language designed by Facebook for smart contracts that emphasizes ownership and safety. Assets in Move are represented as resources. Owing to Move's strong ownership model and explicit resource abilities, Move simplifies the development of safe smart contracts for common blockchain tasks such as transfer ownership of assets, minting, and destroying. The chart below compares common non-Move runtimes against Aptos and Sui Move runtimes, underscoring the different models and benefits of Move.
Aptos / Move | Solana / SeaLevel | EVM | Sui / Move | |
Data storage | Stored at a global address or within the owner's account | Stored within the owner's account associated with a program | Stored within the account associated with a smart contract | Stored at a global address |
Parallelization | Capable of inferring parallelization at runtime within Aptos | Requires specifying all data accessed | Currently serial nothing in production | Requires specifying all data accessed |
Transaction safety | Sequence number | Transaction uniqueness | Nonces, similar to sequence numbers | Transaction uniqueness |
Type safety | Module structs and generics | Program structs | Contract types | Module structs and generics |
Function calling | Static dispatch | Static dispatch | Dynamic dispatch | Static dispatch |
Authenticated Storage | Yes | No | Yes | No |
Object accessibility | Guaranteed to be globally accessible | Not applicable | Not applicable | Can be hidden |
Last updated