"As Twitter user Bill Papas explained, the attacker could extract Loopscale's Interface Description Language from the deployed binary, then analyze transaction patterns to recreate functionality locally - essentially reading the lock's blueprint while everyone thought it was safely hidden."
Oh jeez