Docs

eth_call - Celo RPC Method

Execute smart contract calls without creating transactions on Celo. Essential for reading contract state for mobile stablecoin payments (MiniPay 10M+ wallets), remittances, humanitarian aid, and local currency stablecoins (cUSD, cNGN, cEUR).

Executes a new message call immediately without creating a transaction on Celo. Used for reading smart contract state.

Why Celo? Build on the mobile-first L2 powering 500K+ daily active users and $2B+ monthly stablecoin volume with phone number-based addressing, sub-cent fees, 150+ country adoption, Nightfall privacy layer, and Opera browser integration.

When to Use This Method

The eth_call method serves these key scenarios for mobile payment developers, fintech builders, and teams targeting emerging markets:

  • Read smart contract state - Execute view and pure functions to query token balances, DeFi positions, and protocol data without spending gas
  • Simulate transactions - Test contract interactions before submitting them on-chain, avoiding failed transactions and wasted gas costs
  • Multi-call aggregator queries - Batch multiple read calls into a single request using multicall contracts, reducing API overhead on Celo
  • MEV and arbitrage analysis - Simulate transaction bundles to evaluate profitable opportunities before execution on mobile stablecoin payments (MiniPay 10M+ wallets), remittances, humanitarian aid, and local currency stablecoins (cUSD, cNGN, cEUR)

Common Use Cases

1. Read ERC20 Token Balance

Query an ERC20 token contract to retrieve the balance for a specific wallet address using the balanceOf(address) function selector encoded as calldata. The selector is derived from the first 4 bytes of keccak256("balanceOf(address)"), followed by the 32-byte zero-padded address argument.

JavaScript
import { JsonRpcProvider } from 'ethers';

const provider = new JsonRpcProvider('https://api-celo-mainnet-archive.n.dwellir.com/YOUR_API_KEY');
const tokenAddress = '0x471EcE3750Da237f93B8E339c536989b8978a438';
const walletAddress = '0x471EcE3750Da237f93B8E339c536989b8978a438';

const balanceSelector = '0x70a08231' + walletAddress.slice(2).padStart(64, '0');

async function getTokenBalance() {
  const result = await provider.call({
    to: tokenAddress,
    data: balanceSelector
  });
  console.log('Balance (raw):', BigInt(result).toString());
  return result;
}

getTokenBalance();

2. Query DeFi Protocol State

Read protocol reserves, price oracles, or user positions from DeFi contracts on Celo. Each protocol exposes view functions that let you inspect pool state without modifying it - ideal for building analytics dashboards and trading bots.

JavaScript
import { JsonRpcProvider, Interface } from 'ethers';

const provider = new JsonRpcProvider('https://api-celo-mainnet-archive.n.dwellir.com/YOUR_API_KEY');

const poolAbi = [
  'function getReserves() view returns (uint112 reserve0, uint112 reserve1, uint32 blockTimestamp)'
];
const poolInterface = new Interface(poolAbi);
const poolAddress = '0x471EcE3750Da237f93B8E339c536989b8978a438';

async function getPoolReserves() {
  const data = poolInterface.encodeFunctionData('getReserves');
  const result = await provider.call({ to: poolAddress, data });
  const decoded = poolInterface.decodeFunctionResult('getReserves', result);
  console.log('Reserve 0:', decoded[0].toString());
  console.log('Reserve 1:', decoded[1].toString());
  return decoded;
}

getPoolReserves();

3. Simulate a Swap Before Execution

Before committing a token swap, call the router contract's quote function to calculate the expected output. This lets you validate slippage tolerance and compare rates across DEXes without risking gas on a failed trade.

JavaScript
import { JsonRpcProvider, Interface, parseEther } from 'ethers';

const provider = new JsonRpcProvider('https://api-celo-mainnet-archive.n.dwellir.com/YOUR_API_KEY');
const routerAddress = '0x471EcE3750Da237f93B8E339c536989b8978a438';

const routerAbi = [
  'function getAmountsOut(uint amountIn, address[] calldata path) view returns (uint[] amounts)'
];
const routerInterface = new Interface(routerAbi);

async function simulateSwap(amountIn, tokenIn, tokenOut) {
  const data = routerInterface.encodeFunctionData('getAmountsOut', [
    parseEther(amountIn),
    [tokenIn, tokenOut]
  ]);
  const result = await provider.call({ to: routerAddress, data });
  const decoded = routerInterface.decodeFunctionResult('getAmountsOut', result);
  console.log('Expected output:', decoded[0][1].toString());
  return decoded[0][1];
}

simulateSwap('1.0', '0xTokenA...', '0xTokenB...');

Best Practices

  • Use latest for current-state reads and pending for pre-confirmation simulation on Celo
  • Encode function selectors correctly: take the first 4 bytes of the keccak256 hash of the function signature
  • Handle revert errors gracefully by parsing the revert reason from the error response data
  • For batch reads, use multicall contracts to combine multiple eth_call requests into a single RPC call
  • eth_call does not consume gas, making it ideal for unlimited read queries on Celo

Code Examples

Error Handling

Error CodeMessageDescription
-32000Execution revertedContract function reverted
-32602Invalid parametersInvalid data encoding
-32015VM execution errorContract logic error