Connecting to Movement Network

This guide provides an overview of how to connect to the Movement Network, including details on available networks, configuration steps, and accessing network endpoints.

Network Status

You can check the current status and uptime of the Movement Network, visit:
https://status.movementnetwork.xyz/

Available Networks

Movement Network consists of different environments to support development and production deployments. Below are the currently available networks:

Movement Developer Mainnet

Movement Bardock Testnet

Suzuka Devnet

The Suzuka Devnet is used for testing updates before they are deployed to the Testnet.

Configuring Movement CLI for Movement Network

To interact with the Movement Network, you need to configure your environment using the Movement CLI.

Switching Between Networks

Ensure that you have the Movement CLI installed.

You can use the Movement CLI to initialize profiles for different networks:

Mainnet Profile:

movement init --profile mainnet --network mainnet

Testnet Profile:

movement init --profile testnet --network testnet

Devnet Profile:

movement init --profile devnet --network devnet

Once initialized, switch between networks using:

movement account list --profile mainnet

Running a Local Testnet

To set up a local testnet for development, follow these steps:

movement node run-local-testnet --with-faucet

movement init --profile local --rest-url http://localhost:8080 --faucet-url http://localhost:8081

movement account create --profile local
movement account fund --profile local --account <new_account_address>

movement node run-local-testnet --force-restart --assume-yes

By following these steps, you can efficiently connect and interact with the Movement Network for development and production use.