member tier

The latest version of OptractContract (https://github.com/elevenbuckets/OptractContract/commit/d8d2b1f2db30f1c1caca73abd5045c55ae70b167 ) has included member tier. The contract has not yet deployed.

Todo once deployed:

• dapps/OptractMedia/OptractMedia.js: in memberStatus(), the getMemberInfo return also the member tier, should update the res[].
• design the features for each tier and implement these features

About tiers (in current smart contract):

• the tier is a uint8, i.e., from 0-255.
• treat the uint8 as 8 bit, which means 8 different features a user can unlock
  • For example, tier 255 means the user can unlock all features (since 255 in binary is 11111111), tier 1 (00000001) means the user can only use the feature in the lowest digit.
  • For now, if the highest digit is 1, i.e., the tier (uint8) is greater than 128, it's a VIP tier. A VIP user has a much longer memberPeriod
  • For now, only tier 1 and tier 255 are used: 1 is for regular user, and 255 is for coreManagers
  • Don't use tier 0 to avoid confusion

As I remember, (in the future) the member tier is related to the amount of tokens the user owned, right? The more a user owned, the higher tier he/she can own.

Start with dapps/OptractMedia/OptractMedia.js and its memberStatus() entry point, then review the referenced OptractContract commit and deployment status. Update the member-status result for the tier once the contract is deployed, and define and implement the tier features, including the currently described tiers, with the completed behavior documented.