Skip to content

docs(mesa): warn about --minimum-block-reward after the fork #1244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dkijania merged 2 commits into from
Sep 14, 2026
+12 −0
Merged

docs(mesa): warn about --minimum-block-reward after the fork #1244

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1eaffdd
docs(mesa): warn about --minimum-block-reward after the fork
glyh Sep 9, 2026
86fa458
docs: regenerate llms-full.txt
glyh Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,12 @@ Then run the role-specific checks below.

Verify block production the same way you would on Berkeley — see [Block Producer Node](/node-operators/block-producer-node) for the relevant `mina client status` fields and checks. If you are a Delegation Program participant, your uptime continues to be tracked on the Mesa chain.

:::caution `--minimum-block-reward` above the new coinbase
Mesa halves the coinbase from 720 MINA to 360 MINA ([Faster Blocks — MIP6](/network-upgrades/mesa/glossary#faster-blocks--mip6)). If you set `--minimum-block-reward` to a threshold that made sense on Berkeley, it is probably above the Mesa coinbase now. A block producer whose reward falls under the threshold still wins its slot but produces an **empty block**, which carries no coinbase and no fees. Block production looks healthy while you earn nothing.

The daemon does not currently warn about this ([mina#18919](https://github.com/MinaProtocol/mina/pull/18919) adds a startup warning but is not merged). Check the flag yourself and lower or remove it after the fork.
:::

#### Check logs for errors

```bash
Expand Down
6 changes: 6 additions & 0 deletions static/llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5782,6 +5782,12 @@ Then run the role-specific checks below.

Verify block production the same way you would on Berkeley — see [Block Producer Node](/node-operators/block-producer-node) for the relevant `mina client status` fields and checks. If you are a Delegation Program participant, your uptime continues to be tracked on the Mesa chain.

:::caution `--minimum-block-reward` above the new coinbase
Mesa halves the coinbase from 720 MINA to 360 MINA ([Faster Blocks — MIP6](/network-upgrades/mesa/glossary#faster-blocks--mip6)). If you set `--minimum-block-reward` to a threshold that made sense on Berkeley, it is probably above the Mesa coinbase now. A block producer whose reward falls under the threshold still wins its slot but produces an **empty block**, which carries no coinbase and no fees. Block production looks healthy while you earn nothing.

The daemon does not currently warn about this ([mina#18919](https://github.com/MinaProtocol/mina/pull/18919) adds a startup warning but is not merged). Check the flag yourself and lower or remove it after the fork.
:::

#### Check logs for errors

```bash
Expand Down
Loading