Previously, Tech Update focused on IBC and BOS3s LIB and how these two technologies complement each other, with fast LIB consensus finality impacting IBC and that in turn being a key component to multi-chain scaling, it’s not too difficult to see how important technological advancements in these areas are to the EOSIO ecosystem as a whole.

The main topic of this week’s Tech Update is the BOSCore testnet (test network), BOS 3s LIB is currently deployed on the BOSCore testnet undergoing rigorous testing that must be carried out before it can be deployed on the BOSCore or EOS mainnet, there is a substantial bug bounty program, announced during the latest testing phase.

BOSCore Bug Bounty Program

We also take a look at how to explore BOSCore’s testnet, deployment guides for BOS IBC and node setups, while discussing the value “near live” testing environments bring to the ecosystem.

BOSCore’s initiating team had launched the public EOS Testnet, CryptoKylin during July 2018. Many EOS Block Producers contribute to the development of the ecosystem by providing developer support and project testing infrastructure on public testnets, infrastructure that is crucial for the ecosystem of Dapps to thrive and it is from here, in Sept 2018, 3 months after the EOS mainnet launch that Huobi Pool, CTO Huaqiang Wen, joined by BP teams began to initiate the BOSCore side-chain to bring the envisioned technological advancements of multiple side-chain scalabilities to the EOSIO ecosystem.

Exploring BOS Testnet

EOSX.IO

BOSCore’s testnet along with several other EOSIO based testnets can be explored through BOS block explorers, from an explorer select [BOS Testnet] chain to see live status information relating to the BOS testnet.

Bloks.io

Testnets are important for testing and finding bugs in the underlying blockchain protocol, by replicating mainnets in “near live” environments, testnets and those who participate in them strengthen the ecosystem. System tokens on testnets known as faucets have no $ price and are solely used for testing, everything from voting, leasing to IBC can be tested in these environments.

DApp developers will use private and public testnets for development and testing of smart contracts before deploying their software on a live blockchain.

With the advent of BOS IBC and interoperability between blockchains, testing in multi-chain environments is made possible, BOSCore as innovators and leaders in the field of emerging open-source IBC standards have made available a detailed deployment guide between the Kylin and BOS testnets.

Setting up a node and participating on the testnet is relatively straight forward, BOSCore, uses Docker images available for deploying across nodes simplifying the build process, as building from source code, compiling the binary files, etc., can take several hours longer.

https://github.com/boscore/bos-testnet

Details on joining BOSCore’s testnet can be found on BOSCore github pages and there’s a dedicated Telegram channel at t.me/BOSTestnet.

It’s worth pointing out that while testing of BOS 3s LIB is ongoing, the BOS testnet is under-going frequent updates, such as the nature of testnets, in that the test environments can be subject to frequent change, including network resets while debugging updates on the underlying blockchain protocol takes place. The most recent release candidate, at the time of writing, is BOSCore version 3.0.1-rc2

https://github.com/boscore/bos/tree/v3.0.1-rc2

Thank you for reading, hope you enjoy these updates and please feel free to comment or contact us, links below.

Contact: dev@boscore.io

Website: https://www.boscore.io

Github: https://github.com/boscore

Twitter: https://twitter.com/Boscore_BOS