It is time: Cryptix Atomic is coming on DAA 33,739,200.

The official DAA for the hardfork has now been announced, and a new page has been added to the website with a countdown, exact date, and time information.

https://cryptix-network.org/cryptix-atomic-hardfork

You must replace your Go nodes and Rust nodes within the next few days, before the hardfork.

Hardfork Upgrades:

Messenger
Encrypted L1-native group chats, token group chats, group tipping and token airdrops.

Free Payloads
Transactions can carry payload data, currently up to 2 KB, with miner fees paid per byte.

Simple Data
Transactions can include plain subject, invoice or reference data. Not encrypted.

Atomic Tokens
Native L1 tokens can be created from the Web Wallet or CLI without smart contracts.

Atomic Swaps
Native token swaps against CPAY become available, optionally with Lock Gate support.

Header Sync
L1 data can be synced without external indexers for connected off-chain systems.

Autoban
Nodes can ban malicious behavior such as reconnect spam, dust attacks and DDoS patterns.

Strong Node ID
PoW-based node identity, signed block forwarding and stronger visibility of block finders.

Quantum-Safe Handshakes
Node handshakes and connections move to ML-KEM-1024.

Maintenance:
This release also fixes an IBD resume case where a node already at the peer's pruning point could abort instead of continuing normal header/body sync.

This update introduces the HFA feature as the first step in Cryptix Fastchain technology. HFA is a fast system for transaction visibility.

Read more:
https://cryptix-network.org/hfa-fastchain-technology

The update is not mandatory — existing nodes will continue to function as before, including the Go node.
The system is currently adaptive and optional, and everything remains fully backward compatible.

However, I strongly recommend enabling and using HFA.

HFA

To activate the feature, simply download the new node version (Rust) and start it with the following arguments:

--hfa
Enables the HFA fast rail for this process (this alone is sufficient)

Optional:

--hfa-cpu=
Sets the CPU low-water ratio for HFA (0.0 < value <= 1.0)
Example: --hfa-cpu=0.9
--hfa-microblock-interval-ms-normal=
Defines the HFA microblock interval in milliseconds while operating in normal mode
Default: 50

You can also explicitly disable it if needed:

--no-hfa
Forces HFA to be disabled (overrides config)
Datacenter Mode

There is also a new startup argument to prevent false-positive alerts in datacenter or hosting environments (e.g. due to port scanning):

--datacenter