rap_battle.move
Normal behavior: Before any battles, the BattleArena
resource should exist at @battle_addr
so players can join and fight.
Actual behavior:
The module defines a private init_module
, but there is no entry/public call that publishes BattleArena
.
Any call to rap_battle::go_on_stage_or_battle
immediately aborts because the resource does not exist.
Likelihood:
This always occurs on a fresh deployment, since nothing publishes BattleArena
.
First player attempting to start a battle will consistently hit the abort.
Impact:
Battles cannot start at all.
Protocol is effectively bricked until redeployment or manual resource publishing.
Test confirms: go_on_stage_or_battle
aborts immediately when BattleArena
has not been initialized.
Explicitly publish BattleArena
on deployment or add lazy-init logic:
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.
The contest is complete and the rewards are being distributed.