페이지를 넘기고 있습니다.
다음 장을 불러오고 있습니다…
잠깐… 나만의 읽기 환경을 만들어 보세요.
글꼴과 테마는 화면 설정에서 설정하세요. 눈의 편안함도 중요합니다.
다음 장을 불러오고 있습니다…
Permission for another address to borrow against borrowing capacity provided by a collateralized account, subject to the lending protocol's rules.
브라우저의 읽어주기 지원을 확인하는 중…
이 읽기 자료는 현재 영어로 제공됩니다. 인터페이스에는 선택한 언어가 적용됩니다.
영어 원문 읽기 →In Aave, a collateral supplier can authorize another address to draw debt against the supplier's position. The permission is recorded through the relevant debt token's delegation mechanism. It does not create collateral out of nothing or remove the protocol's solvency checks. The delegator's position supplies the borrowing capacity, while the authorized borrower can receive the borrowed assets. Debt and collateral accounting remain essential to understanding who can lose money.
Suppose Alice deposits collateral and authorizes Bob to borrow up to a specified amount. Bob can receive funds while Alice's position carries the associated debt exposure. If collateral prices fall or interest accumulates, that position can approach liquidation. A separate agreement might require Bob to repay Alice, but an agreement outside the protocol is not automatically enforced by the lending pool. Delegation therefore combines on-chain authorization with a potentially separate credit relationship.
Check the exact debt token, permitted borrower, borrowing allowance, collateral configuration, and health factor. Revoking unused borrowing permission does not erase debt already created, and additional collateral does not ensure a borrower will voluntarily repay. Interfaces sometimes request credit delegation as part of a convenience operation such as borrowing and unwrapping a native asset; that should not be confused with granting an unknown person an open credit line. The economic effect depends on the precise transaction being signed.