Token Standard Audit Checklist Form
Review a token implementation against its declared standard.
Token and Standard Identification
Token name, symbol, and implementation address are recorded.
Declared token standard and version are identified.
Network or deployment environment is documented.
Implementation source or verified contract reference is available.
Interface and Required Functions
Required standard interfaces are implemented.
Required functions use the expected names, inputs, and return values.
Function visibility and mutability match the standard's requirements.
Unsupported or optional functions are clearly identified and behave as documented.
Metadata and Identifiers
Required metadata fields are present and correctly formatted.
Token name, symbol, and precision or decimal settings match the declared standard.
Identifiers and interface-detection responses are consistent with the implementation.
Metadata behavior is documented, including any mutable or externally hosted values.
Transfer and Approval Behavior
Transfers follow the standard's expected balance and authorization rules.
Approval and allowance behavior matches the standard's requirements.
Transfer and approval functions handle zero, boundary, and insufficient-balance cases as expected.
Failure behavior and emitted events are consistent for transfer and approval operations.
Permissions and Administrative Controls
Privileged roles and their permitted actions are documented.
Role assignment and revocation follow the intended access-control model.
Administrative functions are appropriately restricted and tested.
Pause, upgrade, mint, burn, or other privileged controls are documented where applicable.
Event and State Consistency
Required events are emitted with the expected names and values.
Event emission is consistent with successful state changes.
Balances, allowances, and aggregate values remain internally consistent after operations.
State and event behavior is consistent across relevant functions and execution paths.
Edge Cases and Failure Handling
Zero-value and boundary-value inputs are handled as specified.
Invalid inputs and unauthorized calls fail safely and predictably.
Insufficient balances, allowances, or other resources are handled as expected.
Failure cases do not leave partial or inconsistent state changes.
Security Review
Access control and privileged operation risks have been reviewed.
Reentrancy, arithmetic, and other implementation-specific risks have been assessed.
External calls and dependencies have been reviewed for trust and failure assumptions.
Known vulnerabilities and relevant security advisories have been considered.
Test and Evidence Review
Automated tests cover required standard behavior and interface conformance.
Tests cover relevant edge cases and expected failure paths.
Test results, tooling, and environment are documented and reviewable.
Supporting evidence, such as source references or execution traces, is recorded.
Findings and Remediation Status
No conformance findings identified.
Findings are documented with severity and supporting evidence.
Remediation actions and owners are recorded for open findings.
Retesting or follow-up review is complete or scheduled.
Submit Audit Checklist
Should be Empty: