Problem: Roller heavily relies on External RPC client

[VictorTrustyDev]

Steps to reproduce it

As you already know, if the roller can not fetch Avai data, the sequencer will be stopped, that means the entire system of RollApp clients will be down. It's single point of failure and that is bad.

Expected result

Sequencer can run standalone during connection issue does it job as normal and when connection restored, it does what it need to do

Actual result

Sequencer: Stopped, Restarting...

RollApp unvailable

rollapp_evm status | jq
# Error: error in json rpc client, with http response metadata: (Status: 503 Service Unavailable, Protocol HTTP/1.1). error unmarshalling: invalid character 'o' in literal null (expecting 'u')

Relevant log output

No response

Notes

No response

[mtsitrin]

Hi @VictorTrustyDev
The rollapp does continues to work even when DA issues are encountered for a short grace period, but it stops after a while and gets into unhealthy mode.

allowing the rollapp to run without active DA makes little sense, as no security guarantees submitted, and rollapp full nodes can't sync to this state

[VictorTrustyDev]

I see, so the DA should load balanced correctly.

I have another question: how long should it take to resolve DA connection issue? Let say 1 day, and Roll App max working time without DA is 6h, so the gap is 18h. Shall we design a better solution for the case?

[mtsitrin]

Connectivity wise,
DA chain is expected to be live with multiple RPC available

In case of blockspace load,
u can set higher gas price to increase the likelihood of the state update to be included