Ethereum [ETH]Constantinople's hard fork receives support from Koinex after Binance

In a recent report, Koinex, one of the best known exchanges of Indian cryptocurrencies affirmed that the company will support the much discussed Ethereum [ETH] Fork of Constantinople. Koinex had tweeted:

"Announcement: we will support the upcoming Hardover of Ethereum Constantinople.The Hard Fork will occur when the height of the block is 7,080,000 and the estimated fork date is January 16, 2019. Stay tuned for more updates. "

Koinex also hosts other popular cryptocurrencies like Tron [TRX], Lumen stars [XLM] and XRP. The announcement was greeted enthusiastically by the community of cryptocurrencies with many users applauding the cryptocurrency move.

Koinex joins a series of other popular cryptocurrencies that have announced their support to the hardfork, a roster that also includes Binpeng Zhao led by Binance. The exchange has even asked the cryptocurrency holders to allocate sufficient time for the deposits to be fully processed before the block height established by Constantinople is reached. Binance said:

"We will manage all the technical requirements involved for all users who keep Ether in their Binance accounts: Hard disk height: 7.080.000 Estimated time: between 2019/01/14 and 2019/01/18."

The hardfork met many expectations in the Ethereum user base, with some reports even stating that Constantinople could also involve other forks. Binance also added:

"If during the period of the rigid fork of Constantinople there will be other forks or hard launches, we invite these respective project teams to contact us at [email protected] for further discussions. "

The rigid fork of Constantinople was first discussed in 2017 during a meeting between developers and stakeholders with a launch plan in 2018. The launch in 2018 was further delayed due to problems with the launch of Ropsten TestNet. During the test, Lane Rettig, an independent core developer Ethereum, pointed out that there was a bug in the network's Parity implementation. He also added:

"Apparently, in this case, there was some confusion about the meaning of terms like" transaction "and" execution frames "that might have contributed to the bug."