SASEUL's Hard Fork (2.3) Is a Big Update Moving Nodes to Version 2.3, and the Date Is on the Official Notice Channel
What is the SASEUL hard fork (2.3)?
It's a big update moving the node program to version 2.3. Check the date on the official notice channel
February 13, 2026
First version 2.2 update file
June 15
Version 2.2.0.4, part of the hard fork (2.3) put in early
July 28
Version 2.2.0.5, expected last fix of the 2.2 line
Hard fork (2.3)
Date: on the official notice channel
SASEUL's next hard fork, 2.3, is a big update that moves the program a node (a computer holding a copy of the record book) runs up to version 2.3. After the new version, old versions can't share the record book with it. The date will be on SASEUL's official notice channel.
How is an update different from a hard fork?
An update fixes a program and puts out a new version. Usually you can keep using the old version a little longer and still share the record book with other computers.
A hard fork is an update that changes the rules of the record book. After a set point, nodes running the old program no longer match the new record book.
Think of a savings-club ledger. If you only change the handwriting, the old ledger still works. If the club says "from this month, we split the columns differently", someone with the old format can't check their ledger against the others. The second case is a hard fork.
What has been announced about the hard fork (2.3)?
The December 31, 2025 notice (#69) said "hard fork" is just a convenient name and that it is fundamentally a core engine upgrade, meaning a big fix to SASEUL's core program.
The first update file of version 2.2 came out on February 13, 2026 (#73). It said the updates would come in several steps, and once all are done, old versions will no longer match. These files followed.
| Date (Korea time) | Version | Notice | What it was |
|---|---|---|---|
| 2026-02-16 | 2.2.0.2 | #74 | A file fixing a small bug found in the first update |
| 2026-02-23 | 2.2.0.3 | #75 | Version 2.2.0.3 |
| 2026-06-15 | 2.2.0.4 | #79 | An update fixing a main-block creation problem on some nodes. Part of what was planned for the hard fork (2.3) was put in early |
| 2026-07-28 | 2.2.0.5 | #82 | Expected to be the last fix of the 2.2 line. Development now moves to the hard fork (2.3) |
The "Notice" column is the number of a post on SASEUL's official Telegram notice channel. Click it to open the post.
As for what exactly changes in 2.3, the notices say the team will share more when it is ready. This post will be updated when new details come out.
What hard forks has SASEUL had before?
These are typical times when notices mentioned a hard fork or said old versions no longer match. Click the number in the notice column to open it.
| Date (Korea time) | 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-09-09 | #13 | Version 2.1.2. No longer matches version 2.0 from main block 150,000 |
| 2023-07-19 | #50 | Version 2.1.9.2. A hard fork from resource block 625,000 to fix an error in the difficulty (how hard it is to find the answer) on the mining side of the record book |
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 | No notice asked for anything because of the hard fork | 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.
If you mine through a pool, check the pool's own announcements for which version it runs.
Where can I check the date?
- SASEUL's official Telegram notices: viewable on the web without logging in. A hard fork date will be posted here
- Update history in the official docs: the change log by node version
- The front page of the official explorer: if the Resource Blocks number rises within a minute or two, the record book is growing
Nothing in the official notices says "a hard fork is coming, so move your coins" or "enter your private key". If someone uses hard fork talk to rush you, first check the notice channel for the same words. Similar cases are in the post on buying coins person to person.
What SASEUL is, is covered in SASEUL basic facts, and past events are in the timeline.
Sources
- Official SASEUL Telegram notice #5 · 2.0.4 and a hard fork · 2022-06-30
- Official SASEUL Telegram notice #6 · 2.0.6 and a hard fork · 2022-07-06
- Official SASEUL Telegram notice #13 · version 2.1.2, splits at block 150,000 · 2022-09-09
- Official SASEUL Telegram notice #50 · 2.1.9.2, hard fork at resource block 625,000 · 2023-07-19
- Official SASEUL Telegram notice #57 · 2nd anniversary, key-keeping notice before the Guardee update · 2024-05-16
- Official SASEUL Telegram notice #58 · Guardee update · 2024-06-02
- Official SASEUL Telegram notice #62 · how the hard fork will proceed · 2025-03-12
- Official SASEUL Telegram notice #69 · hard fork progress · 2025-12-31
- Official SASEUL Telegram notice #73 · first hard fork update file · 2026-02-13
- Official SASEUL Telegram notice #74 · new file fixing a small bug in the first update · 2026-02-16
- Official SASEUL Telegram notice #75 · version 2.2.0.3 · 2026-02-23
- Official SASEUL Telegram notice #79 · version 2.2.0.4, part of 2.3 put in early · 2026-06-15 06:52 (Korea time)
- Official SASEUL Telegram notice #80 · Guardee overhaul · 2026-06-19
- Official SASEUL Telegram notice #82 · 2.2.0.5, expected last fix of 2.2 · 2026-07-28
- Official SASEUL Telegram notice channel, all posts · checked 2026-09-27
- SASEUL Docs · Node (update history) · checked 2026-09-27
I opened and checked the official notices and the official docs myself on September 27, 2026.