We’re placing the solo staker list where it belongs: in the hands of the community.

The solo-staker filter and repository, originally curated by Rated Labs, is being handed over to EthStaker for ongoing stewardship.

What’s Changing

1. Management & Oversight

   • Before: Rated managed and updated the “solo-stakers” repository, which contains heuristics and lists mapping addresses to potential solo validators on Ethereum.

   • Now: EthStaker will assume primary responsibility for maintenance, updates, and community support. This includes curating new releases, reviewing community feedback, and stewarding the underlying dataset.

2. Methodology & Data

   • The existing methodology documentation (including the September 2024 update and prior versions) remains publicly accessible.

   • EthStaker now manages all relevant data and methodologies, including deposit address mappings, withdrawal address associations, and the supporting heuristics.

3. Community Involvement

   • Feedback, issues, and pull requests will now be directed to EthStaker, fostering a broader decentralized ethos for the project.

   • For the transition period in the near term, Rated will stay involved as an advisor, helping address any questions on methodology while EthStaker manages the dataset.

Why EthStaker?

EthStaker is a community dedicated to fostering a healthy and decentralized Ethereum staking ecosystem. With their active presence in the Ethereum solo staker community, they are well-positioned to guide the repository’s future growth and ensure it remains a trusted resource for identifying self-sovereign stakers.

Looking Ahead

• Community Feedback: We encourage validators, researchers, and the broader Ethereum community to provide feedback on the solo staker filter and make suggestions for improvements.

• Periodic Updates: EthStaker will continue publishing refreshed lists based on new data, feedback, and evolving best practices, ensuring the dataset remains accurate and relevant.

• Opportunities for Innovation: This handover paves the way for deeper integration with new staking tools, potential airdrops targeting solo stakers, and other community-led initiatives that benefit from identifying solo validators.

How to Get Involved

• Star & Fork the repository to show your support and keep track of updates.

• Open Issues or Pull Requests with questions or improvements.

• Join EthStaker’s Channels (e.g., Reddit, Discord) to participate in discussions, share feedback, and stay informed about the latest development.

By entrusting management to EthStaker, we hope to further democratize access, stewardship, and innovation in Ethereum staking. We appreciate the continued support from the entire staking community and look forward to seeing how EthStaker evolves this initiative.

We’re excited to announce the launch of Celestia on the Rated API!

Starting today, you can access and query rewards data for validators on the Celestia, both at an individual level and network level over a specified time period:

GET /v1/celestia/validators/{node_id}/rewards

• Provides a detailed summary of all rewards earned by a specific validator, identified by their validator_address Sample Request

curl -X 'GET' 'https://api.rated.network/v1/celestia/{validator_address}/rewards?fromDate=2025-01-01&toDate=2025-01-05' 
-H 'accept: application/json' 
-H 'Authorization: Bearer <api_token>'

Sample Response (trimmed for brevity)

{
   "previous":null,
   "next":null,
   "pages":1,
   "results":[
      {
         "day":"2025-01-05",
         "validator":"{validator_address}",
         "validatorMoniker":"{validator_name}",
         "consensusAddress":"celestiavalcons1uh9wyuh",
         "consensusPubkey":"vrSsYrWno/rLAE0aGsqO/XkrE=",
         "accountAddress":"celestia1xqc7wkg4tswjt7mn4p38v",
         "fromBlockNumber":3330254,
         "toBlockNumber":3346421,
         "totalDelegationRewards":3458.99139127356,
         "totalCommissionRewards":345.899139127356,
         "commissionRate":0.1
      },
...
      {
         "day":"2025-01-01",
         "validator":"{validator_address}",
         "validatorMoniker":"{validator_name}",
         "consensusAddress":"celestiavalcons1uh9wyuh",
         "consensusPubkey":"vrSsYrWno/rLAE0aGsqO/XkrE=",
         "accountAddress":"celestia1xqc7wkg4tswjt7mn4p38v",
         "fromBlockNumber":3314016,
         "toBlockNumber":3330253,
         "totalDelegationRewards":3731.780361524,
         "totalCommissionRewards":373.17802385361523,
         "commissionRate":0.1
      }
   ]
}

GET /v1/celestia/network/rewards

• Provides historical network level validator rewards for Celestia Sample Request

curl -X 'GET' 'https://api.rated.network/v1/celestia/network/rewards?fromDate=2025-01-01&toDate=2025-01-02' 
-H 'accept: application/json' 
-H 'Authorization: Bearer <api_token>'

Sample Response

{
   "previous":null,
   "next":null,
   "pages":1,
   "results":[
      {
         "day":"2025-01-02",
         "fromBlockNumber":3330254,
         "toBlockNumber":3346421,
         "totalBondedValidators":100,
         "totalDelegationRewards":208637.819,
         "totalCommissionRewards":26793.123,
         "avgCommissionRate":0.0932
      },
      {
         "day":"2025-01-01",
         "fromBlockNumber":3314016,
         "toBlockNumber":3330253,
         "totalBondedValidators":100,
         "totalDelegationRewards":208605.944,
         "totalCommissionRewards":26792.561,
         "avgCommissionRate":0.0932
      }
   ]
}

Learn more We encourage you to check out our API documentation to learn more about rewards behavior on Celestia. You can also find a glossary for the different fields in the responses returned by these endpoints. Lastly, we have historical rewards data going back to December 1, 2024, and are currently working to extend this further back into October 1, 2024.

Beta Release and Pricing During the beta period, access to these new endpoints will be free. Compute unit based pricing will be introduced post-beta.

More to come This is part of Rated’s ongoing effort to expand its coverage to more chains and networks. Stay tuned for more!

If you have any questions or feedback, especially on which networks we should cover, feel free to reach out to us at feedback.rated.network or at hello@rated.network.

We’re excited to announce the launch of Avalanche on the Rated API!

Starting today, you can access and query rewards data for validators on the Avalanche Primary Network, both at an individual level and network level over a specified time period:

GET /v1/avalanche/validators/{node_id}/rewards

• Provides a detailed summary of all rewards earned by a specific validator, identified by their node_id Sample Request

curl -X 'GET' 'https://api.rated.network/v1/avalanche/validators/{node_id}/rewards?fromDate=2024-12-01&toDate=2024-12-05' 
-H 'accept: application/json'  
-H 'Authorization: Bearer <api_token>'

Sample Response (trimmed for brevity)

{
   "previous":null,
   "next":null,
   "pages":1,
   "results":[
      {
         "day":"2024-12-05",
         "nodeId":"{node_id}",
         "validationStatus":"inactive",
         "validatorPubkey": "0x8f8df4745a1329a6318634e60332df71ecc4a9430d",
         "totalDelegatorRewards":1.55,
         "totalValidatorRewards":290.90,
         "totalValidatorFeeRewards":0.08,
         "totalPotentialDelegatorRewards":0,
         "totalPotentialValidatorRewards":0,
         "totalPotentialValidatorFeeRewards":0
      },
<...>
      {
         "day":"2024-12-01",
         "nodeId":"{node_id}",
         "validationStatus":"active",
         "validatorPubkey": "0x8f8df4745a1329a6318634e60332df71ecc4a9430d",
         "totalDelegatorRewards":0,
         "totalValidatorRewards":0,
         "totalValidatorFeeRewards":0,
         "totalPotentialDelegatorRewards":2516.64,
         "totalPotentialValidatorRewards":7904.87,
         "totalPotentialValidatorFeeRewards":51.50
      }
   ]
}

GET /v1/avalanche/network/rewards

• Provides historical network level validator rewards for the Primary Network Sample Request

curl -X 'GET' 'https://api.rated.network/v1/avalanche/network/rewards?fromDate=2025-01-26&toDate=2025-01-27' 
-H 'accept: application/json' 
-H 'Authorization: Bearer <api_token>'

Sample Response

{
   "previous":null,
   "next":null,
   "pages":1,
   "results":[
      {
         "day":"2025-01-27",
         "totalActiveValidators":1518,
         "totalValidatorRewards":6920.434755523,
         "totalValidatorFeeRewards":2.489666824,
         "totalDelegatorRewards":1717.71544618,
         "totalPotentialValidatorRewards":7156084.009812852,
         "totalPotentialValidatorFeeRewards":37273.058757847,
         "totalPotentialDelegatorRewards":494018.077133481
      },
      {
         "day":"2025-01-26",
         "totalActiveValidators":1505,
         "totalValidatorRewards":1488.872838484,
         "totalValidatorFeeRewards":3.09354756,
         "totalDelegatorRewards":2440.470582821,
         "totalPotentialValidatorRewards":7152926.77444416,
         "totalPotentialValidatorFeeRewards":37281.047946395,
         "totalPotentialDelegatorRewards":494245.251667358
      }
   ]
}

Learn more As with all networks, there are nuances to how rewards behave on Avalanche. We encourage you to check out our API documentation to learn more, which also contains a glossary for the different fields in the responses returned by these endpoints. Lastly, we have historical rewards data going back to October 1, 2024.

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

More to come This is part of Rated’s ongoing effort to expand its coverage to more chains and networks. Stay tuned!

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

The issue we mentioned last week with the ethPrice and usdPrice being returned by our Eigenlayer rewards endpoints has been fixed. Specifically these endpoints are:

• /v1/eigenlayer/entities/{operator_address}/rewards/

• /v1/eigenlayer/delegators/{delegator_address}/rewards/

• /v1/eigenlayer/eigenpods/{eigenpod_address}/rewards

We have also applied the correct historical conversion rates to past rewards. This means that both historical rewards and rewards moving forward will have the correct ETH and USD pricing as long as the particular set of rewards are claimable (activatedAt) and the related token has the appropriate liquidity.

Rest assured that we have taken steps to ensure that instances like this are minimized moving forward.

If you have any questions or feedback, feel free to go to feedback.rated.network.

For more information on our API endpoints, please see our documentation.

Compute units (CUs) consumed for API calls are now available in the response header. This has been requested by our customers in order to have more visibility on consumption, and we are glad to have finally enabled this feature.

Below is an example using one of our rewards endpoints.

Request

curl -v -X 'GET' 'https://api.rated.network/v1/eigenlayer/delegators/{delegator_address}/rewards?fromDate=2025-01-15&toDate=2025-01-16' 
-H 'accept: application/json' 
-H 'X-Rated-Network: mainnet' 
-H 'Authorization: Bearer <api_key>

Response header

using HTTP/1.x
GET (…)
Request completely sent off 
< HTTP/1.1 200 OK 
(...)
< x-rated-bytes-consumed: 2069 
< x-rated-compute-units: 6869 
(...)
Connection #0 to host api.rated.network left intact

x-rated-compute-units is the field the that gives the total compute units consumed by the request and the successful response. In this case, the CUs consumed is 6869.

Stay tuned for more releases regarding billing and usage transparency.

For more information on our pricing and the computation of compute units, please see here.

We are aware of an issue with the ethPrice and usdPrice being returned by our Eigenlayer rewards endpoints below:

• /v1/eigenlayer/entities/operator_address/rewards/

• /v1/eigenlayer/delegators/delegator_address/rewards/

• /v1/eigenlayer/eigenpods/eigenpod_address/rewards/

The prices being returned are wrong and we are working on a fix to address this. For now, please only use the amount field to measure the rewards for the corresponding token information being given in the response.

We apologize for any inconvenience this may have caused and will immediately keep you all updated as we address this issue in the coming week (week of January 20, 2025).

We have made changes to what was then the v1/eigenlayer/rewardsApiMetadata endpoint. Previously, this returned metadata specific to the latest complete rewards data available from our Eigenlayer rewards APIs. With the release of our new daily stake state endpoints, we have now turned this endpoint into a more generalized one. Two main changes below.

New name: v1/eigenlayer/apiMetadata

Old name: v1/eigenlayer/rewardsApiMetadata

New response schema:

{  
     "rewardsLastFullDay": "2024-12-16",  
     "rewardsLastSnapshotTimestamp": 1734393600000,  
     "rewardsDistributionRootIndex": 21,
     "stateLastFullDay": "2024-12-30"
}

There are now fields specific to the latest data freshness of the rewards API endpoints and the state endpoints.

For more information, see our docs here: Eigenlayer API Metadata

We’ve released three new endpoints regarding daily restaked balances in Eigenlayer. These are:

• v1/eigenlayer/eigenpods/eigenpod_address/state

• v1/eigenlayer/entities/operator_address/state

• v1/eigenlayer/delegators/delegator_address/state

These endpoints allow you to track restaked balances across operators, delegators, and eigenpods on a daily level.

Sample response:

{
     "date": "2024-10-01",
     "earner": "0xB0bd0c91798d720a5585364bb4be7396c5b9731",
     "strategy": "0x54945180dB7943c0ed0FEE7EdaB2Bd24620256bc",
     "tokenAddress": "0xBe9895146f7AF43049ca1c1AE358B0541Ea49704",
     "totalShares": 12000000000000000000,
     "totalBalance": 12000000000000000000
}

Coupled with our Eigenlayer rewards endpoints, you’ll be able to track rates of return per operator and asset, and manage strategies accordingly.

Speaking of our rewards endpoints, the functionality of these existing endpoints have been extended to enable time-based aggregations using the granularity parameter, specifically weekly aggregations. As such we’re also changing the compute unit consumption of this endpoint to reflect this change; 7x increase to account for the capability to aggregate weekly (from daily).

For more information on these endpoints, please see here:

• Stake state endpoints: Eigenlayer API Metadata

• Expanded rewards endpoints: Eigenlayer Rewards

We’ve completed the migration of all Solana API endpoints to the v1 standard, introducing improvements and consistency across our infrastructure:

Key Updates

• Standardized endpoint naming aligned with v1 schema

• Enhanced performance via optimized v1 routing

API Reference 👉

Solana API Reference

Legacy endpoints will remain operational until we deprecate the v0 endpoints in Q1 2025.

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

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. If you have feedback, please let us know via feedback.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!

We are excited to announce the support of Solana on the Rated API, Explorer, and documentation hub. This update allows developers to access curated Solana data, develop reporting applications, create custom dashboards, and integrate a real-time, outside-in view into their monitoring stack.

• Validators: Monitor performance, benchmark against peers, and gain an external view on their infrastructure. View all validator endpoints and validator views on Explorer.

• Delegators: Make informed delegation decisions, review performance, manage rewards, and view commission rates. View all delegator endpoints and delegator views on Explorer.

• Pools & Active Set Managers: Evaluate validator performance for onboarding, SLAs, and off-boarding. View pool view on Explorer.

• Network Researchers: Monitor network health and gain insights for research and development. View all network endpoints and network views on Explorer.

Check out Solana on the Explorer and view our docs to help navigate through the different views.

Get started with the Rated API for Solana at rated.network/apis and explore our comprehensive API documentation hub for detailed guidance.

If you have any questions or need support, don’t hesitate to reach out to our team at hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

Rated API v1 is now available in public beta! After iterating on months of valuable feedback from our users, we have upgraded from v0 to bring you a more intuitive API design.

API v1 comes on Ethereum first. In the coming weeks, we’ll enhance the Ethereum suite to match the full capabilities of v0 on v1. We’ll also be working on bringing Polygon & upcoming network APIs to v1.

Enhanced User Experience

We’ve redesigned our API from the ground up, focusing on simplicity and usability. No more heavy endpoints that are difficult to parse. The new endpoints are categorized as:

• Performance APIs: Accurately track, improve and benchmark your current and historical validator fleet performance.

• Rewards APIs: Deploy precise accounting in a few simple calls, with granular tracking of validator rewards earned.

• Metadata APIs: Help users make informed decisions around staking with access to rich metadata about an entity’s useful life.

Improved Pagination

Navigating through data is now more efficient. We’ve upgraded to a limit-based pagination and introduced sorting to ensure that you can access large datasets quicker and with less hassle.

Performance Enhancements

Smaller payloads means faster response times and reduced latency so that your applications can operate more efficiently and reliably.

Important Links

• API Reference

• Swagger docs

• How pagination works

Disclaimer As we step into the public beta phase, anticipate encountering bugs and areas in need of UX refinement. This period is crucial for us to enhance feature stability, integrate user feedback, and ensure a seamless experience moving forward. Your understanding and contributions are invaluable!

We will also be gradually releasing guides and documentation on v1 as we complete the full rollout in Q2 2024. Rest assured that we will be maintaining both v0 and v1, until we sunset v0 in early Q3 2024.

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

Organizations within the Build and Growth tiers can now create and utilize private pre-materialized sets. This feature enables the creation of custom sets of validators, each marked with a unique tag for private use. It is aimed at enhancing capabilities in performance benchmarking, rewards accounting, and validator set management.

Quickstart

• Tags: Validators within a set are tagged with identifiers unique to your organization, allowing for private viewing of performance and rewards metrics. This facilitates efficient analysis, A/B testing of node setups, and confidential grouping of validators for specific customers.

• Easy API Integration:

To create a tag, initiate a POST request to /v1/eth/tags with your desired validators

• Retrieve performance and reward metrics via GET requests to /v1/eth/sets/:id/effectiveness or /v1/eth/sets/:id/rewards

Limits

• Build tier users can create up to 4 tags

• Growth tier users can create up to 20 tags

Important links 👇

• API Reference

• How-To Guide

• Compute Units

If you’d like support or have questions, please reach out via hello@rated.network. As we have launched this in beta, your feedback is crucial. Let us know at feedback.rated.network!

A new page, Native Restaking, on the Rated Explorer is now available, dedicated to detailed restaking stats. This enhancement provides users with access to comprehensive metrics surrounding the Ethereum native restaking ecosystem. Key metrics featured include:

• Total amount of ETH natively restaked

• Percentage of the validator fleet natively restaked at the operator level and their market share

• RAVER of validators at an operator level engaged in native restaking

To further aid in the visibility and understanding of native restaking participation, a restaking icon has been introduced in the operators list view. This icon serves as a quick visual indicator of which operators are actively participating in native restaking.

As the restaking ecosystem continues to evolve and mature, we are committed to regularly updating and enriching this data.

Restaking dashboard 👉 explorer.rated.network/restaking

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

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 hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

In preparation for the Dencun Upgrade on Ethereum slated for 13th March, we are introducing the following changes to the API:

• We’re tracking the count of type 3 transactions (0x03; blob transactions) and the corresponding fees related to these transactions in the blocks endpoint. Impacted endpoints:

/v0/eth/blocks

/v0/eth/blocks/{consensus_slot}

• Accordingly, the validator rewards from these transactions are tracked in all our rewards endpoints which ensures we are accounting for all rewards that validators receive. Impacted endpoints:

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

/v0/eth/validators/effectiveness

/v0/eth/validators/{validator_index_or_pubkey}/apr

/v0/eth/operators/{operator_id}/effectiveness

/v0/eth/operators/{operator_id}/apr

/v0/eth/network/overview

Important links 👇

• API Reference: https://api-docs.rated.network/rated-api/api-reference

• Glossary: https://api-docs.rated.network/rated-api/glossary/ethereum/blocks

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

We’ve revamped the Rated Explorer, enhancing design and functionality for a better user experience. Key updates include a cleaner interface for efficient data access, intuitive navigation across networks, and improved sorting. The search feature is also upgraded for easier discovery of pool operators, addresses, or indices.

The explorer also got its own dedicated namespace in👉 explorer.rated.network

Following the launch, navigating to rated.network will direct users to Rated’s homepage. Access to all explorer pages will require visiting explorer.rated.network (bookmark for ease of access!).

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

We’ve launched a Python SDK for the Rated APIs to make integrating with our data easier and faster. The SDK support comes on Ethereum first with plans to add other networks in the coming weeks.

Important links 👇

• Rated API Python SDK documentation: https://github.com/rated-network/rated-python

• PyPI library: https://pypi.org/project/rated-python/ The Rated API Python SDK comes with examples for straightforward tasks, including retrieving operator summaries, APR, effectiveness, and network statistics.

We will be adding more complex scenarios such as performance benchmarking, rewards accounting, incident troubleshooting amongst others soon™.

If you’d like support or have questions, please reach out via hello@rated.network. If you have feedback, please let us know via feedback.rated.network!

We’ve adjusted the Compute Unit (CU) formula to better reflect the processing demands on Rated for generating the data.

What’s changed?

Initially, a constant weight of 32 was applied as a denominator to the content length, resulting in the formula:

Compute Units =  (Content Length Bytes/32) + (Item Count x Business Value)

We’ve modified this approach to incorporate variable weights, which better account for the processing costs associated with producing this data. The new formula is:

Compute Units =  (Content Length Bytes/Weight) + (Item Count x Business Value)

Downstream impact on a per endpoint basis

This update changes the overall CU requirement to query certain endpoints that the Rated API supports, and are effective as of today. The updated weights, on a per endpoint basis, are available here.

If you’d like support or have questions, please reach out via hello@rated.network.

We have updated our list of solo-staker associated addresses to include another ~1.1k deposit addresses we identified, after collating all the feedback we received following the STRK airdrop announcement.

You can find the updated list in this repo: https://github.com/rated-network/solo-stakers

We have updated the heuristics that underlie the model, and done a lot of manual validation work drawing from various datasets available to us (e.g. EL activity patterns, gossip messages). The additional ~1.1k addresses represent an additional 15% to all the addresses that we had previously tagged as “high confidence solo-stakers”.

The updated list still respects the original definition of a solo-staker as outlined in this blog post.

This implies that addresses associated with validators that run on whitelabel providers are still not included. The same stands for validators that have been reported to us by Node Operator entities via the Self Report API. Finally, the list does not include “whales” that appear to run a very large number of validators in professional-looking setups, but with no clear association to any of the known to us operators, whether that be implicit or explicit.

Finally the list still considers validators up to index 500,000 and no further.

If you’d like support or have questions, please reach out via hello@rated.network.

We are excited to announce updates to the Rated API pricing and the introduction of a new tier to better serve our diverse user base. These changes are designed to provide more flexibility to different users’ needs and usage patterns.

• Free Tier Update:

Previous Allowance: 100,000 compute units per month.

• New Policy: 100,000 compute units lifetime allowance.

• Introduction of Starter Tier:

Allowance: 100,000 base compute units per month.

• Rate Limit: 2 requests per second, with no limit on the number of requests.

• Sunsetting of Pro Tier:

In response to user feedback, the Pro Tier will be discontinued. Users have expressed a preference for the Enterprise Tier, which offers greater flexibility and is better suited to their needs.

The Terms of Service have been updated to reflect these changes. These updates took effect on February 13, 2024. Users are encouraged to review the new terms.

You can view the plans in detail by visiting the console or docs.

If you’d like support or have questions, please reach out via hello@rated.network.

We are updating how we compute and display “performance metrics” on the Rated Explorer, namely (i) Source Vote Accuracy, (ii) Target Vote Accuracy and (iii) Head Vote Accuracy on Ethereum, to more closely reflect user interpretations of these terms.

Please note: the change is purely illustrative and does not affect the RAVER calculation and methodology.

Specifically, we are shifting the basis of each metric from the number of submitted attestations to the total number of attestation duties.

Previously:

- Source Vote Accuracy = sum of correct source votes/total attestations submitted

- Target Vote Accuracy = sum of correct target votes/total attestations submitted

- Head Vote Accuracy = sum of correct head votes/total attestations submitted

Moving forward:

- Source Vote Accuracy = sum of correct source votes/total attestations duties

- Target Vote Accuracy = sum of correct target votes/total attestations duties

- Head Vote Accuracy = sum of correct head votes/total attestations duties

These updates were applied retroactively (on 6th Feb 2024 at 1200 UTC) to all time window (1d, 7d, 30d and All time) views across validators, operators and pools pages for Ethereum mainnet and holesky.

If you’d like to reach out to us for support, please reach out via hello@rated.network.

In line with the ongoing phase-out of the Goerli network on Ethereum, we’re updating our services at Rated.

Starting today, our products (API, Explorer, and Oracle) have ceased support for Goerli. Certain API customers will be able to access Goerli this week but we highly recommend switching to Holesky for your testing needs.

To learn more about how to use the APIs, please visit our docs.

If you’d like to reach out to us for support, please reach out via hello@rated.network.

We’ve updated our methodology for tracking mev-boost rewards between builders and proposers on Ethereum to include additional payment patterns. Previously, we only recognized payments made directly from the builder’s address that received transaction fees. Now, we track two new cases:

• Payments from Different Addresses: Builders using different addresses for paying proposers at the end of the block, separate from the address receiving transaction fees.

• Payments via Internal Transactions: Builders paying proposers through an end-of-block transaction to an alternate address, which then sends funds to the proposer via an internal transaction.

These updates were applied retroactively (on 22nd Jan 2024 at 2300 UTC) to our validator rewards database from September 2022, affecting approximately 23,000 blocks, or roughly 0.6% of all blocks since the Ethereum Merge. This change will impact all API endpoints and fields related to Ethereum execution layer rewards, including aggregations and APR values.

You can find details about these changes on our forum here.

If you’d like to reach out to us for support, please contact us via hello@rated.network.