Fizz Node, Migration to Spheron Testnet Chain, CLI & Provider Updates

Fizz Node (Spheron Light Node)

We’re excited to introduce Fizz Nodes, a lightweight version of our Provider Nodes, designed to scale our decentralized compute infrastructure. Fizz Nodes enable anyone with a smaller device, such as a laptop or a small server, to participate in the Spheron network. Here’s what you need to know:

Key Features of Fizz Nodes:

  • Lightweight Participation: Fizz Nodes are ideal for individuals who want to contribute to the network using underutilized compute resources.

  • Subnet Formation: Multiple Fizz Nodes can connect to a single Provider Node, forming subnets that can develop their own economy, self-govern, and earn rewards.

  • Decentralized Economy: Each subnet contributes to the overall dynamism and scalability of the Spheron Protocol by participating in a decentralized economy.

Components:

  • Fizz Client: A software run by individuals on small devices to offer compute resources for monetary rewards.

  • Gateway Service: Managed by providers, this service facilitates communication between users and Fizz Nodes.

How to Set Up Your Fizz Node:

  • Visit fizz.spheron.network: Explore the leaderboard of Fizz Nodes and click on “Register New Fizz Node.”

  • Registration: Enter your node’s name, select your OS (currently supporting MAC and Linux), choose the node type (GPU or CPU), configure resources (CPU units, RAM, storage), select your region, choose accepted payment tokens, and select a Provider based on region and trust tier. Then, click “Register your Fizz Node.”

  • Installation: Download the installation script (fizzup.sh) from the Installation page and run it using sh <script_path>/fizzup.sh. Click “Check Status” to verify the installation.

  • Dashboard Access: After successful installation, you will be redirected to your dashboard, where you can monitor your node’s details and rewards. To check logs, use the command: docker compose -f ~/.spheron/fizz/docker-compose.yml logs -f.

This release marks a significant milestone in expanding the Spheron Protocol’s scalability and inclusivity. We encourage all users to participate and contribute to the decentralized compute ecosystem by setting up their own Fizz Nodes.

Migration to Spheron Testnet Chain

We are pleased to announce the successful migration of our platform from Arbitrum Sepolia to our own Spheron Testnet (L3) Chain. This transition includes the movement of all chain operations from Arbitrum Sepolia to the new Testnet (L3) chain.

Key Updates:

  • Migration to Spheron Testnet: All contracts, providers, and chain operations have been fully migrated to the new Spheron L3 Testnet chain. This change enhances the network’s performance, scalability, and security.

  • Token Bridge: To facilitate the transition, we’ve created a bridge that allows you to transfer your existing Sepolia test tokens to the Spheron Testnet chain.

How to Transfer Tokens:

To transfer your Arbitrum Sepolia test tokens to the Spheron Testnet chain, please use the following bridge link: Spheron Testnet Bridge.

Get Test Tokens:

If you need test tokens on the Spheron L3 Testnet, you can get them using our faucet: Spheron Faucet.

This migration marks a new era for Spheron, providing greater control and scalability for our network while ensuring a seamless experience for our users and providers.

Provider & CLI Updates

We’ve rolled out an update to our CLI that introduces support for Deployment Mode. This feature allows you to specify whether to deploy in Provider Mode or Fizz Mode within the ICL YAML file under profiles.

Key Features:

  • Deployment Mode Selection: You can now choose between Provider Mode and Fizz Mode based on your specific needs regarding resources, stability, and cost.

  • Flexibility: This update gives you greater control over your deployments, allowing you to optimize for different factors depending on your project’s requirements.

How to Upgrade:

To upgrade to the latest CLI version, run the following command:

curl -sL1 https://sphnctl.sh | bash

For more details on configuring the Deployment Mode, please visit our documentation.