Handling Permissioned Tokens in the Morpho App
Some loan assets and collaterals supported by the Morpho protocol are permissioned tokens. These tokens require specific contract whitelisting to function properly in the Morpho app (frontend & SDKs).
Indeed, Morpho’s Bundler3 system uses adapters to handle token operations and the main Morpho app and SDK require the general adapter to simulate and execute transactions involving permissioned tokens. If the general adapter is not whitelisted, the bundler flow breaks and users cannot interact with permissioned tokens through the app.
Issuer whitelisting requirements
To enable a permissioned token to work in the Morpho app, the token issuer must whitelist at token level the following contracts:
Morpho— core lending protocolGeneralAdapter1(EthereumGeneralAdapter1for Ethereum mainnet)— required for the frontend and SDK to handle permissioned tokens
All contracts deployments addresses are available in the addresses page.
Without the general adapter whitelisted, the Morpho app cannot simulate or execute user transactions with permissioned tokens.
When listing a permissioned token, curators must review and confirm with the asset issuer that the contracts whitelisting is properly implemented.