yAcademy TODO_protocol_name Review

Fellows:

• Fellow name
• Fellow name
• Fellow name

High Findings

1. High - Finding title (Fellow name that found the finding, can put multiple fellow names here)

Describe the issue here. Examples from past audits are available at https://github.com/YAcademy/audits. Additional style guide recommendations are available at https://github.com/YAcademy-Residents/report-style-guide.

Proof of concept

Link to the line of code that has the problem here. It is best to use a permalink that includes the proper commit hash so the link points to the proper line number even when the file is changed in the future.

Impact

High. Brief summary explaining why this issue is high risk.

Recommendation

Provide your recommendation on how to mitigate this issue.

Medium Findings

1. Medium - Finding title (Fellow name that found the finding, can put multiple fellow names here)

Describe the issue here. Examples from past audits are available at https://github.com/YAcademy/audits. Additional style guide recommendations are available at https://github.com/YAcademy-Residents/report-style-guide.

Proof of concept

Link to the line of code that has the problem here. It is best to use a permalink that includes the proper commit hash so the link points to the proper line number even when the file is changed in the future.

Impact

Medium. Brief summary explaining why this issue is medium risk.

Recommendation

Provide your recommendation on how to mitigate this issue.

Low Findings

1. Low - Finding title (Fellow name that found the finding, can put multiple fellow names here)

Describe the issue here. Examples from past audits are available at https://github.com/YAcademy/audits. Additional style guide recommendations are available at https://github.com/YAcademy-Residents/report-style-guide.

Proof of concept

Link to the line of code that has the problem here. It is best to use a permalink that includes the proper commit hash so the link points to the proper line number even when the file is changed in the future.

Impact

Low. Brief summary explaining why this issue is low risk.

Recommendation

Provide your recommendation on how to mitigate this issue.

Gas Savings Findings

1. Gas - Finding title (Fellow name that found the finding, can put multiple fellow names here)

Describe the gas savings improvement here. Examples from past audits are available at https://github.com/YAcademy/audits. Additional style guide recommendations are available at https://github.com/YAcademy-Residents/report-style-guide.

Proof of concept

Link to the line of code that has the problem here. It is best to use a permalink that includes the proper commit hash so the link points to the proper line number even when the file is changed in the future.

Impact

Gas savings

Recommendation

Explain how to achieve gas savings

Informational Findings

1. Informational - Finding title (Fellow name that found the finding, can put multiple fellow names here)

Describe the informational finding here. Examples from past audits are available at https://github.com/YAcademy/audits. Additional style guide recommendations are available at https://github.com/YAcademy-Residents/report-style-guide.

Proof of concept

Link to the line of code that has the problem here. It is best to use a permalink that includes the proper commit hash so the link points to the proper line number even when the file is changed in the future.

Impact

Informational

Recommendation

Informational explanation summary or mitigation if relevant

Final remarks

Fellow name

A brief summary about what you think of the contract's overall security, possible weaknesses, and areas for the devs to focus on improving.

Fellow name

A brief summary about what you think of the contract's overall security, possible weaknesses, and areas for the devs to focus on improving.

Fellow name

A brief summary about what you think of the contract's overall security, possible weaknesses, and areas for the devs to focus on improving.