grin
grin copied to clipboard
add utxo_sum and kernel_sum to block (header) api json
These are important pieces of internal data that we maintain per block.
It would be really useful to expose them at the individual block level via the api somehow.
Most people won't care about these but useful when debugging kernel summing issues etc.
Question: Would this be useful enough to justify adding to the API? Do we want to consider some dev or debug level APIs? Should these be different to the regular APIs?
All burning questions. Would it? Do we? Should they?
Something similar was pointed out late last year (something was missing from the header json). I think we agreed the header via the api should reflect the full header (with all fields).
@tromp I recall you being in that discussion. I forget what was missing from the header there specifically, maybe the mmr sizes?
This can be done on the API v2 also while keeping v1 as is.