The ten market roles
A market starts with no role holders. The lender of record names them when it takes the market, in one transaction. The guardian is the only role granted afterwards. The first four sit on the market and the next two on its liquidation router. The price signer and the oracle owner act on the price oracle, and the last two own the rate model and the insurance fund.
Two adoption fields therefore carry more than one role. The
admin wallet becomes market admin, router admin and insurance fund owner. The issuer wallet becomes issuer and rate model owner. Set Access Role later grants or revokes the seven roles that sit on the market, the router and the oracle, and Get Access Role checks any address.
Loan approver
A market can run approve-only loans, where every draw needs the lender of record’s approval. The market admin signs approvals, and so does any wallet that holdsLOAN_APPROVER_ROLE.
LOAN_APPROVER_ROLE approves and revokes loan approvals, nothing else. It is granted and revoked by the market admin.
Named at adoption, but not roles
Adoption also names two addresses that carry no capability on the market. Collateral agent (collateralAgent). Recorded as the pledgee on every collateral lock. It can do nothing on the market, the adapter or the router.
Sale recipient (saleRecipient). Where seized collateral goes when the router operator withdraws it for sale.
The wallet that signs the adoption becomes the operator wallet. It is the only address besides registered vaults that deposits into the pool directly, and it receives the operator share of interest. It moves only by its own signature, with Rotate Operator Wallet.
Other parties
These parties act on a market without holding any of its roles.
The deployer can name the register provider of the collateral token on the market, with Set Market Register or on the page of the market in the Issuer Portal, under Asset register. That assignment is a record beside the market and not an eleventh role. It grants nothing on the market, the adapter or the router, and the lending contracts never read it. The register belongs to the token, so only the deployer names or clears it, and the lender of record reads it. The named register provider takes the market into its own instance with Import Market. From then on it reads the pledge record and receives each change as a pledge webhook.
