ignite

Ignite Chain is powering the decentralized finance ecosystem not only for the individuals or end-users but for financial institutions & businesses that have cryptocurrency exposure. Defining itself as the next generation of blockchain, Ignite provides decentralized solutions to a number of on-chain partners ranging from small enterprises to big-tech & investment management funds.
Ignite uses a self-regulating and self-sustainable network model that enable pervasive of trustless economy & the ideology of pure decentralization.
Ignite blockchain network is created with the goal of forming a decentralized and distributed community that would be able to develop, test and launch new exciting blockchain technology powered financial products and applications.

With the aim to bring down heavy transaction fees and confirmation time, we are aiming for mass market adoption by providing lower costs yet ultra fast peer-to-peer network
Ignite Chain is a public blockchain that is designed for mass adoption of blockchain technology by business users of all sizes. It is intended to serve as the foundation for a sustainable and scalable business blockchain ecosystem.

From a technical point of view, the Ignite Chain is built upon existing proven blockchain innovations and novel technologies that are created for achieving mass adoption. These technologies include Proof-of-Stake (PoS) consensus mechanism, meta transaction features, protocols of transaction fee delegation, on-chain governance, built-in smart contracts as well as tools for developers.
The Ignite blockchain is open to the public, allowing participants from around the world to join in to secure and verify the record reflect accurate state of affairs. Ignite Blockchain is not just a platform for recording transactions, it executes “smart contracts”–computer programs that directly control asset transfer between parties with objective and fair logic.
 
Ignite Consensus Protocol
If a sufficiently large portion (alpha α) of the validators sampled reply that they think the transaction should be accepted, the validator prefers to accept the transaction. That is, when it is queried about the transaction in the future, it will reply that it thinks the transaction should be accepted. Similarly, the validator will prefer to reject the transaction if a sufficiently large portion of the validators replies that they think the transaction should be rejected.

The validator repeats this sampling process until alpha of the validators queried reply the same way (accept or reject) for beta β consecutive rounds.