Problem Statement
The fee logic was reviewed for the fee_bps > 0 cases. The
fee_bps = 0 case (no fee) but fee_recipient is still set — does the
contract skip the fee transfer cleanly? The path is short, partly
covered.
Why it matters
A bug here means users are tipped 100% with fee logic still touching
storage. Risk of confused book-keeping.
Acceptance Criteria
Files/Modules Likely Affected
Difficulty Easy. Estimated Effort XS.
Labels
area:testing, area:fee, priority:medium,
good-first-issue
F. Testing — Coverage / Property
Imported from docs/open-issues-draft.md as draft issue #33 (commit 7becd4b). Original draft-order cross-references in this body have been remapped to current GitHub issue numbers at import time.
Problem Statement
The fee logic was reviewed for the
fee_bps > 0cases. Thefee_bps = 0case (no fee) butfee_recipientis still set — does thecontract skip the fee transfer cleanly? The path is short, partly
covered.
Why it matters
A bug here means users are tipped 100% with fee logic still touching
storage. Risk of confused book-keeping.
Acceptance Criteria
fee recipient changed mid-session.
fee_recipientpanic for these.Files/Modules Likely Affected
src/test.rsDifficulty Easy. Estimated Effort XS.
Labels
area:testing,area:fee,priority:medium,good-first-issueF. Testing — Coverage / Property
Imported from
docs/open-issues-draft.mdas draft issue #33 (commit7becd4b). Original draft-order cross-references in this body have been remapped to current GitHub issue numbers at import time.