Website catalogue: 151 chains. Current AI connection: 14 chains; approved accounts only.

Layer 1 blockchain

Movement ticker MOVE

  • No public-data lookups yet
  • 5 reviewed developments
  • 40 cited sources

Summary

Proof-of-stake BFT chain built on a Movement fork of the Aptos node software. The whitepaper describes a protocol based on Jolteon (a HotStuff variant): a stake-weighted rotating leader proposes each block, validators holding more than two-thirds of voting power certify it, and it commits once a short chain of certified blocks builds on it, tolerating fewer than one-third faulty. Block-STM executes transactions in parallel. On 27 September 2026 the on-chain validator set had four active validators with near-equal voting power, and the docs say running a validator node is not supported yet. Slashing is defined in the protocol but not active. Epochs last two hours; on-chain staking settings require at least 100,000 MOVE per validator and a 14-day lockup. 234715162028

Design

System
Layer 1 blockchainMovement's current chain (M1, chain ID 126) runs its own proof-of-stake validators and BFT commit rule and settles to no other chain; Ethereum is linked only through a token bridge. It launched in December 2024 as an Ethereum-anchored network with one leader node, and its October 2025 MiCA white paper still called it a side chain run by Movement Labs. Move Industries announced the Layer 1 mainnet live on 22 December 2025, saying funds, contracts and activity carried over without user action, and on 29 December 2025 the foundation called the transition complete.
Settlement family
Its own design
Scarce resource
Stake (proof of stake)
State model
Accounts
Finality
Other
Who makes blocks
One leader per round, taken from a fixed per-epoch order weighted by stake (the whitepaper also mentions reputation). Four validators were active on 2026-09-27. Movement's liquid staking post says it delegates to the Foundation-operated validator; the operators of the other three were not disclosed in reviewed sources.
Fork choice
No open weight-based fork choice: a block is final once the commit rule is met, which requires certificates from validators holding more than two-thirds of voting power. Movement's own pages disagree on whether a two-chain or three-chain commit rule applies. With four validators, one faulty validator is tolerated, and two offline validators stop new blocks from committing.

Qualifications

Tradeoffs

This view follows one way of thinking about design priorities, often called the blockchain trilemma. The design-priorities lesson sets out the counter-view. Read the design-priorities lesson.

Emphasizes
Scalability
Gives up
Decentralization. Four validators produce every block, all four register network addresses on AWS load balancers in a single region (us-east-1), the public cannot yet run a validator, and upgrades appear to run through an administrative account rather than token-holder votes. Two validators going offline together would halt commits.Safety rests on no more than one of four validators misbehaving, with no active slashing to penalize double-signing. The single-region reading comes from on-chain validator configuration, not an operator disclosure, and can change.
Full node at home
Unknown 891020Movement publishes storage figures but no CPU or memory minimums: roughly 50 to 100 GB for a pruned full node on one page, 'several hundred GB' on another, and about 700 GB for a full-history mainnet node. Production full nodes are told to match validator specifications that are still marked coming soon. Nodes run Movement's fork of the Aptos node software, usually in Docker, and can restore from hourly backups published by Movement Labs.
Throughput claims
  • Unclassified: 10,000 tx/s 22122Unclassified; do not compare.A '10,000+' target on Movement's architecture page, restated as delivered in December 2025 launch announcements; no method, workload or measurement date is given.Not stated.A capacity statement with no published method, workload or window, so it cannot be treated as a benchmark or an observation. Ignores transaction propagation, state growth and decoy or spam load. Says nothing about observed mainnet usage, which this review did not measure. Not comparable with any other chain's headline figure.
  • Theoretical peak: 160,000 tx/s 624Theoretical peak; not comparable across chains or with observed load.MiCA white paper (notified 28 October 2025) and the March 2025 mainnet beta post, both describing the Block-STM execution engine as capable of this figure in theory.Not stated; the figure describes the parallel execution engine, not this network's validators.Movement itself labels the figure theoretical; it describes the execution engine, not network capacity. Ignores consensus rounds, propagation, storage commit and state growth. Ignores decoy or spam load and contended workloads. Theoretical peak; not comparable across chains or with observed load.
Headline figures are not comparable across chains. A theoretical peak is never a like-for-like number.

Scaling layers

Capabilities

Capabilities of Movement: how each one is provided, or its research status
CapabilityHow it is providedNotes and sources
Account abstractionStructured assessment pendingNot yet assessed for any chain.
Atomic swapsUnknownNot yet assessed under the current definitions; no hash-locked or time-locked swap mechanism for Movement was reviewed. NEAR Intents routes swaps into Movement through competing solvers, which is an intent service rather than a protocol-level atomic swap. 13
Authenticated data publicationUnknownNot yet assessed under this row's current definition.
Light clientsUnknownNot yet assessed under the current definitions; Movement's docs describe light nodes that sync only relevant account data, and the whitepaper says its state tree supports light-client proofs, but no released light client was found. 34
Native staking or delegationStructured assessment pendingNot yet assessed for any chain.
On-chain governanceStructured assessment pendingNot yet assessed for any chain.
Parallel executionStructured assessment pendingNot yet assessed for any chain.
Payment or state channelsPartial (layer not stated) Earlier definitionMove Industries publishes a one-way streaming payment channel contract with a testnet deployment, plus a machine-payments SDK that uses it. No mainnet deployment or channel network was verified. 3839
Programmable spendingNative (protocol or core-team software) Earlier definitionEvery transaction runs Move code against resources stored under accounts and objects, so spend conditions live in Move modules. Movement follows the Aptos flavour of Move. 41429
Protocol-verified messagingStructured assessment pendingNot yet assessed for any chain.
Reversible transfers or recoveryUnknownNot yet assessed under this row's current definition.
RollupsUnknownNo rollup settling to Movement was found. Movement itself was presented in 2025 as a network anchored to Ethereum; the current chain settles to no other chain. Absence was not exhaustively verified. 2124
Shielded transfersStructured assessment pendingNot yet assessed for any chain.
Signed partial offersUnknownNot yet assessed under this row's current definition.
Reading these values
How this feature is provided
Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
Structured assessment pending
The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
Unknown
The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
Earlier definition
Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
Reading across rows
The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.

Definitions, schema version and review history

Ecosystem & custody

Ecosystem products for Movement
Product typeStatusNotes and sources
Automated market makersEstablished in the ecosystemYuzu FinanceYuzu documents a concentrated-liquidity market maker built on Movement, and Movement named it the network's primary exchange in May 2026 after a request-for-protocol process. Liquidity depth was not measured and other venues were not reviewed. 2627 As of Sep 27, 2026.
Issuer-native stablecoinsThinUSDCx (backed by USDC in Circle xReserve), USDC.e and USDT.e (bridged from Ethereum)Neither Circle's USDC address list nor Tether's supported-protocol list includes Movement. USDCx is minted on Movement against USDC held in Circle's xReserve contract; Circle calls such tokens USDC-backed stablecoins, distinct from USDC itself. The .e tokens are bridged wrappers. 1225303132 As of Sep 27, 2026.
Algorithmic stablecoinsUnknownNo algorithmic or hybrid stablecoin with material use on Movement was verified. As of Sep 27, 2026.
BridgesFirst-partyMovement Bridge (LayerZero token contracts, Ethereum), Circle xReserve (USDCx), NEAR Intents (swap route into Movement)Movement's bridge moves MOVE, USDC, USDT, ETH and WBTC between Ethereum and Movement using LayerZero token contracts, with daily MOVE limits at launch and a 3-day wait on withdrawals of the other assets to Ethereum. LayerZero lists Movement mainnet as endpoint 30325. NEAR Intents converts USDT from other chains into USDCx through solvers. Risk: Bridged tokens depend on the LayerZero verification settings the bridge operator chose, on the contracts' admin and upgrade keys, and, for USDCx, on Circle's xReserve attestations and the Movement-side minting contract. None of these contracts or settings were audited here. 12133133 As of Sep 27, 2026.
Block explorersFirst-partyMovescan (explorer.movementnetwork.xyz)Movescan is Movement's own explorer, listed in its endpoint table. Independent explorers were not verified. Explorer views are indexed provider data, not consensus. 1137 As of Sep 27, 2026.
Hardware walletsThinLedger (through Motion, Aptos device app)See custody rows: Ledger signing on Movement works only through Movement's Motion wallet with Ledger's Aptos app and blind signing. Trezor lists MOVE only as a token on Ethereum, Base and HyperEVM, which is not custody on the Movement network. 2935 As of Sep 27, 2026.

Hardware-wallet custody

Hardware-wallet custody for Movement
Device makerStatusWhat users can and cannot do
LedgerThrough an intermediaryMotion wallet (Move Industries), using Ledger's Aptos device appSame as native: NoCan: Import Ledger accounts into Motion and sign Movement transactions with keys kept on the device, per Movement's August 2026 guide
Can: Install and update the Aptos device app through Ledger Wallet
Cannot: Manage MOVE on the Movement network inside Ledger Wallet itself; Movement's guide says Motion handles accounts and tokens
Cannot: Read transaction details on the device: Motion requires blind signing, so the device may show only a hashLedger's coin-page address for Movement returned 404 and its Aptos page does not mention Movement. Whether Ledger Wallet lists the Ethereum token version of MOVE was not verified. Motion's own homepage still lists hardware wallet support as on the way, which conflicts with the August 2026 guide. 2934 As of Sep 27, 2026.
TrezorNone foundSame as native: NoCannot: Sign transactions on the Movement network: Trezor lists no Movement network for MOVE and separately states that it does not support Aptos, whose account and signing format Movement usesTrezor's Movement page describes the M1 network but lists only Base, Ethereum and HyperEVM as networks for MOVE, used with Trezor Suite, MetaMask or Rabby. Holding that token version on another network is not custody on the Movement network, so it does not count here. 293536 As of Sep 27, 2026.

Public data

iKnow Blockchain has no public-data lookups for Movement yet. This is a limit of the service, not a statement about the network.

Public-data lookups for Movement
LookupStatusWhat it covers and its limits
Address or accountNot available yetPublic-data lookups for this chain are not built yet.
Tokens and assetsNot available yetPublic-data lookups for this chain are not built yet.
NFTsNot available yetPublic-data lookups for this chain are not built yet.
TransactionsNot available yetPublic-data lookups for this chain are not built yet.

A lookup covers one address or transaction from one provider. It is never a complete wallet, and an error or private value is reported as unknown, not zero. About public data · Connect your AI

Sourced developments

Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.

Publication date · newest first

Topics your AI can explain

Your AI can explain these topics for Movement through the connection, with sources.

Known gaps

What this profile's review did not establish:

Sources

Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.

All 40 sources were checked in the last 30 days.

  1. What is M1 (external site)Movement Docs · retrieved
  2. M1 Architecture (external site)Movement Docs · retrieved
  3. Node-Level Architecture (external site)Movement Docs · retrieved
  4. M1 Whitepaper (protocol specification) (external site)Movement Docs · retrieved
  5. Staking & Delegation (external site)Movement Docs · retrieved
  6. MOVE crypto-asset white paper under MiCA (date of notification 2025-10-28) (external site)Movement Network Foundation · retrieved
  7. Validator Node (external site)Movement Docs · retrieved
  8. Nodes overview (external site)Movement Docs · retrieved
  9. Full node requirements (external site)Movement Docs · retrieved
  10. movement-networks README (genesis, configs and restore scripts) (external site)Movement Network (GitHub) · retrieved
  11. Network Endpoints (external site)Movement Docs · retrieved
  12. Bridge (external site)Movement Docs · retrieved
  13. NEAR Intents (external site)Movement Docs · retrieved
  14. Token Standards overview (external site)Movement Docs · retrieved
  15. Mainnet REST API: 0x1::stake::ValidatorSet resource (external site)Movement mainnet public API · retrieved
  16. Mainnet REST API: 0x1::staking_config::StakingConfig resource (external site)Movement mainnet public API · retrieved
  17. Mainnet REST API: 0x1::aptos_governance::GovernanceConfig resource (external site)Movement mainnet public API · retrieved
  18. Mainnet REST API: resources of account 0xa550c18 (external site)Movement mainnet public API · retrieved
  19. Mainnet REST API: 0x1::governed_gas_pool::GovernedGasPoolExtension resource (external site)Movement mainnet public API · retrieved
  20. movement-network/aptos-core releases (fork of aptos-labs/aptos-core) (external site)Movement Network (GitHub) · retrieved
  21. Movement Network Foundation and Move Industries Announce Completion of Operating Change (external site)Movement Network · retrieved
  22. Movement's M1 Mainnet Goes Live: The People's Chain Is Here (press release, 22 December 2025) (external site)Move Industries via GlobeNewswire · retrieved
  23. An update from Torab Torabi, CEO, Movement (external site)Movement Network · retrieved
  24. Public Mainnet Beta is Now Live (external site)Movement Network · retrieved
  25. Introducing USDCx: Movement's Native USDC-Backed Stablecoin (external site)Movement Network · retrieved
  26. Movement Selects Yuzu Finance as its Primary DEX (external site)Movement Network · retrieved
  27. Yuzu documentation: introduction (external site)Yuzu Finance · retrieved
  28. gMove - Movement's liquid staking token is live (external site)Movement Network · retrieved
  29. How to Use Ledger with Motion Wallet (external site)Movement Network · retrieved
  30. USDC Contract Addresses (external site)Circle · retrieved
  31. How xReserve works (external site)Circle · retrieved
  32. Supported Protocols (external site)Tether · retrieved
  33. Movement (LayerZero V2 mainnet endpoint) (external site)LayerZero · retrieved
  34. Aptos Wallet (external site)Ledger · retrieved
  35. Movement wallet (external site)Trezor · retrieved
  36. Aptos wallet (external site)Trezor · retrieved
  37. Movescan - Movement Network Explorer (external site)Movement Network · retrieved
  38. MovementStreamChannel Move contract README (external site)Move Industries (GitHub) · retrieved
  39. mpp-movement: Machine Payments Protocol SDK for Movement (README) (external site)Move Industries (GitHub) · retrieved
  40. Movement Network status (external site)Movement Network · retrieved

Report an error

Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.

Funding disclosure

Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding