LogoLogo
HomeCommmunityLegal
  • Getting started
    • Welcome
    • Useful links
    • Framing the problem
    • Design goals
  • Methodologies
    • Ethereum Beacon Chain
      • Resources
      • Network explorer definitions
        • Landing page
        • Entity views
          • Top screener
          • Entity overview
          • Consensus layer statistics
          • Execution layer statistics
          • Aggregate rewards statistics
        • Aggregate views
          • Trending
          • Network overview
            • Gini coefficient measurement
          • Relayer landscape
          • Builder landscape
        • Misc
          • Index Coop dsETH
      • RAVER methodology
        • Proposer effectiveness
        • Attester effectiveness
        • Effectiveness rating
        • Slashing moderator
        • Sync committees
        • Post-hoc analysis of the Rated v0 effectiveness rating
      • Penalties and Missed Rewards methodologies
        • Penalties computation
          • Pre-Altair penalties computation
        • Validator missed rewards computation
          • Consensus missed rewards computation
          • Execution missed rewards computation
      • Baseline MEV computation
      • Aggregating validator indices
        • Classes of aggregation
    • Miscellaneous
      • Value enabled by Rated
  • API documentation
    • Introduction
    • Getting past authentication
    • API guide
    • Swagger schema
  • Legal
    • ToU & Privacy Notice
      • Website Terms of Use
      • API Terms of Use
      • Privacy Notice
  • Community
    • 🍬Let's Rate!
Powered by GitBook
On this page
  • Aggregating by deposit address
  • Higher order aggregations

Was this helpful?

  1. Methodologies
  2. Ethereum Beacon Chain

Aggregating validator indices

Aggregating by deposit address

Up to this point we have described how rated’s validator effectiveness model works, on the basis of indexing for individual validator ids, distinguished by a unique index number and public key address pair.

These unique validator ids are often operated by a single entity. In order to get to a grouping that more closely resembles that of a whole operator entity, we work based on the assumption that an eth1 deposit address is controlled by a single entity.

Deposit addresses are available on-chain, paired to public key data, such that one deposit address could be common to thousands of unique validator public keys.

We therefore proceed to compute the validator effectiveness per unique deposit address as a simple average between all keys that map to that same deposit address.

Higher order aggregations

Both on the front-end and the API layer of Rated, we are further grouping deposit addresses up to the entities that they are associated with. At the moment, there is no standard way via which we collate this information; it is a combination of Etherscan research, Ethereum transaction log queries, block graffiti and in some cases operators coming straight to us willing to self-disclose.

PreviousBaseline MEV computationNextClasses of aggregation

Last updated 2 years ago

Was this helpful?