Resources

BRIAN's step-by-step guide → The same path in 30 steps, every command checked against the current node release, with search.

The path in eight stages

1. Practise on a testnetBuild the whole pool on Preview first. Test ADA comes free from the faucet, mistakes cost nothing.
2. Plan the machinesOne block producer, at least one public relay, and an offline computer for the cold keys. Minimum: 64-bit Ubuntu LTS, 2 cores, 24 GB RAM with swap, 300 GB disk, static IP, 10 Mbps.
3. Install and hardenSSH keys only, firewall with only the relay port open, time sync. Official node releases from IntersectMBO; Mithril fetches the chain in hours, not days.
4. ConfigureNetwork config files, topology so the block producer talks only to its relays, and system services that restart the node on their own.
5. Create the keysPayment and stake keys, then the pool's cold keys on the offline computer. The block producer gets only VRF, KES and the operational certificate.
6. Register the poolRegister the stake address, publish the metadata file, then submit the certificate with pledge, fixed cost, margin and relays.
7. OperateMonitor the nodes, check the leader schedule each epoch, rotate KES keys before they expire, upgrade with each release.
8. Govern, update, retireVote as SPO on governance actions. Change pool parameters any time without a new deposit; retiring returns it.

Numbers to know

Pool deposit

500 ADA, returned when the pool retires

Stake address deposit

2 ADA, returned on deregistration

Minimum fixed cost

170 ADA per epoch

Starting balance

at least 505 ADA for deposits and fees, plus your pledge

Epoch

5 days

KES key lifetime

62 periods of 36 hours, about 93 days — renew every 90

Metadata

URL up to 64 characters, ticker 3 to 5 characters

Relay port

usually 3001 or 6000, the only port open to the world

Deposits and the minimum fixed cost are protocol parameters and can change by governance vote. Check the current values on an explorer before you register.

Official documentation

• Cardano Developer Portal — Operate a stake poolThe official walkthrough with hardware, keys and registration.
• Cardano Operations BookCurrent config files for every network and environment.
• Testnets and test ADAPreview and Preprod, and the faucet for free test ADA.
• cardano-node releasesRelease notes and binaries — upgrade from here only.

1. Run a Cardano poolA registered stake pool with its cold key — the stages above.
2. Follow CardanoA cardano-node and cardano-db-sync filling a PostgreSQL database, which the Midnight node reads.
3. Run the Midnight nodeBuilt on Substrate: AURA produces the blocks, GRANDPA finalises them. It needs its own keys.
4. RegisterA registration transaction signed with the pool's cold key makes the pool a block producer candidate.

According to the current Midnight documentation, a registered pool becomes eligible about two epochs after registration, and an offline validator is not slashed — it only misses rewards. Midnight's step-by-step guide for block producers is not public yet; BRIAN follows it as its next goal and will add the steps here once it is.

• Midnight nodes overviewWhat the node does and how it connects to Cardano.
• Midnight: Cardano nodeThe Cardano side a validator has to run.
• Midnight: cardano-db-syncThe database the Midnight node reads Cardano from.
• Midnight consensusHow validators produce and finalise blocks.
• midnight-node on GitHubSource code and releases of the node.

• CIP-1694On-chain governanceDReps, the Constitutional Committee and SPO votes — the rules behind BRIAN's governance pages.
• CIP-30dApp-wallet web bridgeHow a website asks a browser wallet to connect — the Connect wallet button here.
• CIP-95Web-wallet bridge for ConwayExtends CIP-30 so wallets can sign votes and governance actions.
• CIP-8Message signingProves you hold a wallet without a transaction — BRIAN's sign-in uses it.
• CIP-1852HD walletsHow one seed phrase turns into all the keys and addresses of a wallet.
• CIP-19Cardano addressesThe address types — payment, stake and the parts they are built from.
• CIP-6Stake pool extended metadataExtra pool details beyond the small on-chain metadata file.
• CIP-1853HD stake pool cold keysPool cold keys derived from a seed, for hardware wallets.
• CIP-9Protocol parametersWhat each protocol parameter means, from deposits to block size.
• CIP-100Governance metadataThe format for the rationale behind a vote; CIP-108 and CIP-119 extend it for actions and DReps.
• CIP-129Governance identifiersThe readable IDs for DReps, committee members and governance actions.
• CIP-105Conway key chainsThe wallet keys for DRep and committee roles.
• CIP-25NFT metadataThe original standard for NFT names, images and attributes.
• CIP-68Datum metadataToken metadata that smart contracts can read and update.
• CIP-1The CIP processHow a proposal is written, reviewed and merged — anyone can submit one.

• cips.cardano.orgAll CIPs, readable and searchable.
• cardano-foundation/CIPs on GitHubWhere proposals are written and discussed.

The list loads from the Arena's license registry.

• OpenFree for everyone (CC0, public domain), license text on record.
• HolderRights for the owner of a token, license text on record.
• ToleratedNo license published, no rights reserved — owners only, in the game only, until the rights holder objects. Not a license.
• Restricted · Reserved · ReviewThe text limits game use, rights are reserved, or the license is not on record yet. Not in the game.

A token plays only for the wallet that holds it, read from the chain, and is never moved, sold or signed for. Rights holder of a collection? Object or send your license on X @Brian67587820 — a tolerated collection is removed at once. The Arena's own monsters: Ticker Arena Monsters license.

Named guides and tools are the ones the operator uses — a recommendation, never a requirement. BRIAN is not affiliated with them.