Contracts
Every contract on your Stagenet can have its own dashboard — one place to inspect and drive it: its activity, assets, state, and functions.
They live on your Stagenet’s Contracts page.
How dashboards are created
Automatically, for contracts you deploy
- Push your contracts to your Stagenet with
contract.dev push-contracts. - Deploy them with your normal scripts.
When a deployment’s bytecode matches a pushed contract, its dashboard is created automatically — with the ABI, name, and storage layout already attached. A contract deployed before the push gets its name and ABI when the push lands; decoded storage needs the layout, which is attached when a deployment matches a contract pushed beforehand.
Manually, for everything else
From your Stagenet’s Contracts page you can also add:
- Mainnet contracts — third-party contracts that exist on the replicated chain (pools, tokens, oracles); the ABI is fetched automatically.
- Any other contract — supply an ABI yourself.
What a dashboard shows
- Overview — live vitals and the address’s recent transactions.
- Money — asset balances and approvals granted.
- Interact — call read and write functions directly on the fork, with your browser wallet or the gasless Platform Wallet.
- Storage — named storage variables, decoded live (contracts with a storage layout).
Each contract is tagged with its origin: forked state replicated from the target chain, or stagenet native — deployed or created on your Stagenet.
Last updated on