casper-network / casper-network/casper-node

[SRE] Enable VM 2.0 in DevNet for development & testing

Open
#5,180 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
399
Forks
224
Avg merge
15h 44m
Merged PRs (30d)
2

Description

Joe suggests:

- DevNet is alive with old Mainnet data (~3M blocks).
- Can enable VM 2.0 via config flag.
- Proposal to transform DevNet into a nightly test network.
- Automated test suite would validate upgrades across Node, Sidecar, and Client.
- DevNet should not be considered production-stable; resets possible after failures.
- Joe is working on scripting architecture to automate refreshes and test execution.

Michał prefers launching DevNet with a fresh state post Mainnet release of 2.0.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by locating the DevNet configuration flag for VM 2.0, then review the proposed scripting architecture and how Node, Sidecar, and Client tests are run. Done means a repeatable nightly DevNet workflow exists, including refreshes, upgrade validation, and documented reset behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
blockchain, devops, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.