Slashing

Slashing — Protecting Network Integrity at UAX

In the UAX.Network ecosystem, slashing plays a critical role in maintaining validator honesty, discouraging harmful behavior, and reinforcing the network’s long-term security. As UAX evolves toward full Proof-of-Stake (PoS) consensus, validator responsibility becomes paramount—and so do the consequences of misconduct.

Why Slashing Matters

Validators are responsible for proposing, validating, and confirming blocks. They’re not just passive participants—they’re entrusted with securing user data and consensus. Slashing is the network’s way of enforcing that trust.

Slashing is triggered when a validator:

• Runs the same validator key on multiple machines (key duplication).

• Goes offline for extended periods, reducing reliability.

• Tries to manipulate, deceive, or bypass protocol logic.

Such violations undermine network health. Slashing neutralizes them through automatic financial penalties—removing some or all of the staked UAXN coins.

Minimum Stake Requirement & Commitment

To join UAX as a validator, you must stake a minimum equivalent of $10 in UAXN tokens, locked for one full year. This isn’t a fee—it’s a commitment. During this period:

• Staked coins are non-transferable.

• Withdrawals are not supported until a future upgrade.

• Validator rewards depend on maintaining uptime and compliance.

Slashing is enforced if protocol terms are violated—even unintentionally.

Performance Expectation

In optimal conditions, a validator can submit over 3.1 million bandwidth shares annually, contributing directly to network throughput and earning proportionate rewards. But performance isn’t optional—it’s tracked via Machine ID signatures, uptime logs, and validator behavior.

Validators must maintain near-continuous uptime to remain eligible for rewards and to avoid penalties.

Terminal Proficiency & Keypair Management

Becoming a validator requires basic command-line (terminal) fluency. Tasks such as generating keys and configuring the validator software are done through terminal-based setups.

You must also:

• Securely generate and store validator key pairs.

• Understand that these keys cannot be regenerated later.

• Keep your node online consistently, or risk penalties.

• Losing or mismanaging keys = loss of funds.

Long-Term Commitment

Validators should treat their role as a long-term responsibility, not a casual engagement. With validator exits currently unsupported, you cannot pause your participation and return later. Validator transfers and withdrawals are coming in future protocol upgrades—but for now, committing means staying engaged.