dVPN Service Provider

Through this panel, the provider can review and manage requests submitted by node owners who want to become dVPN-node operators. Each request can either be approved or rejected based on the validation of the details provided. In addition, the provider can create and configure new service plans, setting the pricing for hosting nodes and the bandwidth that end users can later purchase to access the dVPN. The panel also provides visibility into the network by displaying a list of all active and inactive nodes, enabling administrators to monitor and manage the overall health of the Qubetics dVPN infrastructure.

Connect Wallet

To access the Qubetics Service Provider Panel, the provider must first connect their Cosmos-compatible wallet (such as keplr). This step is required to verify their identity and grant secure access to the platform. Once the wallet connection is established, the provider can manage all core functions.

Registration Process

To become a service provider, you must stake 1000 TICS using the same wallet you’ll use to register in the Qubetics dVPN. Before you start, make sure you’re connected to the correct Keplr wallet. The wallet you connect will be used to verify your identity, register your node, and process all blockchain transactions. If you connect the wrong wallet, your registration may fail, or your ownership can’t be verified.

To register as a service provider on Qubetics, click Become Service Provider on the home page. You’ll be taken to the Service Provider panel there, and click Connect Keplr Wallet. If this is your first time, fill in the required details. Before you begin, make sure you’ve met all the prerequisites for becoming a service provider.

Module	Description
Name	Enter a display name for your service provider profile. This helps node operators find and choose you when leasing their nodes in the Qubetics dVPN.
Email Address	Enter your email. Qubetics will use this to send important updates and notifications related to your service provider account.
Website URL	You can add your organization’s website link. This information is stored on-chain.
Submit Button	After filling in all required fields, the “Submit” button will become active. Click it to complete your service provider registration.

Dashboard

Navbar	The navbar shows the service provider’s balance and wallet address from their Keplr wallet. It also has a logout option. Clicking logout will sign the service provider out of the panel, disconnect the wallet, and redirect them back to the service provider panel landing page.
All Nodes	Shows the total number of nodes irrespective of their status (e.g., 60).
Active Nodes	Shows the total number of active nodes currently connected and providing service (e.g., 50).
Inactive Nodes	Shows the total number of inactive nodes currently not connected and providing service (e.g., 10).
Node Request Table	This section lists all incoming requests from users who want to operate or manage dVPN nodes. Each row in the table represents a single request, containing details of the request.
Operator Name	The operator name associated with the node (e.g., Mysterium, Qubetics-1).
Email Address	The email ID of the requester, used for communication and approval status updates (e.g., [e-mail]).
Location	The country from where the node is being deployed (e.g., India, China).
Node Address	The unique node address generated when the user ran the setup script (e.g., qubeticsnode1...cyr1239wc).
Bandwidth	The bandwidth allocated for this node (e.g., 100 GB, 1TB).
Plan	The pricing plan selected by the user while registering shows the cost in TICS tokens (e.g., 1000 TICS/month).
Request Type	Indicates the type of request made: Link Node: Request to connect a new node to the Qubetics ecosystem. Unlink Node: Request to disconnect an existing node.
Action	Each request has two action buttons for the provider: Approve: Confirms the request, allowing the user to link or unlink their node based on their request type. Reject: Denies the request, preventing changes to the node status.

Plan List

The Plans Page allows the provider to manage the pricing and bandwidth packages that node service providers can offer to end users. Each plan defines the price, data allocation, and usage period, ensuring transparency and consistency across the dVPN ecosystem.

Create Plan Button	Located on the top-right corner, the “Create Plan” button allows the provider to set up new subscription packages.
Plan ID	A unique identifier for each plan (e.g., PI1209).
Price	The cost of the plan, charged monthly in TICS tokens (e.g., 1000 TICS/month).
Bytes	The data bandwidth-wise price assigned to the plan (e.g., 1000 MB).
Creation Date	The exact date and time when the plan was created (e.g., 2024-09-28 04:14 am).
Duration	The usage validity period (e.g., 24 hours).
Action	Activate: This button allows the provider to activate a plan so that it becomes available for node operators and end users. Activated: This status shows that the plan is already active and cannot be reactivated.

Create Plan

The Create Plan form allows the provider to set up new subscription packages for dVPN node service providers and end users. Each plan defines the cost, data allocation, and validity period of the service.

Plan Price	The first field in the form is Plan Price, where the provider enters the cost of the plan in TICS tokens. This value determines how much a user will need to pay in order to access the plan. For example, a provider might set the plan price as 1000 TICS/month depending on the bandwidth and duration being offered.
Plan GB	The provider specifies the Plan GB, which defines the amount of data included in the plan. This value is entered in gigabytes (GB), although it can also be set as megabytes (MB) if required. For example, the provider might enter 10 GB or 1000 MB to represent the bandwidth allowance that end users can consume under this plan.
Validity (Hours)	Allows the provider to set the duration for which the plan will remain active once purchased. This value is entered in hours, giving the provider the flexibility to create short-term or long-term plans. For instance, entering 24 hours would make the plan valid for one day, while entering 720 hours would make it valid for 30 days.
Create Button	The provider completes the process by clicking the Create button. Once clicked, the system validates all inputs. If the details are correct, the new plan is added to the Plans List and becomes available for node providers and end users. Once submitted, a success pop-up will appear.

Node List

The Node List page provides the provider with a complete overview of all nodes operating within the Qubetics dVPN ecosystem. From here, the provider can track node activity and check their operational status.

Node Filters	At the top of the Node List, providers can toggle between three categories: All Nodes: Displays every node in the ecosystem, regardless of status. Active Nodes: Shows only active nodes that are currently connected and providing service. Inactive Nodes: Shows only inactive nodes that are disconnected or offline. This filtering helps providers quickly focus on the nodes they need to monitor.
Node List Table (All Tab)	The main table displays detailed information about each node in the ecosystem. Each row represents a node and includes the following fields: Operator Name: The operator’s name that owns or runs the node (e.g., Shinobi). Node Address: The unique blockchain address associated with the node (e.g., 0x47685…4c8B145). A copy icon is provided to copy the node address easily. Node Status: Indicates whether the node is currently active (green) or inactive (red). Request Type: Shows the latest request action associated with the node, such as: Request Status: Shows the status of the node, whether it’s linked/unlinked, approved by the service provider, or rejected from joining the provider’s ecosystem.
Node Monitoring	The Status column is especially important for network health monitoring. Active nodes are currently online, passing bandwidth, and available for end users. Inactive nodes are offline, disconnected, or awaiting validation. The provider can use this view to identify and troubleshoot inactive nodes quickly.