TL;DR
|
Full Story
This November has been a month of significant undertakings and unexpected challenges. A considerable portion of our efforts went into addressing and resolving issues that emerged during our Mainnet operations, particularly with the IBC relay. These efforts, while unplanned, were crucial to ensure the stability and efficiency of our systems as we gear up for upcoming launches.
🔄 IBC Relay: A major focus was on resolving several bugs found in our IBC relay during Mainnet testing. This work was prioritized to ensure smooth functioning for Balanced’s upcoming launch. We have successfully fixed and tested these bugs on both Testnets and the Mainnet.
⏸️ Hop Chain Integration: Progress on Hop Chain was temporarily paused due to the relay issues. Consequently, there hasn't been further advancement on this front, but we're aiming to resume in December.
🌐 xCall Wormhole and LayerZero Adaptor Contracts: All development work for these contracts is complete. We're currently testing them across various chains alongside xCall v2.0 Solidity contracts. The key task for December is building a robust testing framework, aimed at streamlining the expansion of xCall across different interoperable solutions. This framework is expected to take around two months, spanning December and January.
🛠️ BTP Redeployment and Testing: In November, we successfully deployed BTP to Lisbon and began testing with xCall v2.0. This was the first instance of testing BTP with xCall v2.0, leading to the discovery of a bug in the xCall v2.0 Solidity contract; this has been fixed.
🚀 BTP Mainnet Launch: We are targeting the week of December 18, 2023, for BTP's Mainnet launch. This plan depends on timely node synchronization and the recent BSC hardfork not impacting our implementation. Post-launch, we'll undertake thorough testing before making any official announcements.
🔗 ICON and Injective Integration: We aim to connect ICON to Injective by the end of December, contingent on a successful governance vote on Injective.
📈 IISS 4.0 Update: Work on IISS 4.0 is complete, and we're currently developing a migration plan. Expect to receive updates in December about the changes, migration timeline, and necessary actions for validators and voters.
We remain committed to transparency and diligence as we move forward with these integrations and enhancements to the ICON ecosystem.
📅 November’s Accomplishments:
Development completed for Injective on ICON berlin and Injective Testnets.
Deployment of Injective integration complete on ICON berlin and Injective Testnets.
Deployment of BTP on Lisbon, ETH and BSC Testnets complete.
Development of Central Relay completed.
Finished mapping of xCall v2.1.
Fixed all bugs identified in the IBC relay on Mainnet.
Fixed Bug identified in the xCall v2 solidity contract and deployed to Lisbon.
🎯 December’s Goals:
Deployment of the IBC connection for Injective to Lisbon.
Continue testing of xCall v2 contracts and adaptor contracts on various EVM chains as noted on the milestone board.
Test framework for xCall adaptors.
Continue the delayed work on Hop chain integration development.
Complete ongoing BTP testing with xCall v2 on Lisbon, ETH and BSC Testnets.
Test the Central Relay on Avalanche Testnet.
External Audits of IBC contracts.
Release Central Relay for Mainnet.
Deploy BTP to ICON, Ethereum and BSC Mainnets.
For those looking to stay up to date on development as the month progresses, rather than waiting for the next monthly update, we have a couple of extra options. You can stay abreast of our ongoing integration efforts with our Integrations Milestone board or take a deep dive on IBC development with the iBriz integrations report.
Next Month
Continuation of the ICON Validator Support Program.
Continue development of IISS 4.0.
In the month of December there will be a few posts about next steps for all our validators and what our voters need to consider as we commence plans to migrate to IISS 4.0. First step will be migration on Testnets more details will be released in a separate announcement.
Documentation updates
Find the latest update from the Dev relations team here.