bhonetwork / bholdus-chain Goto Github PK

Description
Phoenix Runtime with instant seal consensus stops creating block at block height 199.
I was running redspot integration tests for ink! contract. While running the tests to reach block height 199, Phoenix stops creating new blocks.
This error can be reproduced deterministically.

Chào ad
Mình có VPS rảnh nên đang chạy mainnet của BHO
Mình có thể làm gì với nó?

cargo build --features with-ulas-runtime --release
./target/release/bholdus --chain=ulas

Motivation
According to #83, phoenix with manual seal has problem with creating new blocks after block height 199.

It's hard to identify where the problem is. phoenix is a complex runtime of many built-in substrate pallets to make NPoS feasible. Phoenix includes Staking, Session, Session Historical, Election Provider, I'm Online, Authority Discovery,.... . Even though, the pallets are designed to be loosely coupled to each other, in runtime configuration, they are assembled to work with each other. Hence, identifying where the problem is can be troublesome.

To integrate manual seal into phoenix, I used substrate-contracts-node, frontier template as reference. I already ran contract tests against substrate-contracts-node and everything works fine. substrate-contracts-node runtime is very simple hence I'm guessing integrating manual seal consensus with such complex runtime is not trivial and requires more in-depth research.

To solve the problem in a different way without phoenix being retouched, I ask myself again why we need manual-seal runtime in this repository in the first place:

• We need a manual seal runtime that behaves the same as substrate-contracts-node to be our development environment with ink! smart contracts.
• We need that runtime to live in the same repository as BHO Chain so that we can easily try out new pallets and especially chain extension on that runtime. This allows BHO Ink! contract developers to have a development environment with extended features provided by BHO Chain besides stock features provided by pallet-contracts.

In the end of the day, what we need is a development runtime that is never used in production. Based on that, I decide to introduce a new runtime called Hyper with minimal configuration so that manual seal could work without errors.