Learn
Guides and gotchas for PulseChain smart contract development.
How to verify a contract on PulseChain
- Deploy your contract on PulseChain mainnet (chain 369) or testnet v4 (chain 943).
- Copy the deployed contract address.
- Go to Verify Contract and select your verification method.
- Match the compiler version and EVM version used during compilation. PulseChain currently uses shanghai.
- Submit and wait for Sourcify to confirm the match.
How to read a verified contract
Use the Verified Contracts page or search for an address. The contract page shows source code, ABI, and read/write functions.
Proxy patterns
ContractLab detects common proxy standards automatically: EIP-1167 minimal proxies, EIP-1967 transparent proxies, and EIP-1822 UUPS proxies.
PulseChain-specific gotchas
- Chain IDs: mainnet 369, testnet v4 943.
- EVM version:
shanghai. Compiling forcancunwill produce non-matching bytecode. - Gas token: PLS.
- Fork block for post-fork contracts: ~17,233,000.