ICON 2.0 is approaching, and we are currently preparing the network migration process. To make this as smooth as possible, effective communication is essential.
Currently, the main communication channel between the ICON Foundation and node operators is the
ICON P-Rep MainNet telegram channel. If you are already in this channel, please make sure you can receive notifications. If you are a P-Rep and you are not in this channel, please contact me on telegram
@nymkappa and I will add you in there.
The network migration process is still being drafted by engineers and it is close to completion. We will run internal test in order to identify major issues in the coming weeks.
The migration plan will be shared with the community in a transparent manner, and we will release updates in real time during the migration.
- ICON1 -
- Running LOOPCHAIN to follow the current ICON1 blocks
- ICON2 -
- SSD near 2TB+ ( 300GB for LOOPCHAIN data, 1.1T+ for ICON2 data )
- CPU with 8 Cores (the more the better)
- 16G RAM (the more the better)
- Connection to LOOPCHAIN RPC Server
- Internet connection
- Accessible P2P (TCP) ports
Note that not all P-Reps are required to run the migration process. If you are interested in running the migration process, please let us know on Telegram.
If you are not a technical user or do not want to do the migration manually, blockchain snapshots for ICON 2.0 will be available for download.
During the network migration process, the network should be paused. We expect this interruption in network operation to last for a couple of hours, but could last longer in case there are unexpected issues during the process. We would like smart contract operator to assess related risks linked to such pause in the network and prepare accordingly. If you have any concerns about this, please let us know as soon as possible.
We will keep updating this thread to share more details about the migration process. Make sure to monitor the forum and telegram channels in the mean time.