So hm. EOSForce founder Cyborg (Gushi) went to and spoke at the Global Blockchain Developer Conference 2018 in Hong Kong held over the past weekend (Dec 15 -17).
As shown above, top representatives from the BCH community were the main organizers and participants of the event. Half of the blockchain industry was there. Cyborg finished his talk. And the final output of this whole event effort is that EOSForce will be developing BCH. Specifically, the EOSForce team will divert half of its developer effort to the development of BCH. Seems rather confusing how all this came. Here’s a list of potential questions I came up with that I imagine you are having right now:
- What is EOSForce?
- What is the relation between EOSForce and the BCH community?
- What kind of development is EOSForce going to have on BCH?
- Everything else you need to know between EOSForce & BCH
Enjoy the story.
Cyborg, from the BCH community, decided to develop EOSIO in March this year. Right now EOSForce the most active parallel chain launched on EOSIO, providing a richer blockchain support for developers and a fairer governance mechanism for the community. And the EOSForce development team is so far the only team that’s able to develop on the fundamental level of the EOSIO code outside Block.One, the creator of EOSIO.
Launching a parallel mainnet on EOSIO has placed EOSForce in a unique place in the blockchain space. On one hand, EOS has often been criticized for being too centralized. On the other hand, it is the most active blockchain there is and developing it requires the most capable blockchain talents in the industry. Having some of the most technically capable talents, the EOSForce team went ahead to develop its own chain, bearing both great attention and criticisms for the move.
However, EOSForce differs from the EOS Mainnet in many aspects. We don’t believe that one single network is capable of supporting a great number of applications. It is in all likelihood that one application should have its own public blockchain. So we want to maximally reduce the difficulty of developing a public blockchain and making customizing one really fast.
The current EOS Mainnet is also called the “gambling chain.” The reason is that most of the Dapps that run on the chain are gambling games. These Dapps have high liquidity and profits, which can pay for transactions resources however expensive they might be during network congestions. However, Dapps outside the gambling such as philanthropy, non-government organization (NGO), social platforms etc. do not have the rich liquidity to pay for expensive network resources. Practically, NGO Dapps and gambling Dapps cannot run on the same blockchain for the high resource cost. Many teams are now coming to EOSForce wanting to launching their own blockchain.
The next blockchain boom will be customized public blockchains running their individual Dapp.
Right now we have just finished our latest version of our single chain network. Next up we will be developing multichain and interblockchain aspects. 2019 Q2 will see the access of a heterogeneous chain. With respect of this interblockchain development, EOSForce is leading in the blockchain industry.
We have been in contact with the BCH community for a long time. They understand our technical capabilities and what we are good at. Engineering is our strong suit. Bringing our effort into the BCH community can provide a better version from the perspective of community governance. The issue with BCH has always been with governance. Developing a version that’s compatible with many others, although takes a long time, but is much better than forking and forking again and again. Seeing that we are able to help with the community governance on a technical level, the BCH community and EOSForce have decided to come together and explore options. Hence, we will divert half of our developer capacity to developing BCH.
With regard to a development roadmap, we expect to release more details at a later date. For now please stay tune with EOSForce official channels and community development.
Not bad for a DevCon event eh?
Contact EOSForce
Twitter | English Telegram | Reddit | Github |Korean Telegram
