Using Devnet, Testnet and Mainnet

Warning

Instructions here are for devnet, but it is the same for other networks. Just replace "devnet" with testnet/mainnet and dsui with tsui/msui.

Starting

Works similar to localnet, except you are now interacting with a public network:

$ devnet start

The first time may take longer because of downloading and building some binaries.

You do not call sui directly anymore, instead call dsui:

$ dsui client active-address
0x92c03721eabfc753453b097d14d87e4012a9fe562da3582a6a023da7c6120c95

You no longer have to "switch env". You can assume dsui always transparently execute with its proper sui client and keystore for devnet (in same way, tsui for testnet, msui for mainnet).

Type devnet for help.

Where are the key stores?

Network	Keystore Location
localnet	~/suibase/workdirs/localnet/config/sui.keystore
devnet	~/suibase/workdirs/devnet/config/sui.keystore
testnet	~/suibase/workdirs/testnet/config/sui.keystore
mainnet	~/suibase/workdirs/mainnet/config/sui.keystore

Suibase storage design helps your app find what it needs consistently (More Info).

Status

You can check the client version and devnet services status with devnet status.

You can monitor the RPC node servers with devnet links (More Info).

Upgrading Sui Client

Do devnet update to download/rebuild to the latest client.

By default, the recommended branch from Mysten Labs is used, you can choose a different branch or repo by editing the suibase.yaml (More Info).