Shunkichi Sato

If we go forward with this, I'd like to have a more solid basis for rejecting other candidates. For example, I suggested implementing multi-signature using triggers, but I'm not sure...

### Motivation Currently, new participants cannot take any action without having their accounts registered by others, which is not what a public blockchain does. It is therefore a requirement that...

@Mingela - My understanding is both any personal `PublicKey` and any shared `PublicKeyLike` addresses are valid. - To target the latter address before registration, while I don't know if that...

@mversic - To be honest, as I mentioned before, I don't understand what the concept of primary and secondary keys brings. If you have any ideas please share - I...

## A short summary so far ### Changes - `AccountId` will be some type that can be parsed to `PublicKey` or `PublicKeyLike` (which is invalid as but has the same...

I think we can close this issue as the title became a bit misleading, or rename the title and keep it as a tracking issue @mversic

Just like 10^18 wei for ETH, what if the resolution of the base unit for the named unit is determined on the asset definition creation and only the number of...

I don't think it's too late to remove one feature after coming up with an alternative implementation. I agree with stopping transactions pending in the queue because, if my memory...

#4276 would be one of the possible solutions

> [#4309 (comment)](https://github.com/hyperledger/iroha/pull/4309#issuecomment-1957724414) > > This is a new feature introduced by #4276 to automatically label and notify someone of specific code changes. Currently `config-changes` reacts to any change under...