Shunkichi Sato

Results 67 issues of Shunkichi Sato

BREAKING_CHANGE: - `Account` contains `is_active` field - `AccountEvent::Created` divides into `Recognized` and `Activated` - `ValidationFail` contains `UnrecognizedAuthority` and `InactiveAuthority` variants ## Description When an account is _recognized_, - it becomes...

Enhancement
api-changes

_Last updated: May 26, 2025_ Emulate RDBMS data integrity. ## Motivation - We have relied on ad-hoc solutions to remove orphaned entries when parents are deleted. These are error-prone and...

Bug
api-changes
Refactor
Security
Performance

I guess trigger will be able to be identified as an account. > I don't think it has been broken down into issues yet. > If we want to support...

question

Since currently `Sumeragi::round_start_time` updates only on block commit (or view change) and the block timer keeps ringing under situation of no transactions, the next transaction arrival meets [the condition](https://github.com/hyperledger/iroha/blob/a27bc2eaa7e3cfab6c35cae3b2bcace63a3fee2b/core/src/sumeragi/main_loop.rs#L844) and...

Optimization
Consensus

### OS and Environment Linux, `test_env.py` ### GIT commit hash 76dafdc ### Minimum working example / Steps to reproduce Prepare `transaction.json` ([example](https://github.com/hyperledger/iroha/issues/4952#issuecomment-2275820415)) with a few instructions and, ```zsh git checkout...

Bug

### OS and Environment Linux, `test_env.py` ### GIT commit hash 76dafdc ### Minimum working example / Steps to reproduce Prepare `transaction.json` ([example](https://github.com/hyperledger/iroha/issues/4952#issuecomment-2275820415)) with a few instructions and, ```zsh git checkout...

Bug

BREAKING CHANGES: - (api-changes) `CanRegisterAnyTrigger` `CanUnregisterAnyTrigger` permission - (config-changes) `defaults/genesis.json` assumes `wasm_triggers[*].action.executable` is prebuilt under `wasm_samples/target/prebuilt/` Major commits: - feat: support multisig recursion - feat: introduce multisig quorum and weights...

Enhancement
api-changes
config-changes

The stronger the trigger authority, the higher the risk of compromise of the corresponding private key. Such a system-side trigger authority should be a system-side account whose ID would be...

api-changes
Security

## Context In my latest assessment, the failure of the `domain_owner_trigger_permissions` test after PR #5457 is not because this PR introduced a bug, but because correctly routing trigger execution to...

Bug

> S. Sato, [2025/05/22 0:26] > The second case suggests an improvement to the trigger spec I had in mind: > > Currently, trigger authorities are fixed to the registrants....

Bug
Security