Token Module
ERC20 tokens, authority contracts and adapters for exiting and joining collateral in an out of the system
Relevant smart contracts:
The token module has four distinct parts:
- 1.System Coin: token that the core system considers equal in value to its internal debt unit.
- 3.Protocol Token Authority: authority contract that determines who is eligible to mint and burn protocol tokens.
- 4.Geb Printing Permissions: permissioning system to allow multiple debt auction contracts to mint protocol tokens.
- 5.Token Adapters:
- Collateral Adapters: contracts that allow anyone to join or exit collateral in and out of GEB
- Coin Join: adapter for the system coin to exit the system in the form of an ERC20 and enter the system in the form of
SAFEEngine.coinBalance
- System Coin: this contract is the user facing ERC20 token maintaining the accounting for external system coin balances.
- Protocol Token: a token adhering to the ERC20 standard which also has DSAuth-protected mint and burn functions as well as delegation capabilities. The protocol token has two main use-cases:
- As a governance token: tokens can be used as a representation of voting power
- As a recapitalization resource: protocol tokens can autonomously be minted by the
DebtAuctionHouseand sold for system coins which are used to recapitalize the system in times of insolvency
- Protocol Token Authority: determines who can mint and burn protocol tokens. Can be controlled directly by token holders, by the Protocol Token Authority or in some cases all control can be withdrawn from it.
- Geb Printing Permissions: forces governance to adhere to specific rules in order to allow multiple, independent
DebtAuctionHouses to print protocol tokens. - Token Adapters: these are custom contracts that can allow anyone to deposit and withdraw collateral or they can have whitelisting in place to
- Emergency shutdown cannot be triggered if governance calls
PROTOCOL_TOKEN.stopbeforehand - There is the possibility for a user to have their funds stolen by a malicious adapter which does not actually send tokens to the
SAFEEngine, but instead to some other contract or wallet.
Governance can withdraw their voting power over all contracts, although, if they wish to allow the Protocol Token to protect multiple GEBs, they may retain influence over the Geb Printing Permissions.
All of the contracts in this module are part of Level 1 Gov Minimization.
Last modified 1yr ago