GUI console RPC reflects different config value than bitcoin-cli query
Observed in !1776 (merged) :
when I try to run the GUI app standalone with
-blockmaxsize
values, the RPC's new field always return 32000000
[in the GUI's Console window. If the GUI is queried via bitcoin-cli, the correct expected value from configuration is returned]
An issue was confirmed already back with v24.0.0 (albeit a different config, accessed through setexcessiveblock/getexcessiveblock) where the updated EB does not reflect via RPC in the GUI (but in that case it also does not reflect when GUI was queried via bitcoin-cli).
The GUI seems to have its own idea of what the excessive block size and the mining block size are. Possible (likely even) this extends to more configuration items.
The expected behavior is that all config values accessible via RPC queries, show the same values whether queried via bitcoin-cli or in the GUI Console.