Skip to navigation Skip to main content
  • Home
  • Price
  • Docs
  • Learn
  • Contact us

Technical & Architecture

19
  • Control vs. Data Plane Architecture: Decoupling Web Dashboard from Client Engine
  • Client Core Architecture: TUN Interface & Split Tunneling Specs
  • Webhook Event Pipeline for Automation & Billing Platforms
  • BEX Reseller REST API Specification & OAuth Authentication
  • Automated Top-Up Market & Crypto Instant Settlement Architecture
  • Sub-Reseller Hierarchy & Multi-Tier Credit Allocation Engine
  • Tokenized Bandwidth Economics & Balance Solvency Architecture
  • Edge Rate-Limiting & Traffic Anti-Abuse Architecture
  • Ā Zero-Log Edge Telemetry & Real-Time Gateway Health Monitoring
  • Cryptographic Key Exchange & DNS/IPv6 Leak Prevention
  • Zero-Log Pipeline & RAM-Only Server Operating Environment
  • BEX Global Routing Infrastructure & Gateway Node Distribution
  • Shared Bandwidth Pools & Multi-Device Volume Allocation in Gigify
  • Ā Cumulative Quota Engine & Validity Rollover Protocol
  • Gigify Real-Time Metering Engine & Per-GB Bandwidth Accounting
  • Priority Routing & Dedicated Gateway Bandwidth Allocation
  • Concurrent Device Handshake & Hardware ID Allocation
  • Premiume Subscription Lifecycle & Fixed Timeframe Engine
  • Active vs. Inactive Session Detection Protocols

Legal & Transparency

8
  • Refund Eligibility & Balance Adjustment Terms
  • Cryptocurrency Billing & Wallet Top-Up Terms
  • Sub-Reseller Hierarchy Regulations & Compliance Guidelines
  • Reseller Partner Agreement & Token Ownership Rules
  • Service Availability & SLA Commitments
  • End User Lisense Agreement (EULA) & Acceptable Use Policy
  • RAM-Only Processing & Non-Retention Policy Specs
  • BEX Strict Zero-Logs Privacy Policy & Data Handling Specifications

Frequently Asked Questions

16
  • What should I do if I experience connection timeouts or speed degradation?
  • What encryption algorithms and routing protocols are implemented?
  • How does BEX prevent DNS, WebRTC, and IPv6 leaks?
  • Does BEX VPN log my browsing activity, IP address, or traffic data?
  • Can I integrate BEX services with Telegram bots or custom WHMCS platforms?
  • How does instant settlement work in the automated Top-Up market?
  • How do I configure Sub-Reseller accounts and commission tiers?
  • How do bandwidth tokens work in the BEX Reseller ecosystem?
  • What cryptocurrency payment methods are accepted for top-ups?
  • Does unused bandwidth expire in Gigify plans?
  • How is bandwidth usage calculated and tracked in Premium and Gigify plans?
  • What is the difference between Premium and Gigify plans?
  • Can I use my account across multiple devices simultaneously?
  • How do I create and secure my BEX account?
  • Do I connect to the network from the web dashboard or the client app?
  • What is BEX VPN and how does it differ from traditional VPNs?
  • Home
  • Docs
  • Technical & Architecture
  • Sub-Reseller Hierarchy & Multi-Tier Credit Allocation Engine
View Categories

Sub-Reseller Hierarchy & Multi-Tier Credit Allocation Engine

1 min read

1. Overview & Architectural Purpose #

The BEX Sub-Reseller Hierarchy & Multi-Tier Credit Allocation Engine provides a recursive, highly scalable framework for multi-level bandwidth distribution. Built to support complex B2B distribution networks, this architecture enables master distributors to spawn sub-resellers, partition bandwidth token pools, enforce permission scopes, and manage downline accounts dynamically. The system ensures that credit transfers down the distribution tree remain mathematically isolated, audited, and cryptographically verified in real time.

2. Multi-Tier Tree Topology & Role-Based Access Control (RBAC) #

BEX structures reseller networks using a Directed Acyclic Graph (DAG) tree model that supports N-tier organizational depth without performance degradation:

  • Recursive Parent-Child Nodes: Every reseller node operates as an independent administrative entity with explicit scope over its direct children while remaining bound to parent-defined allocation ceilings.
  • Fine-Grained Scoped RBAC: Administrative capabilities (e.g., account creation, credit issuing, session revocation, user quota editing) are governed by inherited role policies that restrict child entities from exceeding parent privilege boundaries.
  • Organizational Branch Isolation: Sub-resellers are strictly sandboxed within their own organizational sub-tree, preventing horizontal data exposure or visibility into sibling or competitor distributor branches.

3. Real-Time Credit Allocation & Sub-Pool Partitioning #

The credit allocation engine manages bandwidth token movement across hierarchical tiers using atomic reservation mechanics:

  • Sub-Pool Partitioning: Master distributors can allocate dedicated credit pools to sub-resellers from their main ledger balance, setting hard quotas, expiration dates, or floating credit limits.
  • Instant Dynamic Reclamation (Clawback): Parent resellers retain cryptographic administrative rights to reclaim unused or idle credit allocations from non-performing sub-reseller pools back into the parent master balance instantly.
  • Cascading Credit Validation: When an end-user initiates a network session, the authorization system validates the credit path up the parent chain to ensure solvency at every tier before granting edge gateway access.

4. Atomic Ledger Transactions & Fraud Prevention #

  • ACID-Compliant Ledger Transfers: All token movements between parent and child accounts are processed as atomic ledger transactions. Credit transfers either succeed entirely across all database shards or rollback completely to prevent balance inflation.
  • Cryptographic Transaction Signatures: Transfers generate immutable audit records signed with system keys, creating an unalterable trail of credit provenance.
  • Hierarchical Fraud Containment: If a sub-reseller exhibits fraudulent activity or security compromise, the parent or system administrator can execute a single-command branch freeze, instantly suspending all downstream sub-accounts and reclaiming remaining token balances.

5. Key Strategic Benefits #

  • Infinite Organizational Scalability: Supports multi-tiered global distribution networks with zero degradation in authorization speed.
  • Complete Administrative Autonomy: Empowers distributors to manage their own sub-reseller networks without requiring manual intervention from BEX platform administrators.
  • Zero-Deficit Financial Integrity: Guaranteed mathematical alignment across master pools, sub-pools, and end-user session consumption.
Still stuck? How can we help?

How can we help?

Updated on October 4, 2026
Automated Top-Up Market & Crypto Instant Settlement ArchitectureTokenized Bandwidth Economics & Balance Solvency Architecture

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Table of Contents
  • 1. Overview & Architectural Purpose
  • 2. Multi-Tier Tree Topology & Role-Based Access Control (RBAC)
  • 3. Real-Time Credit Allocation & Sub-Pool Partitioning
  • 4. Atomic Ledger Transactions & Fraud Prevention
  • 5. Key Strategic Benefits
Based on WoodMart theme© 2026 WooCommerce Themes.
payments
Close
  • Home
  • Price
  • Docs
  • Learn
  • Contact us
  • Languages
    • You need WPML plugin for this to work. You can remove it from Header builder.
Shop