Closed SeiyaKobayashi closed 1 year ago
We don't need the other way around (e.g. enableModel()
), just because there is no use-cases / motivation for users to do so. If model is updated, IPFS issues totally different content ID for the updated one, leading users to call registerModel()
again instead of calling enableModel()
.
📝 Overview
Implement
disableModel()
function ofVerifier
contract.🖋 Details
This function should soft-delete the registered model using a flag field (e.g.
isDisabled
). Hard-deletion should be avoided to prevent model developers from re-registering same models (could be a potential attack when this contract becomes incentivized).📚 References
n/a