You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2019. It is now read-only.
A component needs to be created for the inbox / request notifications.
Spec
All notifications can be presented in the list, but the required information may be different between service request and buy / sells from the curve.
Service Requests
Show address of account requesting (or name if they've signed up with an ENS name already).*
Show time and date of request.
Show service requested.
Show message parsed in a nice format.
Show amount paid. ( can be color coded blue for service request)
Buy / Sells
Show address of account which bought or sold (or name if they've signed up with an ENS name).*
Show time and date of operation.
Message blank.
Show amount bought / sold. ( Can be color coded so green = buy and red = sold)
Additional requirements
Name should be clickable and link the in order of priority 1) their economy if one exists, 2) ???, 3) their etherscan page
Also consider reverse name lookup. So first it tries to find a convergent-id then it will do a reverse lookup, and if these fail it falls back to showing a short version of the address.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A component needs to be created for the inbox / request notifications.
Spec
All notifications can be presented in the list, but the required information may be different between service request and buy / sells from the curve.
Service Requests
Buy / Sells
Additional requirements
convergent-id
then it will do a reverse lookup, and if these fail it falls back to showing a short version of the address.The text was updated successfully, but these errors were encountered: