Dear Iroha Community,
It's time for us to share some updates on the progress of Iroha. We've made major strides towards 2.0.0-rc.1
over the past two weeks:
Singular and iterable queries have been separated into their own traits: users can no longer add filters, sorting, batching or pagination to singular queries at compile time (this was a runtime error previously). The permission schema has been generalized, making it part of the customizable executor data model – this prepares a foundation to implement user-defined instructions, parameters, and metadata. Configuration system has been greatly improved through a new ConfigReader
API, its debuggability enhanced via better error-reporting and logging. Finally, Iroha crates and binaries have been renamed: irohad
for the peer crate/binary, iroha
for the client crate/CLI.
- feat!: Add traits for iterable and non-iterable queries (#4638)
- feat!: generalize permissions schema to executor data model (#4658)
- feat: improve config debug-ability (#4456)
- feat: support
https
fortorii_url
(#4617) - refactor!: rename iroha server and client (#4662)
- refactor!: rename TransactionValue into CommittedTransaction (#4610)
- refactor(executor): Check custom visit functions in
#[derive(Visit)]
(#4632) - refactor(executor): remove
Visit
bound fromValidate
(#4642) - refactor: Make
SignedBlock
immutable (#4620) - refactor: Reject
BlockMessages
eagerly (#4606) - refactor: rename
PermissionToken
toPermission
(#4635) - fix(crypto): do not panic if the passed Ed25519Sha512 public key is of invalid length (#4650)
- fix(executor): Added register trigger permissions in the default executor (#4616)
- fix(sumeragi): Use proper view_change_index on init block load (#4612)
- fix: Don't prematurely execute time-triggers before their
start
timestamp (#4333) - fix: remove serde(flatten) from SetKeyValue/RemoveKeyValue (#4547)
If you have any questions, feedback, or concerns regarding the updates or any other project-related matters, please feel free to discuss them in our Telegram and Discord chats.
Thank you for being part of the Iroha community.
Best regards,
Hyperledger Iroha team