Sergi Rene

the current version only takes into account the upper bound limit for celestia da, which is 500k bytes.

this module will be used to keep and update the necessary params, that are not already defined in the x/params module, as described in here https://www.notion.so/dymension/ADR-x-Rollapp-Consensus-Params-d60daee1f8cb42e38e43e1ef5289a220?pvs=4

feat(manager): state update validation

1

# PR Standards ## Opening a pull request should be able to meet the following requirements -- PR naming convention: https://hackmd.io/@nZpxHZ0CT7O5ngTp0TP9mg/HJP_jrm7A --- Close #1109 For Author: - [ ] Targeted...

nodes can start with wrong last submitted height from the Hub after rotation

1

when restarting, nodes may miss state updates. it may happen the state update was sent before the node was restarted but accepted after the node starts, and therefore the node...

# PR Standards ## Opening a pull request should be able to meet the following requirements -- PR naming convention: https://hackmd.io/@nZpxHZ0CT7O5ngTp0TP9mg/HJP_jrm7A --- Close #1015 For Author: - [ ] Targeted...

block production not stopping after max_batch_skew

1

it only stops after max_batch_skew * batch_submit_bytes, but it does not accumulate batches based on time, i.e. it will not stop after max_batch_skew. * batch_submit_time without submitting batches.

get last submitted height from hub when batch submission to SL fails because of already submitted height

1

now sequencers subscribe to new batch events, to avoid not updating submitted height in case of restart, and it just panics in case it happens. but this could be improved.

and replace all used fields by rollapp params module

and replace current DRS version per state info.