MintRapperEvent should accurately log the minter as the module owner.
The specific issue is emitting minter: to (recipient) instead of actual minter (@battle_addr).
Likelihood: High
A mint occurs.
Event logs recipient as minter.
Impact: Low
Confusion in off-chain tracking or UIs.
Misattribution of mint actions.
Mint to addr: event shows minter as addr, not @battle_addr.
The intended behavior is the first argument of the event to be the person who receives the token. Therefore, the event emitts correct arguments. You can see the use of `minter` in the test file: https://github.com/CodeHawks-Contests/2025-09-one-shot-reloaded/blob/b4843930562e6f98468a7ca7c99e2c4e1e71d3d9/tests/one_shot_tests.move#L12
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.