SASEUL Blog
EN

When Will the SASEUL Hard Fork Be Finished? How Is a Hard Fork Different From an Update?

· Holder guide

#HardFork

When will the SASEUL hard fork be finished?

2.2 has had what's expected to be its last fix, and no date has been announced for 2.3

February 13, 2026

First 2.2 update file

June 15

2.2.0.4, some of 2.3 brought forward

July 28

2.2.0.5, expected last of 2.2

2.3

No date announced

Based on notices in SASEUL's official Telegram channel. Dates are Korea time. The whole notice channel was checked again on September 27, 2026.

Nobody knows when it will be finished. On September 27, 2026, I went through SASEUL's official notice channel again from start to end. There was no date anywhere for 2.3, the next hard fork (a big update after which old programs no longer fit).

The most recent related notice is #82, from July 28, 2026. It put out what's expected to be the last fix for version 2.2 and only said "we'll now focus on 2.3 and share more when it's ready". The only notice since then is the September 15 mining pool list (#84).

How is an update different from a hard fork?

An update is fixing a program and putting out a new version. Usually, even if you keep using the old version for a while, you can still share the record book with other computers.

A hard fork is the kind of update that changes the record book's rules. After a set point, a node (a computer holding a copy of the record book) running the old program no longer matches the new record book.

Think of a club's shared account book. If you only change the handwriting, it's fine to keep the old book. But if you change it to "from this month, the columns are split differently", anyone holding the old form can't match their book against everyone else's. The second one is a hard fork.

SASEUL's notices use it in exactly this sense. The September 9, 2022 notice (#13) said version 2.1.2 would split off on its own at main block (one page of the transaction record book) 150,000, and would no longer match version 2.0.

What hard forks has SASEUL had so far?

Here's when the notices mentioned a "hard fork" or "no longer matching old versions". Dates are Korea time.

Date Notice What happened
2022-06-30 #5 Version 2.0.4. Hard fork at 1 a.m. on June 30
2022-07-06 #6 Version 2.0.6. Hard fork at 9 a.m. the same day
2022-08-18 #11 Said 2.1 would come out on August 24 with a hard fork at the same time
2022-08-25 #12 2.1.0 (unstable). Hard fork planned after testing through the next week
2022-09-09 #13 Version 2.1.2. No longer matches 2.0 from main block 150,000
2022-09-15 #18 Version 2.1.3.7 must be installed. Without it, you split off at 150,000
2023-07-19 #49, #50 Hard fork to fix a difficulty (how hard the answer is to find) error in the mining-side record book. 2.1.9.2, from resource block 625,000
2023-07-20 #52 Computers on the new version had trouble finding each other, so 2.1.9.3 went out in a hurry
2024-09-14 #61 Said the hard fork would be done within September
2025-03-12 #62 Explained the method: the hard fork happens exactly 30 days after the new file is uploaded
2026-01-14 to 02-01 #70, #71, #72 Pushed back from January 15 → 19 → 25 → February 3
2026-02-13 #73 First update file. Released in several steps, and once all are out, old versions won't match
2026-02-16 #74 A new file fixing minor bugs in the first update (2.2.0.2 in the official docs' history)
2026-02-23 #75 Version 2.2.0.3
2026-06-15 #79 Version 2.2.0.4. Brought forward some of what was planned for 2.3
2026-07-28 #82 Version 2.2.0.5. Expected to be the last fix for 2.2

The September 2024 notice (#61) said the hard fork would be done that month. But the update history in the official docs goes straight from 2.1.9.6 in July 2023 to 2.2.0.1 in February 2026. And from late 2025 to February 2026, the date was pushed back three times.

Is 2.2 finished? When is 2.3?

Version 2.2 started with its first file on February 13, 2026 (#73). The notice said the second and third updates would likely come 2 to 3 weeks apart. What actually came out just three days later, on February 16, was 2.2.0.2 (#74). The notice called it a fix for small bugs found in the first update, not the second update. After that came 2.2.0.3 on February 23, 2.2.0.4 on June 15 and 2.2.0.5 on July 28.

Official SASEUL Telegram notice #82. Announces version 2.2.0.5, expected to be the last fix in the 2.2 line, with development moving on to the hard fork (2.3)
Official SASEUL Telegram notice #82 (July 28, 2026). It's expected to be the last fix for 2.2, and says the team will now focus on the hard fork (2.3). No date.

The June 15 notice (#79) and the July 28 notice (#82) call 2.3 the "hard fork (2.3)". So it reads as if this hard fork ends when 2.3 comes out. But no notice has directly said "it's done when 2.3 is out". That part is a guess.

Official SASEUL Telegram notice #79. Says main block creation delays are being fixed, and version 2.2.0.4 brings forward some of the coming hard fork (2.3)
Official SASEUL Telegram notice #79 (6:52 a.m. Korea time, June 15, 2026). It put out 2.2.0.4, bringing forward some of what was planned for 2.3, and said the 2.3 plan would be shared separately.

No date for 2.3 had been announced as of September 27, 2026. Past schedules were pushed back several times, so even when a date comes out, it's safer to check the notices again.

How did the team explain the hard fork?

The December 31, 2025 notice (#69) said it's only called a "hard fork" for convenience. At heart, it's a big overhaul of the SASEUL engine (the core program). The original wording is "fundamentally a core engine upgrade". It also said a hard fork isn't something you can do often, so fixes were gathered up to go out all at once, which is why it took longer.

The September 22, 2025 notice (#68) said they're very careful because once an update goes out, it can't be rolled back even if something goes wrong. The March 12, 2025 notice (#62) said uploading the new file doesn't mean the hard fork is finished. Its explanation was that performance improves little by little as more nodes move to the new version.

Was there a warning about people using the hard fork as bait?

Yes. The September 22, 2025 notice (#68). It said it was put out because many people lost money over false information and pushing around the coming hard fork. It also said some people use the hard fork for their own gain.

What was going around isn't in the notice, so that's unknown. If you see a post about a hard fork date or what it includes, first check whether the official notice channel says the same thing. No notice up to September 27, 2026 has told anyone to move coins somewhere else or enter their private key because of a hard fork.

What should node runners and people who just hold coins do?

What the notices say to do depends on who you are.

Who What the notices say to do Notice
People running their own node Switch to the new version. They asked people to install 2.2.0.4, and recommended 2.2.0.5. Instructions are on the official download page (Docker Hub) #79, #82
People starting a new node Use the latest version on Docker Hub. They said they won't answer setup questions #62, #73
People who only hold coins Nothing to do because of the hard fork Checked all notices
People using the official wallet app Guardee Before updating the app, write down your recovery phrase (the set of English words that brings back a wallet) and private key separately #57, #58

The Guardee row came from wallet app updates, not a hard fork. The June 19, 2026 app overhaul (#80) added a new wallet type. It said the old (Classic) wallet can still be used, and recommended moving to the new type.

The notices say nothing specific to people mining through a pool. Which version the pools use is unknown.

Where can I check?

What SASEUL is, is covered in SASEUL basic facts, and past events are in the timeline.

Sources

Finished reading? These go well with it