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
Right now supersim, creates all the L2s & L1s at once. However, there's a UX journey that would be great to test with supersim, A new member gets added to the superchain
We could simulate this with the following flow.
Start supersim in the default setting with 1 L2, and 2 L2 chains
In a new window, start supersim again with some flags like --l1.endpoint and --l2.starting.port and --l2.starting.chainid which allows new L2s chains to start using the same L1 started in step (1)
This would allow developers to dynamically increase/decrease the number of L2s and test the dapp flow. An open question is how the superchain registry works in non fork mode
The text was updated successfully, but these errors were encountered:
Would also be nice to add the ability to do this through admin rpcs as well. For unit and integration testing I think being able to do this through the rpc would be very useful so we don't need to have all the L2's running for tests that don't need them.
yep totally agree, maybe the admin rpcs is the right way to do this. This admin rpc could also serve the needed registry config info for the frontend to shim with as well! I like this approach better
will need to some library to dynamically render terminal output
Right now supersim, creates all the L2s & L1s at once. However, there's a UX journey that would be great to test with supersim, A new member gets added to the superchain
We could simulate this with the following flow.
--l1.endpoint
and--l2.starting.port
and--l2.starting.chainid
which allows new L2s chains to start using the same L1 started in step (1)This would allow developers to dynamically increase/decrease the number of L2s and test the dapp flow. An open question is how the superchain registry works in non fork mode
The text was updated successfully, but these errors were encountered: