The emergencyRevoke function in RAACReleaseOrchestrator transfers unvested tokens back to the contract itself (address(this)) without any mechanism to redistribute or manage these tokens.
the issue can appear here :
so When emergencyRevoke is called:
The schedule is deleted but the categoryUsed amount remains unchanged.therefore For new vesting schedules:
The categoryUsed tracking means:
Previous allocations still count against the category limit
New schedules must fit within remaining allocation
Revoked tokens can't be reused because their allocation remains counted
tokens transferred to address(this) by emergencyRevoke are truly locked.
Manuel review.
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.