Nobody can change the rules, and the hash is why
The validator has no upgrade path, no admin key and no parameter control, and there is no governance process because there is nothing for one to govern.
That is not a promise about our intentions. A Plutus validatorThe on-chain Cardano program that approves or rejects every transaction touching it; WHAT's checks the work and mints the reward. is its script hashThe hash computed over a Plutus script. It is the script's minting policy ID outright, and it is also what the script's address is built from, as that address's payment credential. Change one byte and you have a different script. — the hash computed over the script's own bytes. That hash is the policy IDThe identifier of a Cardano token's minting policy, and the only thing that tells the real WHAT from a token with the same name and logo. Here it is the hash of the validator script with this chain's three parameters applied — the script's own hash, before them, is not a policy ID. The validator's address is built from that same hash, used as its payment credential, so the two come from one value without being the same string., and it is also the payment credential the script's address is built from. Change one byte and the hash changes, so you get a different policy ID and a different address together: a different token, one that any holder's wallet will show as unrelated to what they hold.
What that makes permanent
- The cap and the schedule
- 21,000,000, fifty a block, halving every 210,000 blocks, indexed on height. Nobody can lift the cap, re-issue, inflate or shift the interval. See how many WHAT there will ever be.
- The one mint path
- A valid header spending the tip. No path can be added later, because adding one is editing the script. See how a WHAT comes into existence.
- The difficulty rule
- Including its half-life, which is compiled in beside the target rather than stored where a later transaction could move it. See how difficulty moves here.
- The payout rules
- Six of them, and together they say a block can add to what sits at the committed address and can never take from it. An account contract is a separate deployment that the validator knows nothing about, so that one can be replaced; these cannot. See where a block reward lands.
A mistake is permanent too. There is no mechanism to fix a flaw found after genesis, and the only remedy anybody would have is a different chain with a different policy ID. This is not a safety feature. It is a control that has been removed, and it cuts both ways.
How you check it rather than take our word
Read the script and look for the paths. A script with no admin path cannot grow one, because growing one changes the bytes, and changing the bytes changes the hash you verified. So the check is finite: it is a read of one script, once.
The hash you compare against is the one you worked out yourself when checking the minting policy ID. Nothing in this argument asks you to trust a statement on this page, including this one.
Which leaves the last thing to look at directly: what the validator does when a block arrives.