As we move into October, the ICON team continues to make progress on BTP, ICON Bridge Integrations, and ICON 2.0. This article will cover our September development and October development plans.
Architectural Framework for BTP
We tested and planned potential feature implementations including block update rewards, relay fees for routed messages, and xCall service features this month. Unless there are any issues or architectural design challenges, BTP integration testing is expected to be completed in October.
Relay fees for routed messages have been the main challenge. It is expected that a final decision will be reached in the coming weeks after a few architectural design options have been outlined.
As of October, routed message fees will also be implemented. Integration testing may also be required as a result of these implementation details.
Within the last 30 days
- We evaluated the work for rewarding block updates but ultimately decided that this feature is not necessary at launch. The design is ready if it proves necessary.
- Developed a few options for handling relay fees for routed messages.
- Continually run integration tests on new features and edge cases.
- Continually fixed bugs discovered during integration testing.
- Based on the relay fee design, we have added new features to the xCall service.
In the next 30 days
- Handle relay fees for routed messages in a finalized manner.
- Implement relay fees for routed messages and begin implementation.
- Implement and debug the BTP block state sync.
- BTP Messages should contain more event logs for easier tracking of message status.
- Relay fees in the BMC and protocol fees in the xCall service specs need to be added to the Message Broker and xCall service specs.
Integrations with interoperability
ICON is doubling down on open-sourcing development and integration of ICON Bridge. ICON Bridge integration GitHub has been made public, and integration teams will move to a monthly release schedule for releases (published here) and progress reports (published here). A separate report summarizing what has been accomplished and what is planned for next month will be released once these updates are submitted.
Version 2.0 of ICON
As part of our efforts to upgrade GoLoop, integrate Rosetta API, and develop a new method for calling ChainSCORE, we made progress in September. Every time ChainSCORE is updated, the new custom proposal will make it easier to extend functions by adding parameters instead of submitting a new proposal for a new function (current version).
ICON 2.0 for the last 30 days
- Launched “GoLoop version 1.2.12”, onboarding SejongNet, BerlinNet, LisbonNet, MainNet Citizen, ICON_Foundation, ICONFi, and Velic as validators
- Developed a new proposal for ChainSCORE’s ICON calling method
Rosetta for the last 30 days
- Extensive testing was conducted to fix errors such as the incorrect handling of locked accounts and the incorrect transfer of addresses
- After observing speed issues with MainNet due to disk usage and database pruning, we completed a mainnet data sync. Mid-September, the team fixed the speed issue and completed the sync
- Implemented exception handling for duplicate tx incidents that occurred during the previous migration
- As required in the Rosetta Readiness Checklist, created a docker file based on Ubuntu (the current version is Alpine).
Within the next 30 days
- Create a Rosetta Docker file based on Ubuntu
- As a custom-made function, vet downloading the Mainnet Backup DB
Via this site
