Iron Fish primary sources

Reviewed: 2026-05-14 UTC

Whitepaper introduction / project framing

https://ironfish.network/learn/whitepaper/introduction
- Best concise statement of what Iron Fish claims to be.
- Used to confirm that Iron Fish frames itself as a chain-agnostic privacy platform for crypto, that mainnet launched in April 2023, that it is a proof-of-work L1, that all transactions are private, and that wallet-scoped view keys are a first-class auditability surface.

https://ironfish.network/learn/whitepaper/protocol/accounts
- Best source for the lower-layer account construction.
- Used to confirm that the account model is explicitly inspired by Sapling and is decomposed into secret/spending, authorization, nullifier, outgoing-view, incoming-view, and transmission keys.
- Especially useful for understanding that disclosure and spend authority are intentionally separated.

https://ironfish.network/learn/whitepaper/protocol/transactions
- Best source for transaction structure and privacy boundaries.
- Used to confirm that spend/output actions remain hidden and are validated with Groth16 zk-SNARKs, that notes and nullifiers are the core accounting objects, and that custom assets are supported.
- Also used to confirm the analytically important split where mint/burn actions and asset supply are public even though ordinary transfer flows are private.

https://ironfish.network/learn/whitepaper/protocol/blocks
- Best source for block structure, PoW framing, emissions, and mining-level mechanics.
- Used to confirm the heaviest-chain framing, 60-second target block time, block reward path, and the transition from Blake3 hashing to FishHash after Hardfork 1.
https://ironfish.network/learn/whitepaper/protocol/consensus
- Best source for consensus parameters and fork-choice details.
- Used to confirm heaviest-chain selection by cumulative work first, probabilistic finality, minimum fees, activation-gated consensus parameters, and the explicit role of governance in changing consensus.

https://fips.ironfish.network/fips/intro
- Best source for the protocol’s formal change process.
- Used to confirm that Fish Improvement Proposals govern protocol, consensus, networking, interface, and hardfork changes, and that practical authority over upgrades remains institutionally organized rather than constitutionally absent.
https://fips.ironfish.network/fips/fip-2-enforce-sequential-block-time
- Useful concrete governance example.
- Used to confirm that consensus changes can be activated at chosen block heights and that even timestamp-ordering policy is explicitly governed through the FIP process.
https://fips.ironfish.network/fips/fip-3-memory-hard-mining-algorithm
- Best concrete example of mining-policy governance in this pass.
- Used to confirm that Iron Fish changed its PoW design toward FishHash, a memory-hard algorithm intended to reduce ASIC/FPGA advantages and democratize mining hardware access.

https://github.com/iron-fish/ironfish
- Best repository-level source for current implementation framing.
- Used to confirm that the main codebase still presents Iron Fish as a privacy-focused Layer 1 using zk-SNARKs, and to ground the protocol docs in a live reference implementation rather than whitepaper prose alone.

Iron Fish is best understood as a privacy-default settlement chain with explicit wallet-level auditability and partially public asset-policy surfaces, not as a monolithic private coin.
The most useful comparison split is between hidden note-based transfers and the public policy/control layer around fees, mint/burn, asset supply, mining, and hardfork activation.
Iron Fish is especially valuable in the corpus because it sits between Zcash-style shielded accounting and more governance-heavy privacy-infrastructure ambitions: privacy is default, but consensus and mining policy remain actively governable through formal upgrade machinery.