HX Softwares – Clarification Notice

1. Purpose of this notice

We are addressing the false and misleading claims made by Keyser regarding the sale and current state of HX Softwares. This notice sets out what was actually transferred, who is responsible for what, and how SERYX is separate from HX.

2. HX sale and the Tiger Mods agreement

The sale of HX was conducted transparently. All outstanding agreements – including the Tiger Mods reseller deal – were clearly disclosed and acknowledged prior to the transaction. These obligations were to be honoured by the new operators after the transfer.

After acquiring HX, Bakhaw chose to push for additional monetisation. Those decisions and their outcomes belong entirely to the new ownership. Screenshots and logs exist to support this timeline and can be produced if necessary.

3. Issues under current ownership

Since HX came under new ownership, multiple reports from the community have mentioned:

• Missing or undelivered licenses;
• Lack of service delivery after payment;
• Ongoing support failures and unanswered requests.

These are issues under the current operators. Shifting this responsibility back onto the former owner is inaccurate and misleading.

4. Reseller scam allegations

Claims that a reseller was scammed prior to the sale are categorically false. No fraudulent activity took place under our management. All reseller and partnership arrangements, including Tiger Mods, were communicated to Keyser before the sale was completed.

5. What Keyser actually received

Keyser received roughly 99% of the HX project. The only elements not transferred were:

• YouTube – retained, non‑critical to license or backend operation;
• Telegram – channel ownership is non‑transferable; admin permissions were granted but not accepted by the new operators (including for log‑related reasons);
• TikTok – linked to a personal account, therefore not technically transferable.

It also did not take two weeks to deliver assets. The effective delivery time was about three days. With 12‑hour workdays offline, instant responses are not always possible – but delivery was made within a reasonable timeframe.

6. Where SERYX stands

SERYX (seryx.gg) is a new and independent project. It is not HX, it does not use HX infrastructure, and it does not inherit HX‑related obligations. Any attempt to tie current HX operational issues to SERYX is incorrect.

7. Example reported case (evidence)

As one example of the problems occurring under the new ownership, a user reported purchasing an HX key and not receiving anything in return. This is after the project was under Keyser's control.

Screenshot of the report:
View screenshot evidence in a new tab

8. Final position

We stand by the facts above and remain open to professional, good‑faith resolution with anyone acting honestly. At the same time, we will not accept ongoing misrepresentation or attempts to rewrite what actually happened with HX.

This notice is provided for transparency and community clarity. It is not legal advice. For formal legal guidance, consult a qualified professional in your jurisdiction. On live deployment, this page may be configured to redirect users to the official SERYX platform at https://seryx.gg.