Elegance tradeoff: store a hashed confirmation code, or regenerate across all unconfirmed users when a confirmation hit comes in? Hmm...