Mykhailo Lohachov
Mykhailo Lohachov
#5209 Introduces wasm builds in `release` mode with default strip and optimizations. Should be checked if enough information can be obtained by setting `WASMTIME_BACKTRACE_DETAILS` .
> 1. Why is it important to keep within transactions? Initially, I thought it should be kept in a single transaction to ensure that account assets don't change. It is...
One possible approach designed with @0x009922 ### Pipeline 1. User calls `InitTransaction` (custom isi or trigger) with payload (`::InitTransaction`) `{transaction_id, instruction}` - Execute the instruction or wasm without committing it...
The CBDC case has been delayed for some time. Meanwhile, a more fundamental approach can be implemented to cover all potential cases (including wasms). As for the network fees, from...
On second thought, there is no need to set individual fuel limits for the executables. They can be executed as usual, but later, checks can be added to verify that...
I can work on it.
## Some notes from a fresh perspective: 1. For `iroha`: The documentation clearly defines its function: > "Iroha Client CLI is a 'thin' wrapper around functionality exposed in the iroha...
I would like to work on this issue.
> * Is the technical account expected to be replaced after deployment? I doubt technical account and fee options will be frequently changed after deployment. In the initial implementation, an...
As @mversic pointed out, the fees processing logic can be implemented in the custom executor. It would allow to separate the fees-related features from the core iroha. Since it would...