Skip to content
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

Request: Beacon Status Button in the Wallet #1552

Closed
jring-o opened this issue Oct 6, 2019 · 3 comments · Fixed by #1646
Closed

Request: Beacon Status Button in the Wallet #1552

jring-o opened this issue Oct 6, 2019 · 3 comments · Fixed by #1646
Assignees
Milestone

Comments

@jring-o
Copy link

jring-o commented Oct 6, 2019

From cleaning the gridcoin-tasks issues.

###Spec:
make a status monitor which functions also as a button that fits in the notification strip right next to locked, staking, up to date, etc. are.
###Suggestion:
The button be shapped like a chainlink. Examples: image or image
for examples.
Let that status button be for joining (sending a beacon) and monitoring your beacon on the network.

Reason:

Right now sending a beacon is cryptic for new users.
Why not color code it clearly:

  • Green - Beacon is on the network.
  • Yellow - Beacon is 5 months old and needs renewal. (Click to resend your beacon, you will be prompted to unlock your wallet if necessary.)
  • Red - you have no beacon matching your current CPID on the network. (Click to send your beacon, you will be prompted to unlock your wallet if necessary.

Bonus: hover over the JOIN button and see your receiving address attached to your beacon.

gridcoin-community/Gridcoin-Tasks#214

@jamescowens
Copy link
Member

This is a good idea.

@9swampy
Copy link

9swampy commented Oct 23, 2019

Slightly tangential but I don't see how this could be derived from current RPC command responses; if you're to implement could you make the status available over RPC please? MTIA.

@jamescowens
Copy link
Member

While I am waiting on cycy on a portion of the contract stuff for Fern, I think I can do some work on this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants