The Token
Project MUST maintain
documentation identifying the parties and contracts that participate
in authorizing key modifications including:
Minting Tokens
Burning Tokens on a user's behalf
Restricting any account's ability to transact (e.g. freezing Token
balances, blocking an account, or any other bespoke functions that limit
user actions or balances)
These functions are core to maintaining the value of a Token.
Identifying responsible parties as controllers of these functions
provides some transparency into who can make changes.
Audit procedures
Determine whether the Token Project's Documentation correctly
identifies relevant Smart Contract code for the functionalities
listed
Determine whether the Token Project's Documentation identifies
parties with control over the relevant code functions
Interview parties to determine whether they actually hold and meet
roles the documentation attributes to them, and follow sound security
practices for authorizing those actions (for example, that no single
party can act alone and that use of those controls is logged)
Success Criteria
All parties able to affect the relevant functionalities are
identified.
Failure Criteria
There is Smart Contract code that is not correctly identified
There are unidentified parties who can affect relevant
functionalities.
Documentation is out of date, following an update in
responsibilities or code update