Skip to main content
HyperPaxeer is fully EVM-compatible. Running on the Alexandria Fork with Hyperpax-OS Cronos, all standard Ethereum tooling works — Foundry, Hardhat, Remix, ethers.js, wagmi, and viem. Use --legacy --slow flags with Foundry for reliable transaction inclusion.

Overview

Deploy and interact with smart contracts on HyperPaxeer (Chain ID 125). Foundry is the recommended framework; Hardhat and Remix are also supported.

Deployment Options

Deploy with Hardhat

Configure Hardhat to deploy on HyperPaxeer.

1. Install dependencies

2. Configure hardhat.config.js

hardhat.config.js

3. Deploy

Store your private key in a .env file and never commit it to version control.

Example Contract

Here’s a simple ERC-20 token contract example:
MyToken.sol

Deploying the Example

scripts/deploy.js
Run the deployment:

Verifying Contracts

After deployment, verify your contract on PaxScan for transparency and easier interaction.

Using Hardhat

Using Foundry

Interacting with Contracts

Using ethers.js

Using wagmi

Best Practices

  • Use appropriate data types (uint256 vs uint8)
  • Minimize storage writes
  • Use events for logging instead of storage
  • Batch operations when possible
  • Use OpenZeppelin contracts for standards
  • Implement access control
  • Validate all inputs
  • Test thoroughly before mainnet deployment
  • Consider getting an audit for critical contracts
  • Write comprehensive unit tests
  • Test locally or on private networks before mainnet
  • Test edge cases and failure scenarios
  • Use fuzzing for complex contracts

Network Information

Next Steps

Configuration

Configure different libraries for HyperPaxeer

Examples

View complete integration examples

API Reference

Explore all available RPC methods

Tools

Recommended SDKs and development tools