Users have difficulty identifying their eligible IDs
Thắng Nguyễn
Current status:
- User has difficulty identifying eligible IDs of Cross Boss, namely flow as follows: Unstake Cross Boss from Cross Boss Testers pool -> See if Eligible NFT portion of Random Cross Boss pool increases -> Otherwise bring unstaked Cross Bosses back to previous Cross Boss Testers pool.
- Testimonials (see also the first attachment section to see user flow):
- My wallet address to check user flow: https://bscscan.com/address/0x24695e871abef73e9c5eeeb674a681ec40c074b8#tokentxnsErc721
Objective:
- Minimize the time in flow users doing NFT staking.
- Reduced gas fee when users have to unstake and re-stake
Suggested solutions:
and. Create an additional Activities tab for the purpose of recording user logs related to staking.
b. Assign tags on NFTs images in the NFTs tab. Tag format: Staked + [Name of the pool being staked]
Summing up:
- Both solutions have their own cost and both make the site heavier and I also noticed that the solutions have a tracking nature. Therefore, the Hotcross team can consider turning this part into a paid feature in common with the Dashboard mentioned by Phi (i.e. the user who makes the payment to unlock the Dashboard will also unlock the feature above).
*Note: The 2.3 attachments are other user actions that are unstaked and then re-staked. I track the last 100 transactions of Staking Contract from the Cross Boss Testers pool
Sung Pham
Hi Thang, thank you for your very detailed feedback. actually this is not so much the case, usually this pool is done before the other pool runs, since the first pool is a test pool so it only runs in parallel.
Moreover, option B will not work because after staking, NFTs will send to the address of the pool and not to the wallet, making it difficult to query the data.
In addition, users can check IDs when unstaked, and decide which NFTs to unstake to stake a new pool.
In the end, every change of dApp should solve dc 80% still the user's problem, that is, 20% change can solve dc 80% problem. then the new change is ok. This case is not a common problem.
Thắng Nguyễn
Sung Pham: Hi Sung, if your team's plan is to run the pool independently and not in parallel, then the issue and suggested solutions can be skipped. Thank you!