Different extensive incoming header scenarios in chain simulator for sovereign block processing
Proposed changes
Test1
// In this test we simulate:
// - a sovereign chain with the same round time as mainnet
// - for each generated block in sovereign chain, we receive an incoming header from mainnet
Test2
// In this test we simulate:
// - a sovereign chain with a lower round time than mainnet
// - we will receive a mainnet block at every 3 generated sovereign blocks
Test3
// In this test we simulate:
// - a sovereign chain with a higher round time than mainnet
// - we will receive 3 mainnet block for every generated sovereign blocks
Testing procedure
Pre-requisites
Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:
was the PR targeted to the correct branch?
if this is a larger feature that probably needs more than one PR, is there a feat branch created?
if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?
Reasoning behind the pull request
Proposed changes
Test1
Test2
Test3
Testing procedure
Pre-requisites
Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:
feat
branch created?feat
branch merging, do all satellite projects have a proper tag insidego.mod
?