Starting the sandbox without PXE doesn't deploy initial funded accounts and the network is stuck

[critesjosh]

Problem

Starting the sandbox without PXE doesn't deploy initial funded accounts and there is no way to manually progress sandbox blocks to make messages from L1 available on L2 (typically we recommend people send 2 arbitrary transactions to progress 2 blocks to make the messages available on L2, but since there are no funded accounts on the L2, this can't be done).

@porco-rosso-j flagged this as an issue when starting the sandbox without the PXE, to work on browser PXE development.

Suggestion

A cheatcode or something similar, available from browser PXE, to allow devs to progress blocks so that people can claim bridged fee assets.

[porco-rosso-j]

Thanks for creating issue, Josh. It'd be really helpful if we could have such a cheatcode.

Also, one thing is starting sandbox with PXE doesn't actually publicly deploy test accounts if I'm not mistaken. I think they should be publicly deployed by setting skipClassRegistration and skipPublicDeployment options to false with accountManager.deploy() in here so that other PXEs, e.g. browser-pxe, can fetch it via node, i.e. node.getContract(), and register them.

[sklppy88]

Thanks for creating issue, Josh. It'd be really helpful if we could have such a cheatcode.

Also, one thing is starting sandbox with PXE doesn't actually publicly deploy test accounts if I'm not mistaken. I think they should be publicly deployed by setting skipClassRegistration and skipPublicDeployment options to false with accountManager.deploy() in here so that other PXEs, e.g. browser-pxe, can fetch it via node, i.e. node.getContract(), and register them.

Because they're deterministic though, you can always register them with the util funcs. See here