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.

Sign up for GitHub

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

Jump to bottom

Upgraded Q -> 2 from #382 [1709854904599] #407

Closed
c4-judge opened this issue Mar 7, 2024 · 5 comments
Closed

Upgraded Q -> 2 from #382 [1709854904599] #407

c4-judge opened this issue Mar 7, 2024 · 5 comments
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value duplicate-205 unsatisfactory does not satisfy C4 submission criteria; not eligible for awards

Comments

@c4-judge
Copy link
Contributor

c4-judge commented Mar 7, 2024

Judge has assessed an item in Issue #382 as 2 risk. The relevant finding follows:

[L-01]Signed messages should have deadline
@c4-judge c4-judge added the 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value label Mar 7, 2024
c4-judge added a commit that referenced this issue Mar 7, 2024
@c4-judge
0xHelium issue #407 (File generated from upgraded finding by judge Ma…
1b64d1b 
…rioPoneder)
@c4-judge c4-judge closed this as completed Mar 7, 2024
@c4-judge
Copy link
Contributor Author

c4-judge commented Mar 7, 2024

MarioPoneder marked the issue as duplicate of #205

@c4-judge
Copy link
Contributor Author

This auto-generated issue was withdrawn by MarioPoneder

@c4-judge c4-judge added downgraded by judge Judge downgraded the risk level of this issue QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax withdrawn by judge Special case: this finding was auto-generated by a judge and is now withdrawn; it can be ignored and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Mar 14, 2024
@c4-judge c4-judge reopened this Mar 17, 2024
@c4-judge c4-judge added 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value and removed downgraded by judge Judge downgraded the risk level of this issue QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax labels Mar 17, 2024
@c4-judge
Copy link
Contributor Author

This previously downgraded issue has been upgraded by MarioPoneder

@c4-judge c4-judge added the satisfactory satisfies C4 submission criteria; eligible for awards label Mar 17, 2024
@c4-judge
Copy link
Contributor Author

MarioPoneder marked the issue as satisfactory

@thebrittfactor
Copy link

Judge confirmed via private DM that the withdrawn by judge label should be removed.

@thebrittfactor thebrittfactor removed the withdrawn by judge Special case: this finding was auto-generated by a judge and is now withdrawn; it can be ignored label Mar 20, 2024
@CloudEllie CloudEllie added unsatisfactory does not satisfy C4 submission criteria; not eligible for awards and removed satisfactory satisfies C4 submission criteria; eligible for awards labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value duplicate-205 unsatisfactory does not satisfy C4 submission criteria; not eligible for awards
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@CloudEllie @c4-judge @thebrittfactor