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.
@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/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/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)
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
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.