🧱 Implement Cap-Collusion (Alpha Stake Cap per Validator)

[ultrashiny]

📝 Summary

To prevent validator collusion and over-centralization of influence, we will introduce an Alpha Stake Cap inside the subnet.
Each validator’s stake will be limited to a maximum of 20% of the total alpha stake across all validators.

Any stake exceeding this cap will not contribute to validator weighting.

---

🎯 Goal

• ✅ Prevent validator collusion and dominance.
• ✅ Maintain fair stake distribution across the subnet.
• ✅ Ensure no single validator can manipulate rankings or rewards.
• ✅ Encourage decentralization and diversity of participation.

---

⚙️ Rules

• Each validator’s effective alpha stake is capped at 20% of the total validator alpha stake.
• If a validator’s real stake exceeds the cap, the excess stake is ignored in emission weighting calculations.
• Total reward weights are normalized again after applying the cap.
• The system should log capped validators for transparency.

---

✅ Acceptance Criteria

• Add alpha stake cap mechanism (default: 20%).
• Adjust reward and weight calculations accordingly.
• Log when validators exceed the cap.
• Ensure emissions remain balanced after normalization.
• Add config for cap percentage (ALPHA_STAKE_CAP=0.2).
• Update governance and economic documentation.

---

🧱 Tasks

• Modify validator weight calculation logic.
• Implement alpha cap enforcement before emission distribution.
• Add logging/metrics (capped_validators_count, cap_ratio).
• Write test cases for various stake distributions.
• Update docs (ECONOMICS.md, GOVERNANCE.md).

---

🏁 Outcome

A collusion-resistant subnet where no validator can hold more than 20% effective stake, ensuring fair governance, balanced emissions, and strong decentralization.