> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fene.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Node Operators Overview

> Run and operate Fenine Network infrastructure

## Introduction

Fenine Network provides infrastructure options for organizations and developers who want to run their own nodes. Unlike traditional blockchain networks, Fenine operates with a **contract-layer validator system**, meaning validators are managed through smart contracts rather than requiring node operators to run validator software.

<Info>
  **Network Info**:

  * Chain ID: 89
  * Block Time: 3 seconds
  * Consensus: Fenine PoA (Proof-of-Authority)
  * EVM Compatible: Yes (London hardfork)
</Info>

## Node Types

Fenine offers three types of node infrastructure:

<CardGroup cols={3}>
  <Card title="Non-Validator Nodes" icon="database">
    Monitor network status and serve RPC requests
  </Card>

  <Card title="RPC Providers" icon="cloud">
    Professionally hosted endpoints with enterprise features
  </Card>

  <Card title="Private Nodes" icon="building">
    Closed enterprise nodes for private application integration
  </Card>
</CardGroup>

### 1. Non-Validator Nodes

**Purpose**: Infrastructure for monitoring network status and serving RPC requests to applications.

**Use Cases**:

* dApp backend infrastructure
* Development and testing environments
* Network monitoring and analytics
* Block explorer backends
* Independent data verification

**Key Features**:

* Full blockchain synchronization
* RPC endpoint for Web3 applications
* WebSocket support for real-time events
* Archive mode for historical queries
* No staking requirement

<Check>
  ✅ **Perfect for**: Developers, dApps, explorers, analytics platforms
</Check>

### 2. RPC Providers

**Purpose**: Professionally hosted RPC endpoints with enterprise-grade features.

**Use Cases**:

* Production dApp infrastructure
* High-availability applications
* Multi-region deployments
* Load-balanced services
* SLA requirements

**Key Features**:

* 99.9% uptime SLA
* Global CDN distribution
* DDoS protection
* Rate limiting & analytics
* 24/7 technical support
* Custom endpoints

**Available Providers**:

* **Fenine Official RPC**: `https://rpc.fene.app`
* **Enterprise Plans**: Contact `enterprise@fene.network`

<Check>
  ✅ **Perfect for**: Production apps, enterprises, high-traffic dApps
</Check>

### 3. Private Nodes

**Purpose**: Closed enterprise infrastructure for private application integration on Fenine Network.

**Use Cases**:

* Enterprise blockchain integration
* Regulated industry compliance
* Private transaction relay
* Internal monitoring systems
* Custom business logic

**Key Features**:

* Dedicated infrastructure
* Private RPC endpoints
* Custom firewall rules
* VPN integration
* Compliance support
* White-glove onboarding

**Requirements**:

* Enterprise agreement
* Minimum infrastructure commitment
* Security audit compliance
* Technical operations team

<Check>
  ✅ **Perfect for**: Financial institutions, regulated businesses, large enterprises
</Check>

## Validator System

<Warning>
  **Important**: Fenine uses **contract-layer validators**, not node-layer validators.

  Validators are managed entirely through the FenineSystem smart contract. To become a validator:

  1. Stake 10,000 FEN tokens via smart contract
  2. Register validator parameters on-chain
  3. The protocol automatically includes you in block production

  **You do NOT need to run special validator node software.** Block signing happens through the consensus layer independently of node operation.
</Warning>

For validator information, see:

* [FPoS Protocol Documentation](/architecture/fpos)
* [Validator Staking Guide](/guides/staking)
* [FenineSystem Contract Reference](/api-reference/contracts/fenine-system)

## Getting Started

Choose your path based on your needs:

<CardGroup cols={2}>
  <Card title="Non-Validator Node Setup" icon="gear" href="/node-operators/non-validator-setup">
    Set up your own RPC node
  </Card>

  <Card title="Hardware Requirements" icon="microchip" href="/node-operators/hardware-requirements">
    System specifications and recommendations
  </Card>

  <Card title="RPC Provider Options" icon="cloud" href="/node-operators/rpc-providers">
    Choose a hosted RPC service
  </Card>

  <Card title="Enterprise Solutions" icon="building" href="mailto:enterprise@fene.network">
    Contact us for private nodes
  </Card>
</CardGroup>

## Support & Resources

<CardGroup cols={3}>
  <Card title="Discord Support" icon="discord" href="https://discord.gg/fenines">
    \#node-operators channel
  </Card>

  <Card title="GitHub" icon="github" href="https://github.com/fenines-network/fene-geth">
    Source code and releases
  </Card>

  <Card title="Network Stats" icon="gauge" href="https://stats.fene.app">
    Real-time metrics
  </Card>
</CardGroup>

<Note>
  **Node Operators Support**:

  * Discord: #node-operators
  * Email: [operators@fene.network](mailto:operators@fene.network)
  * Office Hours: Thursdays 3PM UTC
</Note>