POST
/
v0
/
selfReports
/
validators

Here’s how to interpret the inputs required to operate it:

ParameterContext
validatorsArray of validator pubkeys associated with the node operator
poolTagString for pool name, must match exactly to the pool name listed on the Explorer.

And here’s how to you might go about implementing it:

Please note the following:

  • You can self report on Ethereum Mainnet, Goerli and Holesky.

  • Do not pass your operator name as pool name. If you’re not getting delegations via a pool or pool share, please leave the “poolTag” empty.

  • Each request has a strict limit of 1,000 validator public keys. Please submit multiple requests if you need to report more than 1,000 validators.

  • We cannot assign a key to your entity if it has already been reported by another operator. In case of false attribution, please contact us at hello@rated.network, and we will address the issue.

  • As this API is self-reported, it relies on the honest behaviour of all participants reporting their validators. Any instances of misconduct may lead to the exclusion of the entity from our platform.

  • It typically takes about 24 hours for the reported keys to appear on rated.network/explorer. Please note that your keys need to be activated (ie not in the activation queue) for them to show up on the Explorer.

  • If your activated keys have not shown up after the 24h period, please contact us at hello@rated.network, and we will investigate the issue.

Headers

X-Rated-Network
enum<string>
Available options:
mainnet,
holesky

Body

application/json
validators
string[]
required
poolTag
string | null

Response

201
application/json
operatorName
string
required
validators
string[]
required
network
enum<string>
required
Available options:
mainnet,
holesky
poolTag
string | null