bitshares / bitshares/bitshares-ui
Whitelist tab enhancement - added features to whitelist/blacklist tabs
- Dominant language
- JavaScript
- Stars
- 520
- Forks
- 575
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 5
Description
**Is your feature request related to a problem? Please describe.**
1. Consider the enclosed mock-up to illustrate a way to improve the user experience by providing them
with tools to avert threats or attacks from accounts and assets. Additionally, it allows BitShares an
opportunity to display the decentralization that BitShares operates on by consensus and without
interference and that lengths have been taken providing the users with the self securing tools and
data to make informed decisions and react accordingly in their best interest. Please see #2417
2. Consider adding the ability to send a memo to self to create a personal memo. This feature could be
used to generate interest in Life-Time Memberships by providing the memo feature at no cost to LTM
and apply the normal fee to non-LTM.
3. Consider applying the same template to each tab; Blacklist, Whitelist, Whitelisted by, and Blacklisted
by.
4. Consider that I included two mock-ups. One does not show the memo to self feature I propose to be
offered to LTM.
The other mock-up includes the memo feature. It also includes a colorization that should be self
explanatory, but it reflects the authorized accounts results of blacklisted/whitelisted accounts/assets r
respectively. There is a list feature. The colorized number represents the number of other accounts
that have blacklisted/whitelisted and their account name (could replace with account ID/ or list both).
The list feature provides transparency but it also provides disclosure, which is readily available on a
number of Explorers anyways. We have access to this data and should easily be extrapolated for
population.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.


Contributor guide
Research direction
Review the two mock-ups, the existing Whitelist, Blacklist, Whitelisted by, and Blacklisted by tabs, and issue #2417 before work begins. Confirm which of the proposed features are in scope, then define completion as an agreed tab template, threat-related account or asset information, and any memo-to-self behavior working consistently with the product requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, javascript, react
- Domain
- blockchain, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100