Open gheise opened 2 years ago
I don't fully understand the goal here.
Please define "to assess the perfomance of the relay."
I don't fully understand the goal here.
Please define "to assess the perfomance of the relay."
I clarified above based on our conversation, thanks 😄
how do you calculate validator rewards? do you take into account that builders set their own feeRecipient and send the value in a transaction to the proposer feeRecipient that's sent outside of the chain to the builders?
To understand at validator behavior, block hashes and additional on-chain data needs to be collected to assess the ~perfomance of the relay~ rate of slashing and calculate validator rewards
We've heavily relied on scripts reading from db + access controls to integrate on-chain and relay data, but this has several flaws:
A better solution would be to use AWS Glue, an integrated AWS service for ETL, where scripts that read on-chain data can transform data from the relay db upon a trigger, like a new payload delivery, gathering on-chain data and writing to separate tables on the relay database without the overhead of maintaining scripts scattered in EC2 instances or altering the relay setup
Update
With the help of many we've decided to go with Apache Airflow, managed by Amazon. The repository for the graphs that will replace our internal scripting with regards to data collection can be found here