Movement Labs announced a $38 million Series A on April 25, 2024, led by Polychain Capital, to build an Ethereum-focused execution environment using Move and the Move Virtual Machine (MoveVM). The original pitch combined Move’s resource-oriented programming model with Ethereum’s liquidity, applications and settlement ecosystem. At announcement, the flagship product was described as M2, a MoveVM-based Ethereum Layer 2, with a reported design target above 30,000 transactions per second (TPS).
That description is now historical context rather than a complete account of the project. Movement later launched public networks and, in December 2025, Move Industries announced a migration to M1, a sovereign Layer 1. Current documentation is not perfectly consistent: some pages still describe an Ethereum L2 while newer materials describe the L1 architecture.
The deal in brief
| Item | What was announced |
|---|---|
| Date | April 25, 2024 |
| Round | Series A |
| Amount | $38 million |
| Lead investor | Polychain Capital |
| Other named participants | Hack VC, Placeholder, Archetype, Maven 11, Robot Ventures, Figment Capital, Nomad Capital, Bankless Ventures, OKX Ventures, dao5 and Aptos Labs |
| Stated use of funds | Hiring, developer tooling, developer education and ecosystem expansion |
The financing was a bet that developers would value Move’s asset-safety model without giving up Ethereum’s network effects. It was not proof that the proposed network had achieved its performance or security goals.
CoinDesk’s funding report covered the round and its Ethereum-rollup thesis. Aptos Labs’ participation was notable because Aptos is a separate, prominent Move ecosystem, but that investment does not independently validate Movement’s technology or business prospects.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Move, MoveVM, Aptos and the EVM are different things
Move is the programming language
Move originated in Meta’s Libra/Diem blockchain project and was later adopted by projects including Aptos. It is an open-source smart-contract language built around digital resources, ownership and controlled asset movement. Calling it simply “Facebook’s blockchain” is misleading: Meta created the original technology context, but Movement is not a Meta-operated cryptocurrency.
MoveVM executes Move programs
MoveVM is the virtual machine that runs compiled Move bytecode. It is comparable in role to Ethereum’s Virtual Machine, but it is not the EVM and does not execute ordinary EVM bytecode by default.
Aptos is a separate blockchain
Aptos uses Move, but Aptos and Movement are separate networks with different architecture, teams and economic models. Sui is another distinct Move-family ecosystem; its object-centric design is not interchangeable with either Aptos or Movement.
The EVM is Ethereum’s native execution environment
Ethereum’s EVM is principally associated with Solidity and EVM bytecode. When Movement coverage uses terms such as “EVM-compatible,” readers should ask whether compatibility means source-level tooling, a translator, an adapter or literal bytecode execution. Existing Solidity contracts should not be assumed to deploy unchanged.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Why put Move next to Ethereum?
Movement’s argument was that Ethereum supplies deep liquidity, applications, developers and a valuable settlement ecosystem, while Move supplies a different programming and execution model.
Resource and ownership semantics
Move treats assets as resources whose ownership and movement are explicitly controlled. That design can constrain accidental copying, duplication or unauthorized access to assets more directly than conventional application code.
Reentrancy-related protections
In a classic reentrancy attack, a contract makes an external call before completing its own state updates. An attacker re-enters while the state is inconsistent and exploits that intermediate condition. Move’s resource and ownership rules are designed to prevent or constrain some patterns of unsafe asset access and control flow.
That is narrower than saying Move eliminates hacks. Move cannot correct faulty business logic, manipulated oracles, governance attacks, bad access control, unsafe upgrades, compromised bridges, vulnerable wallets, compiler bugs or flawed surrounding infrastructure. Movement representatives attributed broad reductions in common Solidity attack classes to Move; those are claims by the project, not an independent guarantee.
Parallel execution
Movement promoted Block-STM or related execution technology to process transactions in parallel when their state access is sufficiently independent. That can improve throughput for suitable workloads. Applications with heavy contention around the same pool, account, counter or other shared state may see less benefit.
What M2 and Move Stack meant in 2024
M2: the original Ethereum-facing network
At the time of the financing, M2 was described as a MoveVM-based Ethereum Layer 2. The intended flow was for users to submit transactions to Movement, have them executed with MoveVM, and use a settlement and data-publication design tied to Ethereum. “Ethereum security” in that context needed to be unpacked: settlement, data availability, bridges, sequencers and validators can each have different trust assumptions.
The proposal aimed to let Ethereum users access Move-native execution without moving to a completely unrelated liquidity ecosystem. It did not mean that every Solidity application was drop-in compatible.
Move Stack: a framework, not a single chain
Move Stack was presented as a modular framework for building Move-based rollups or execution environments. Movement materials discussed compatibility with rollup ecosystems associated with Optimism, Polygon and Arbitrum. In this context, “compatible” describes an intended technical integration or shared design direction, not proof that every component was live in April 2024.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesLater specifications described selectable data-availability services, including Celestia, and possible sequencer designs such as a decentralized shared sequencer. Those later specifications should not be read back into the original funding announcement as production features.
What the TPS numbers actually say
| Figure | Meaning and limitation |
|---|---|
| More than 30,000 TPS (2024) | Reported design or engineering target for the proposed system; not independently verified sustained mainnet throughput in the cited coverage. |
| More than 160,000 TPS (2025) | Movement’s theoretical capability claim for MoveVM and Block-STM in the Public Mainnet Beta; not directly comparable with the 2024 figure. |
A TPS number is useful only with its workload, transaction size, hardware, validator or sequencer count, confirmation definition, failure rate and whether settlement and data publication are included. Synthetic execution throughput is not the same as application throughput, Ethereum settlement throughput or bridge capacity. The 2024 and 2025 figures therefore should not be combined into a claim that “Movement processes” a single number of TPS.
The contemporary 30,000-TPS report appears in Cointelegraph’s coverage. Movement’s later Public Mainnet Beta announcement reports the theoretical 160,000-plus figure at movementnetwork.xyz.
What happened after the funding
- April 25, 2024: Movement announced its $38 million Series A.
- July 2024: Movement described the Parthenon public testnet and developer and user onboarding plans in its testnet materials.
- November 30, 2024: Movement Mainnet Beta began; the announcement was published December 5.
- November 25, 2024: The Movement Foundation disclosed the $MOVE token design, including a maximum supply of 10 billion.
- January 27, 2025: Developer Mainnet launched.
- March 10, 2025: Public Mainnet Beta opened permissionless deployment and user onboarding.
- December 22, 2025: Move Industries announced M1, a sovereign Layer 1, and a migration away from the earlier Ethereum-L2 model.
The relevant announcements are the Mainnet Beta release, Developer Mainnet release, $MOVE disclosure and the M1 announcement.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Why the L2-to-L1 change matters
An Ethereum rollup and a sovereign Layer 1 are not interchangeable labels. An L2’s security story centers on how it posts data and commitments to Ethereum, how disputes or proofs work, and how users exit. A sovereign L1 instead has its own validator, staking, consensus, data-availability and governance assumptions. Its bridge to Ethereum is an interoperability component, not automatically Ethereum settlement.
The M1 announcement therefore changes the original investment thesis. Readers evaluating the current network should examine validator economics, native staking, data availability, bridge contracts, token roles and upgrade authority rather than relying only on 2024 descriptions. Movement’s current L1 documentation and its public GitHub repository use architecture labels that are not fully consistent, so the release and deployment being evaluated should be identified explicitly.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Trade-offs for developers, users and investors
Move safety versus ecosystem maturity
Move may provide stronger asset semantics, but the EVM has a much larger pool of Solidity developers, auditors, libraries, wallets, exchanges, indexers and battle-tested production code. A language-level advantage does not remove the cost of learning a new language or rebuilding tooling.
Ethereum access versus infrastructure dependence
An Ethereum connection can expose applications to established liquidity, but bridges, sequencers and data-availability providers add failure modes. Users may face withdrawal delays, limits, fees or smart-contract risk. Early networks may also rely on centralized or permissioned sequencing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Parallel execution versus workload reality
Parallelism helps when transactions touch separate state. A highly contested automated market maker or shared accounting contract may serialize much of its activity, reducing the practical gain relative to a laboratory result.
EVM compatibility versus native Move design
Translation or adapter layers can accelerate adoption, but they may create semantic mismatches, incomplete library support, debugging difficulties and unclear audit boundaries. Teams should test the exact compiler, SDK, wallet and contract path they plan to use.
Token and liquidity risk
If $MOVE is used for gas, staking or security in the relevant release, token economics become part of operating the network. A new execution environment can also fragment liquidity from Ethereum, Aptos, Sui and other chains.
What to verify before building or using Movement
- Which release and architecture are being evaluated: the original M2 L2 design or M1’s sovereign L1.
- Whether required Solidity contracts work through a translator, adapter or not at all.
- Availability of native Move compilers, debuggers, SDKs, auditors and indexers.
- Bridge withdrawal times, limits, fees, contracts and security history.
- Sequencer and validator permissions, decentralization plans and upgrade keys.
- Data-availability provider, publication costs and recovery procedures.
- Independent benchmarks that disclose workload, hardware and settlement conditions.
- Wallet, exchange, RPC and monitoring support in the user’s jurisdiction.
- $MOVE’s actual utility, supply schedule and governance role for the network being used.
Bottom line
Movement’s 2024 financing was a significant bet on combining Move’s resource-oriented programming model with Ethereum’s network effects. The strongest case was not that Move makes protocols safe automatically, nor that headline TPS figures represented production capacity. It was that a different execution environment might offer useful asset-safety properties and parallelism while remaining connected to Ethereum’s developer and liquidity base.
That thesis must now be date-stamped. Public networks launched during 2024 and 2025, and the December 2025 M1 announcement moved the project toward a sovereign Layer 1. Evaluate the specific release, benchmark methodology, bridge and validator assumptions—not just the $38 million round or the original Ethereum-L2 headline.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
