Blocks are produced with a coinbase value to zero.

[dannywillems]

The 0 coinbase issue recently on OpenMina’s side is very likely the pull-based SNARK rpc is not implemented on Rust’s side. I didn’t check, though.

Source: Increase events&actions limit MIP

See threads:

• https://o1-labs.slack.com/archives/C01SJSXSM7H/p1750847390448099
• Bring back snark persistence: iteration 1 MinaProtocol/mina#17559 (and related Slack thread: https://o1-labs.slack.com/archives/C0206B5S80Y/p1753342125959099).
• https://o1-labs.slack.com/archives/C07EYM9GR1U/p1752557619350869?thread_ts=1752066464.097739&cid=C07EYM9GR1U
• Channel: debugging-devnet-failures-june2025

[tizoc]

The 0 coinbase issue recently on OpenMina’s side is very likely the pull-based SNARK rpc is not implemented on Rust’s side. I didn’t check, though.

For the libp2p network it is not implemented (probably applies to any feature introduced to the OCaml node after 3.0.0 or 3.0.1). For the WebRTC network, snarks and transactions are fetched from peers after the initial sync is complete.

[0xMimir]

I believe the Rust implementation’s code in ledger/src/staged_ledger/staged_ledger.rs (lines ~1552–1563 and ~1592–1613 on the develop branch) does in fact permit blocks with non-zero coinbase rewards.

I also found evidence that the OCaml node implementation of Mina produces equivalent blocks with coinbase rewards (e.g., mainnet block 3NKa4dBL7axCvoTEGrCydzw6jvGrm1yaPYdo3uLKXSdgQzsojfpx and 3NL77Xq3iDEqLnW91xPGLe2MSCcvn2Kth6SvAoh9CTDYwSjxxCh5).

Therefore, this behaviour is not unique to the Rust node and may in fact reflect the protocol / expected behaviour rather than a bug exclusive to the Rust implementation.

This is also an issue on ocaml node #14543