Demonstrate the known vulnerabilities for which the
Token Contract has been tested.
Audit procedures
Verify that the Security Audit or attestations provided as evidence for
previous: Pass Code Audit attests that the
Token Contract
conforms to the BSSC Smart Contract Security Standard [SCSS].
If it does not do so, verify that the audit identifies a methodology or set of tested requirements
that is equivalent to the BSSC Smart Contract Security Standard [SCSS]
in the professional opinion of the assessor.
Success Criteria
At least one Code Audit Report attests that the
Token Contract
conforms to the BSSC Smart Contract Security Standard [SCSS].
At least one Code Audit Report attests that the
Token Contract
conforms to a set of requirements equivalent in the professional opinion of the assessor
to the BSSC Smart Contract Security Standard [SCSS].
Failure Criteria
No published code reviews or attestations for the currently deployed
Token Contract
indicate that it has passed the requirements of the BSSC Smart Contract Security Standard [SCSS],
nor that it meets a set of requirements that are equivalent in the professional opinion of the assessor.
Justifiable Exceptions
The code, and its reviews, are old, and there is no published methodology.
The review represented best practice at the time it was done, although it is not
equivalent in the professional opinion of the assessor
to the BSSC Smart Contract Security Standard [SCSS].
Exceptions to meeting the requirement need to be explicitly documented and justified.
Common Failures
Only outdated reports are available following an upgrade
Audit reports provide limited information on assessed requirements or methodology
Audit reports clearly do not assess a set of requirements that are equivalent to
the BSSC Smart Contract Security Standard [SCSS]
Publicly available reports identify vulnerabilities that are not
fixed in the currently deployed Token
Contract