steelgeek091
steelgeek091
OMO: **O**perating system for **M**ultichain **O**ptimistic rollup with fraud proofs A compatibility layer is added on the basis of OMO to act as a bridge between the system and the...
In `crates/rooch-integration-test-runner/tests`, only the `CompiledModule` after compilation can be checked, and checking the `ModuleEnv` during compilation is not supported. Therefore, it is not possible to write test cases for `compile-time...
We should write test cases for `runtime verification of the entry function`. These test cases can be divided into two categories: `successful verification` and `failed verification`. Additionally, multiple test scenarios...
resolve https://github.com/rooch-network/rooch/issues/2399
When using `rooch move run` to execute a transaction, a dry run checks if the transaction can be executed properly.
There should be a global, thread-safe, asynchronous, and easy-to-use subscription and notification mechanism to notify multiple subscribers when a Gas upgrade event occurs. Subscribers can be any function, either in...
Currently, objects are queried based on the latest root state. An interface is needed to query objects based on a specific root state.
1. Implement a command to initiate a transaction that upgrades the on-chain gas config after execution. 2. Use the version number to control which part of the Rust code runs,...
resolve https://github.com/rooch-network/rooch/issues/2169
The current gas statistics for running the transfer command are as follows: ``` gas_used: 910165, time_used 1 -> "rooch_framework::account_coin_store::can_auto_accept_coin" gas_used: 950158, time_used 1 -> "rooch_framework::account_coin_store::is_accept_coin" gas_used: 8754, time_used 0 ->...