RE: LeoThread 2025-05-09 13:17

[rujiraupdates]

The Merge is temporarily on hold while the upgrade to v3.5 is underway. Hold any Merge transactions until an official update confirms the process is live again.

"Tomorrow, around 3 PM UTC, the network will be upgraded to v3.5.

Comments

[rujiraupdates]

This update addresses the $NSTK issue and will allow the merging of $NSTK tokens. Due to changes affecting the Bifrost, additional measures are necessary, including the temporary suspension of trading and transaction signing.

[rujiraupdates]

Consequently, the Merge process will be paused during the upgrade. The community will receive further notifications when trading is halted and the Merge disabled (Step 2) and again when trading resumes and the Merge is reactivated (Step 8).

[rujiraupdates]

Important: Merge buttons on the provided link will be disabled during this period.

[rujiraupdates]

Attempting to merge tokens via alternative methods, whether direct contract interaction or other platforms, is done at users’ own risk and falls outside of any responsibility.

[rujiraupdates]

Once trading resumes and the Merge buttons are reactivated, the $NSTK token merging can recommence.

[rujiraupdates]

The TC v3.5 process is scheduled as follows:

1. Halt churning one day before the upgrade to avoid mid-process disruptions.
2. Cease trading 15 minutes before the upgrade.
3. Stop transaction signing 10 minutes before the upgrade.

[rujiraupdates]

Discontinue scanning 5 minutes prior to the upgrade.

1. After the first successful post-upgrade block, wait 5 minutes for any lagging validators to ensure consensus.
2. Resume scanning and send test inbounds.
3. Restart signing once test

[rujiraupdates]

inbounds are observed.

1. Resume trading after refunds are signed and confirmed.
2. After two hours with no trading issues, restart churning and monitor until completion."