We are gearing up for the initial release of 2.0 on 2024/10/10 at 11:00pm UTC (this time likely won’t be exactly precise, but within a few minutes or so). Here are a few quick questions that keep coming up, with answers.
How do I claim my tokens?
If you earned tokens before 1.4.19, those are already assigned to the address derived from your peer id, or to the bridge if you already bridged them.
If you earned tokens during 1.4.19/1.4.20/1.4.21, those will be minted out automatically by your node after the network exits stasis lock (provided you are running 2.0).
How quickly do I need to upgrade?
You’ll probably want to do it sooner than later. If you earned tokens during 1.4.19/20/21, the sooner the better, as there is a one-week open period to start claiming those tokens earned, and afterwards the ability to claim them is shut off permanently.
How do I combine keys?
If you ran multiple nodes during different generations and they don’t overlap (or overlap very minimally), you might want to combine them for prover seniority. See this page for details: Advanced Configuration | Quilibrium Docs
When will the token commands become functional?
After we exit stasis lock, or approximately 24 hours after the release of 2.0. While the token commands are stubs presently, please review the qclient command help for more information.
When does the bridge come online?
After we exit stasis lock, and after the network is confirmed to be stable. Shouldn’t take too long to confirm, but confirmation is key here.
As updated on the status page (with additional notes):
Release is presently scheduled for 2024/10/10 at 11:00pm UTC.
We are monitoring geomagnetic activity associated with an unexpectedly large solar flare that may impact data centers and especially residential users on commodity hardware/satellite internet. In order to ensure a fully fair launch for prover ring membership (corrupted messages or system RAM/dropped packets, especially on residential hardware and satellite internet users), if NOAA reports indicate sufficient concern, we will respond accordingly either with extending the stasis period itself, or pausing the launch until the storm’s end, which is approximately on the afternoon of 2024/10/11. If this rescheduling happens, we will give a definitive updated time for the process to begin or the stasis lock period to end. For more information about direct impacts to affected systems and current weather information: https://www.youtube.com/watch?v=eBh5-uB77ns
Worst case scenario to ensure the initial launch is safe for all, we may be looking at a launch move to ~36 hours from scheduled time.
After monitoring NOAA data, it is an extremely high likelihood that a G4-G5 geomagnetic storm event is expected to occur over the next 24-36 hours. This has a high risk of power outages in some regions, and memory/data corruption, especially on non-server grade hardware. Due to many node operators running on commodity hardware, the risk for data corruption is far higher than normal, and equal risk of prover ring entry message failure. To protect both the success of the network launch, prover key merging, and to ensure users do not risk key material or token loss, we are rescheduling the launch to begin 36 hours from the original date, to 2024/10/12 11am UTC, after the geomagnetic storm has dissipated. We strongly advise that users take backups of their .config directory immediately if they are not regularly doing so.
Also, quick note: some folks running clusters are reporting strange yaml generated by the merge command. It appears to be a yaml library bug, so be sure to check your yaml generated is valid, or if you prefer, just edit your config.yml manually via instructions here: Advanced Configuration | Quilibrium Docs
