Currently the Status alpha builds use testnet, but using Mainnet is a key milestone for the public launch of Status. There will be potentially major performance and security implications so the goal is to surface these issues early enough by testing the app in a real-world environment.
From a users perspective, Mainnet should be a default network as it is required by most popular DApps, and is needed for real transactions, so the full potential of Status can't be seen until we switch. The other networks will continue to be available, e.g. for developers and tests.
## Product Description
This is a default setting change, so there aren't any user facing options. The other networks are still visible.
Some users, such as DApp creators may want to test their app on testnet (or some other use case), so they will be able to toggle networks as can be done currently.
## Requirements & Dependancies
Security and performance should should be discussed and considered.
Also, several DApps should be tested.
## Minimum Viable Product
**This MVP does not mean that after it's finished we release the app with Mainnet enabled by default but defines prerequisites that should be done before we consider doing so.**
1. [ ] All reported security issues and recommendations are evaluated and finished.
### Updates
#### 2018-04-26
- security audit got extended to May 7th,
- security issues are tracked with `security` label in [status-react](https://github.com/status-im/status-react/issues?q=is%3Aissue+is%3Aopen+label%3Asecurity) and [status-go](https://github.com/status-im/status-go/issues?q=is%3Aissue+is%3Aopen+label%3Asecurity),
- [a feature request](https://github.com/status-im/status-react/issues/3994) to allow custom upstream address was created
