SASEUL Node Program Version 2.3.0.0 and the Hard Fork (2.3) on November 30, 2026 at 9 a.m. Korean Time

· News

#HardFork

When is the SASEUL hard fork (2.3)?

Update to version 2.3.0.0 before 9 a.m. Korean time on November 30, 2026

November 20, 2026

Notice #88, node program version 2.3.0.0 released

November 30, 2026, 9 a.m. (Korea)

Hard fork (2.3), 00:00 UTC on November 30, 2026

After that

Notice: nodes on the old version can't keep up with the network

Based on official SASEUL Telegram notice #88 (November 20, 2026). Time runs from left to right, and the darker box is the hard fork date.

On November 20, 2026, notice #88 appeared on the official SASEUL Telegram notice channel. It says node program version 2.3.0.0 is out and that this version includes a hard fork. The hard fork is set for 00:00 UTC on November 30, 2026. In Korean time that is 9 a.m. the same day. The original notice is in English.

What is the news? One rule changes, and the mining program gets faster

A hard fork is a day when every node switches to the new rules together. The notice lists four changes this time.

  1. The rule for how blocks come out. It was changed so that blocks (one page of the ledger) keep coming out steadily even when the number of mining computers goes up and down. This is the part the hard fork changes.
  2. The graphics card mining program is about 100% faster. That is a figure the notice measured on an RTX 4090 graphics card. The notice doesn't say the SL you receive grows by the same amount.
  3. Block syncing and fork recovery got better. That means matching the ledger, and getting back after landing on a wrong branch.
  4. A PHP security measure was added.

Here is what it means for whom.

This post is one of the posts collected on the hard fork page.

When is it? 00:00 UTC on November 30, 2026, which is 9 a.m. Korean time

Time zone Hard fork (2.3) time
UTC (world standard time) November 30, 2026, 00:00
Korean time Monday, November 30, 2026, 9 a.m.

The notice is dated November 20, 2026. What a hard fork is and how the last one went are in the post explaining the hard fork (2.3).

Who does what? People who run a node or mine are the target

Here is what the notice asks. "Please update your node before the hard fork. After that, nodes on the previous version can't keep up with the network, and blocks mined on the previous version won't be accepted. If you mine, please update ahead of time."

Who What the notice and Docker Hub say
People who only hold coins The notice doesn't list anything to do
People who run their own node Move to version 2.3.0.0 before 00:00 UTC on November 30, 2026
People who mine with a graphics card on their own node Same as above, and pick the Docker image that matches your driver number
People who only run a mining program in a pool The notice doesn't mention pools, so I don't know. More on this below

What about pool miners? I couldn't confirm

The notice only said "if you mine, please update ahead of time." It didn't say whether the pool's mining program (miner.exe) also has to be updated. On November 20, 2026, I opened the front page of the pool site and didn't find anything about 2.3.0.0 or the hard fork. I couldn't confirm whether the pool will update or when. It's worth watching the pool site and the notice channel for new announcements over the next few days.

Running your own node? Pick the Docker image that matches your driver

For people who run a node with Docker (a way of running a program packed in a box), the notice listed three images (boxes).

Image name (tag) When to use it
latest For graphics card mining. NVIDIA driver 580 or newer (CUDA 13)
2.3.0.0-cuda12.2.2 For graphics card mining when your driver is older. 535 or newer
lite For running only a node, with no graphics card mining

The "Update" section of the Docker Hub page says to update before November 30, 2026, and lists the commands in order. The same page says the arm64 image is still version 2.2.0.3 and hasn't been updated to 2.3.0.0 (checked November 20, 2026). For how to update, the Docker Hub page is the reference.

Update commands on Docker Hub (the "Update" section of the page the notice points to)

This is for the case where you've mounted the data folder (/var/saseul-data). What follows is copied from the Hub page as written.

sudo docker stop saseul-node
sudo docker rm saseul-node

If you only run a node, pull it like this.

sudo docker pull artifriends/saseul-network:lite
sudo docker run -d --init --name saseul-node -p 80:80 -v /var/saseul-data:/var/saseul/saseul-network/data --entrypoint /bin/saseul-init artifriends/saseul-network:lite

For graphics card mining (latest), put latest where lite is and add --gpus all. If your driver is older than 580, use 2.3.0.0-cuda12.2.2. The Hub page has one line for each of the three.

After pulling, install and start with these two lines.

sudo docker exec -it saseul-node saseul-install
sudo docker exec -it saseul-node saseul-script start

The Hub page also has a separate note about fixing permissions after the update, only for people coming from version 2.2.0.2. If that's you, read that part of the page after you finish updating. I haven't run these commands myself.

What changes? The mining program gets faster, and syncing and security were improved

I put what the notice says is in 2.3.0.0 into a "before / now" table. Where the notice doesn't describe how things were before, the table says so.

Item Before Now (the notice's wording)
Rule for how blocks come out The notice doesn't describe how it was before Improved so blocks come out steadily even when the mining computers' power swings (the part that changes with the hard fork)
Graphics card mining program Versions before 2.3.0.0 About 100% faster. The notice says it measured this on an RTX 4090 graphics card
Block syncing and fork recovery The notice doesn't describe how it was before Matching the ledger, and getting back after landing on a wrong branch, got better
PHP The security issue explained in the earlier notice #86 PHP 8.5.13 is in the Docker image, and the notice says a measure was also taken so the node isn't affected by new PHP vulnerabilities that come out later

Being about 100% faster is a statement about the mining program's speed. The notice doesn't say how the SL you receive changes. It also doesn't mean every graphics card gets the same figure.

If you use PHP yourself, the numbers changed

This follows the PHP security update notice (notice #86). If you installed PHP (a program widely used for web servers) yourself to run SASEUL, it needs to be at least the number in this notice.

PHP you use Number in notice #88 (For reference) number in notice #86
8.2 8.2.36 or newer 8.2.35 or newer
8.3 8.3.37 or newer 8.3.36 or newer
8.4 8.4.28 or newer 8.4.27 or newer
8.5 8.5.13 or newer 8.5.12 or newer

Each number went up by one step. The notice doesn't say why. If you use the Docker image, PHP is already inside it, so you don't have to update PHP separately.

Questions people often ask

When is the hard fork (2.3)? 00:00 UTC on November 30, 2026, which is 9 a.m. Korean time. The notice is dated November 20, 2026.

Where do I have to move my coins? The notice never says to move coins. If a message uses the hard fork as an excuse to tell you to move coins, or asks for your recovery words or private key, first open the official notice channel above and check whether it says the same thing.

What happens if I miss that time? The notice says nodes on the previous version can't keep up with the network, and blocks mined on the previous version won't be accepted. It doesn't say what happens if you update afterward. So updating before the time is the way the notice describes.

Which driver do I have? If your NVIDIA driver number is 580 or newer, use latest. If it's 535 or newer but below 580, use 2.3.0.0-cuda12.2.2. If you don't mine with a graphics card and only run a node, use lite.

Sources


I hold SL. I checked the notice against the original on the official SASEUL Telegram, and the update steps against the Docker Hub page, on November 20, 2026.

Questions after reading this

Leave a question you want answered. Useful ones are added to this post with an answer. Please do not include your name, contact details, wallet address or recovery phrase.