What's new in IRIShub?
IRIShub dev team cut a fresh releases of IRIShub v0.6.0 and IRISnet development team is ready to launch Fuxi-4000. This version of IRIShub contains many breaking changes, since we upgraded the dependency of Cosmos-SDK and Tendermit.

As shown in the diagram above, IRIShub is built upon Cosmos-SDK. For those new to Cosmos, Cosmos-SDK is a modular blockchain framework. It’s designed as a developer toolkit for building blockchain on top of PoS BFT consensus engine: Tendermint. The key features of Cosmos-SDK is its modularity. Anyone can create a module for the Cosmos-SDK and integrating the already-built modules is as simple as importing them into your blockchain application.
In IRIShub, it inherits some existing modules in Cosmos-SDK, namely Auth, Bank, Staking, Slasing & Distribution. The team modified Gov and Param modules to support specific functionalities. Meanwhile, We introduce two brand new modules: Record and iService. More will be explained in this article.
New Features:
- Record Module:
The record module functions to record the DNA of a piece of data and store it on blockchain. The mechanism is explained in the chart blow:

As you could see, now the client can get the hash of some data and record it onchain. This valuable storage will provide certificate later on.
Record module is the work of collaboration between core team and community contributors. The workflow could be tracked by this issue on GitHub:
Learn how to use Record module here.
- Software Upgrade Module
IRISnet believe in the power of evolution of blockchain. The codebase will contain certain level of bugs and developers will introduce new features someday. On-chain governance gives all stakeholders a chance to implementing changes to protocols. It supports major upgrades or patches in the source code.

In this version of IRIShub, Upgrade module is introduced since. Its process will be fully compatible with the historical data on the blockchain.The overall workflow is:
- Monitor the Software Upgrade Proposal in IRIShub and actively participate in the governance process of Software Upgrade Proposal。
- When the Software Upgrade Proposal is passed, Install a new software, send a switch message, and broadcast to the whole network.Install a new software, send a switch message, and broadcast to the whole network.
- Once reach the limited time, it will be counted whether the proportion of voting power of upgraded software exceeds 95%.
- If it exceeds 95%, the software will be upgraded, otherwise the upgrade fails.
- The validators who didn’t upgrade in time need to re-download the new software and blocks synchronized.
If the validator operator failed to participate in the upgrade process, they can run into some error by keeping the older version of IRIShub node running. To keep live in the new network, they need to download the proper version and replay some blocks.
IRISnet development team believes that by on-chain governance voting, we will see a more and more powerful IRIShub in the future. And the community could recover more easily from bugs.
After the upgrade process is done, the historical data on the blockchain is still avaiable. The new produced blocks will inherit the historical data.
- iService
In this version of IRIShub, the definition of iService is availble. iService is one of the key innovations of IRIShub. As stated in whitepaper:
IRIS Services (a.k.a. “iServices”) intend to bridge the gap between the blockchain world and the conventional business application world, by mediating a complete lifecycle of off-chain services — from their definition, binding (provider registration), invocation, to their governance (profiling and dispute resolution). By enhancing the IBC processing logic to support service semantics, the IRIS SDK is intended to allow distributed business services to be available across the internet of blockchains.
Now, it’s possible to define the basic info of certain iService and it’s achieved with “Interface-definition-language”, IDL. IDL is a powerful innovation which offers a bridge between the two different systems. This feature is essential as iService is designed to be revoked across heterogeneous systems: public blockchain, private blockchain and legacy system. It’s definition is also open to upgrade. More info is available here.
What’s New in IRISplorer
IRISplorer is a powerful website for browsing blockchain transactions and monitoring validator uptime.
The development team released a new version this month and it comes with the following new features:
- Improve Validator Menu

In this version of IRISplorer, validator set is divided into three categories: Active, Revoked and Candidate. Active validators are the ones who are bonded and eligible to sign votes. Revoked validators are the ones who are slashed, so they are unbonding. The voting power of Candidate validators are not enough to make top 100.
- Add Declaration Transaction Icon
As you can see, transactions are divided into four categories. Declaration transactions include CreateValidator,EditValidator &Unrevoke. These are common operations for validator operators. Delegators could use Stake tab to see their operations: Delegate / BeginRedelegation / CompleteRedelegation / BeginUnbonding / CompleteUnbonding.

- Improve Display of Proposal Info

Now, it’s possible to see proposer address in each proposal info.
Join Fuxi-4000 testnet
Please follow this guide!






