Skip to content

LibraryPrivacy2021Design paperCorpus record

Iron Fish: a shielded payments chain

Iron Fish. Iron Fish.

Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
4

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    Shielded by default still has a view-key story and a consensus story. Default privacy is not the absence of those.

  2. Claim 02 · Paper model

    The proposal

    Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.

  3. Claim 03 · Paper model

    The mechanism

    Notes hide the amount and the parties. Nullifiers prevent double spends. That pair is the payment design.

  4. Claim 04 · Paper model

    The bound

    This note does not say the network is the only deployment of this paper.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    Shielded by default still has a view-key story and a consensus story. Default privacy is not the absence of those.

    Model

    What has to hold

    You are reading the Iron Fish whitepaper, not a miner dashboard.

    Falsifier

    What would retire it

    What consensus rule orders the notes?

  2. 02 The proposal

    Observation

    What the study says

    Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.

    Model

    What has to hold

    The document is the one at the source URL. A marketing page with the same brand is not this text.

    Falsifier

    What would retire it

    What does a transaction reveal on the public chain?

  3. 03 The mechanism

    Observation

    What the study says

    Notes hide the amount and the parties. Nullifiers prevent double spends. That pair is the payment design.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    What consensus rule orders the notes?

  4. 04 The bound

    Observation

    What the study says

    This note does not say the network is the only deployment of this paper.

    Model

    What has to hold

    You are reading the Iron Fish whitepaper, not a miner dashboard.

    Falsifier

    What would retire it

    Who can decrypt a note, according to the paper?

03 Sequence

One action, as an operating tape

  1. 01Notes hide the amount and the parties. Nullifiers prevent double spends. That pair is the payment design.
  2. 02A viewing key is how a user or an auditor sees a specific account. The existence of viewing keys is a deliberate disclosure tool, not a leak to ignore.
  3. 03Consensus on the chain of notes is still proof of work or whatever the whitepaper names. Privacy does not pick the fork.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    Sapling-like is not Zcash. The chain parameters differ.

  2. What actually moves

    The cut

    A viewing key is how a user or an auditor sees a specific account. The existence of viewing keys is a deliberate disclosure tool, not a leak to ignore.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

  3. What a later deployment may change

    The cut

    Consensus on the chain of notes is still proof of work or whatever the whitepaper names. Privacy does not pick the fork.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    Sapling-like is not Zcash. The chain parameters differ.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading the Iron Fish whitepaper, not a miner dashboard.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

Sapling-like is not Zcash. The chain parameters differ.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  1. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

Shielded by default still has a view-key story and a consensus story. Default privacy is not the absence of those.

What the design proposes

  • Notes hide the amount and the parties. Nullifiers prevent double spends. That pair is the payment design.
  • A viewing key is how a user or an auditor sees a specific account. The existence of viewing keys is a deliberate disclosure tool, not a leak to ignore.
  • Consensus on the chain of notes is still proof of work or whatever the whitepaper names. Privacy does not pick the fork.

How the mechanism is specified

  • Notes hide the amount and the parties. Nullifiers prevent double spends. That pair is the payment design.
  • A viewing key is how a user or an auditor sees a specific account. The existence of viewing keys is a deliberate disclosure tool, not a leak to ignore.
  • Consensus on the chain of notes is still proof of work or whatever the whitepaper names. Privacy does not pick the fork.

What this page does not treat as proven

  • This note does not say the network is the only deployment of this paper.
  • It states no hash rate and no anonymity-set size.
  • Sapling-like is not Zcash. The chain parameters differ.

Why the desk still reads it

Iron Fish publishes a payments chain whose transfers are shielded by default, using a note and nullifier construction in the Sapling line.

09 Lexicon

Terms, opened into the record

Viewing key
A key that reveals one party's notes without spending them.
Shielded by default
Transfers that are notes unless a user chooses a public path the paper allows.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.