Confirmation
Problem
As of now, localnet runs multiple hemi nodes. It runs a sequencing and non-sequencing node. Both of these nodes are started at the same time, so they do not require a "sync".
We need a way to test both snap sync and full sync in localnet.
Suggested solution
Add two more Hemi l2 nodes (both running op-geth+op-node). These should be started far enough in the future from the current ones, where they'll require a "sync".
Set one to "snap sync" and the other to "full sync".
Add the following test cases:
- reorg the bitcoin canonical chain so that at least one bitcoin attributes deposited tx is not on the canonical chain, ensure that the nodes recover
- run all existing test cases against these new nodes
Additional Information
as of now, let's leave this as one issue. if it becomes two large I will split it into 2. this may require #785 to be completed, but I am unsure at this time
Confirmation
Problem
As of now, localnet runs multiple hemi nodes. It runs a sequencing and non-sequencing node. Both of these nodes are started at the same time, so they do not require a "sync".
We need a way to test both snap sync and full sync in localnet.
Suggested solution
Add two more Hemi l2 nodes (both running op-geth+op-node). These should be started far enough in the future from the current ones, where they'll require a "sync".
Set one to "snap sync" and the other to "full sync".
Add the following test cases:
Additional Information
as of now, let's leave this as one issue. if it becomes two large I will split it into 2. this may require #785 to be completed, but I am unsure at this time