NEAR Documentation
  • Basics
  • Develop
  • Stake
  • Integrate
  • Tokens
  • Contribute
  • API
  • Community
  • GitHub

›Quickstart

Quickstart

  • Orientation
  • Building Apps
  • Networks

Tutorials

  • Introduction
  • Guided Walkthroughs

    • Figment Tutorials
    • Create Transactions
    • Issue a Token
    • Cross-Contract Calls
    • Simple AssemblyScript tests
    • Simple Rust smart contract

    Helpful References

    • Contract Structure
    • Project Structure

    Videos

    • Accounts & keys
    • Smart Contract Reviews
    • Misc

JavaScript library

  • Introduction
  • Guides
  • Examples

Smart Contracts

  • Introduction
  • Creating Contracts

    • Rust
    • AssemblyScript

    Using Contracts

    • Rust
    • JavaScript
    • API

    Testing Contracts

    • Testing contracts

    Virtual Machine Limits

    • Runtime Limits

Ethereum Compatibility

  • Network status
  • Simple script & NEAR CLI guide
  • Pet Shop example
  • Web3 provider
  • Using Truffle
  • Local setup
  • Proxy RPC Server
  • Testing contracts

Machine Setup

  • Local Development on TestNet
  • Local Development on Local Network
  • Running a node
  • Running a Node on Windows

FAQ

  • Developer FAQ
Edit

Connecting to NEAR

NEAR Protocol operates on several networks each operating with their own independent validators and unique state. These networks are as follows:

  • mainnet
  • testnet
  • betanet
  • localnet

mainnet

mainnet is for production ready smart contracts and live token transfers. Contracts ready for mainnet should have gone through rigorous testing and independent security reviews if necessary. mainnet is the only network where state is guaranteed to persist over time (subject to the typical security guarantees of the network's validation process).

  • [ Status ]
  • [ Explorer ]
  • [ Wallet ]

Note: near-cli network selection flag is production.


testnet

testnet is intended for testing all aspects of the NEAR platform prior to mainnet deployment. From account creation, mock token transfers, development tooling, and smart contract development, the testnet environment should closely represent mainnet behavior. We make every attempt to maintain the integrity of network state across updates but this is still a volatile network that receives heavy testing. Therefore, we recommended all user-facing applications are deployed to mainnet to ensure persistent state.

  • [ Status ]
  • [ Explorer ]
  • [ Wallet ]

Note: near-cli network selection flag is development or testnet. (This network is selected by default with near-cli and may not need additional configuration)


betanet

betanet usually has daily releases with protocol features that are not yet stabilized. State is maintained as much as possible but no guarantees with its high volatility.

  • [ Status ]
  • [ Explorer ]
  • [ Wallet ]

near-cli network selection variable is betanet


localnet

LocalNet is intended for developers who want to work with the NEAR platform independent of the public blockchain. You will need to generate nodes yourself.

More on local development here

near-cli network selection variable is local


Got a question? Ask it on StackOverflow!

Last updated on 1/21/2021 by Josh Ford
← Building AppsIntroduction →
  • mainnet
  • testnet
  • betanet
  • localnet
  • Wallet
  • Explorer
  • Examples
  • Docs
  • Twitter
  • GitHub
  • Discord
  • Telegram
  • WeChat
  • YouTube

Developers

  • Overview
  • Technology
  • Docs
  • GitHub
  • Bounties
  • Developer Program
  • Survey

Ecosystem

  • Events
  • Contributor Program
  • Guild Program
  • Startup Accelerator
  • Bounties
  • Tokens

About

  • Team
  • Careers
  • Backers
  • Press Kit
  • Brand Guidelines
  • Privacy Policy

2020 NEAR Protocol|All rights reserved|hello@near.org|Privacy Policy