Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Hyperledger Iroha v1.0 beta-3 version
Compare
Choose a tag to compare
@neewy neewy released this 22 Jun 16:31
· 552 commits to master since this release
v1.0.0_beta-3
60075d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

In this release following changes were made:

Experimental multi-signature transactions support

This is one of the most important features so far, since it allows integrators of Iroha to customise validation logic and may help people who want to have smart-contracts support. Let me tell you more:

As per definition of multi signature account on wikipedia, it is a type of account, which has a special condition, associated with the account: it is related to a number of cryptographic signatures required to issue valid transactions from the account, or "quorum". Quorum is a requirement to have M of N signatures, attached to transaction, where N is a total number of public keys associated with the account.

It helps to build following logic:

  • in order to form a valid transaction a user of Iroha has to apply several keys distributed across several people or devices to her transactions
  • in order to form a valid transaction a user of a service with Iroha may send her transactions to a service, which validates some custom logic (amount of transferred assets, special fields, whatever) and this service can add a signature to transaction if it passed custom validation

What is different in Iroha, compared to other services, is that a user is able to send transactions to peer network which don't have all required signatures, "half-baked". Iroha puts them in a temporary storage and distributes across the network. In the end, when Iroha peer network has received enough "half-baked" transactions (quorum condition is valid) such transaction is sent to Iroha validation and is written in the ledger in case of successful validation.

If you are curious — check code in hyperledger-iroha/iroha#1260. Docs are going to be available gradually in our documentation website.

Block streaming

This would allow people to create services around Iroha that can listen to events happening on the chain — like specific transactions. In the future, it would allow us to implement block explorer functionality as well.

Python and Java Bindings for Windows platform

Check it in hyperledger-iroha/iroha#1335 and at artifact.soramitsu.co.jp website

Other features

Fixes

Docs

CI Improvements

Assets 12
Loading