Sabaun Taraki

Implement all `pallet_gear` extrinsics generation and test

4

Preferably after #1448. That requires implementing: MVP - [x] #1601 Phase 2: - [ ] send_reply - [ ] claim_value Note: these extrinsics require some additional context to be introduced...

Currently loader waits for events, emitted during `process_queue` of `on_idle`. Need to adapt it to wait for results of extrinsic only.

Even better logging fmt for the `gear-node-loader`

2

1. Need some balance in logging information. Logging at what field the log was done or the stack of functions with full path is noisy. Need to make from this...

### Problem to Solve Block of log records about execution of one task (batch) must be presented in the file or stdout as sequentially, one after another, not mixed with...

Test `gear-node-loader` on the cluster

1

- [ ] Implement script for running/upping Vara network on various architectures and, possibly, on various OS. - [ ] Implement Tool/script to take node’s snapshots and logged data from...

### Problem to Solve After #1505, `gcore` and `gstd` users will have an opportunity to reserve gas from the message on their programs. The downside of the implementation is that...

Fork `subxt` and change it's substrate dependencies to gear version

1

### Problem to Solve `gear-program` being used in `gear-node-loader` sets in `Cargo.lock` external substrate dependencies from crates.io, while the workspace crates depend on our forked version of the substrate

### Problem to Solve When using randomized tests, time is a crucial factor, because the longer they run, the higher is a probability to find disaster input. I suggest queuing...

### Problem to Solve Possible scenarios: - [ ] actors communicating with each other by sending replies. - [ ] wait/wake logic with different time periods and different execution scenarios...

Phase 1 and 2 require that fails reports caused by the `gear-node-loader`, are explored manually on the node. It's preferable that all the needed data is sent by email, or...