5-todo-comment.md

TODO comment

Description

• Vulnerability Category: Best practices
• Severity: Enhancement
• Detectors: todo-comment
• Test Cases: todo-comment

As a best practice, it is recommended to remove TODO comments from the code.

Exploit Scenario

(define-public (mint (recipient principal))
	;; TODO: implement this function
	(ok 1)
)

;; ToDo: Implement the rest of the contract

The vulnerable code example can be found here.

Remediation

Remove unnecessary comments from the code before deploying it.

(define-public (mint (recipient principal))
	;; corresponding implementation
)

The remediated code example can be found here.