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
In this test a full-node must sync using blocksync protocol, requesting blocks on demand from the sequencer using P2P, when it joins the network.
Preconditions
1 rollapp (rollappA) registered to the hub.
1 sequencer registered for rollappA
1 sequencer node configured using mock DA
1 full-node configured using celestia as a DA
batch_submit_max_time set to 1h to avoid syncing from DA
full-node is started using p2p info from sequencer (instructions)
gossip block cache size (p2p_gossip_cache_size) is 1
blocksync enabled. p2p_blocksync_enabled set to true
p2p_blocksync_block_request_interval set to 10
Test Steps
sequencer generates blocks at 0.2 seconds rate
sequencer starts generating blocks
Full node joins after X blocks created.
Full node syncs after joining, from P2P only
Expected Results
After the full node joins, it should start receiving gossiped blocks, but without being possible to apply because there are some previous blocks missing.
After some time, the full-node receives the missing blocks using block sync, and the node is able to sync applying all pending blocks.
Live Test
Yes
Comments
No response
The text was updated successfully, but these errors were encountered:
Test Case Type
New
DRS
ALL
Target Milestone
3D
Test Case Issue link
No response
Epic
full node sync
Test Case Description
In this test a full-node must sync using blocksync protocol, requesting blocks on demand from the sequencer using P2P, when it joins the network.
Preconditions
Test Steps
Expected Results
After the full node joins, it should start receiving gossiped blocks, but without being possible to apply because there are some previous blocks missing.
After some time, the full-node receives the missing blocks using block sync, and the node is able to sync applying all pending blocks.
Live Test
Comments
No response
The text was updated successfully, but these errors were encountered: