LogoLogo
HomeDiscover WeSenditLanguage
  • WeSendit at a Glance
  • WeSendit Introduction
    • Meet the Team
    • WeSendit Token
    • Social Media
    • FAQ
  • Problem
  • Our Solution Strategy
  • Technology
  • WeSendit Token / Usecases
    • Access to Data Management and Administrative Functions
    • WSI Rewards for Data Sharing
    • Level Rank and NFT Rewards
    • Web3-Referral-System
    • Reward System for Node Operators
  • Data Protection at WeSendit: Core Principles and Innovations
  • Blockchain Integration
    • 👨‍💻Smart Contract
    • 🔎Contract Audit (Hacken)
  • Tokenomics
    • DEX & CEX Listings
    • Vesting Schedule
    • Token Burn Strategy
    • Token Allocation
  • Competitive Analysis
    • Market Situation and Developments
    • Market Segments and Target Audiences
    • Competitors
    • Market Success Factors
    • Summary and Outlook
  • Roadmap
    • WeSendit Roadmap: Detailed Outlook
      • Current Developments Q2 2024
      • A Glimpse into the Future: Our Exciting Roadmap for Q3/2024
    • Planned Feature Expansions and Foundational Activities Q3 & Q4 2024
    • AI Integration Planning and Development 2024-2026
  • Security Protocols and Privacy Measures in Web3
  • Comparative Analysis with Existing Web3 Storage Solutions
  • WeSendit Node Network
    • Preparation for Operation
    • The Multiplier
    • Functionality
      • Security and Redundancy
      • Encryption
      • Score and Rewards
      • Processes and Requirements
      • Network Schema
    • The Participants
      • Master Node
      • Node Balancer
      • Indexer
      • Storage Node
      • Blacklist
    • The Networks
      • Checknet
      • Testnet
      • Mainnet
    • Onboarding for Node Operators
      • Get a NodeNFT
      • Minimum Requirements
      • Installation Instructions
      • Operating Multiple Nodes
      • Troubleshooting
      • Install FAQ
    • FAQ
  • Terms of Service
    • Privacy Policy
    • WeSendit General Terms of Service
    • Node Presale Terms of Service
    • Legal Notice
Powered by GitBook
LogoLogo
On this page
  • Hardware
  • Internet Connection
  • Response Time
  • Node License

Was this helpful?

  1. WeSendit Node Network
  2. Onboarding for Node Operators

Minimum Requirements

PreviousGet a NodeNFTNextInstallation Instructions

Last updated 1 month ago

Was this helpful?

To act as a node operator in the WeSendit network, certain system requirements are necessary to ensure that the node can work effectively and store data securely and reliably. Please note that these requirements represent only the minimum standards. Depending on the scope and nature of the data to be stored, it may be advisable to have a system with higher specifications.

Please note that the System relys on your score. Your score is based on 4 factors with different weights. Please read Score and Rewards for more details.

Metric
Min. Requirement
Recommanded

CPU

2 cores, 1.5-3GHz

2 cores, 1.5-3GHz

CPU Architecture

x86

x86

Storage

10 GB

1TB

Bandwidth Impact score

UP: 10 Mbps/s Down: 10 Mbps/s

UP: 100 Mbps/s Down: 100 Mbps/

Uptime* Impact score

95%

99%

Ping** Impact score

150ms

50ms

*Uptime of 95% = 18 days of downtime per year. Uptime of 99% = 3 day downtime per year. Calculate here your uptime: ** You don't have the chance to impact the distance to the next master node, read Roadmap to see regions you can run the node.

Hardware

The hardware requirements for participating in the WeSendit network are moderate, making it accessible for a wide range of systems. Any system that supports the architectures listed above and has Docker capabilities can effectively run a WeSendit Storage node. This includes a variety of hardware configurations, ensuring flexibility and ease of integration. By meeting these requirements, your system will be able to contribute to the network's storage capabilities efficiently. Additionally, we plan to extend support to other architectures in the future, further broadening the range of compatible systems.

Storage Space

Even with just 1 GB of available storage space, you can operate a node and earn rewards in the form of WSI tokens for providing that storage. The system will reserve the amount of storage you specified during the onboarding process. It's important not to allocate 100% of your storage, as Linux systems may increase the swap partition (depending on the configuration), and Windows systems will write log files and perform updates. If you occupy 100% of your storage, your system is likely to crash or fail.

Operating System

We recommend using a Linux distribution such as Debian LTS or Ubuntu LTS with Docker installed. These operating systems are particularly well-suited and stable for running nodes. If you choose to run the node on Windows, ensure it is on a Windows Server, as Windows Home and Business editions are designed for desktop clients and are not intended for 24/7 operation. For those looking to install the node on a NAS OS, please check the compatibility for virtualization.

The following lists will not be monitored. Please verify your NAS type and its compatibility with virtualization independently.

Synology Container Manager or Synology Docker packages are available for certain devices. Check these links to see if your NAS is compatible with Docker and check the Architecture (which is most likely x86)

For QNAP, check if your device supports the Container manager

Internet Connection

A stable 24/7 internet connection is essential to ensure continuous availability of data and prompt acceptance of new data packets. Providing a static IP address is not required, as your node will regularly report to the storage node and update its IP address if it changes. However, please note that dynamic IP addresses (DHCP) typically do not change daily or hourly. Frequent IP changes may be detected by the system as a failure.

Response Time

Response time is crucial for the system to operate efficiently. Shorter response times mean packages are collected faster and are likely transferred with higher bandwidth due to shorter distances and fewer hops. Response time primarily depends on the distance between your node and the nearest Master Node. The shorter the response time, the closer you are to the next Master Node.

Node License

For information about node License, check Preparation for Operation

DSM 6.2

DSM 7.2

OS 4.4.3

https://uptime.is/
https://www.synology.com/de-de/dsm/packages/Docker?os_ver=6.2&search=Docker
https://www.synology.com/de-de/dsm/packages/ContainerManager
https://www.qnap.com/en-in/how-to/faq/article/i-am-not-able-to-find-container-station-for-my-nas