bitshares / bitshares/bitshares-ui

Permissions enhancement - Committee invoked security measure

Open
#2,417 2 comments 0 reactions 0 assignees View on GitHub
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.**
Given the recent Random-k.com compromise of accounts, I think that it is possible to increase security measures within the client using global listeners.

A clear and concise description of what you want to happen.
1. If someone blacklists another account, nothing more happens (current state-P2P)

2. If someone blacklists another account, and 2 more (or 1 more-consensus) holders blacklist the same said account, committee members are alerted in some way in addition to delegated Committee member blacklisting said account upon verification of attack/compromise. (auto-initiated memo using listeners?)

3. If someone blacklists another account, 2 more holders blacklist, Committee members are notified, a single delegated Committee member blacklists PLUS another Committee member blacklisting said account results in auto-lock out of attackers account until further investigation from HacktheDEX team (again, by auto-memo to delegated HacktheDEX team).

**Describe alternatives you've considered**
Additionally and if possible or feasible, if all accounts were scanned for double key entries (active and memo) they could be notified (via memo) informing them that they need to change their keys and how to do so. Eventual goal of no more accounts with double key for active and memo.

A fair system of
1) account holder blacklisting +
2) Committee member blacklisting +
3) Witness member blacklisting may be more ideal and collusion free but it would also present Witness exposure which would not be ideal.

**Additional content**
http://docs.pybitshares.com/en/latest/_modules/bitshares/notify.html#Notify

Contributor guide

Open the contributing guide

Research direction

Review the linked bitshares/notify.py documentation and map how the client currently handles blacklist actions and committee notifications. The issue does not name repository files or tests; completion would require an agreed design for consensus alerts, committee-driven account locking, and any double-key scan and notification flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
blockchain, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.