We can introduce a Reward Factor based on the user Segments.

The Factor will increase when the user moves to a more active segment and decrease when moving to a less active segment.

The reward factor will be multiplied by the contribution score.

Improve push notifications related to rewards

• Sending a daily notification about the total rewarded tokens in the previous day and allow the user to click and see the breakdown.
• Sending a notification to inform the user on his move to a higher activity user segment (e.g. congratulations, you have moved from the casual to the core league).
• Sending a preemptive notification and an email to inform the user about the risk of dropping to a lower activity segment (e.g. oops, you are about to drop down from the core league to the casual league, you will earn less token because of that).

changed title from goal: to goal:

added scoped labels

added 1 deleted label

changed title from New rewards to New rewards

changed the description

changed the description

@ottman got a start on this

Nice. Let's squeeze it in next Sprint and get time estimate from mark.

@markeharding bill and i have been talking and think this may need some immediate attention. it is essential to align our rewards system with the business goals, which is not currently the case. interested in your feedback on this...i think the contribution score amounts need a deeper analysis, but give us your thoughts. need to make sure nothing can be easily gamed, but we should not be scared to offer big rewards for the outcomes the network needs.

changed the description

changed title from ewards to ewards

@JakePassi can you add important referral related issues to this epic?

added issue engine#221 (closed)

added issue engine#222 (closed)

Need to address reminds issue so that original content creators are still earning rewards when reminds of their posts gain interaction

changed title from Rewards to Rewards

removed issue engine#222 (closed)

removed issue engine#221 (closed)

added issue front#1488 (closed)

added issue engine#587 (closed)

added issue engine#588 (closed)

added issue engine#589 (closed)

@ramialbatal please can you copy over your doc to this epic?

added issue engine#590 (closed)

added issue front#1489

changed title from New to New

changed the description

added issue docs#3 (moved)

changed title from New Reward Program to New Reward Program

changed the description

I'm not really clear on what exactly this means "Reward Factor based on the user Segments" so you might need an in depth explanation on launch. Because to me it can mean one of two things (and you might even think of it as a third thing)

1. It can mean that the more I engage the bigger the reward factor becomes or
2. If I engage in popular topics my factor goes up. Now this could potentially be a problem if you nudge people away from the more unpopular posts or topics people will get the feeling that you are soft censoring them, since people will be disincentivized to engage in less popular stuff.

I'm not saying that I think of it this way, but given your roll out of the new NSFW and penalty system and how people reacted to that you should be really careful how you word and present this and also be aware of the consequences of the incentives you put in place.

added issue engine#636 (closed)

changed title from to

changed the description

added issue mobile-native#1255 (closed)

added issue mobile-native#1256 (closed)

added issue front#1859 (closed)

added issue front#1858 (closed)

@jotto141 where is this visible on the site?

changed title from Reward to Reward

@gthouret what is current status of this project?

@jotto141 As far as I'm concerned this has been complete for some time. There was a minor change to something made last week that was flagged by Mark, now that's resolved it should be good for deployment. The UIs going to get out of date pretty quick if changes to wallet are coming.

@gthouret where is the UI component in the wallet?

Any word here?

@jotto141 @gthouret if it is completed, we need to write a blog post about it when we deploy it.

Right, but where is it visualized? Where in UI can we see if we are being multiplied? It should be VERY visual so that if it goes away a user knows.