WIP-002: Boost Rewards for Targeted Rollouts (TROv2)

Title

Boosting Rewards for TROv2 Deployed Stations

Abstract

This proposal introduces a Rewards Boost for all stations deployed under Targeted Rollouts (TROv2). Instead of multiplying rewards, the boost is implemented as a separate “Rewards Boost” component, equal to the station’s Base Reward, for two years from deployment. During this period, the station’s daily reward = Base Reward + Rewards Boost. Boosted rewards are included in R_total and split per existing rules (25% to deployers, 75% to the supporters pool, distributed by Blocks).

Motivation

Targeted Rollouts (TROv2) require upfront capital from supporters and operational commitments from WeatherXM and deployers (staking and KPIs). A time-bound Rewards Boost:

• Improves incentives for supporters participating in TROv2.
• Encourages deployers to meet a 2-year operational commitment.
• Accelerates high-priority, targeted network growth in line with program goals.

Specification

• Applies only to devices flagged as TROv2 (Controlled Rollout).
• Boost is additive (separate reward stream), not a multiplier.
• Boost duration: 730 days (2 years) from each device’s deployment date.
• All boosted amounts flow into R_total and are split per existing rules (25% deployers, 75% supporters pool).
• Supporter pool distribution remains linear by Blocks.

Examples:

• Non-TRO station: BaseReward = 10 WXM → Total = 10 WXM.
• TROv2 station within 2 years: BaseReward = 10 WXM, BoostReward = 10 WXM → Total = 20 WXM.
• Split: Deployers 25% = 5 WXM, Supporter Pool 75% = 15 WXM.
• TROv2 station after 2 years: BoostReward = 0 → Total = BaseReward only.

Rationale

• Supporters: Larger supporter pool during the 2-year window, improving incentives; distribution remains fair by Blocks.
• Deployers: Increased earnings (25% of a larger total) while maintaining KPI and staking obligations.
• Community & DAO: Faster growth in targeted regions through structured deployments, aligned with program goals.
• Customers & Data Users: Denser, more reliable coverage in prioritized areas.

Implementation

• Policy Update: Add a Rewards Boost stream for TROv2 devices in Reward Mechanism v2.0.
• System Adjustment: Implement the additive BoostReward(i) = BaseReward(i) logic for 730 days from deployment.
• Effective Date: Upon approval, apply the Rewards Boost to all new and existing TROv2 devices (counting from their deployment date).
• Integrity Controls: Immutable TROv2 program flags, single boost window per device, auditable deployment records.

Affected Stakeholders

• Supporters: Benefit from larger supporter pool rewards.
• Deployers: Higher earnings for 2 years per TROv2 station.
• Community & DAO: Better alignment of incentives and capital for growth.
• Customers & Data Users: Improved coverage in high-priority regions.

Potential Downsides

• Reward Dilution: Increases R_total, which could slightly reduce per-station rewards outside TROv2.
• Implementation Complexity: Requires updates to Reward Mechanism v2.0 codebase.
• Monitoring Effort: Boost windows and program flags must be carefully tracked to prevent abuse.

References

• WeatherXM Documentation
• Reward Mechanism v2.0

Voting

Voting Question

Do you approve WIP-002 to introduce a Rewards Boost for TROv2 deployed stations, equal to their Base Reward for two years?

Voting Options

• For: I approve introducing a 2-year Rewards Boost for TROv2 stations.
• Against: I do not approve introducing the Rewards Boost.
• Abstain: I choose not to express approval or disapproval on WIP-002.

Eligible Voters

All WeatherXM ($WXM) token holders in Arbitrum One or Ethereum, including vesting locked tokens of initial supporters; excluding all WeatherXM Association held or controlled tokens.

Voting Method

• Voting will be conducted via Snapshot at WeatherXM Snapshot.
• Voters will connect their wallets and cast votes directly through the Snapshot interface.

Voting Duration

• The voting period will last for 7 days from the announcement date.
• Voting will begin immediately upon announcement.
• Basic voting is used.
• No shielded voting.

Result Requirements

• A simple majority (50% + 1) of total valid votes will determine the outcome.
• Abstain votes will be counted towards quorum but will not influence the majority required for approval.

Result Announcement

Final results will be announced within 24 hours after the end of the voting period. The announcement will be made in the #announcements Discord channel and pinned for visibility. It will also be added in GitHub discussions as a finalized vote.

Post-Voting Actions

If approved, the WeatherXM team will proceed to implement the Rewards Boost logic in Reward Mechanism v2.0 immediately, latest within 1 month.

Communication

Clear guidelines, FAQs, and direct support will be provided via Discord and official WeatherXM documentation channels.

Audit and Transparency

All votes will be publicly visible and transparent to ensure fairness and accountability. Voting records will be archived for future reference and auditing purposes.