Working with the NEAR network is currently possible under 5 deployment scenarios:
Our MainNet is in Phase 0, a higly restricted Proof of Authority network. This is intended for apps that are production ready, and have already gone through testing. Find more info on our multi-phase approach to releasing MainNet here: The Road to MainNet and Beyond
MainNet status is available at https://rpc.testnet.near.org/status
The flag for this in near-shell is 'production'
State Management MainNet
We guarantee maintanaince of state on MainNet.
TestNet is intended for development on the NEAR platform.
TestNet status is available at https://rpc.testnet.near.org/status
The flag for this in near-shell is 'development'
We make every attempt to maintain the integrity of network state across updates, but this is still a volitile network that receives heavy testing.
DevNet is intended for developers who want to work with or test the latest (
master branch) features of the NEAR platform.
Releases happen daily at 0:00 UTC.
The flag for this in near-shell is 'devnet'
The state of the network is not preserved across updates since breaking changes are likely.
BetaNet is intended primarily for validators who wish to test their infrastructure. If you are interested in testing an application that
Releases happen weekly.
BetaNet status is available at https://rpc.betanet.near.org/status
The flag for this in near-shell is 'betanet'
State is maintained as well as possible.
LocalNet is intended for developers who want to work with the NEAR platform independent of the public blockchain. You will need to generate nodes youerself.
More on local development here
The flag for this in near-shell is 'local'
Staging/testing environments are mostly for us to test our code and run CI. We don't recommend you use these unless you're contributing to the code base.
The flags in near-shell are 'test', 'ci' and 'ci-betnet'.