@LoopGhost007@MitchellAmador Oh, then, without offense, i understand more the ban.
But i agree they should never be permanent, as a web3 whitehat its completely life changing in the bad way
@LoopGhost007@MitchellAmador Wow, thanks for clarifying, this is really bad honestly.. one last thing if you could answer, did you just submit some invalid reports to get banned or you broke some rule?
@LoopGhost007@MitchellAmador but wait, i just read that you said that your confirmed findings were on other protocols/platforms.
So, do you have an actual paid report in Immunefi? Could you link your profile or something? Sorry but this is important to me.
@LoopGhost007@MitchellAmador Wow, did not know you could get banned even with confirmed findings, thats scary as hell honestly, for most of us this is our life work
@MitchellAmador Thanks, great improvement!
One feedback i can give, for the latest duplication feature:
sometimes, protocol teams close a report with "duplicate" but only text-wise, they don't actually mark as duplicate selecting the original, and this just defeats the whole feature
@adrianhetman@Haxatron1 brother, he just explained to you what by “see what happens” he didn’t mean “see if bug is valid” but rather “see if protocol team is reliable and honest”, jesus christ
@MitchellAmador@japzdivino please show the reason of invalidation of the original finding in case it got invalidated.
otherwise i have either no reason to know if decision is correct nor to learn from my mistakes
@MitchellAmador But i myself got one of my report duped, the original report was “Closed” thus invalid and reason of invalidation was not shown.
So this does not apply to the example in this tweet