-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
When an user reaches max verified t1 referrals for his specific mining boost level (for now we only allow that for mining boost level 5 -- logic done only by the client apps --), that user will be forced to make a choice between 2 options: 1. Accept 2. Reject -- this means nothing changes for the user; everything would behave exactly like before If user accepts, 2 things will happen: 1. every new user registered in our app, that inputs that specific user as their referral (via referred_by) will be redirected automatically to a different, random user as their referred_by, that has to verify 3 conditions (has to be verified, has to not have any mining boost level enabled and has to have <3 verified t1 referrals) 2. the user that accepted, will now always have the max t1 referrals of that mining boost level counted as active, even if none of the t1 referrals are mining at all. I.E. for mining boost level 5, max t1 referrals is 25, this means that user will always have +625% (25*25) bonus on their mining rate even if 0 of his 25 verified t1 referrals are mining/active related eskimo commit: ice-blockchain/eskimo@cc17d4a
- Loading branch information
Showing
10 changed files
with
48 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters