Consensus block value calculation for produceBlockV3 API call.

[cheatfate]

No description provided.

[github-actions]

Unit Test Results

         9 files  ±0    1 113 suites  ±0   27m 41s ⏱️ + 4m 24s
  4 240 tests ±0    3 893 ✔️ ±0  347 💤 ±0  0 ❌ ±0 
16 915 runs  ±0  16 517 ✔️ ±0  398 💤 ±0  0 ❌ ±0 

Results for commit c53822f. ± Comparison against base commit 2d519ac.

♻️ This comment has been updated with latest results.

[tersec]

#6022 doesn't replace the "front-end" parts of this, but does provide a new back-end calculation approach

[tersec]

This 1000000000.u256 is unnecessarily runtime-constructed, complete with the customary usually pointless nimZeroMem():

N_LIB_PRIVATE N_NIMCALL(void,
                        blockConsensusValue__validatorsZbeacon95validators_112)(
    tyObject_BlockRewards__9c3PGRoMCH9aJ4gpUEVcHWJA *r,
    tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg *Result) {
  tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg T1_;
  tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg T2_;
  nimZeroMem((void *)(&T1_), sizeof(tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg));
  u256__specZvalidator_12417(
      (NU64)((NU64)((NU64)((NU64)((NU64)((NU64)((*r).attestations) +
                                         (NU64)((*r).sync_aggregate))) +
                           (NU64)((*r).proposer_slashings))) +
             (NU64)((*r).attester_slashings)),
      (&T1_));

  nimZeroMem((void *)(&T2_), sizeof(tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg));
  u256__OOZvendorZnim45ethZethZcommonZeth95types_308(((NI)1000000000), (&T2_));

  star___OOZvendorZnim45stintZstint_435((&T1_), (&T2_), Result);
}

Better to define it as a const to avoid the

  nimZeroMem((void *)(&T2_), sizeof(tyObject_StUint__ExULMdD1zVCTKy89cyuy4Dg));
  u256__OOZvendorZnim45ethZethZcommonZeth95types_308(((NI)1000000000), (&T2_));

part.

[cheatfate]

I wish not to change it, because its annoying, please re-read all the comments before and lets end it please. If you think its correct, lets use it as it is, because i wish not to check c-code on this specific thing, there is a lot more u256 conversions around which was not highlighted.
Also block-proposal is made once per 12 seconds on mainnet, so its CPU intensive operation.