Facing issues while running Chainlink node on XRPL EVM Sidechain network

Question

Basically, I’m trying to run a Chainlink node on XRPL EVM Sidechain network.

Here's the content of the config.toml file that I'm using:

[Log]
Level = 'warn'

[WebServer]
AllowOrigins = '\*'
SecureCookies = false

[WebServer.TLS]
HTTPSPort = 0

[[EVM]]
ChainID = '1440002'
MinContractPayment = '0 link'

[[EVM.Nodes]]
Name = 'Ripple EVM Sidechain'
WSURL = 'wss://ws-evm-poa-sidechain.peersyst.tech'
HTTPURL = 'https://rpc-evm-sidechain.xrpl.org'

It’s running fine for a while giving this warning:

[WARN] Chain length supplied for re-org detection was shorter than EvmFinalityDepth. Re-org protection is not working properly. This could indicate a problem with the remote RPC endpoint, a compatibility issue with a particular blockchain, a bug with this particular blockchain, heads table being truncated too early, remote node out of sync, or something else. If this happens a lot please raise a bug with the Chainlink team including a log output sample and details of the chain and RPC endpoint you are using. txmgr/confirmer.go:928 chainLength=1 evmChainID=1440002 evmFinalityDepth=50 logger=EVM.1440002.Txm.Confirmer nConsecutiveBlocksChainTooShort=22

Then, after sometime, it's escalated to this critical error:

[CRIT] RPC endpoint detected out of sync; but cannot disable this connection because there are no other RPC endpoints, or all other RPC endpoints are dead. Chainlink is now operating in a degraded state and urgent action is required to resolve the issue client/node_lifecycle.go:208 evmChainID=1440002 logger=EVM.1440002.Node.Lifecycle.Alive noNewHeadsTimeoutThreshold=180 node=(primary)Ripple EVM Sidechain:wss://ws-evm-poa-sidechain.peersyst.tech:https://rpc-evm-sidechain.xrpl.org nodeName=Ripple EVM Sidechain nodeTier=primary pollFailureThreshold=5 pollInterval=10 stacktrace=github.com/smartcontractkit/chainlink/v2/core/chains/evm/client.(*node).aliveLoop

I'll be really grateful, if anyone can help me out with this.

Answer 1

The error messages you're seeing indicate that your Chainlink node is having difficulty communicating with the XRPL EVM Sidechain network. The warning message suggests that the node is not receiving enough blocks from the network to maintain re-org protection, which could be due to various issues such as a problem with the remote RPC endpoint, compatibility issues, or the remote node being out of sync.

The critical error message escalates the issue further, stating that the RPC endpoint is detected as out of sync, but the node cannot disable the connection because there are no other available RPC endpoints. This puts the Chainlink node in a degraded state, requiring urgent action to resolve the issue.

While the response from the Chainlink team indicates that XRPL EVM Sidechain is not officially supported at the moment, there are a few things you can try to troubleshoot the issue:

1. Check the XRPL EVM Sidechain status: Ensure that the XRPL EVM Sidechain network is functioning properly and that there are no known issues or outages. You can check the official channels or community forums for any updates or announcements.

2. Verify the RPC endpoints: Double-check that the WebSocket (WSURL) and HTTP (HTTPURL) endpoints in your config.toml file are correct and accessible. Try connecting to these endpoints using other tools like wscat or curl to ensure they are responsive.

3. Increase the re-org protection threshold: The warning message mentions that the chain length supplied for re-org detection is shorter than EvmFinalityDepth. You can try increasing the EvmFinalityDepth value in your configuration to see if it resolves the issue. Keep in mind that increasing this value may introduce more latency in transaction confirmations.

4. Add additional RPC endpoints: To mitigate the critical error where the node cannot disable the out-of-sync connection due to a lack of alternative endpoints, consider adding more RPC endpoints to your configuration. This will provide fallback options for the node to switch to if one endpoint becomes unresponsive or out of sync.

5. Engage with the XRPL EVM Sidechain community: Reach out to the XRPL EVM Sidechain community through their official channels, such as Discord or forums, to seek guidance and support from developers and other users who may have encountered similar issues. They might have specific recommendations or workarounds for running a Chainlink node on their network.

6. Monitor Chainlink's official integration progress: Keep an eye on Chainlink's official channels and announcements regarding the integration of XRPL EVM Sidechain. As mentioned by the Chainlink team, they have a waitlist for chain integrations driven by user demand and their own roadmap. Filling out the contact form and expressing your interest in XRPL EVM Sidechain integration can help prioritize it for future development.

In the meantime, you can explore alternative oracle solutions that are compatible with XRPL EVM Sidechain or consider using external adapters to bridge the gap between Chainlink and the sidechain network.

Remember that running a Chainlink node on an unsupported network comes with risks and challenges, so it's essential to proceed with caution and be prepared for potential issues. Actively engaging with both the Chainlink and XRPL EVM Sidechain communities can help you navigate these challenges and find suitable solutions.

*The full text of this answer was passed through GPT-4 with the prompt (notifying according to the policy https://ethereum.stackexchange.com/help/gen-ai-policy): "Correct the grammatical errors without changing the actual meaning of the text"

Answer 2

Basically, the issue is that the Chainlink node doesn't support XRPL EVM Sidechain network as of now.

This was the response that I received from the Chainlink team:

We’re currently officially integrated with 17 chains and having a waitlist of chains to be integrated however this is mainly driven by User demands/request and the blockchain integration team’s roadmap.

Bear in mind that Chainlink integrates natively on each chains. So it will take time for development and engineering to maintain highest security standards.

Kindly fill in the form at https://chain.link/contact > choose Others > specify the chain you’re proposing.

The support team will help arrange.

If you require quicker feedback from the community, perhaps post it on our Chainlink Discord as someone might encounter and solved similar issues with other non-supported chains.