Build · Deploy

Deploy to the network

The network is EVM-equivalent, so your contracts and tooling work unchanged. Deploy against the testnet RPC, then read the full guide in the docs.

EVM equivalence

Deploy what you already have.

Solidity contracts, compiled bytecode, and the standard toolchain run here without modification. There is no custom compiler and no opcode divergence to work around.

EVM-equivalent

If a contract compiles and runs on Ethereum, it compiles and runs on the network. Keep your existing build pipeline; only the RPC endpoint changes. The example below targets testnet.

One example

Deploy with Foundry.

Set OSS_RPC_URL to the testnet RPC endpoint and deploy a contract with forge create. This is testnet only.

# Deploy a contract to the OpenStateStack testnet (testnet)
export OSS_RPC_URL="https://rpc.testnet.openstatestack.network"

forge create \
  --rpc-url $OSS_RPC_URL \
  --private-key $DEPLOYER_KEY \
  src/Registry.sol:Registry

A returned contract address means the deploy landed on testnet. Open it in the explorer to confirm the code and the deploy transaction. Open the explorer

Full guide

The full deploy guide lives in the docs.

Verification, constructor arguments, gas, multi-contract deployments, and CI are documented in full. This page is the quick path; the docs are the reference.

Testnet

Everything on this page targets testnet. Endpoints, addresses, and parameters are indicative pre-mainnet and may change. Confirm against the docs before operating beyond testnet.

Full deploy guide

Deployed. Now debug against live data.

Open the explorer to inspect your contract, or read the full deploy guide in the docs.

Run a node Open the explorer