Skip to main content
Version: 0.2.3

Predeployed contracts

Devnet predeploys a UDC, an ERC20 (fee token) contract and a set of predeployed funded accounts.

The set of accounts can be controlled via CLI options: --accounts <NUMBER_OF>, --initial-balance <WEI>, --seed <VALUE>.

Predeployed account preservation

note

Once you shut down your Devnet, the predeployed account you used ceases to exist. This may be a problem with tools such as starkli which hardcode your account details in a local file. One option then is to delete your account entry from starkli's account file. Another option is to spawn the same account on next Devnet startup. To do this, you can use:

  • the --seed <VALUE> CLI option which always predeploys the same set of accounts if using the same <VALUE> (the seed is logged on startup)
  • the dump and load feature

Account class selection

Choose between predeploying Cairo 0 (OpenZeppelin 0.5.1) or Cairo 1 (default; OpenZeppelin 0.8.1) accounts by using:

--account-class [cairo0 | cairo1]

Alternatively, provide a path to the Sierra artifact of your custom account using:

--account-class-custom <SIERRA_PATH>

Deploying an undeclared account

If you want to deploy an instance of an account contract class not predeclared on Devnet, you can use forking. Just fork an origin network which has the needed class already declared, e.g. the Sepolia testnet. Why? Because new versions of wallets like ArgentX and Braavos tend to be declared on testnet/mainnet soon after release.

How to get predeployment info?

Logged on startup

The startup log includes:

  • the addresses and class hashes of predeployed contracts
  • the keys and initial balance of predeployed account contracts

API

Account class info can be found in the response to config request.

Predeployed account details can be retrieved in JSON format by sending a GET request to /predeployed_accounts or via JSON-RPC. With the additional query parameter with_balance set to true, ETH and STRK balances at the pending state will be provided, in WEI and FRI, respectively:

GET /predeployed_accounts?[with_balance=true]

Alternatively, send a JSON-RPC request:

JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_getPredeployedAccounts"
}
JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_getPredeployedAccounts",
"params": {
// optional; defaults to false
"with_balance": true | false
}
}