You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: