- site/build.html and site/grants.html rendered by site/build.mjs from docs/build/build.md and docs/build/grants.md (the gate's site-only copy keeps the committed pages, as for /bench); site-relative links in the markdown renderer - the nav's fourth group, Build (/build, /faucet, /grants), in the partial, the sheet, the footer, the sitemap and tools/ci/site-nav-check.mjs; the faucet leaves the Mine panel - site/faucet.html is the Devnet 3 faucet: 10 IGN per address per day, 500 a day, chain id 4463, no value, resets without notice; the page posts to https://faucet.igneum.network/api/faucet and shows the balance - infra/build-server/faucet: faucet.mjs (zero dependencies, signs with site/lib/eth.mjs, limiter self-test known-failed first, 100 IGN cap on the amount), the unit, faucet.sh install/status; live on build-1 behind Caddy since 10:16Z, funded 2,000 IGN by the fleet's funder at 10:01Z; first drip 0x8620e9d8 at 10:17Z - docs/build: README, first-contract.md with its test script and the PASS line (24 s end to end through the public RPC and faucet, Foundry 1.8.5, Counter deployed at block 27055), rpc.md read from the node (75 methods probed, served and not served), faucet.md, verify-a-block.md, grants.md - .forgejo/issue_template/grant.md: the grant application template on git.igneum.network Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
6.6 KiB
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 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, and the proof follows the tip by tens of seconds. Your contract runs on a chain whose state is proven, not assumed.
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
| Devnet 3 | Testnet | Mainnet | |
|---|---|---|---|
| Chain id | 4463 (0x116f) |
4462 (0x116e) |
4461 (0x116d) |
| Network id | igneum-devnet-3 |
igneum-testnet-1 |
not started |
| RPC | https://rpc.devnet.igneum.network (a node you run serves http://127.0.0.1:26790) |
https://rpc.testnet.igneum.network (answers; nothing mines there yet, so a transaction waits) |
none |
| Coins | no value, resets without notice | no value, resets with notice | not started |
| Symbol, decimals | IGN, 18 | IGN, 18 | IGN, 18 |
Devnet 3 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. The public testnet exists, its RPC answers, and no blocks are being produced on it until it opens. Mainnet has no date. Devnet 3 answers chain id 4463 until its class v5 floor, then 4464.
Endpoints and tools
- Wallet. Any Ethereum wallet. Add Igneum to MetaMask with one click, or the Igneum wallet.
- Faucet. 10 IGN of Devnet 3 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. A swap on Devnet 3 is being built. This page links it when it serves.
- 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 Devnet 3 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 4463, the RPC above.
The RPC the node serves
Read from a Devnet 3 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_getBudgetsand the segment and proof calls.igneum_estimateGasreturns 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. Polleth_blockNumberandeth_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 and testnet coins have no value. Nothing on this page is an offer to sell anything.