Why FarmX Uses Only the Master Address

FarmX currently supports staking only through the primary Sage Wallet master address.
This is an intentional platform rule. It exists not only for economic efficiency, but also for clarity, consistency, and user protection.

Why this rule exists

Allowing unrestricted staking from multiple wallet addresses creates avoidable fragmentation and unnecessary confusion. With a very low entry threshold, one user could split funds across many addresses and open large numbers of tiny stakes. That leads to several obvious problems:
1. Fragmented staking structure
Too many small positions make the system less efficient and harder to manage.
2. Dust-level reward activity
Tiny stakes produce tiny claims and unnecessary low-value on-chain activity.
3. Higher operational overhead
Fragmented micro-stakes create avoidable cost and processing overhead for the platform.
4. A broken user view
One user should see one clear staking view.
If a user opens a stake from one address and later connects from another, the position may no longer appear in the visible session view. The stake is not lost — but from the user’s perspective, it can look exactly like it disappeared.
That creates false “missing stake” situations, unnecessary support cases, and completely avoidable reputational damage.

Why the master address model is better

Using one master address keeps staking cleaner, clearer, and safer.
It gives us:

  • fewer fragmented positions
  • lower dust-related overhead
  • simpler stake tracking
  • clearer reward management
  • one consistent staking view per user

Can staking from any wallet address be enabled?

Yes. The technical capability already exists. But that model only makes sense under different conditions.
Our current model is:

  • 1 FMX minimum → primary master address only

If a user wants staking from any wallet address, that can be enabled — but with a different threshold:

  • any wallet address → minimum stake of 100 FMX

The reason is straightforward: low-entry staking and unrestricted address usage are a bad combination.

Our position

For now, FarmX uses the primary Sage Wallet master address as the default staking address. This rule protects platform efficiency, prevents fragmented micro-stakes, and ensures that each user sees one clear and consistent staking view.
No address sprawl. No false missing stakes. No unnecessary friction.

Restricting staking to the primary master address is not only about efficiency. It is also about clarity, consistency, and user protection. One user should see one clear staking view. Without that, address switching can easily create false “missing stake” situations, unnecessary support cases, and avoidable reputational damage.

Nach oben scrollen