A zkRollup with no history transaction data (Intmax) report 1

I report on the algorithm/solution that succeeded in removing transaction history data from zkRollup announced last October 2021. This allows an operator to run zkRollup with extreme security in the trade-off of accepting the demerit of online assumption. Almost all cost of zkRollup was removed by the combination of these algorithms we published.

https://ethresear.ch/t/a-zkrollup-with-no-transaction-history-data-to-enable-secret-smart-contract-execution-with-calldata-efficiency/10961

https://ethresear.ch/t/a-pre-consensus-mechanism-to-secure-instant-finality-and-long-interval-in-zkrollup/8749

First, we created a WP integrating these algorithms/methods.
https://hackmd.io/ZTImRSapRH-zADmY7cNJVA?view#4-Intmax-zkRollup-details

Quite simply, since only the diff of finalized states is recorded in the L1 case regarding smart contract balances, it is necessary to safely lengthen the Layer1 commitment in order to make these more efficient by compressing many state diffs.

The next step was to develop the zkSTARKs library, which is now functional.
This useful library allows zkSTARKs circuits to be implemented in Circom, which is well known in the ZKP communities.
https://github.com/InternetMaximalism/stark-pure-rust

We then developed a library for the Verkle Tree, which is also functionally complete now.
https://github.com/InternetMaximalism/verkle-tree

We have also added a function to verify the Verkle Tree with ZKP.
https://github.com/InternetMaximalism/verkle-tree-circuit

And we are currently developing the main part of the zkRollup.