From 1eaffdd485360e25cd5c7c9bd485373c46c978ca Mon Sep 17 00:00:00 2001 From: glyh Date: Wed, 9 Sep 2026 13:47:22 +0800 Subject: [PATCH 1/2] docs(mesa): warn about --minimum-block-reward after the fork Mesa halves the coinbase from 720 to 360 MINA, so a Berkeley-era --minimum-block-reward threshold silently turns every won slot into an empty block. The daemon has no startup warning until MinaProtocol/mina#18919 lands, so document the check in the post-upgrade block producer tab. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_014798mUd8z65RxR38qcmm37 --- docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx b/docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx index c435123f5..79bc9ddfb 100644 --- a/docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx +++ b/docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx @@ -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 From 86fa4580a6e6c06291ffa10498925b540d965193 Mon Sep 17 00:00:00 2001 From: glyh Date: Wed, 9 Sep 2026 13:49:34 +0800 Subject: [PATCH 2/2] docs: regenerate llms-full.txt Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_014798mUd8z65RxR38qcmm37 --- static/llms-full.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/static/llms-full.txt b/static/llms-full.txt index 7173330c3..8227a2688 100644 --- a/static/llms-full.txt +++ b/static/llms-full.txt @@ -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