Guide to Agoric Testnets

Platform & BLDers
1

At present, there are two purpose-built, mainstay networks that support development and testing in the Agoric Ecosystem: devnet and emerynet. This thread is intended to develop a shared understanding of their purpose and processes. Stay tuned for refinements and please do add your comments and questions.

devnet

This network is the proving ground for mainnet-2 and mainnet-3 development, and it is home to upcoming releases. Generally, whatever code Agoric Engineering is planning to ship in our next release will be deployed in devnet, and there may be significant churn in network changes as new versions of software and functionality become available.

Community developers who are interested to move beyond testing in a local chain are welcome to try their apps on devnet.

https://devnet.agoric.net/ provides details such as chain-id, RPC endpoints, software version, explorer, and faucet.

emerynet

Emerynet is a production testnet that is primarily used for the qualification of software before it is promoted to production (aka mainnet) via governance in a network upgrade. Emerynet validators are expected to have mainnet experience. Emerynet is a long-lived, stable network that is the proving ground for mainnet. It is the last stop before mainnet where the community can observe for bugs or defects.

https://emerynet.agoric.net/ provides details such as chain-id, RPC endpoints, software version, explorer, and faucet.

2

A corresponding point about devnet: it’s where we try to do validator training.

3

Devnet voting period: 5 min*

* subject to governance, as usual

We can see in parameters on the devnet explorer that voting_period is currently 300 sec, i.e. 5min.

image

4

If what you are doing is not in support of some proposal already under discussion, please post something here on community.agoric.com to let everyone know how you’d like to use the shared testnet (devnet / emerynet) resources.

1 Like