Closed code423n4 closed 1 year ago
0xRobocop marked the issue as sufficient quality report
JustDravee marked the issue as grade-c
Hi @JustDravee
Thank you for the grade. I believe my report still deserves a better grade.
I have noticed that most of the grade A reports are primarily focused on the protocol's core aspects. However, my focus has mainly been on the codebase. Nevertheless, I believe I have provided valuable insights in terms of code quality suggestions, protocol overview, and identified risks based on my analysis.
Please provide some suggestions for enhancing the quality of my analysis reports. It's worth noting that most of my analysis reports are centered around the codebase.
Thank you,
Hi @sathishpic22, Unfortunately, the provided report does not meet the criteria of an advanced-analysis report. It appears to predominantly consist of a repetition of existing documentation and a listing of submitted findings in your QA and Gas Reports, many of which have been deemed invalid.
Thank you so much for your valuable comments. This will surely help me to improve my analysis reports and rectify my mistakes.
On Sat, Sep 16, 2023 at 3:49 AM Dravee @.***> wrote:
Hi @sathishpic22 https://github.com/sathishpic22, Unfortunately, the provided report does not meet the criteria of an advanced-analysis report. It appears to predominantly consist of a repetition of existing documentation and a listing of submitted findings in your QA and Gas Reports, many of which have been deemed invalid.
— Reply to this email directly, view it on GitHub https://github.com/code-423n4/2023-08-shell-findings/issues/230#issuecomment-1721943903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOA6PHNJQA3FJGHZLXSKEJ3X2TIADANCNFSM6AAAAAA4BX743Q . You are receiving this because you were mentioned.Message ID: @.***>
See the markdown file with the details of this report here.