Have something to say?

Tell Rated how they could make the product more useful to you.

Completed

Method of blockspace distribution detection

Dear Rated team, I am a contributor to the NOM workstream of the Lido DAO and thus especially interested in your dashboards concerning our modules. In the overview of the Curated Module I noticed that you listed severals NOs who the explorer claimed had obtained blocks from unvetted Titan relay in the past 30 days. I was able to confirm this for all but one NO by comparing the slots in which the blocks had been proposed with the relay’s API. Normally such blocks stick out in our own Fees Monitoring Dashboard as being from slots of an “unknown relay”. What was unique for the NO in question, is, that unlike for the other NOs, for none of this NO’s unknown relay slots I could produce a query that was responded to by the proposer_payload_delivered endpoint of the Titan - or by any other of the APIs of widely known relays - making me fairly certain we are looking at locally built “vanilla blocks”. But then, where does the Titan relay blockspace you listed for the NO come from? We got in touch with them - Kiln - and were told that while they do not call the getHeader methode for Titan for blocks available on multiple and ultimately obtained by a different than Titan relay. They do, however, systematically send signatures to all relays, including Titan, to improve the propagation time. Some examples of such slots that then produce responses from several relays are: 9590392, 9589936, and 9589912 Is it possible that this approach is messing with your methode of collecting the blockspace distribution, listing the blockspace for all of the responding relays?

sssngth 2 months ago

4

đŸ—Ŗī¸ Forum

Completed

Empty rewards for a validator

Using https://api-docs.rated.network/rated-api/api-reference/v1-beta/ethereum/rewards Get validator rewards metrics API, I wasn't able to find rewards associate with a validator I was looking for. Parameters URL : /v1/eth/validators/0xaa160542c2b1b9dbf5e11ca044067526c6dfff65efba88ea483d49bdbe478ab7489f8b1a903ea22b6d30cfa57626ca9e/rewards?granularity=hour&fromDate=2023-04-01&toDate=2024-05-13 X-Rated-Network = mainnet Response : { "previous": null, "next": null, "pages": 0, "results": [] } I was expecting to see some consensus rewards for that period. Here's the data on beaconchain https://beaconcha.in/validator/aa160542c2b1b9dbf5e11ca044067526c6dfff65efba88ea483d49bdbe478ab7489f8b1a903ea22b6d30cfa57626ca9e

Jacob Marcil 5 months ago

2

🐞 Bug Reports

Completed

Invalid response for V1 (Beta) Get Validator metrics

The API return a HTTP 400 for a valid request for this API https://api-docs.rated.network/rated-api/api-reference/v1-beta/ethereum/rewards#validator-rewards. Parameters : URL : /v1/eth/validators/0x923285aabe7b6edd1aff2022f6089b7343c9d35bfea3e22792c4b43350153e7323cbbb15ce096e9f3c60b5bc55713a4d/rewards Headers : X-Rated-Network = mainnet Response (HTTP 400) [ { "loc": [ "sumExternallySourcedExecutionRewards" ], "msg": "value is not a valid float", "type": "type_error.float" } ] Same thing when using the validator id Parameters : URL : /v1/eth/validators/1025148/rewards Headers : X-Rated-Network = mainnet This shows the existence of this validator https://beaconcha.in/validator/923285aabe7b6edd1aff2022f6089b7343c9d35bfea3e22792c4b43350153e7323cbbb15ce096e9f3c60b5bc55713a4d It's also possible to get this validator using Rated API URL : /v1/eth/validators/0x923285aabe7b6edd1aff2022f6089b7343c9d35bfea3e22792c4b43350153e7323cbbb15ce096e9f3c60b5bc55713a4d Headers : X-Rated-Network = mainnet Response { "validatorIndex": 1025148, "validatorPubkey": "0x923285aabe7b6edd1aff2022f6089b7343c9d35bfea3e22792c4b43350153e7323cbbb15ce096e9f3c60b5bc55713a4d", "activationEpoch": 242547, "activationEligibilityEpoch": 242529, "exitEpoch": null, "withdrawableEpoch": null }

Jacob Marcil 5 months ago

1

🐞 Bug Reports