In our existing hybrid compute implementation, the off-chain interactions are recorded in non-standard data structures. This requires custom code in the batch submitter, DTL, and l2geth to include these fields in the rollup data and then to extract and replay the interaction on a Verifier node.
Optimism's introduction of a Deposit transaction provides another option, in which our sequencer can "deposit" the off-chain responses into a helper contract. Such transactions would have to be distinguished somehow from the other Bedrock deposits so that the rollup node would treat them as if they were regular L2 transactions rather than as belonging to its own set of Deposits. TBD whether this would best by done with a custom version number, by using a special marker as the 'From' address, or something else.
In our existing hybrid compute implementation, the off-chain interactions are recorded in non-standard data structures. This requires custom code in the batch submitter, DTL, and l2geth to include these fields in the rollup data and then to extract and replay the interaction on a Verifier node.
Optimism's introduction of a Deposit transaction provides another option, in which our sequencer can "deposit" the off-chain responses into a helper contract. Such transactions would have to be distinguished somehow from the other Bedrock deposits so that the rollup node would treat them as if they were regular L2 transactions rather than as belonging to its own set of Deposits. TBD whether this would best by done with a custom version number, by using a special marker as the 'From' address, or something else.