Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Outstanding PR count: 9, all of which are new. PRs are approximately closed in a week.
  • A new QA process is implemented. It focuses on the defect reproduction and MWE generation. 100% of the tickets are filed as bugs and are re-tested.
  • New Sumeragi consensus was implemented, tested and merged into the lts branch; it focuses on ironing out the previous p2p actor problem and it improves the performance.
  • P2P module restructuring leads to the stability improvements.
  • Ursa preliminary cleanup is in progress.
  • Kura inspector CLI is stable and working.
  • Docker and docker-compose configuration was improved
  • WASM: there’s an ongoing work regarding the compilation time, file size, security, introspection and documentation.
  • Iroha configuration parser handles the default values better, covering more edge-cases.
  • The documentation was updated to RC10
  • An initial implementation of iroha_swarm by our intern, Michael
  • A Blockchain explorer demo was implemented
  • A new JSON logging mode improves the diagnostic process.
  • A new feature for Kagami: synthetic genesis blocks
  • A syntax block generation tool was added
  • Load test generation tool was added (both statistic and representative)
  • Kagami UX:
    • Better help messages,
    • More subcommands,
    • Easier generation of keys given passphrase
  • CVE in SignatureCheckCondition fixed
  • Permission validators can be registered at run-time and user-generated with run-time upgradeability.
  • What changed regarding the Kagami UX?
  • Run-time permission validators implementation (?)
  • Sumeragi optimisation (what was changed?)
  • WASM dynamic linkage: FFI interface 95% finished.
  • Fully functional events:
    • Scoped
    • Global
    • Event-based
    • Time-based
    • By-call
    • With event processing
  • QA testing roadmap (De-containerised tests, CI Tests for SDK compatibility)
  • The Websocket connections are closed cleanly
  • Error states are reported with more information and with better feedback to the user

Maintainer Diversity

As of writing the Iroha 2 core development team consists of:

  • 8 Rust developers + 1 tech lead
  • 1 front-end developer
  • 2 full-time QA engineers (functional and load testing/benchmarking)
  • 1 full-time technical writer
  • 1 full-time DevOps
  • 1 community manager, who also handles front-end, back-end, DevOps and writing tasks as needed

Currently, the maintainer team consists of the Soramitsu employees. Gregorz Bazior (Yonix Digital Systems, AGH University of Science and Technology) is interested in Iroha 2 and maintains Iroha 1.

Contributor Diversity

A practice of working with interns was established and will continue.

...

Submission date

11-Nov-2022