@aliencoder I’m trying to wrap my head around this comments. Basically what you are explaining is the zApp can run on its own L2. To accomplish this the zApp embedded contract will keep track of state on the L1. The zApp (the application) runs on the L2. Sequencers on the L2 run the sate transition function for the zApp and the L2 batch settles transactions to the L1 with ZK proofs.
Is this any different than how other L2s help Ethereum scale?
not yet, but this is the first step. this first commit is the generic ‘builder’ to convert binary executables (or zApps) to unikernel. the L2 integration is still in the exploratory phase, but this kit will allow devs to streamline the transition to unikernel.