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
E2E tests will need to be extended to ensure correctness of interactions with EigenDA V2 protocol. We should:
Introduce some new V2_ENABLED flag which when presented results in a V2 configuration being loaded. All the existing E2E tests can be re-leveraged for V2
Introduce V2 specific test cases?
The trickier case will be migration or cross compatibility; ie:
Disperse blob to V1 network (!V2_ENABLED) via rollup batcher and kill proxy instance (cert0)
Spawn new instance (V2_ENABLED) and disperse blob to EigenDA v2 network (cert1)
Sync rollup derivation or inbox reading pipeline from start; sync(cert0, cert1)
This test should enforce that an insecure EigenDA rollup integration can seamlessly start using V2 without any hiccups
The text was updated successfully, but these errors were encountered:
E2E tests will need to be extended to ensure correctness of interactions with EigenDA V2 protocol. We should:
V2_ENABLED
flag which when presented results in a V2 configuration being loaded. All the existing E2E tests can be re-leveraged for V2The trickier case will be migration or cross compatibility; ie:
!V2_ENABLED
) via rollup batcher and kill proxy instance (cert0
)V2_ENABLED
) and disperse blob to EigenDA v2 network (cert1
)sync(cert0, cert1)
This test should enforce that an insecure EigenDA rollup integration can seamlessly start using V2 without any hiccups
The text was updated successfully, but these errors were encountered: