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
After examining the problem seems to be that the RPC of the hub was very slow which caused a timeout in block inclusion:
time="2023-07-12T04:22:15+03:00" level=error msg="Error sending batch to settlement layer[resp %!v(PANIC=String method: runtime error: invalid memory address or nil pointer dereference) error error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). RPC error -32603 - Internal error: timed out waiting for tx to be included in a block]" module=settlement_client
this was interpreted as an error the layer client , however the batch was indeed accepted, hence trying to send the same batch caused the error.
There are few solutions possible but IMO it's best either way to not send the transaction in broacast-mode=block as we're waiting on events anyway and this is prone to yielding such timeout errors if network is slow/congested etc.
In broadcast-mode=sync we shouldn't get this error as we're not waiting for TX to be included in a block but only for the response to pass/fail CheckTx and if an error returns we know for sure it indicates the TX won't be included in a block (unlike in broadcas-mode=block case)
rollapp (2).log
seems like the rollapp goes out of sync sometimes with the hub.
=
The text was updated successfully, but these errors were encountered: