Changelog

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.