Question 1

What kinds of applications can I build on ETC?

Accepted Answer

Anything you can build on Ethereum or any EVM chain. ETC runs the same Ethereum Virtual Machine, supporting Solidity and Vyper smart contracts. This includes DeFi protocols, NFT platforms, DAOs, token systems, on-chain games, and any other smart contract application. The full EVM toolchain (Hardhat, Foundry, Remix, OpenZeppelin) works on ETC.

Question 2

What are the differences between developing for ETH vs ETC?

Accepted Answer

Minimal. Both use the same EVM, same smart contract languages, same development tools, and same ABI encoding. Key differences: ETC uses Chain ID 61 (vs ETH's 1), the RPC endpoint is different (etc.rivet.link), and ETC does not include some PoS-specific EIPs. Your existing Solidity contracts can be deployed on ETC by simply changing the network configuration.

Question 3

How do I deploy a smart contract to ETC?

Accepted Answer

Configure your development framework (Hardhat, Foundry, or Remix) with Chain ID 61 and RPC URL https://etc.rivet.link. Deploy using the same workflow as any EVM chain. For testing, use the Mordor testnet (Chain ID 63, RPC: https://rpc.mordor.etccooperative.org). Get test ETC from the Mordor faucet. Verify your contract on etc.blockscout.com after deployment.

Question 4

What public RPC endpoints are available?

Accepted Answer

The primary public endpoint is https://etc.rivet.link (mainnet). For Mordor testnet: https://rpc.mordor.etccooperative.org. For a comprehensive, performance-monitored list of RPC endpoints, visit chainlist.org/chain/61 (mainnet) or chainlist.org/chain/63 (Mordor). These endpoints support the standard Ethereum JSON-RPC API.

Question 5

Are there grants or funding available for ETC development?

Accepted Answer

The Olympia DAO governance framework (currently in development) will establish a non-inflationary treasury funded by EIP-1559 base fees, with on-chain governance for funding allocation. Until Olympia activates, development funding comes from community initiatives and individual contributors. Check the ETC Community channels for current opportunities.

Question 6

How does the ECIP process work?

Accepted Answer

The Ethereum Classic Improvement Proposal (ECIP) process is how protocol changes are proposed, discussed, and adopted. Anyone can author an ECIP. Proposals go through stages: Draft → Last Call → Accepted → Final. ECIPs are reviewed in Core Developer Calls. The process is documented at the ECIPs repository and mirrors Ethereum's EIP process with ETC-specific adaptations.

Question 7

What development tools work with ETC?

Accepted Answer

All standard EVM tools: Hardhat and Foundry for development/testing, Remix for browser-based development, OpenZeppelin for audited contract libraries, Blockscout for contract verification and blockchain exploration, MetaMask for wallet interaction, and ethers.js/viem/wagmi for frontend integration. No ETC-specific tooling is needed — standard EVM tools work by changing the RPC endpoint.

Developers FAQ

Looking for Something Else?