igneum/docs/build/build.md

Build on Igneum

This file is the source of igneum.network/build. The site build renders it as the page. The other files in this directory are the walkthrough, the RPC list, the faucet, the verifier and the grants.

What is different

Every block is built to be proven. A chain block carries a zero-knowledge proof of its execution. The miners are the provers: the same cards that find blocks prove them, in shards. On the devnet a share of blocks carries a proof today (TEAM-REPORTED, 8 October 2026); the live page shows the share and the lag, and the design target at launch is under a minute (designed). Full nodes execute every block themselves, so a bad proof is a light-client problem and never a chain split.

A lock in minutes, not an hour of confirmations. Miners sign a checkpoint every 30 seconds. When two thirds of the mining weight of the last 30 days have signed, the checkpoint is locked. Weight is blocks mined, nothing else. The lock lands in about two minutes. The litepaper has the rule.

Nothing to stake. No validator set, no delegation, no slashing, no bonded class above the miners. Finality comes from mining weight alone. Nobody holds a key that the chain depends on.

The EVM you already know. Solidity deploys unchanged. Standard JSON-RPC, EIP-1559 transactions, the chain id in the signature, cancun as the EVM version. Gas has two dimensions on Igneum, execution and proving, and the node folds the second into the price it quotes, so eth_estimateGas and eth_gasPrice work as they do on Ethereum.

Networks

	Igneum 2.0 devnet
Chain id	4465 (0x1171)
Network id	igneum-devnet-4
RPC	https://rpc.devnet.igneum.network (a node you run serves http://127.0.0.1:26790)
Coins	no value, resets without notice
Symbol, decimals	IGN, 18
Machine-readable	/release.json: the chain id, the source commits and fingerprints, the mining class, the finality rule, the proof program ids, the fee schedule and the current version per platform, with a generated date

The devnet is where you build today. It is a developer network: it resets without notice and its coins have no value. Its public RPC takes the read methods, eth_sendRawTransaction and a wRPC websocket at /ws, at 20 requests a second per address. Read the chain id with eth_chainId rather than fixing it, since a transaction signed for the wrong id is refused.

Mainnet has not started and has no date. Its chain id, 4461 (0x116d), is reserved in the node.

Endpoints and tools

• Wallet. Any Ethereum wallet. Add Igneum to MetaMask with one click, or the Igneum wallet.
• Faucet. 10 IGN of the devnet coin per address per day. No account.
• Explorer. The explorer shows blocks, the DAG, miners and addresses. The EVM views, transactions and contracts, are being built and link from the same page as they land.
• Swap. The swap: test tokens on the devnet, every swap in a proven block.
• Source. git.igneum.network/igneum-network/igneum: the node, the miner, the site, and these pages under docs/build/.

Your first contract in five minutes

With Foundry. Tested end to end on the devnet on a build box; the full walkthrough with the expected output is docs/build/first-contract.md.

curl -L https://foundry.paradigm.xyz | bash && foundryup
export RPC=https://rpc.devnet.igneum.network
cast wallet new                      # an address and a private key, for the devnet only

Paste the address into the faucet. Then:

export PK=0x...                      # the private key cast printed
cast balance $(cast wallet address $PK) --rpc-url $RPC --ether
forge init counter && cd counter
forge create src/Counter.sol:Counter --rpc-url $RPC --private-key $PK --broadcast

forge create prints Deployed to: 0x.... Call it:

cast send 0xDEPLOYED "increment()" --rpc-url $RPC --private-key $PK
cast call 0xDEPLOYED "number()(uint256)" --rpc-url $RPC

The call answers 1. Paste the transaction hash into the explorer. Hardhat, ethers and viem work the same way: chain id 4465, the RPC above.

The RPC the node serves

Read from a devnet node, not from a spec. web3_clientVersion answers igneumd/2.1.0/execution-layer-v3. The full list, served and not served, with the probe that produced it: docs/build/rpc.md.

• Served. eth_chainId, eth_blockNumber, eth_getBalance, eth_getTransactionCount, eth_getCode, eth_getStorageAt, eth_getBlockByNumber, eth_getBlockByHash, eth_getTransactionByHash, eth_getTransactionReceipt, eth_getBlockReceipts, eth_getLogs, eth_call, eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas, eth_feeHistory, eth_sendRawTransaction, eth_syncing, eth_accounts, net_version, net_peerCount, net_listening, web3_clientVersion.
• Igneum's own. igneum_getExecStatus, igneum_getProvingStatus, igneum_getShardPlan, igneum_getProofRecords, igneum_getTransactionStatus, igneum_estimateGas, igneum_getBudgets and the segment and proof calls. igneum_estimateGas returns both gas dimensions and whether a call exceeds the proving limit.
• Not served. Filters and subscriptions (eth_newFilter, eth_subscribe), txpool_*, debug_*, trace_*, eth_sendTransaction, eth_sign, eth_getProof, the uncle calls. Poll eth_blockNumber and eth_getLogs. Sign on your side.

Verify a block in your browser

The site ships a light client. Your browser fetches the latest certified checkpoint from /api/checkpoint and verifies the BLS aggregate signature, the voter weights and the header chain itself, in the tab. Nothing is trusted from the server but the data. The example, in twelve lines, is docs/build/verify-a-block.md; the live run is verify/test.html, genuine and tampered cases side by side.

import { fetchCheckpoint, verify } from 'https://igneum.network/verify/verify.js';
const data = await fetchCheckpoint('https://igneum.network/api/checkpoint');
const r = verify(data);
console.log(r.verified, r.signers, 'of', r.voters, 'voters', r.ms, 'ms');

Where to ask

• An issue on the repository.
• Discord, the builders channel.
• Grants for tooling, reference apps, infrastructure and research.

Devnet coins have no value. Nothing on this page is an offer to sell anything.