Написать ПО на БЛОКЧЕЙНЕ часть 3

- 3rd deal for backend development and frontend deployment + connection to the smart contract 

frontend (react) according to the design https://drive.google.com/file/d/1TZJkWb4BSQl4Zq7NetWcN5q5IqI1po0o/view?usp=sharing

backend (Nodejs) according to the technical specifications:

Technical specifications for a referral network with 10 levels.

A gamer builds a network through the referral program based on recommendations, i.e., there should be a field for generating a referral link and a QR code.

Definitions:

Gamer - a client who periodically uses the service.

Active Gamer - a client who has made a payment of at least 30 UAH to their account within a calendar month (as an example).

All digital values are variable.

Accruals are made on the first calendar day of the new month for the previous one.

Accruals of rewards (bonuses) are made only for those who have paid an amount of at least 30 UAH; if there are no payments, bonuses are not accrued.

The gamer is considered to be at the zero (root) level by default.

From the first level (those he personally invited), he receives 5% of payments for the month;

From the second level     5%;

From the third level     5%;

From the fourth level     5%;

From the fifth level       5%.

From the sixth level       5%

From the seventh level       5%

From the eighth level       5%

From the ninth level       5%

From the tenth level       5% 

Below the tenth level, there are no accruals for the zero level. Rewards amount to 50%.

The administrator sees the entire network. Gamers see only their own in their accounts.

Clients must attract referrals by all available methods - social networks, QR codes, and others.

Administrator -  two levels - administrator, operator.

In the Administrator's account, there should be:

1. Configurable access levels.

1.1. Administrator 

1.2. Operator

What should be included - the number of all people, how many payments, the number of accruals. 

Document export for BAS.

Charts, selection by relevant parameters. News window advertising banner - settings for clients.

2. Client

The number of invited referrals in total and by levels

The number of active (paid) referrals in total and by levels

The total amount of accrued bonuses

News window or advertising banner.

Window for generating QR code for referral link and a permanent referral link.

Home page 

Request for user registration in a new separate database of referrals with confirmation via email. (plus we add a linking request to check if this user is in the general database and devise a transfer and update of the number of miracoins and payments between the two databases) p.s. it will be possible to schedule a time for a call and discuss possible options.

Request for basic login to the site.

Page “My Profile”

Request that returns the amount of accruals and account status, user balance, and number of referrals. 

Button “top up account” (our payment systems, nothing needed)

Button “Withdraw bonuses” has no request, as it redirects the user to the bonuses page. 

Button “More details” under referrals also does not require a request, it redirects the user to another page.

Page “My Bonuses”

Request for the balance of current user bonuses and statistics of bonus accruals (year, three months, month, week) and deductions with the same intervals.

Request for withdrawal of funds to a card (additional information will be provided during execution)

Request for converting bonuses into miraplay (changing the number of coins in the user's database, I will prepare the necessary route by parameters) 

Request for withdrawal to a crypto wallet.

Page “My Referrals”

      1.Data about invited and active users.

      2.Data about referrals comparatively (all information along with percentages depending on the level) with the name and avatar of the referral user.

      3.Extract of the analytics aggregate about referral registrations  (year, three months, month, week)

Page “My Referral Links”

      1. Request for creating a referral link (in the input field, the user will add the name of the link, which is added to the general format of links on the backend and generated. If possible, make them short).

      1.1 editing the name of the link and regenerating the link. 

     2.Request that returns the user's active links. 

     3. Request to delete a link from the database.

     4. Logging of transitions by request.

     5. Analytics of the number of transitions and registrations for each link by name. 

Page “My Settings”

Request for all data.

Post request for changing data (Last Name, First Name, Middle Name, Login, Email, Phone, Date of Birth, Telegram, Change Password, Identification Code, Passport Series and Number, Your Registration, Issued By, Your Details, KVED, EDRPOU, Company Name, User Avatar)

Page “FAQ” 

Request for obtaining all questions and answers.

Admin request for adding, editing, and deleting questions. (+ dynamic translation needed).

Button “Contact us” accepts data (Subject, question, user) and saves the question in the database. Separately and in the entity of the user who asked the question, so that the correspondence history can be displayed later.  

Page “Users” (Admin)

Request for all users.

Request for sorted active clients who already have registered referrals.

Request for sorted users who have at least 1 payment.

Admin request for blocking a user with logging the reason.

Admin request for transferring a user to operator.

Admin request for information about a specific user. 

Request for lowering an operator back to a user (with logging in the format of “deleted operators”)

Request for all deleted operators.

Request for blocked users with all information and reason for blocking. 

Page “Statistics” (Admin)  

Statistics on user payments (day, week, month, three months, year, input by dates) and total amount for the selected period. 

Statistics on registrations (day, week, month, three months, year, input by dates)

Statistics on active (more than 100 UAH) and inactive users (day, week, month, three months, year, input by dates)

Statistics on referral transitions (day, week, month, three months, year, input by dates)

Statistics on fund withdrawals with variability “to account”, “conversion to miracoins”, “withdrawal to crypto wallet”.

Statistics of the difference in active users compared to the previous month. 

Page “Referral Level Settings” (Admin)

     1.Request for editing the interest rate of referral levels  

Page “Feedback” (Admin)

Request for displaying all sent questions. 

Request that accepts a response to a specific question and adds this response to the information of the user who asked this question.

User Model

The bonus accrual system starts from the moment the user brings the first referral who makes a payment. 

These bonuses are “gray” until the user deposits at least 100 UAH into their account. After changing the account status to “active”, these bonuses are transferred to the “green” category and are no longer recorded as “bonuses” of the user, but as their balance. That is, they are preserved. From the next month, all bonuses are again counted in the “gray” category and reset if during the current month the account was not changed to “active” (the amount of accruals was less than 100 UAH). Withdrawal of bonuses is possible only if at the time of submitting the withdrawal request the user's account is in the “active” status (the amount of top-ups for the current number of days is more than 100 UAH). The start and update of the account and bonus status are tied to the beginning and end of the calendar month. 

Clarifications on important points of the user model, for convenience.

Logging of transitions through the user's referral links (even if without registration, we fix the activity and the number of interested clients). 

Field about the presence of a signed agreement for fund withdrawal (will change through admin request-confirmation).

Field for fixing whether this is a public person, through admin request 

Fields with values for fund withdrawal to different systems.

Array of correspondence with the admin/operator with dates and topics of correspondence.

Field whether the user was an operator

Reason for blocking, if blocked. 

Logging of fund withdrawals on different systems 

Account of total top-ups and deletions for the entire existence of the “user”

Fixation of each withdrawal and top-up with date and time. 

Fixation of the last active month for the user. If a previously active user has a break of 2 months, we send a scheduled message to their email. 

Also, a scheduled message about the possibility of losing accrued “gray” bonuses, 10 days before the end of the month. 

Sending a warning about a large number of referrals who entered through the link but did not register, specifying the name of the link. For a regular user after every 20 “empty” transitions. For a public user after every 50 “empty” transitions.

And connection to the main database for simultaneous updating of the number of payments and coins. 

It is also necessary to highlight and prohibit the deletion of profiles of “clean” admins. But have a request for converting a user into user&operator or user&admin, which can be both blocked and deleted. That is, to have a difference in records in the database for clean and appointed admins.

And track the number of users on the site at the moment.

Logging that must be mandatory.

     Number of transitions through links

     Number of active users by months

     Number of inactive users by months

     Correspondence with clients linked to the id of the user who is asking and the admin/operator who is responding. 

     Deleted operators/admins

Preservation of the user tree in the blockchain system through a smart contract with flexible possibilities to implement additional functionality (modular system)

Example: accounting for bonus balance

Database at discretion

Copy of all users with consideration of the tree to be saved in the database