- The switch lives on chain. The market names a per-market approvals contract, read with
loanApprovals(). The market admin (DEFAULT_ADMIN_ROLE) sets it. - Approvals are signed on chain, by the market admin or by a wallet that holds
LOAN_APPROVER_ROLE. - One approval admits one draw of at most the approved amount until
validUntil. The draw consumes it. - Repayment, closing, collateral moves and liquidation never need an approval.
txHash confirms it.
Switch it on
The market’s creator can ask for approve-only loans at deployment withapproveOnlyLoans on Deploy Market. The deployment itself is unchanged on chain. The wish is recorded and becomes the setup step enableLoanApprovals for the lender of record after adoption. Get Loan Approvals shows it as requested: true until the lender of record switches it on.
A market created with approveOnlyLoans: true hands out no loan calldata through the API until the lender of record signs the switch. Until then Open Loan and Borrow More answer 409 LOAN_APPROVALS_PENDING. The market admin can also clear the request by switching approvals off. The contract itself enforces approvals only once the switch is signed.
The market admin switches approve-only loans on or off with Set Loan Approvals. Switching on takes up to two signatures: the first builds the market’s approvals contract, the second names it on the market.
Get Deployment Options says in loanApprovals.available whether the network carries approve-only loans.
Who approves
LOAN_APPROVER_ROLE approves and revokes loan approvals, nothing else.
Flow
- Request. The borrower side asks for an approval with Create Loan Request: the wallet, the amount, and the loan when it is an additional draw. A new request by the same instance for the same wallet and loan replaces its earlier waiting one.
- Decide. The lender of record approves with Approve Loan Request, or declines with Decline Loan Request. It may approve the requested amount or less. While the request is still
REQUESTED, the borrower side can withdraw it with Withdraw Loan Request. - Draw. The borrower opens the loan with Open Loan or draws with Borrow More. Without a covering approval both answer
409 LOAN_APPROVAL_REQUIRED. With one, the prepared response carriesloanApproval. - Used. When the open-loan or borrow-more confirm sees the approval consumed, the request becomes
USED.
409 APPROVAL_IN_FORCE. Revoke it first, then approve again. A lapsed approval can be replaced directly.
Lost or replaced approver wallet
An approval does not name the wallet that signed it. Removing an approver from the market does not withdraw what it approved. The market admin voids every approval of the market at once with Revoke All Loan Approvals. Approvals also survive a switch off and on, so revoke all before switching approvals back on when the earlier ones should not return.Validity
An approval is valid until itsvalidUntil. Through the API it runs at most 29 days (validHours from 1 to 696, default 72). The contract allows at most 30 days.
States
nextStep on a request says what your side does next: APPROVE_OR_DECLINE, WAIT_FOR_BANK, OPEN_LOAN, WAIT_FOR_BORROWER or NONE.
Limits
Limits are per instance. An instance keeps at most 3 waiting requests per wallet and 25 per market, and a further one is refused with429 LOAN_REQUEST_LIMIT. Requests by different instances for the same wallet do not block each other. 409 LOAN_REQUEST_OPEN only means the same instance made the same request a moment ago.
List Loan Requests pages the queue with limit and offset. Open requests come first, so a waiting request is never cut off by newer history.
What Trusset never receives
- Personal data. The routes carry no personal data fields and refuse them with
PERSONAL_DATA_REFUSED.externalReferencetakes 1 to 64 letters, digits, dots, underscores or hyphens, for your own case number. - A key. Every on-chain write is signed by the wallet that holds the role.
