Contracts Deploy Contracts
You can deploy contracts via CLI or programatically.
From your forge or hardhat project, you can deploy your contract with a single command.
You can also publish your contract to be deployable by anyone on any chain.
You can deploy contracts from ABI and bytecode.
Or alternatively, you can deploy a contract from a previously published contract.
You can also deploy contracts via API by passing the contract bytecode and ABI. This will automatically verify the contract on block explorers and add it to your project dashboard.
x-secret-key
backend
Project secret key - for backend usage only. Should not be used in frontend code.
x-client-id
frontend
Project client ID - for frontend usage on authorized domains.
x-ecosystem-id
optional
Ecosystem ID - for ecosystem wallets.
x-ecosystem-partner-id
optional
Ecosystem partner ID - for ecosystem wallets.
Authorization
frontend
Bearer token (JWT) for user wallet authentication
chainId
Required
The blockchain network identifier. Common values include: 1 (Ethereum), 8453 (Base), 137 (Polygon), 56 (BSC), 43114 (Avalanche), 42161 (Arbitrum), 10 (Optimism).
from
Required
The wallet address or ENS name that will deploy the contract.
bytecode
Required
The contract bytecode as a hex string.
abi
Required
The contract ABI array.
constructorParams
Object containing constructor parameters for the contract deployment (e.g., { param1: 'value1', param2: 123 }).
You can list all deployed contracts for your project.
x-secret-key
backend
Project secret key - for backend usage only. Should not be used in frontend code.
x-client-id
frontend
Project client ID - for frontend usage on authorized domains.
x-ecosystem-id
optional
Ecosystem ID - for ecosystem wallets.
x-ecosystem-partner-id
optional
Ecosystem partner ID - for ecosystem wallets.
limit
integer
The number of contracts to return (default: 20, max: 100).
page
integer
The page number for pagination (default: 1).