SUNFLOWER
  • Introduction
    • What is Sunflower?
    • Mission & Vision
    • Key Features
  • Getting Started
    • System Requirements
    • Installation Guide
    • Creating an Account
    • Setting up a Node
  • User Guide
    • Dashboard Overview
    • Sharing Bandwidth
    • Monitoring Earnings
    • Token Management
    • Participating in Governance
  • Architecture
    • Overview
    • User Layer
    • Client Layer
    • P2P Network Layer
    • Consensus & Mining
    • Smart Contract & Governance Layer
    • Application & Data Consumption Layer
  • Tokenomics
    • Token Distribution Model
    • Mining Rewards & Incentives
    • Use Cases
    • Inflation & Deflation Strategies
  • Sunflower Data
    • Sunflower Architecture
      • Client Layer
      • RPC/Aggregator Nodes
      • Validator
      • Router
      • Sunflower Nodes
      • Public Web Servers
      • ZK Processor / PoB Aggregator
      • Sunflower Data Ledger
      • L1 Settlement Layer (Optional)
      • AI / Edge Features (Optional)
    • Data Flow Overview
      • Step-by-Step Data Flow
      • Data Flow Diagram
      • Key Features and Professional Highlights
  • Security
    • Security Measures
    • Privacy Protection
    • Smart Contract Audits
  • Roadmap
    • Phase 1: Foundation Building
    • Phase 2: Test Iteration & Audits
    • Phase 3: Mainnet Launch
    • Phase 4: Ecosystem Expansion
    • Phase 5: Decentralized Governance
  • FAQ
    • General Questions
    • Technical Questions
    • Mining and Rewards
    • Token & Transactions
    • Security & Privacy
    • Support & Community
    • Future Development
  • Contributing
    • How to Contribute
    • Development Guidelines
    • Reporting Issues
Powered by GitBook
On this page
  1. Sunflower Data
  2. Sunflower Architecture

RPC/Aggregator Nodes

Functionality:

  • Request Handling: Acts as intermediaries between clients and the core network.

  • Data Aggregation: Collects and processes requests from multiple clients.

  • Load Balancing: Distributes network load efficiently to prevent bottlenecks.

Workflow:

  1. Receive Requests: Aggregator nodes receive bandwidth sharing or service requests from clients.

  2. Forward Requests: These requests are forwarded to validators or routers for further processing.

  3. Respond to Clients: Aggregator nodes relay responses back to clients, including mining rewards and service confirmations.

Diagram:

css

[RPC/Aggregator Node]
 ├─> Receive Client Requests
 ├─> Forward to Validator/Router
 └─> Send Responses to Clients
PreviousClient LayerNextValidator

Last updated 3 months ago