| Milestone | Expected Date | GitHub items |
|---|---|---|
| 4.0 Mainnet Staged/Deployed | 2026-02-16 | items |
| 4.1 Mainnet Ready | 2026-03-12 | items |
| 4.2 Mainnet Generally Available | TBD | items |
<aside>
This corresponds with the GitHub milestone “M4.0: mainnet staged” (see items).
</aside>
This is the work that is necessary for mainnet to be staged with our code that has the things we know we need for GA. The purpose is to give focus to getting mainnet as ready as calibration currently is so integration partners can start using mainnet. We won't be 4.1 Mainnet Ready ready when we hit this milestone as there will be operational readiness items still to do, but it at least gets us past the "get on mainnet" hurdle so we can identify any problems with our deployment and other variations between calibration and mainnet.
How is this different than being ready for mainnet or GA?
At GA. all aspects (operations, user/customer support, marketing, etc.) should be in place so we can look users in the eye and feel good about asking them to use the system in exchange for real funds.
Getting our software to work on mainnet with the feature set we expect for GA doesn't mean we're ready for production usage. This is an important stepping stone for the development team for validating their work and to allow early builders to start testing out their application integrations so we can be ready for mainnet.
<aside>
This corresponds with the GitHub milestone “M4.1: mainnet ready” (see items).
</aside>
See https://docs.google.com/document/d/11CVMGTrCHkmQH5ms74mxdpBumTEc5a9sV0W7-G8onP0/edit?tab=t.0
<aside>
This corresponds with the GitHub milestone “M4.2: mainnet GA” (see items).
</aside>