search

sig-net / mpc

6 stars 0 forks source link

Use more or better RPC provider #43

Closed volovyks closed 1 day ago

volovyks commented 2 weeks ago

Description

Now our system is failing each time RPC is experiencing issues. Not sure if we want to run our own node now, we can try a simpler solution for now.

Providers: https://docs.near.org/api/rpc/providers https://www.lavanet.xyz/get-started/near manage underlying RPC operators and route traffic to ones that are working well

auto-mausx commented 2 weeks ago

Lava does load balance between available services, so I think the should be the primary, but I think we should still code some resilience into the system. Maybe have an array of provider URLs that can be rotated against when a 5XX or 4XX error is produced a certain number of times?

volovyks commented 1 week ago

It was decided to stick with FastNEAR for now. RPC provider rotation can be added later, not a blocker to close this.