Conceptual View

This section describes the object model of the design.

Layers

According to Dan Boneh Blockchain applications may be divided into four layers:

We will use this classifications to group Iroha components and 3rd party components that can be integrated with Iroha components.

Layer	Components	Description
User Interface	Iroha Clients + 3rd Party Clients Web/Mobile/CLI	User Facing Services
Applications	Iroha Modules + Custom Iroha Special Instructions	Run on blockchain computer
Compute Layer	Iroha + Iroha Modules + Iroha Special Instructions	Application logic is encoded in a program that runs on blockchain • Rules are enforced by a public program (public source code) ➔ transparency: no single trusted 3rd party • The APP program is executed by parties who create new blocks ➔ public verifiability: anyone can verify state transitions
Consensus Layer	Iroha Sumeragi	A public data structure (ledger) that provides: Persistence: once added, data can never be removed Consensus: all honest participants have the same data Liveness: honest participants can add new transactions Open(?): anyone can be a participant (no authentication)

This section describes the activities of the system, captures the concurrency and synchronization aspects of the design.

This section describes the mapping of software onto hardware and reflects its distributed aspect.

This section describes the static organization or structure of the software in its development of environment.