Tokens integration considerations
As noted in the report written by Runtime Verification after their audit, integration with external smart contract components, especially tokens can be tricky.
As such, integration of tokens in the platform in the form of new pools creation will be closely analysed beforehand.
In particular, the Atlendis Labs team will take the follow criteria into account:
Respect of the ERC20 standard
The ERC20 standard being a set of guidelines to allow for better integration, some tokens follow it closely, some do not. For that reason, the protocol is compatible with known exception, such as the failure to return booleans on transfer, but new ones can appear in the future. For that reason, new tokens integrated into the platform will be closely analysed by the Atlendis Labs team.
Fee charging on transfers
The protocol is currently not compatible with tokens that charge a fee on transfers.
Execution of code before and after transfers
Tokens that allow for arbitrary code execution before and after transfers open a greater attack surface on the protocol. This is not a hard blocker concerning their integration, but the amounts borrowed and the evolution of the total value locked of these tokens in the protocol will be closely monitored.
Token supply evolution
Tokens which supply and individual holders can evolve over time are hard to integrate in a protocol such as Atlendis, and thus will not be supported.
Last updated