Open c4-bot-4 opened 10 months ago
0xean marked the issue as grade-b
Hi, @0xean
Congrats on the quick judgment.
I want a revisit of this because to me, based on others that are marked as grade-a
, this is also grade-a
for sure.
Other analyses that are marked as grade-a
, but are worse than ours.
@141345 please comment on grading here.
I want a revisit of this because to me, based on others that are marked as
grade-a
, this is alsograde-a
for sure.
- It covers the whole project structure.
- There are self-made diagrams of the main flows in the protocol.
- It gives appropriate recommendations for different parts of the codebase.
- Mention where the main issues are (do not explain them in it because this is an analysis, not an issue report).
Other analyses that are marked as
grade-a
, but are worse than ours.
- Analyses that only explain issues and do not cover the analysis points and structure.
- Analyses that explain file by file, without structuring anything, no flow path, images, etc.
my question is, do the following add any value to the sponser?
With regard to the analysis part, it is not as detailed as 380, 420, that's why I think this is a good analysis report, but not best
I'm not saying it's the best, but it's certainly better than others that are grade-a
.
For example: #223, #386 - only provide auto-generated contract flow, deployment gas costs, etc.
Will take the note to give more security value to the sponsor rather than just explaining.
Thanks.
I'm not saying it's the best, but it's certainly better than others that are
grade-a
.For example: #223, #386 - only provide auto-generated contract flow, deployment gas costs, etc.
Will take the note to give more security value to the sponsor rather than just explaining.
Thanks.
I'm not giving diagrams significant weights. Because nice graphs do not add value to sponsors in my opinion. 223 and 386 both give some suggestions and codebase/test feedback, which could be helpful to improve the protocol from different level.
This is analysis report, not summarize/drawing.
See the markdown file with the details of this report here.