Skip to main content

Product updates

Apps​

20250922: 0G Alignment Node supported​

0G Alignment Node support added to NodeOps Console.

20250822: Telegram bot​

Push notifications added to Telegram bot.

20250820: Telegram bot​

We added new functions to the Telegram bot:

  • /mygNODE
  • /redeemnode
  • /myplans

20250721 UNO Node Orchestrators​

We made UNO Node Orchestrators available from the Cloud and Console apps.

20250818: Aethir staking​

We introduced Aethir staking on NodeOps Portal: 100 K gNode pool ends 4th October, 2025.

20250815: Portal as DeFi app​

NodeOps Staking Hub was sunsetted and all its functions supported from the Portal app.

20250810: LNT Vault for liquidity release​

NodeOps Console began support for LNT Vault.

20250723 Free Template​

A free template has been made available to allow users to experience how easy a deployment is at no cost.

20250625 gNODE withdrawl​

Users are able to redeem gNODE with a redemption period between 15 and 150 days.

20250623 Autorenewal​

Cloud deployments can now be set to autorenew.

20250623 Payment partner fee increase​

Copperx increased its fee to 2% on each transaction. Please consider adding credits to reduce the number of transactions needed.

20250524: Node delegation​

We introduced a Node Delegation feature accessible via the Console app, allowing users to delegate their Non-Fungible Tokens (NFTs) and allocate a portion of the commission to NodeOps. This eliminates the complexities of self-managing Nodes, offering a hassle-free experience.

20250414: Enhanced notification system​

To keep our users consistently informed, we implemented a comprehensive notification system. Users now receive in-app notifications directly on their console for various events, complementing our new Email Notification system that delivers timely updates straight to their inboxes.

20250303: Email notification system​

To keep our users consistently informed, we implemented an Email Notification system that delivers timely updates straight to their inboxes.

20250309: $NODE to credit conversion​

We've empowered users with greater financial flexibility through the $NODE to Credit Conversion** feature. This allows users to convert their $NODE tokens into USD credits, usable across the entire NodeOps platform ecosystem.

20250216: Auto-renewal feature​

To ensure uninterrupted service, we've introduced an Auto-renewal feature. When enabled, user-selected subscriptions will automatically renew, provided sufficient credits are available in their account.

Cloud​

Marketplace​

20250929 Correction​

Issues with example template definitions identified and corrected.

20250929: Gensyn Testnet Node supported​

Gensyn Testnet Node compatible with RL Swarm supported in Marketplace.

20250902 Gaia GPU​

Gaia GPU supported in Marketplace.

20250920: Free preview​

Template creators have free deployment tier for template testing.

Mainnet​

20250901 Machine status update​

  • Active
  • Inactive:
    • Pending
    • Inactive
  • Awaiting-Stake
  • Deleted:
    • Suspended
    • Draining
    • Deleted
    • Deleting

Linux Kernel minimum version update to 6.7+​

About​

We have updated the minimum required Linux kernel version to 6.7+ to address a USER_IDMAP related issue found in Debian’s 6.1 kernel version.

Why this change?​

In Debian releases with kernel version 6.1, a USER_IDMAP issue was discovered that could impact system functionality. Upgrading to kernel 6.7 or later resolves this issue.

Action required​

Users running older Linux kernel versions on Debian need to upgrade their kernel to maintain compatibility and avoid issues.

Upgrade steps for Debian​

To upgrade to kernel 6.7 or above on Debian (such as Debian bookworm), users can execute the following commands:

echo "deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware" >> /etc/apt/sources.list
sudo apt update
sudo apt install -t bookworm-backports linux-image-amd64

This enables backports in the sources list, updates package lists, and installs the latest Linux kernel image from backports.

Service log command update​

About​

As part of the migration from testnet to mainnet, the service name used for real-time log monitoring has changed. The journalctl command should now target the nn-provider service rather than the atlas service.

Old command​

Testnet:

journalctl -fu atlas*
New command​

Mainnet

journalctl -fu nn-provider*
Action required​

When monitoring logs on mainnet, use the new command.

Update any automation scripts, aliases, or documentation that still reference the old atlas* service name.

The old service naming will no longer receive logs once all Nodes have transitioned to Mainnet.

Why this change?​

The service name was updated to reflect the new Mainnet infrastructure and provider naming standards, ensuring consistency across deployments and monitoring tools.

Provider onboarding command update​

About​

We’ve updated the provider installation / upgrade command to point to our new Mainnet server. This change ensures you always fetch the latest verified installer script from the updated endpoint.

Old command​
curl -L https://get.atlasnetwork.dev | sh -s - ZxEsuA******************zAJ6
New command
curl -L https://serve-pre-mainnet.nodeops.network | sh -s - ZxEsuA******************zAJ6
Action required​

If you are installing a new provider or re-onboarding a machine, use the new command.

Why this change?​

We have migrated our distribution to a new infrastructure to improve delivery speed, reliability, and version traceability for pre-mainnet operations.

20250707: Testnet sunsetted​

Show me archive

0.0.1-13022025 Provider upgrade​

About​

This upgrade aims to enhance system stability and ability along with the latest runtime and dependency patches

Action required​

Re-run the command that you ran while onboarding the machine, which looks something like curl -L https://get.atlasnetwork.dev | sh -s - <SUPER SECRET STRING>

You can search for the command in your history by running the following.

history | grep -m1 'get.atlasnetwork'

Existing machines​

Open Terminal and run the following command, ensure you're root user by running sudo su

systemctl restart atlasnetwork-provider.service

0.0.1-03012025 Provider upgrade​

About​

This upgrade aims to enhance system stability and address previously identified connectivity issues affecting certain users. Providers anticipate temporary downtime during the upgrade process, which is anticipated.

Action required​

Existing machines​

Open Terminal and run the following command, make sure you're root user by running sudo su

systemctl restart atlasnetwork-provider.service