Skip to main content
Forking a Virtual Environment creates an exact snapshot of its state at a specific moment. The new Virtual Environment inherits all contracts, balances, and transactions from the source network. This allows your team to develop in iterations with minimal interference while working on an accurate, disposable working copy.
The Fork button in the Virtual Environment header copies the latest state. To create a copy at a specific past block, fork from a transaction instead.
After staging smart contracts, and setting up the state by sending transactions or funding accounts, your team members can create personal working copies of the staging Virtual Environment. This way, tests don’t impact the original Virtual Environment’s state, and each team can perform their own tests with no test-data noise and interference. To fork a Virtual Environment:
  1. Click Fork in the Virtual Environment header.
  2. In the Fork Virtual Environment dialog, edit the Name (it defaults to the source name followed by Clone) and click Fork.
Fork Virtual Environment dialog with the text Create a copy of this Virtual Environment with the same configuration, a Name field prefilled with the source name followed by Clone, and Cancel and Fork buttons

Fork dialog opened from the Virtual Environment header.

You can verify the origin of a forked Virtual Environment by checking the details section, which displays the source network from which the Virtual Environment was forked.

​
Next Steps

  • Stage dapps: Learn how to connect the Virtual Environment to your dapp’s UI.
  • Revert state: Revert Virtual Environment state if testing steps aren’t repeatable otherwise.