-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Staking Contract for Clarity #70
Comments
➤ Kenny Hung commented: Scott Yan (cc Sofia Yan) 關於這個需求,我記得github還是gitbook有一個頁面有直接統整最新資訊,是不是這一個就可以滿足了呀? https://github.com/numbersprotocol/community-support/wiki/NUM-Token ( https://github.com/numbersprotocol/community-support/wiki/NUM-Token ) |
➤ Scott Yan commented: Kenny Hung 這也是一種方式 但需要討論清楚統整一下目前可行的方式
|
➤ Kenny Hung commented: 了解,評估上 #2是不是比較好maintain? |
➤ Scott Yan commented: 比較少需要調整的方式 |
Hi, @Lasheron, We have a GitBook document that summarizes the staking pool URLs, and we have also added the address on the staking site. |
Your email:
Lasheron
Is this a general issue/FR report or a ticket that involve your personal account?:
No personal information involved
Select product:
Staking Site & Contract
One line to describe the issue you see or the feature you want to add:
[FR] Staking Contract for Clarity
Let us know what do you expect to see?:
It is advisable to provide a staking contract for each staking pool directly on the website's user interface. This will help users avoid confusion regarding which pool they have staked in.
Please provide some simple steps to help us reproduce the issue or understand how do you want to see the feature.:
Open stake page
Could see each staking pool directly
What's the device or browser do you use?:
N/A
User story
As a user of the staking site, I want to able to see each staking pool directly, So that I can easily participate in staking activities and have a clear view of each staking pool directly from the stake page.
———————————————
This task was submitted through Issue Report/Feature Request
https://form.asana.com/?k=OlNjzNIasZt0uOT5gzb7pw&d=1200886955782960
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: