Developers

Deploying Contracts

StonkBrokerChain is EVM-equivalent — deploy exactly as you would to Ethereum or Arbitrum One. The only difference: the deployer wallet pays gas in STONKBROKER, so bridge some in first.

Foundry

forge create src/MyContract.sol:MyContract \
  --rpc-url https://rpc.stonkbrokerchain.xyz \
  --private-key $DEPLOYER_KEY

foundry.toml profile:

[rpc_endpoints]
stonkbroker = "https://rpc.stonkbrokerchain.xyz"

[etherscan]
stonkbroker = { key = "any", url = "https://Pending Update/api/" }

Hardhat

// hardhat.config.js
module.exports = {
  networks: {
    stonkbroker: {
      url: "https://rpc.stonkbrokerchain.xyz",
      chainId: 0, // TBA — set the published chain ID
      accounts: [process.env.DEPLOYER_KEY],
    },
  },
};

npx hardhat run scripts/deploy.js --network stonkbroker

Remix / MetaMask

Add the network to MetaMask (see Add the Network), select Injected Provider in Remix, and deploy as usual.

Verifying contracts

The explorer is Blockscout — verify through its UI at https://Pending Update (Contract → Verify & Publish), or via the Blockscout API. Foundry users can pass --verifier blockscout pointed at https://Pending Update/api/.

Things to know

Tooling behaves like Arbitrum One (Nitro/ArbOS). If a library special-cases Arbitrum, those code paths apply here.
Blocks are minted per transaction — use timestamps, not block counts, for timing logic.
msg.value is $STONKBROKER — anything priced in “ETH” in ported code is priced in $STONKBROKER here. Re-check hardcoded amounts when porting payable contracts.