Skip to main content

Validator Requirements

This guide covers the requirements for running a Monolythium validator.

Token Requirements​

RequirementAmountPurpose
Self-delegation100,000 LYTH minimumStake in the network
Burn deposit100,000 LYTH exactlyPermanent commitment
Total200,000 LYTHTo create validator

The burn deposit is one-time and non-refundable.

Hardware Requirements​

Minimum Specifications​

ComponentMinimum
CPU4 cores
RAM16 GB
Storage500 GB SSD
Network100 Mbps
ComponentRecommended
CPU8+ cores
RAM32 GB
Storage1 TB NVMe SSD
Network1 Gbps

!!! tip "Storage Growth" Plan for storage growth. The chain data grows over time. Use expandable storage solutions.

Infrastructure Requirements​

Uptime​

Target: 99.9% uptime

Downtime triggers:

  • Missed block rewards
  • Potential jailing (extended downtime)
  • Reputation damage

Network​

RequirementDetails
Static IPRequired for peer connections
Open ports26656 (P2P), optionally others
Low latencyImportant for consensus participation
Redundant connectionRecommended

Security​

MeasureImportance
FirewallRequired
SSH hardeningRequired
Key managementCritical
DDoS protectionRecommended
Sentry architectureRecommended

Operational Requirements​

Monitoring​

Essential monitoring:

  • Node health
  • Block signing status
  • Disk space
  • Memory usage
  • Peer connections

Maintenance​

Regular tasks:

  • Binary upgrades
  • Security patches
  • Log rotation
  • Backup verification

On-Call​

Validators should:

  • Monitor 24/7 (automated alerting)
  • Respond to incidents quickly
  • Have escalation procedures

Key Management​

Consensus Key​

The priv_validator_key.json file:

  • Signs blocks
  • Critical for validator operation
  • Must be backed up securely
  • Consider HSM for production

Operator Key​

The account key used for:

  • Validator transactions
  • Commission changes
  • Unjailing

Sentry Architecture​

Recommended for production validators:

                    Internet
                        |
            +-----------+-----------+
            |           |           |
         Sentry1     Sentry2     Sentry3
            |           |           |
            +-----------+-----------+
                        |
                    Validator
                   (private)

Benefits:

  • DDoS protection
  • Network isolation
  • Redundancy

Cost Considerations​

One-Time Costs​

ItemCost
Burn deposit100,000 LYTH
Self-delegation100,000 LYTH (recoverable)
Initial setupVaries

Ongoing Costs​

ItemEstimate
Server hosting$200-1000/month
BandwidthIncluded or additional
Monitoring tools$0-100/month
Maintenance timeSeveral hours/week

Checklist​

Before registering as a validator:

  • 200,000 LYTH available (100k stake + 100k burn)
  • Server meeting minimum specs
  • Full node fully synced
  • Firewall configured
  • SSH hardened
  • Monitoring set up
  • Backup procedures tested
  • Alert notifications configured
  • Sentry nodes (if using sentry architecture)

FAQ​

Can I run a validator on a home connection?

Not recommended. Home networks lack reliability, static IPs, and enterprise-grade uptime.

What cloud providers work?

Any major provider: AWS, GCP, Azure, Hetzner, OVH, DigitalOcean, etc.

Can I run on ARM?

Check binary availability. x86-64 is primary target.

What if I can't meet uptime requirements?

Consider delegating instead of validating. Running a validator is a commitment.

Next Steps​