Skip to content

Remove opaque // skipped: comments in Bridge freeze flow #762

Description

@nanaf6203-bit

Problem Statement

“skipped: token_id is u64” comments hide a known gap (see #12). Replacing them with real logic and proper events is the goal.

Why it matters

Documentation noise creates a false sense of audit-readiness.

Technical Context

Implement freeze-by-token (#12) and update comments.

Expected Outcome

No // skipped: annotations remain in bridge/src/lib.rs.

Acceptance Criteria

  1. Confirm via grep.
  2. Events emit on every skip case in the future if any legitimate skip remains.
  3. Doc updated.

Implementation Notes

Pair with #12.

Files or modules likely to be affected

contracts/bridge/src/lib.rs.

Dependencies

#12.

Difficulty level

MEDIUM.

Estimated effort

S (~1 day).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions