You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One block is approx. 30 seconds; therefore, the next round starts in approx. 39 minutes. When the next round starts, SPARK evaluates the previous rounds and schedules rewards.
The text was updated successfully, but these errors were encountered:
One block is approx. 30 seconds; therefore, the next round starts in approx. 39 minutes. When the next round starts, SPARK evaluates the previous rounds and schedules rewards.
@patrickwoodhead could you please chime in on how to best convey this message?
I think the second sentence needs a bit of improvement.
When the next round starts, SPARK evaluates the previous rounds and schedules rewards.
How about:
When the next round starts, SPARK evaluates the impact your Station made in the previous round and increases your scheduled reward if you contributed enough.
One block is approx. 30 seconds; therefore, the next round starts in approx. 39 minutes. When the next round starts, SPARK evaluates the previous rounds and schedules rewards.
@patrickwoodhead could you please chime in on how to best convey this message?
I think the second sentence needs a bit of improvement.
When the next round starts, SPARK evaluates the previous rounds and schedules rewards.
How about:
When the next round starts, SPARK evaluates the impact your Station made in the previous round and increases your scheduled reward if you contributed enough.
Sounds good with maybe one tweak:
When each round ends, SPARK evaluates your Station's impact during the round and updates your scheduled rewards based on your contribution.
Idea: Show when the next round starts, because that is where (most likely) your scheduled rewards get updated.
I've been starting at the app a bit and wondering "when will rewards change".
Slack convo: https://filecoinproject.slack.com/archives/C03PQG6UT2B/p1699626131519909
The text was updated successfully, but these errors were encountered: