Endpoints
The three endpoints below answered from a clean read at 11:41 UK on 11 October 2026 with their held state (a 503 and the reason, with the headers a browser needs), so they are listed as held, not as open; they open on the chain's word after its genesis. On 11 October 2026 the development chain of the day is devnet5, sealing from its genesis (run 9) since 12:02 UK on three nodes, on a private mesh until its endpoints are opened. A development chain may reset, and nothing mined on it converts to anything: the development genesis and the launch genesis are different files, so there is no private conversion of development balances by construction.
| item | value |
|---|---|
| chain name | Igneum devnet5, chain id 7315 (the network id 7351): the chain is told apart by its chain id and network id, never by its genesis hash alone, because the genesis hash covers none of the engine block's constants and another development chain with the same genesis fields carries the same hash |
| genesis hash | 0xcb0784a9b97803f8ff38cba00356943a0dd27caf675bfeb051611682414da358, beside the chain id 7315 (run 9, from genesis at 12:02 UK on 11 October 2026, on three nodes); no further reset without the project's word |
| the reset history | two runs on 11 October 2026: run 8 from 11:53 UK (genesis 0xe7adfe8e014bff9498c37c0dacf447f8f4578d950025981daea3b739d84a5a71) read 9.5 s a block because the seal itself took 6 s at the difficulty floor 65536 on the CPU reference and the difficulty rule cannot go under its floor; run 9 from 12:02 UK lowered the floor to 8192, and the genesis difficulty field being the floor, the hash moved; run 8 is dead |
| the node | sha bd97887d |
| joining | a node joining devnet5 must start with the research difficulty flag (--dev.difficulty, with the record's values: the floor 8192, a half-life of 1,200, a maximum step of 1,200), because the genesis hash does not cover the engine block's constants and a node without it refuses from block 5; the record of both runs is cited here and linked the day its public URL is named (Evidence link pending) |
| the chain's parameters (research values) | registry version 3 with the secret-reveal stand-in; a block target of 5 s; epochs of 100 blocks; the seed over 1,024 blocks; S_ref 11,780,607 IGN; the static cap 500,000 IGN; two genesis bonds of 471,225 IGN each; no endorsements on this chain; the proof image id 006bf405 |
| the read-only RPC | https://build.igneum.network/devnet5/rpc (POST, JSON-RPC 2.0; HTTP read-only: the write and admin namespaces refused; 20 requests a second per source, burst 40; batches up to 20); held with a 503 "this endpoint is not open yet" until it is opened, which this page reads as held, never as an error |
| the endpoint's state | https://build.igneum.network/devnet5/health (GET); held the same way until opened |
| the WebSocket for a wallet | wss://build.igneum.network/devnet5/ws (read namespaces; a read-namespace socket cannot filter by method, so a raw transaction remains callable there); held until opened |
| the explorer | not yet named |
| the faucet | not yet named |
| the node binary and its checksum | with the release |
The development chains the project runs
The proofs on this site were carried on two-node development chains the project runs on its own machines, one node of each pair built independently from a different toolchain. Their records are in the repository by height, with both nodes' verdicts; none of them is public and none is listed here as an endpoint.
| chain | what it carried |
|---|---|
| the two-node chain of 10 October 2026 | the seven height-activated transitions of operational succession, with the ratification margin exercised and no manual intervention |
| the two-node chain of 11 October 2026 | the warm round trip from the launch document to the item-as-programme relation and back (consensus final); the same with a CUDA worker on a rented 5090 (final on the tested pair); the cold pair as the bounded fallback |
| the two authority pairs | the work-authority prototype: every keyed-proof refusal, the draw and the fork weight, the payout list paid exactly, liveness with every bonded sealer dark, rotation, 200 invalid keyed blocks refused; a fresh node reproducing the chain from genesis past an epoch change |
| the pool's chain | the non-custodial pool paying members directly from a member-sealed block carrying the payout list, with signed receipts per share; the attribution diagnostic computed from the chain's own records |
The launch design has one genesis and requires every accepted launch rule to activate from block zero; it is not yet a completed genesis. The mining interface is a published RPC: a template in, a solution out, so solo mining against your own node and independent pools exist from the start, and the development stand-in algorithm cannot be named by a launch or test-network genesis.
What is on the feed from the development chains
The attribution diagnostic reads the development chains over their trailing window and publishes each key's share of accepted work: a prototype and a diagnostic, never a trigger, the keys and addresses being payout keys and not people or suppliers. It is on Verify it yourself.
Where it is written
The node's design (the node, the one genesis, the mining RPC, the transition rows), the work-authority prototype's record (the authority pairs) and the ecosystem design (the pool and the diagnostic). Each is linked from this page the day its public URL is named.