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

corrupt nodes can ignore wallets #41

Open
ghost opened this issue Jul 4, 2018 · 9 comments
Open

corrupt nodes can ignore wallets #41

ghost opened this issue Jul 4, 2018 · 9 comments
Labels
bug Something isn't working scope

Comments

@ghost
Copy link

ghost commented Jul 4, 2018

Currently, it is possible that nodes can repeatedly delete specific wallets. Since there is no required connection between the wallets, the node can still be seen as valid by everyone else. The result is, that an attacker can provide nodes, that ignore certain wallets.

@0crat
Copy link

0crat commented Jul 4, 2018

@yegor256/z please, pay attention to this issue

@0crat
Copy link

0crat commented Jul 4, 2018

@oltdaniel/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@yegor256 yegor256 added the bug Something isn't working label Jul 5, 2018
@0crat 0crat added the scope label Jul 5, 2018
@0crat
Copy link

0crat commented Jul 5, 2018

Job #41 is now in scope, role is DEV

@0crat
Copy link

0crat commented Jul 5, 2018

Bug was reported, see §29: +15 point(s) just awarded to @oltdaniel/z

@0crat
Copy link

0crat commented Jul 5, 2018

@yegor256/z everybody who has role DEV is banned at #41; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Jul 10, 2018

@yegor256/z everybody who has role DEV is banned at #41; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256 yegor256 self-assigned this Jul 11, 2018
@0crat
Copy link

0crat commented Jul 11, 2018

The job #41 assigned to @yegor256/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; we should be aware that @yegor256/z is on vacation; this ticket may be delayed; there will be no monetary reward for this job

@0crat
Copy link

0crat commented Jul 11, 2018

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @yegor256/z

@yegor256 yegor256 removed their assignment Sep 10, 2022
@0crat
Copy link

0crat commented Sep 10, 2022

@yegor256/z I see that you unassigned this issue; the order is still assigned to @yegor256/z though; to cancel the order use refuse, as in §6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working scope
Projects
None yet
Development

No branches or pull requests

2 participants