The month of April has been all about testing BTP components in a live testnet environment. During this time, a BSC testnet update required modifications to our relay and BMV contracts. In this article, we share tasks completed and development milestones for May. Work on the IBC integrations of xCall Service continues to be captured in dedicated monthly reports, which are also linked in this article.
xCall Architecture / Product
With BTP being live on Ethereum and BSC testnets our team has been busy using the first month to test all the components of BTP on a live testnet environment, they have already implemented various fixes to improve security and performance. Our team has also been working through the changes shipped to BSC testnet, more details on this can be found in the challenges section below.
BTP blocks testing on Berlin testnet - ongoing/ monitoring
End to end testing on ICON (berlin) & BSC testnet - ongoing
Ongoing BSC and ETH relay testing and debugging
Ongoing BSC and ETH BMV testing and debugging
Commenced working on Relay and BMV changes for BSC due to changes introduced by the proposed Luban update
Update relay and BMV with changes made to the BSC testnet via the Luban update
Continue working on enabling trustless bridging BSC testnet to ICON
Start testing with our focused testing group comprised of our ecosystem builders.
As mentioned earlier, BSC has updated its testnet with the proposed Luban hardfork changes. This alters the finality of block times on BSC, which requires us to modify our relay and BMV contracts. Our team has been diligently working on these changes, and we plan to release the updates to testnet by the end of next week.
Changes like these are rare, but when they occur, they are first deployed on testnet to allow teams to make any necessary modifications and test them on testnet to ensure that they are ready to update their protocols when the changes are implemented on mainnet.
Ibriz and Hygobyte have continued work on the IBC integrations with their monthly progress reports being published below:
Milestone boards for both IBC and BTP integrations are published here:
Released Goloop v1.3.5 on mainnet after monitoring SejongNet, BerlinNet, LisbonNet
Improved stack watcher behavior: fixed Java EE (Execution Environment) StackOverflowErrors
Improved websocket monitoring: added progress notification feature
Improved coverage on Goloop master branch: 44.77%
Code review of new P-rep tool feature completed: subcommand for call method network proposal
Improved Goloop ValidatorState: more efficient memory usage and CPU computation regarding snapshot
Added url parameter to registerValidator API in ChainScore
PR regarding zk-Snark support using BN128 (cryptographic mathematical tool for efficient and secure ways to create and verify digital signature)
Decided to continue with BLS12-381 as it is more efficient and secure pairing curve
Released Javaee-scorex v0.5.4: Fixed copy constructor issue of ArrayList
Ongoing implementation planning for ICON monetary policy change: improving reward/penalty system with new features
Announced ICON Validator Support Program
Goloop v1.3.6 release planned for May to fix consensus issue
ICON monetary policy implementation plans and development
Continuing the ICON Validator Support Program
Improving bug reporting process
Improving code coverage
Find the latest update from the Dev relations team here.