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.

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

(HAL-02) USE OF WRONG ERROR MESSAGES #590

Closed
SA124 opened this issue Sep 12, 2024 · 1 comment
Closed

(HAL-02) USE OF WRONG ERROR MESSAGES #590

SA124 opened this issue Sep 12, 2024 · 1 comment
Assignees
Labels
bridge Source: Audit Issues discovered by audit.

Comments

@SA124
Copy link

SA124 commented Sep 12, 2024

(HAL-02) USE OF WRONG ERROR MESSAGES

Auditor: Halborn
Severity: Informational

Description
MCR SENDS WRONG ERROR MESSAGE ON BLOCK ALREADY COMMITED
In the MCR.sol contract, the error message returned when the proposed block commitment height is behind the tolerable block height is AttesterAlreadyCommitted which can be confusing, as it is not describing the issue and is also used for when the attester tries to submit the same block commitment twice.

Screenshot 2024-09-12 at 12 19 33 PM

Recommendation
It is recommended to:

Replace the MCR error message by a more understandable message such as BlockCommitmentTooFarAhead.
Replace the Bridge error message by a more understandable message such as TimeLockNotExpired.

@andygolay andygolay added Source: Audit Issues discovered by audit. cicd:bridge labels Sep 13, 2024
@0xmovses
Copy link
Contributor

Fixed in #693

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bridge Source: Audit Issues discovered by audit.
Projects
None yet
Development

No branches or pull requests

3 participants