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
{{ message }}
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.
When using an app staked for near in gateway server it fails to grab the block height with an invalid syntax error. Which then results in "cannot find source of truth for data integrity check" which means you get "Something went wrong node selector can't find node" when trying to send a relay.
My guess here is that it is due to near not confirming to jsonRPC spec.
Expected Behavior
Gateway server should be able to grab the block height of near in health checks
Steps to Reproduce
Stake an app with near
Launch gateway server with said app stake
Observe Logs for failed health/integrity check
Try sending a relay on 0052
The text was updated successfully, but these errors were encountered:
Told by Dermot near isn't supported yet, suggested putting a "supported chains" section in docs. Happy to look at adding support for near to gateway server
EVM chains that support eth_getBlockByNumber and eth_blockNumber (encapsulate majority if not all evm chains)
Solana
POKT
Given that Near RPC calls are slightly different and does not conform to the evm, this requires a special checkjob but should be possible with minimal code.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
When using an app staked for near in gateway server it fails to grab the block height with an invalid syntax error. Which then results in "cannot find source of truth for data integrity check" which means you get "Something went wrong node selector can't find node" when trying to send a relay.
My guess here is that it is due to near not confirming to jsonRPC spec.
Expected Behavior
Gateway server should be able to grab the block height of near in health checks
Steps to Reproduce
The text was updated successfully, but these errors were encountered: