Shunkichi Sato
Shunkichi Sato
## Purpose This issue documents the implementation status of Iroha v2 as of commit [`884f870`](https://github.com/hyperledger-iroha/iroha/commit/884f870a791994cccd62da5febf246a1705eeb48). It provides a clear view of the **current milestone status**—covering both implemented and ongoing work—so...
In my view, the only clearly useful programmable execution systems currently identified are the following three: * smart contract (integrated with by-call trigger and custom instruction) * data trigger *...
This is a leftover task from PR #5471. Currently, when a trigger’s executable is implemented in Wasm, its execution is not recorded, and thus cannot be retrieved as part of...
## Background * In cross-chain transaction verification, full nodes (provers) and light clients (verifiers) hold asymmetric amounts of information. * To convince a verifier of a transaction’s persistence and liveness...
> I don’t ask for crypto. M◉⃤| Do we currently have the ability in Iroha through our APIs for webhooks? For many use cases, external systems need to get pushed...
The risk of key loss can be mitigated by using a social-recovery pattern commonly called a *guardian scheme*. In Iroha, a guardian scheme can be implemented as library triggers. However,...
Since PR #3250, view changes have been implemented as a simple rotation. This means that even if there are enough healthy peers overall, if faulty peers are scattered throughout the...