Happy New Year, ICON Community Members!
As we kick off the new year, we would like to share some reflections on the past year and details regarding our strategic focus for 2023.
While 2022 kicked off with a setback on BTP development, we turned things around with the launch of ICON Bridge (which has also just recently completed its audit), progress on open-source development, and teams such as Craft, Balanced, and Havah starting to test BTP applications alongside continued BTP development.
In 2023, we will continue adapting to an evolving interoperability landscape by expanding use cases for xCall, a standard for generic cross-chain messaging, to interoperability protocols beyond BTP.
If you would like to skip to plans for 2023, jump right ahead to here. Otherwise, let’s take a step back to review 2022 in more depth before moving on.
2022: A Year in Review
One of the hardest pills to swallow in 2022 was yet another delay in BTP development. Just when we thought that BTP launch was in reach, the development team discovered, during the final stages of testing before deploying to mainnet, that the gas fee estimates for cross-chain transfers were too high to launch BTP for commercial use. As a result, ICON Bridge was presented as an interim solution, which would maintain most of BTP’s key technical features while centrally validating messages to bypass high gas fee issues until the completion of BTP.
While the unexpected change of course caused more delays than the team would have liked, ICON Bridge launched with integrations to BSC and the open publication of standards that would allow interested third parties to integrate ICON Bridge to their own products while also structuring the codebase. This was in line with the team’s broader initiative to push open-source development by requiring all developers building ICON core protocols including BTP and ICON Bridge to publicly make available the codebase and related progress reports.
Beyond the launch of ICON Bridge, 2022 was an eventful year in which we celebrated the following:
- BSC and SNOW were integrated into ICON bridge. The valuable FYEO Audit for Solidity, CMD/GO and Java-based contracts has completed as well.
- ICON Bridge infrastructure was used to support cross-chain NFT minting between ICON and Harmony
- BTP 2.0: ICONLOOP have worked through all the issues previously encountered with the BTP 1.0 architecture. BTP 2.0 is currently being built out.
- Tracker upgrade: A lot of work was done to build critical infrastructure enabling teams to tap into API’s and pull data from the blockchain.
- ICON held a three-day workshop with its partners at Korea Blockchain Week and later featured at the W3N conference.
- Online content and presence received a boost. The ICON Network handle has established a broad content portfolio with updated accounts across Twitter, YouTube, Reddit and CoinMarketCap. The ICON Blog was brought back in from Medium and a well-filled ICON Learn section was launched to give outside researchers an instant overview of ICON’s tokenomics, governance and technology.
- The Immunifi Bug Bounty Program was launched for the ICON blockchain, in order to ensure we are doing everything we can to make sure ICON is secure.
- Technical Community focus - This has been a considerable focus with work being put into fostering the right culture for an open-sourced development environment. The introduction of * * RFPs from the ICON Foundation, along with community special interest groups.
- With the parachain auction success of the SNOW Network, ICON community members became eligible to claim their airdrop.
2023: What to Expect
Cross-Chain Hub Strategy
As ICONLOOP continues bringing BTP closer to completion, the team will be exploring use cases that extend the application of the xCall feature beyond BTP. In 2023, ICON will push for wider adoption of ICON interoperability standards in the industry by supporting not only BTP but also other interoperability protocols such as IBC, Optimistic Rollups and Zero Knowledge Proofs. We would achieve this by providing xCall services via the aforementioned protocols.
By broadening ICON’s interoperability offerings, ICON will be better positioned to cater to the diverse needs of a broader user base, improving its chances for survival in an ever evolving interoperability landscape while offering flexible security assumptions for application developers.
Wait, but what is xCall and how will it allow ICON to support other interoperability solutions?
xCall is a key feature of BTP and ICON’s unique standard for generic cross-chain messaging between heterogeneous blockchains. Teams and dApps are already using the xCall service with BTP on ICON testnets. Besides using xCall with BTP, the xCall service can be implemented to work with other interoperability protocols as well. The ICON Network becomes a more attractive cross-chain hub when the xCall service supports multiple protocols, each with their own pros and cons, offering maximum flexibility to developers.
Our first area of focus will be integrating the xCall service into IBC, together with the iBriz and HugoByte development teams. Fortunately, IBC is a well-specified protocol with detailed guides already created on how to build new implementations. Our integration teams are working through the planning stages of the xCall-IBC implementation build. Once the planning has been completed and mapped out, a clear list of development milestones will be shared.
Value to ICON
Identical to the way that the xCall service on BTP charges fees, the xCall service on other interoperability solutions will also charge fees. Fees are always paid for on the origin blockchain. This means that cross-chain data with transaction fee estimations gets collected in advance and displayed + paid for in the origin blockchain’s currency. These fees will be used to serve two purposes:
- Reward relay node operators for their part in the cross-chain transaction
- Purchase ICX from the market and burn it
In the past, the accumulation of xCall fees would have been reliant on the widespread adoption and usage of the BTP interoperability protocol. By becoming a cross-chain hub with multiple interoperability protocols implemented, the xCall service can operate on more than one interoperability protocol. A broader availability of the xCall service will increase its usage and attractiveness to teams who are looking to build out secure dApps with cross-chain use-cases.
One of the things to remember is that BTP is an entirely new standard of cross-chain bridging that has never been built before for which original research is being conducted in parallel to development. It’s as if ICONLOOP is writing the manual on how to build something while also building it in parallel. As with all research, unforeseen obstacles are unavoidable. Yet, the ICON team is confident that just as we have already done in 2022, we will be able to meet and rise above any challenges to continue building towards an interoperable future.
Onwards and upwards!
For further information, questions and discussion join the ICON Discord today!