Mainnet readyness

[saimeunt]

• [Mainnet readyness milestone] Integrate the latest revisions of the Rust compiler in the Playground #367
  Why? The Rust compiler is evolving quickly, it is expected to become stable and available as the main choice for developing Miden programs in early Q1 2026 with the release of Miden 0.13. We need the playground to be fully compatible with the current stable toolchain.
  Complexity: Easy

• [Mainnet readyness milestone] Integrate new design from Figma mockups #368
  Why? To better align the playground UI with the rest of Miden websites (docs, faucet, status, etc.)
  Complexity: Medium

• [Mainnet readyness milestone] Improve editor UX #369
  Why? To be on-par with the expected top-notch UX of all the other playgrounds out there.
  Complexity: Medium

• [Mainnet readyness milestone] Refactor state management with Miden React SDK #370
  Why? Refactor how state management and network sync is handled in the playground to better handle race conditions on sync state / transactions concurrent executions. We still have a couple of state sync and transaction race conditions happening (although this has been vastly improved). This is partly due to how the playground was bootstrapped at the very beginning of the projects. Now that we have a more in-depth comprehension of the Miden WebClient inner working, we can refactor some key parts of the playground to try to completely eliminate these problems.
  Complexity: Medium

• [Mainnet readyness milestone] Update to testnet 0.13 (tentative release date around Jan 19th) #371
  Why? This is required as testnet upgrades have breaking changes for every dApp at the moment.
  Complexity: Medium

• [Mainnet readyness milestone] Bring contract verification to MidenScan and midenup. #372
  Why? We developed a working prototype of contract verification using a similar process to Sourcify in the EVM ecosystem. We'd like to bring this feature to the rest of the Miden tooling to improve DevX and let developers verify contracts using their preferred method, eg. BlockScout integrates with the Sourcify API and forge create has a --verify flag to automatically verify contracts upon deployment.
  Complexity: Easy

• [Mainnet readyness milestone] UX quickwins: better mobile support & FAQ #373
  Why? Low complexity task improving overall UX as we open the playground to a broader audience.
  Add mobile support with delegated proving and better UX on small screens.
  Add a FAQ for common pitfalls when using the playground.
  Complexity: Easy

• [Mainnet readyness milestone] Transactions simulations with arbitrary input #374
  Why? At the moment we can execute transactions on testnet with arbitrary input. For better experimentation, we need to allow users to simulate and preview transactions without actually changing the chain state.
  Complexity: Easy

• [Mainnet readyness milestone] Resume an incomplete tutorial #375
  Why? Currently users are unable to leave an unfinished tutorial and come back to it later. For more complex tutorials on which users might be blocked, this is a much needed feature.
  This will also help building the save/load project feature as tutorials will be treated as ongoing projects preserving their own state.
  Complexity: Medium

• [Mainnet readyness milestone] Deploy server-side API to Cloudflare containers #376
  Why? Containers can be spawned on-demand with proper scaling configured, which is a perfect use case for the compilation API which needs high performances for an otherwise low requests count.
  This will also simplify the handover of the playground to Miden as every part of the dApp could be hosted on Cloudflare and not split among providers.
  Complexity: Hard

Easy complexity: a couple days of work.
Medium complexity: a week of work.
Hard: more than a week of work.