dVPN Node & Provider Earnings System

Current Model

In the current architecture, Qubetics operates as one provider among many. Any individual or organization can register as a provider within the Qubetics system by allocating 20,000 TICS. Once registered, a provider is responsible for creating subscription plans, leasing nodes, and managing how nodes are assigned to and serve those subscription plans.

When an individual or organization hosts a node server, they interact with the Node Panel, a management interface provided by Qubetics. Once the node is verified and active, the node operator selected the provider to which the node they have linked. The selected provider then assigns the node to one of its available subscription plans.

Note: A provider can be any participant in the network. If a node operator is also registered as a provider, they may link their own node to the subscription plan they have created and manage it directly.

The revenue-sharing model is as follows among Users, Providers, Node Operators, and Validators across the three related flows in the system:

Subscriptions and Leases:

• Earnings are distributed among Qubetics (the protocol provider), Validators, and Node Operators (the entities running the infrastructure and providing secure tunneling and decentralized routing services). The Node Operators use these earnings to maintain the infrastructure, manage plans, and ensure network reliability.

• Subscription Flow (User → Provider + Validators)

  • User subscribes to a plan.

  • The total subscription price is split between the provider and the validator.

  • 10% → staking rewards via fee collector (Validators)

  • 90% → Provider account .

  • The user receives a data/time allocation tracked under their subscription.

Notes: Subscription payment does not pay Node Operators. It compensates the Provider and Validators.

• Subscription-Based Sessions and Leases

There are two distinct parts here:

1. Subscription Session (User uses allocation)

   1. User starts a session tied to their subscription.

   2. No new payment is taken at session start; allocation usage is tracked.

   3. This path does not pay the Node Operator directly.

2. Lease Flow (Provider → Node Operator + Validators)

   1. Providers compensate Node Operators for serving subscription users by leasing nodes.

   2. At lease start, Provider deposits MaxHours × hourly_price (one-time upfront) into the deposit module.

   3. Every hour while active, a payout occurs from the Provider’s deposit:

      1. 10% → fee collector (Validators)

      2. 90% → Node Operator account.

      3. If the node becomes inactive or the lease ends early, remaining prepaid hours are refunded to the Provider.

Summary by Role

User Subscription: Pays Provider (90%) + Validators (10%); receives allocation.

Provider

• Earns 90% of subscription price.

• Leases nodes to serve subscribers; funds are deposited upfront and paid to nodes hourly (90% to the nodes, 10% to the validators).

Node Operator

• Earns from Provider Leases (time-based hourly payouts, 90%).

Validators

• Earn 10% staking share from all two revenue events: subscription payment, lease payouts.

Currently, nodes added to time-based subscription plans are compensated on a monthly flat-rate basis, providing predictable and stable income for node operators.

Detailed Explaination about the Multi-Provider Subscription & Lease Model

It explains how Node Operators earn revenue in the multi-provider dVPN ecosystem on the Qubetics.

Network Roles and Required Allocations

Provider Registration (20,000 TICS)

Any participant can register as a Provider by allocating 20,000 TICS. This allocation is not staked, does not earn staking rewards, and is transferred to the Community Pool. Once registered, a Provider is responsible for creating and managing subscription plans, leasing nodes to serve subscribers, and managing user allocations associated with those plans.

Node Registration (10,000 TICS)

Each dVPN node requires a 10,000 TICS allocation for registration on Qubetics. This allocation is not staked, does not generate staking rewards, and is transferred to the Community Pool. The purpose of this requirement is to enforce economic commitment from node operators and to support long-term network sustainability.

Note: Node Operators do not earn rewards from token allocation. Earnings come only from providing node uptime.

Revenue Flows Relevant to Node Operators

Node Operators earn exclusively from the Provider → Node Lease Flow.

Lease Flow (Provider → Node Operator + Validators)

1. A Provider selects a node and initiates a lease.

2. At lease start, the Provider deposits: MaxHours × Hourly Price (The hourly price is defined by the node operator. Currently, it is fixed at 1 TICS; however, in future updates, node operators will be given full flexibility to set their own hourly pricing) into the on-chain deposit module.

For every active hour:

1. 90% -> Node Operator

2. 10% -> Validators (via fee collector)

If the lease ends early or the node becomes inactive: Unused prepaid hours are refunded to the Provider

This model is time-based and predictable, with node operator earnings determined by lease duration rather than individual user activity. It operates independently of direct user payments, ensuring stable and consistent compensation for node operators.

Subscription Payments (For Context)

Users subscribe to Provider-defined plans. Subscription payment split:

• 90% -> Provider

• 10% -> Validators

Subscription payments do not pay Node Operators directly. Node Operators are compensated only through leases

For Example:

Monthly Node Operator Earnings Model

Nodes assigned to subscription-based plans are typically leased on a monthly flat-rate, derived from hourly pricing.

Variables

• H = Total active lease hours per month (≈ 720 hours for 30 days)

• Pₕ = Hourly lease price set by the Node Operator (Currently, the hourly price is fixed at 1 TICS; however, in an upcoming update, node operators will be granted the ability to set their own pricing)

• Node Operator share = 90%

Monthly Earnings Formula:

• Monthly Earnings = H × Pₕ × 0.9

Earnings by Time Period

Figures below are illustrative and assume continuous up time.

1) 30-Day Period

• Lease hours: ~720

• Gross lease value: 720 × Pₕ (for now Pₕ is 1 tics because node hourly price is 1 tics)

• Node Operator earnings: 720 × 1 × 0.9 = 648 TICS (Earnings)

• Reward source: Provider lease payouts

2) 60-Day Period

• Lease hours: ~1,440

• Gross lease value: 1,440 × Pₕ (for now Pₕ is 1 tics because node hourly price is 1 tics)

• Node Operator earnings: 1,440 × 1 × 0.9 = 1296 TICS (Earnings)

3) 90-Day Period

• Lease hours: 2,160

• Gross lease value: 2,160 × Pₕ (for now Pₕ is 1 tics because node hourly price is 1 tics)

• Node Operator earnings: 2,160 × 1 × 0.9 = 1944 TICS (Earnings)

Note: Node Operators on Qubetics earn predictable, time-based income by leasing dVPN node capacity to providers. Token allocations secure network participation but do not generate yield rewards come solely from the infrastructure and bandwidth they supply.

If the lease ends early or the node becomes inactive and node operator shut down the node before the lease period. Unused prepaid hours are refunded to the Provider wallet.