Changelog

With the implementation of Timely Vote Credits (TVC) on Solana mainnet-beta starting from Epoch 703 (November 26, 2024 07:57:15 UTC), vote latency is now integrated into how we measure how effective a validator is on Solana.

Vote latency is the slot distance between the slot being voted for and the slot where the vote transaction lands. With the implementation of TVC, the protocol now rewards validators based on latency accordingly.

A validator that correctly votes within two (2) slots for the slot it is voting for will get the maximum 16 vote credits. For every slot that a validator delays its vote, it gets one (1) less vote credit, until such that it can only get the minimum of one (1). This means that at 18 slots of worth of latency or more, as long as a validator's vote is correct and is no later than 512 slots, it gets the minimum vote credit.

As such we assign a vote_score for every correct vote based on the vote credits it receives. We then multiply the total number of confirmed blocks by 16 to get the maximum possible vote credits such that the voting effectiveness rating is:

voting effectiveness = vote_score / (total number of confirmed blocks * 16)

We have reflected this change in our methodology docs, under Version 2.0 of the Solana Validator Effectiveness Rating.

You can now retrieve performance and rewards data for Ethereum based on UTC time intervals through our v1 endpoints!

How to Use It

Simply add utc=true to your existing API queries. That's it!

Note: UTC data is available for dates from October 1, 2024 onwards

Here's an example of how this would work 👇 When querying Coinbase's effectiveness from Nov 1-7 2024, you'll receive data in daily UTC intervals. 

Day alignment 
Since Ethereum epochs don't align perfectly with UTC midnight (they start at ~23:57 and end at ~00:03), we group epochs that start within a UTC day together. You can learn more about this here.

Ready to try it out? Check out the API docs here  👉  API Reference

If you have any questions or need support, don't hesitate to reach out to our team at hello@rated.network!

We’re excited to announce the Beta launch of EigenLayer on the Rated API! Starting today, you can access and query:

• Rewards data for EigenLayer operators and eigenpods, giving you a breakdown of all rewards earned by an operator and eigenpods over a specified time period across all networks that they are involved in.

  • GET /v1/eigenlayer/eigenpods/{address}/rewards

    • Provides a detailed summary of all rewards earned by a specific Eigenpod across all networks over a specified time period

  • GET /v1/eigenlayer/entities/{entity_id}/rewards

    • Provides the rewards earned by an entity (operator) across all networks over a specified time period

• Metadata related to EigenLayer operators and delegators, such as the delegation history by delegator or operator address.

  • GET /v1/eigenlayer/delegators/{address}/delegations

    • Data includes delegation details like the delegator’s address, Eigenpod address, operator, and time range for the delegation

  • GET /v1/eigenlayer/operators/{operator_id}/delegations

    • Returns operator delegation data, detailing delegator addresses, Eigenpod addresses, and the time periods for which the operator had delegated stake

    • Data is stored in daily snapshots

API reference for these endpoints can be found 👉 here

Beta Release and Pricing
During the beta period, access to these new endpoints will be free (no CU consumption). CU-based pricing will be introduced post-beta.

If you have any questions or feedback, feel free to reach out to us at hello@rated.network.

• 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

Effective Date: September 06, 2024

We are officially deprecating support for the Polygon network on both the Rated Explorer and the Rated API. Due to a lack of widespread adoption and the high cost of maintenance, we’ve made the decision to discontinue support.

• Impact: Users will no longer be able to access Polygon-related data or functionality in the Rated Explorer and Rated API after the deprecation date.

If you’re impacted and need assistance, please reach out to us at hello@rated.network!

We are discontinuing support for hourly updates on the validator endpoints and the predicted withdrawals feature due to low adoption rate and increased maintenance costs.

This change is effective as of July 24,2024.

Impacted Endpoints

Validator Endpoints

/v1/eth/validators/{validator_index_or_pubkey}/effectiveness

/v1/eth/validators/{validator_index_or_pubkey}/attestations

/v1/eth/validators/{validator_index_or_pubkey}/proposals

/v0/eth/validators/{validator_index_or_pubkey}/effectiveness

Predicted Withdrawal Endpoints

/v0/eth/withdrawals/predicted/operators/{operator_id}

/v0/eth/withdrawals/predicted/operators/{operator_id}

Key Resources

• API Reference

For support inquiries, please contact us at hello@rated.network. If you have feedback, we would love to hear from you at feedback.rated.network!

We have enhanced our Ethereum blocks endpoints to support real-time data retrieval. Users can now access data that is up to 2 epochs behind the current head of the chain at any time.

Impacted Endpoints

/v0/eth/blocks

/v0/eth/blocks/{consensus_slot}

Key Resources

• API Reference

• Glossary

For support inquiries, please contact us at hello@rated.network. If you have feedback, we would love to hear from you at feedback.rated.network!