Changelog

• SyncSignatureCount added to entities endpoint

  • The syncSignatureCount field has been added to the /v1/eth/entities/{entity_id}/attestations endpoint, providing a more complete view of validator performance in the sync committee. This field was previously only available in the /v1/eth/validators/{validator_index_or_pubkey}/attestations endpoint

  • Impacted endpoints: v1 entities endpoints

• Fix for from parameter in ChainDailyRewards endpoint

  • Resolved a 500 error occurring when using the from parameter in the chainDailyRewards endpoint, caused by a datatype mismatch (int vs. string)

  • Additionally, functionality has been added to support using UTC days in the from parameter for greater flexibility

  • Impacted endpoints: v0/eth/network/chainDailyRewards

• New Ethereum chain days endpoint

  • Added a new chainDailyRewards endpoint based on Ethereum chain days, in addition to the existing dailyRewards endpoint which is based on UTC days

  • Impacted endpoints: v0/eth/network/chainDailyRewards and v0/eth/network/chainDailyRewards/{day}

• Additional validator balance field in Rewards endpoint

  • The v0/eth/network/chainDailyRewards endpoint now includes the latest total effective balance of validators, providing more insight into validator performance

• Slot and timestamp fields added to Rewards endpoints

  • Introduced startSlot, endSlot, startTimestamp, and endTimestamp fields to rewards endpoint

  • The changes impact validator, entities, and network endpoints for enhanced data consistency across different API responses

• Data type update for execution rewards on Rewards endpoints

  • Modified the data type for execution reward columns (e.g., sum_priority_fees_wei and sum_baseline_mev_wei) from StrictInt to Decimal to improve accuracy.

  • Impacted endpoints: v1 rewards endpoints for validators

We've addressed an issue affecting the blocks endpoint, which resulted in the overstated reporting of execution layer rewards for a subset of blocks proposed via mev-boost.

This discrepancy was identified in cases where proposers were partially compensated by builders through internal transactions, with failed payments not being excluded from the calculations.

To rectify this, we've implemented a filter to exclude these failed transaction traces, and performed a comprehensive refresh of the blocks endpoint data. The columns updated include baseline_mev, execution_rewards, missed_execution_rewards, total_rewards, and total_rewards_missed.

Impacted endpoints 👇

• /v0/eth/blocks

• /v0/eth/blocks/{consensus_slot}

This fix was applied retroactively (on 13th March 2024 at 8:43PM UTC) and impacts less than 0.5% of all blocks since the merge.

If you’d like support or have questions, please reach out via [email protected]. If you have feedback, please let us know via feedback.rated.network!