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
Is your feature request related to a problem? Please describe.
Some proposals and proposal updates do not appear on the dashboard.
Our indexer relies on the Nearblocks API to track new transactions. However, since it depends on a specific Nearblocks endpoint, our dashboards went down when Nearblocks experienced issues.
We can track contract state changes for proposals and RFPs by implementing a FIFO queue-style changelog. This would allow our indexer to bypass Nearblocks and retrieve data directly from the contract.
Describe alternatives you've considered
We initially used Nearblocks as the source of truth, but it has proven unreliable.
Steps to take:
Deploy a new version of the contract
Deploy a new version of the indexer
Test if has all the proposals
The text was updated successfully, but these errors were encountered:
Today we hit the nearblocks API rate limit of 20.000 calls a day. The tests of PR #18 aren't functional anymore for today. I will replace the api key so the tests can succeed and we can merge.
Is your feature request related to a problem? Please describe.
Some proposals and proposal updates do not appear on the dashboard.
Our indexer relies on the Nearblocks API to track new transactions. However, since it depends on a specific Nearblocks endpoint, our dashboards went down when Nearblocks experienced issues.
According to the Nearblocks API documentation, the endpoint we are using is no longer recommended.
Describe the solution you'd like
We can track contract state changes for proposals and RFPs by implementing a FIFO queue-style changelog. This would allow our indexer to bypass Nearblocks and retrieve data directly from the contract.
Describe alternatives you've considered
We initially used Nearblocks as the source of truth, but it has proven unreliable.
Steps to take:
The text was updated successfully, but these errors were encountered: