Fork Parents

Fork Parents are a feature that allows for greater control over Simulations you run on your Forks, and much easier repeated testing of specific (historical) scenarios on your forked networks. 
For starters, we will run a Fork Simulation as we normally would. On the right under the section Transaction Parameters, you will have an option called Parent that will allow you to set the Parent for your Fork. 
The empty state for your Fork Parent if you don't have any branch roots defined is Latest Simulation. Naturally, in the Forks tab, you can choose any of your previous Fork Simulations and mark it as a branch root so you can use it as a Fork Parent in your Fork Simulations.
Choosing Latest Simulation uses the parent ID from the Fork i.e. the latest transaction that happened on that Fork. If you just created a Fork, the last transaction will be defined as the last transaction in the block you forked the network from - this is neatly covered at the end of creating a Fork section.
​
You can also read more about Pending and Historical Blocks here.​
Marking your Fork Simulation as a branch root will add it to the list of Fork Parents you will be able to use going forward (and you can remove it as a branch root at any time). 
Branch roots will allow you to define any number of fixed points when forking networks so you can run Simulations from that or any other Parent.
You can also name your Fork Parents for easier navigation:
Now, when you run a new Fork Simulation, you will see all of your Forks that were added as branch roots:
All of the Fork Simulations that were ran with a Parent will be clearly marked:
If you clear the branch root from a Fork the Parent column will be properly updated:
If you mark a Fork as a branch root again after removing it, the Parent column will again be properly updated:
You can also mark Forks as branch roots straight from the Transaction Overview tab:

Sending Transactions to Forks

How to Get a Fork JSON-RPC URL & ID

Last modified 10mo ago

Copy link