Open hyunsooda opened 2 years ago
Thanks for your suggestion! I will take a look at this issue
Hey @hyunsooda, I may actually implement this issue. Do you think governance.itemsAt
will be enough for governance related data? Also feel free to suggest other features too. Thank you!
Yes maybe.
For the other suggestion, the extra
field is also an interesting value, which consists of a list of current validators, a signature of the proposer, and the signatures of validators. It would help to track where the list of validators was changed and who was a proposer at a specific block and etc. Also, collecting and decoding all headers that have a change of governance at every epoch interval may be the next task candidate. It would help to track the history of the chain's governance in the chain's lifetime.
I took a quick look at what
klaytn-etl
provides for chaindata processing and one feature suggestion was popped up.The Klaytn block header contains
Governance
andVote
which are RLP-encoded data. If this project can help to parse as human-readable for post-processing of their favors, it would be leveraged by third parties that do business with data viewer, processing, etc. The APIgovernance.itemsAt
may be leveraged to implement this feature by iteration of a query with every block number parameter.I'm not sure this suggestion is out of this project's scope. However, kindly, the extension of features that fit Klaytn would be attractable rather than the
ethereum-etl
which provides only general stuff like fetching blocks and transactions.