Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archival Check Basic Implementation #36

Open
nodiesBlade opened this issue May 1, 2024 · 0 comments
Open

Archival Check Basic Implementation #36

nodiesBlade opened this issue May 1, 2024 · 0 comments

Comments

@nodiesBlade
Copy link
Collaborator

Describe the Feature

Currently we do not check if a node currently is archival or not. We can include a check to query a block in a random range from 1 to N to determine if a node is archival. N blocks can be set custom via the chain configurator.

Additional Context / Pre-requisite

While the archival check is useful and simple to implement, POKT Network is extremely confusing on which chain ids should actually be archival or not. For example, there is:

0021 - Ethereum
0027 - Ethereum Archival
0028 - Ethereum Archival Trace
000B - Polygon Archival

Then there are some chains that have the expectation of being archival without archival suffix being attached to them, i.e all the testnets (according to Grove).

Due to the standardization of chain listings, it would be difficult to apply an archival check to the right chain ids without prior research.

In order to solve this, we can allow node operators to enable archival check via chain configuration table and leave it up to the node operators discretion and have it disabled by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant