Daniil Polyakov

Add logs to `smartcontracts/wasm.rs`

1

As @appetrosyan mentioned [here](https://github.com/hyperledger/iroha/pull/2523#discussion_r929069912) we should consider adding some logs in this file

[suggestion] Expand `Multiply` expression to more types

5

### Feature request @appetrosyan suggested [here](https://github.com/hyperledger/iroha/pull/2523#discussion_r929083075) to impl `Multiply` expression for more than just `U32` ### Motivation More types `Multiply` supports -- the more flexible this instruction is ### Who...

After the merge of #2641 we should revise how we pass transactions to *Wasm Validators*. @Erigara [have mentioned](https://github.com/hyperledger/iroha/pull/2641#discussion_r970634627) that it's against our rules to construct `Transaction` from `AcceptedTransaction` and pass...

After the merge of #2596 we will have to clone transaction in order to be validated. @mversic [has suggested](https://github.com/hyperledger/iroha/pull/2641#discussion_r969229558) to find a way to get rid of clonning. We need...

Right now we have some union tests for `Predicate`. We also need some integrations tests. This will be helpful to ensure the whole system with predicate works and also that...

[bug] `model` macro produces unexpected fields visibility

2

`model` macro docs say that private fields will be genereted with `pub(super)` visibility, but in fact they still remain private

[feature] Pass wasm payloads directly

2

Need to remove unpacking inside exntrypoints macro and pass payloads directly to user function. Also need to annotate all payloads as `#[non_exhaustive]`.

Consider signing by KeyPair reference not by value

1

Related fixme: https://github.com/hyperledger/iroha/blob/a3fad9b02b64cbc67e99f0fbe19a4802dda841c8/genesis/src/lib.rs#L63-L69 Also see this discussion: https://github.com/hyperledger/iroha/pull/4181#discussion_r1445734786

While I was debugging failing tests in #4181 I noticed that our current usage of `tracing` macros in data_model, primitives, crypto or in any other crate with multiple *client* types,...

Type inference for triggers and validators

1

Originally suggested by @mversic [here](https://github.com/hyperledger/iroha/pull/3106#discussion_r1115262135). We can infere the type of input parameters by looking at function parameter type names. It won't work in 100% cases because user can name...