The contract is designed to allow users to store their own secret vaults at their respective addresses through the set_secret()
function
However, the get_secret()
function only retrieves secrets from a hardcoded owner address, creating a fundamental mismatch between storage and retrieval operations
Likelihood:
Every user who calls set_secret()
will store their vault at their own address
Every call to get_secret()
will fail for regular users since it only reads from the owner address
Only the hardcoded owner address can successfully retrieve secrets, but only if they also stored one
Impact:
Complete loss of functionality for all users except the hardcoded owner
User secrets become permanently inaccessible after storage
Broken contract logic renders the system unusable for its intended purpose
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.