UPE Network Whitepaper

1. Abstract

UPE Network is an EVM-compatible blockchain ecosystem designed to support digital assets, NFTs, wallet connectivity, marketplace infrastructure, smart contracts and Web3 applications. The network uses the native UPE currency and provides public infrastructure through an official RPC endpoint and a public explorer.

The project is designed around practical blockchain utility: users can interact with the chain through wallets, developers can integrate RPC access, and applications can use UPE Network as a transparent blockchain layer for transactions, contracts and digital asset activity.

2. Vision & Purpose

The goal of UPE Network is to create a blockchain environment where digital infrastructure is simple, visible and accessible. UPE Network is intended to support practical blockchain use cases such as:

• Digital asset infrastructure.
• NFT deployment and verification.
• Smart contract execution.
• Marketplace and payment infrastructure.
• Wallet-based access to blockchain services.
• Transparent transaction history through the public explorer.

3. Network Specifications

4. Blockchain Architecture

UPE Network follows an Ethereum-style execution model, allowing wallets and applications that understand EVM networks to interact with the chain. The network is intended to support standard account addresses, JSON-RPC communication, smart contract deployment, transaction signing and explorer-based verification.

4.1 Core Components

• Validator Nodes: nodes responsible for block production and consensus participation.
• RPC Layer: public endpoint used by wallets, dApps, scripts and monitoring tools.
• Explorer Layer: Blockscout-based interface for blocks, transactions and addresses.
• Application Layer: products such as UPE Ecosystem, future marketplace tools and Web3 services.
• Wallet Layer: user-facing wallets such as MetaMask or other compatible EVM wallets.

4.2 Design Principle

The architecture separates the public user experience from node operations. Users access the network through RPC and explorer endpoints, while validator nodes remain controlled, monitored and protected as infrastructure components.

5. Consensus Model

UPE Network is designed around a validator-based Proof-of-Authority model using Hyperledger Besu and QBFT-style consensus. QBFT is an enterprise-grade PoA consensus protocol supported by Besu for private and controlled blockchain networks.

5.1 Why Validator-Based Consensus?

• Predictable block production.
• Lower operational cost than proof-of-work networks.
• Controlled validator onboarding.
• Suitable for business-oriented applications and ecosystem platforms.
• Efficient transaction confirmation for utility and NFT activity.

5.2 Validator Set

In QBFT-style networks, validators are defined in the genesis configuration through the consensus metadata and can later be managed through validator governance processes. Validator keys must be protected and never exposed publicly.

6. UPE Token Utility

UPE is the native token of UPE Network. It is used as the primary unit of account for network activity, transaction execution, ecosystem operations and blockchain-based utility. The total supply is fixed at 10,000,000,000 UPE.

6.1 Utility Areas

• Native Network Currency: used by wallets and applications to interact with the chain.
• Transaction Utility: used for network-level activity and blockchain operations.
• NFT Utility: used for minting, transferring and interacting with NFT-based assets.
• Smart Contract Utility: used by applications that deploy or interact with contracts.
• Marketplace Utility: future settlement and digital asset activity inside the ecosystem.
• Infrastructure Utility: supports applications, wallets, explorers and Web3 services.

6.2 Token Supply Statement

The total supply of UPE is 10,000,000,000 UPE. Any public communication, explorer display, platform interface or whitepaper update should use the same number to avoid inconsistency across the ecosystem.

7. Node Installation Reference

This section describes a reference node deployment approach. It is not a replacement for production security review, but it documents the general structure needed to operate Besu nodes for UPE Network-style infrastructure.

8.1 Minimum Server Recommendations

• Ubuntu 22.04 LTS or Ubuntu 24.04 LTS.
• 2 vCPU minimum, 4 vCPU recommended.
• 4 GB RAM minimum, 8 GB recommended for explorer/RPC-heavy services.
• SSD storage recommended.
• Static public IP address.
• Firewall allowing required P2P and RPC ports only when needed.

8.2 Install Docker

apt update
apt install -y ca-certificates curl gnupg

install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor -o /etc/apt/keyrings/docker.gpg

chmod a+r /etc/apt/keyrings/docker.gpg

echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] \
https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo "$VERSION_CODENAME") stable" \
> /etc/apt/sources.list.d/docker.list

apt update
apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin

8.3 Example Besu Node Structure

/root/upe-network/
├── genesis.json
├── node1/
│   ├── docker-compose.yml
│   └── data/
│       ├── key
│       └── key.pub
├── node2/
│   ├── docker-compose.yml
│   └── data/
│       ├── key
│       └── key.pub
└── rpcnode/
    ├── docker-compose.yml
    └── data/

8.4 Example Docker Compose Node Template

services:
  besu-node:
    image: hyperledger/besu:latest
    container_name: upe-besu-node
    restart: always
    command:
      - --data-path=/data
      - --genesis-file=/config/genesis.json
      - --network-id=883388
      - --sync-mode=FULL
      - --rpc-http-enabled=true
      - --rpc-http-host=0.0.0.0
      - --rpc-http-port=8545
      - --rpc-http-api=ETH,NET,WEB3,QBFT
      - --rpc-http-cors-origins=*
      - --host-allowlist=*
      - --p2p-host=YOUR_PUBLIC_IP
      - --p2p-port=30303
      - --bootnodes=YOUR_BOOTNODE_ENODE
    ports:
      - "30303:30303/tcp"
      - "30303:30303/udp"
      - "8545:8545"
    volumes:
      - ./data:/data
      - ../genesis.json:/config/genesis.json:ro

8. Validator & Genesis Configuration

A validator-based blockchain starts from a genesis file. In Besu QBFT networks, the genesis configuration defines chain parameters, initial allocation, block settings and the validator metadata used at genesis.

9.1 Genesis File Responsibilities

• Defines the chain ID.
• Defines consensus settings.
• Defines initial validator metadata.
• Defines block gas limit and network parameters.
• Defines initial account allocations.
• Creates the first block of the chain.

9.2 Example Genesis Concept

{
  "config": {
    "chainId": 883388,
    "qbft": {
      "blockperiodseconds": 5,
      "epochlength": 30000,
      "requesttimeoutseconds": 10
    }
  },
  "nonce": "0x0",
  "timestamp": "0x0",
  "gasLimit": "0x1fffffffffffff",
  "difficulty": "0x1",
  "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "coinbase": "0x0000000000000000000000000000000000000000",
  "alloc": {
    "TREASURY_OR_GENESIS_WALLET": {
      "balance": "TOTAL_SUPPLY_IN_WEI"
    }
  },
  "extraData": "QBFT_VALIDATOR_EXTRA_DATA"
}

9.3 Validator Expansion

Future validator expansion should be handled through a controlled process. New validators should meet infrastructure, security and uptime requirements before being added. Changes to validators should be tested on a test network before production use.

9. RPC, Wallets & Network Access

UPE Network exposes a public RPC endpoint for wallets and applications. RPC allows software to query chain data, send signed transactions and read blockchain state.

10.1 Wallet Configuration

Network Name: UPE Network
RPC URL: https://rpc.upe.network
Chain ID: 883388
Currency Symbol: UPE
Block Explorer: https://explorer.upe.network

10.2 Basic RPC Checks

curl -s -X POST https://rpc.upe.network \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Expected result:
{"jsonrpc":"2.0","id":1,"result":"0xd7abc"}

curl -s -X POST https://rpc.upe.network \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

10.3 RPC Security Notes

• Do not expose admin APIs publicly.
• Use Nginx or equivalent reverse proxy for SSL termination.
• Apply rate limits if public usage grows.
• Monitor traffic, errors and block synchronization.
• Use separate validator nodes and public RPC nodes when possible.

10. Explorer Layer

UPE Network uses an official explorer to provide visibility into blocks, transactions, addresses, smart contracts and network activity. The explorer is an important transparency layer for users, developers and ecosystem participants.

11.1 Explorer Use Cases

• Verify transactions.
• View wallet balances and activity.
• Inspect blocks and gas usage.
• View contract deployments.
• Provide user-facing trust and transparency.

Official Explorer: https://explorer.upe.network

11. Security Model

Security for UPE Network depends on correct node operations, validator key protection, infrastructure monitoring, safe contract deployment and responsible wallet practices.

12.1 Infrastructure Security

• Protect validator private keys.
• Use SSH keys and disable password login when possible.
• Restrict ports with firewall rules.
• Separate validator nodes from public RPC nodes as the network grows.
• Back up genesis files, node keys and configuration files securely.
• Monitor disk, RAM, CPU, block production and peer count.

12.2 User Security

• Users should never share seed phrases or private keys.
• Users should verify the official domain before connecting wallets.
• Users should confirm Chain ID 883388 before transactions.
• Users should use the official explorer to verify transaction results.

12.3 Smart Contract Security

Any smart contract deployed to UPE Network should be tested on a test network first. Contracts managing NFTs, treasury flows, digital utility, marketplace escrow or ecosystem fees should receive additional review before production use.

12. Governance Direction

UPE Network starts as a controlled validator-based network. Over time, governance may evolve to include documented validator requirements, ecosystem policy, application standards and community-facing proposals.

13.1 Initial Governance Priorities

• Maintain network stability.
• Protect validator infrastructure.
• Keep official endpoints reliable.
• Document token and platform changes.
• Use testnet before mainnet upgrades.

13. Roadmap

14. Disclaimer

This whitepaper is provided for technical, ecosystem and educational purposes. It does not constitute financial advice, investment advice, legal advice or tax advice. Digital assets, NFTs and blockchain networks involve risk. Users are responsible for understanding wallet security, transaction finality, smart contract risk and regulatory considerations before interacting with any blockchain network.

UPE Network information may be updated as the project evolves. Official domains, RPC endpoints, explorer links and technical documentation should be verified before use.