Dusk Network. DevNet. Staging Environment. Sandbox. Mainnet.

Why we have a Staging Environment and sandbox version of Mainnet

Dear Dusk Community,

The coming weeks see important milestones for the Dusk Network. We release the first iteration of our Dusk Network Mainnet in sandbox mode that is used for partner integration. Using this post, we explain how that works, how we release new features and share them with the community, and what else we have in store for Mainnet. PLONK! (read below)

The four stages of tech releases

At Dusk Network we create bleeding-edge technology based on proven technical and mathematical concepts. Our code releases follow strict procedures.

New code is first tested extensively on our Devnet where it needs to pass strict criteria before it is moved to the Staging Environment (Testnet) (the term Staging Environment is common within tech development for financial applications). In short, the Staging Environment is a final public testing ground. Upon positive conclusion, components of the Staging Environment are released on Dusk Network’s Sandbox, before its turned public.

A separate explanation of the different stages can be found below. Bear in mind that the Sandbox Mainnet enables the Dusk Network business team to get well underway with partner integrations. It is important to speed up the adoption process in this manner, because after all, once we go public, it’s important we hit the ground running.