Fork

To interact with contracts deployed on mainnet or testnet, you can use the forking feature to copy the remote origin and experiment with it locally with no changes to the origin.

starknet-devnet --fork-network <NAME|URL> [--fork-block <BLOCK_NUMBER>] [--fork-retries <NUMBER>]

The value of --fork-network can either be a network name (alpha-goerli, alpha-goerli2, or alpha-mainnet) or a URL (e.g. https://alpha4.starknet.io).

The --fork-block parameter is optional and its value should be the block number from which the forking is done. If none is provided, defaults to the "latest" block at the time of Devnet's start-up.

You can use the --fork-retries parameter to specify the number of retries of failed HTTP requests sent to the network before giving up, defaults to 1

All calls will first try Devnet's state and then fall back to the forking block.

If you are forking another Devnet instance, retrieving Cairo 1 classes might not work as expected if the class is only declared on the origin Devnet. Redeclaring it in the fork should fail (as expected).

Chain ID

Devnet defaults to using the TESTNET chain ID (the one corresponding to Alpha Goerli). If you want Devnet to use another chain ID, you can provide it using:

starknet-devnet --chain-id [MAINNET | TESTNET | TESTNET2]

where MAINNET refers to Alpha Mainnet, TESTNET refers to Alpha Goerli and TESTNET2 refers to Alpha Goerli2.

Get fork status

GET /fork_status

Response when in fork mode:

{
    "url": "https://alpha4.starknet.io",
    "block": 438839
}

Response when not in fork mode:

{}