Rollup simplification

[mpolitzer]

Context

The rollup system is the bridge that allows a DApp to speak with the blockchain. It was initially designed to receive input-metadata and input for the blockchain -> DApp direction, and vouchers and notices on the DApp -> blockchain direction. Recently there is interest in doing different types of outputs[1] from vouchers and notices and we realized that it would be impractical handling every one of them across the SDK stack. Along those lines, there is also a plan to simplify the input handling by merging the input-metadata with input[2].

[1] cartesi/rollups-contracts#42
[2] cartesi/rollups-contracts#84

Possible solutions

The proposed solution is to simplify the rollup, make it handle inputs and outputs as opaque blobs of data and do the encode/decode of blockchain related data in the DApp itself, in userspace.

Tasks

• remove input-metadata, notices_hashes and voucher_hashes from the emulator, grpc, defines
  • feat: rollup rework #136
  • feat: rollup rework grpc-interfaces#22
  • feat: rollup rework machine-emulator-defines#7
• update src/cartesi-machine.lua to reflect those changes
  • --rollup-advance-state and --rollup-inspect-state calls should be reworked (and simplified if possible)
• do the rollup memory range operations based on HTIF yield data
• update rollup-memory-range.lua tool to reflect those changes
• update the linux driver to reflect those changes
  • rollup driver simplification linux#4
• update the tools to reflect those changes
  • libdriver machine-emulator-tools#24
  • update tools to use the new library
• update server-manager to reflect those changes
• update rom to reflect those changes
  • feat: rollup rework machine-emulator-rom#13