| ID | Item | EPIC | Importance | ADR/RFC | Brief description | Notes |
|---|
| IF2-100 | Peer to Peer Network Library | HI2-6 HI2-30 | | Networking stack | Iroha must have a specific peer-to-peer protocol for effective communication and provided it as a detachable library. | Plain TCP\IP based protocol with SCALE as de\serialization format. |
| IF2-101 | Transactions Time to Live | HI2-38 | | Prevent replay of rejected transactions | Iroha must provide the possibility to explicitly state time-to-live (TTL) for each transaction, so the clients will have control over the can set time interval in which transactions should be confirmed and put into the block store or removed from the queue by timeout. |
|
| IF2-102 | Multisignature Transactions | HI2-13 | |
| Iroha must provide the possibility to configure each account to have a list of signatories, which needs to provide their signatures to confirm the transaction. Also, Iroha should provide the possibility to perform conditional multi-signature transactions, so the conditions will automate transaction creation or signing them |
|
| IF2-103 | Transaction dependencies |
| | Transaction tags | (Proposed by Kamil') Iroha may provide a possibility to perform tag-based dependencies between transactions for making their sequence configurable by the client |
|