Marin Veršić
Marin Veršić
the unfortunate difference from `iroha` client is that we take instruction by reference instead of value _Originally posted by @mversic in https://github.com/hyperledger/iroha/pull/5073#discussion_r1758212396_
Similar to #5119, I think, we should implement `Instruction` macro to remove boilerplate of custom instructions
We should implement `Metadata` macro and place it into `iroha_data_model_derive` (not executor data model). The implementation should convert between a Rust type and `Metadata` similar how we do for `Permission`...
On the one hand, would be great to keep these primitive and build on top of them (maybe through some concept of permission bundles). On the other, I can't come...
IMO carries too much mental overhead for the end user. Can we simplify it? _Originally posted by @mversic in https://github.com/hyperledger/iroha/pull/5073#discussion_r1758214955_
we have very little facilities to debug `wasm`. As @DCNick3 suggested we should try to include [this](https://docs.wasmtime.dev/api/wasmtime/struct.Config.html#method.wasm_backtrace_details)
Currently a user can insert as much of things into metadata as they want. This can lead to abuse. We should put some limits on the metadata size. This could...
The number of triggers per user is unlimited. We should define one. Could be a built-in or custom parameter
As far as I can see the privilege to grant/revoke permissions/roles is transitive. This means that if an account has a certain permission/role they can grant/revoke this permission to any...
Since #3624 it should be possible to export permission tokens in `permission_token_schema.json` when generating schema