The RAACReleaseOrchestrator's emergencyRevoke function currently transfers tokens to itself, which is both redundant and inconsistent with the function's event emission. This should either be removed entirely or the tokens should be transferred to the beneficiary based on the intended behavior.
The issue is:
Emergency revoke removes the vesting schedule
Tokens remain in the contract
The contract has no function to release/withdraw these tokens
release() function only works for active vesting schedules
No admin/emergency function exists to recover these tokens
Tokens become permanently locked in the contract after emergency revoke.
Manual Review
Add functionality to handle revoked tokens.
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.