Дослідження з перевіркою джерел: AAVE VS LIDO EXIT

Decision Matrix

Source Map

• Aave Protocol Documentation: Market Operations (aave-market-operations)
• Aave Help: Withdraw Tokens (aave-withdraw)
• Lido Docs: WithdrawalQueueERC721 (lido-withdrawal-queue)
• Lido Docs: Public Risk Disclosure (lido-risk-disclosure)

Control Notes

1. Position type

Position type is the decision point where public documentation must become an operating rule. In this package, it means Aave lending collateral and Lido liquid staking token exits solve different jobs. The practical action is to name the object before signing: supplied collateral, debt-backed collateral, stETH or wstETH. The unresolved edge is wallets that aggregate both positions into one balance, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Health factor

Health factor is the decision point where public documentation must become an operating rule. In this package, it means Aave withdrawal can change borrow safety when supplied assets support debt. The practical action is to preview the health-factor impact and repay or add collateral before withdrawing. The unresolved edge is future price movement after the preview, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Queue state

Queue state is the decision point where public documentation must become an operating rule. In this package, it means Lido protocol exit may depend on withdrawal queue and finalization status. The practical action is to track request, unstETH NFT, finalization and claim as separate evidence. The unresolved edge is future Ethereum validator exit congestion, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Secondary market

Secondary market is the decision point where public documentation must become an operating rule. In this package, it means Lido users may exit through swaps outside the protocol but then accept venue liquidity and price risk. The practical action is to separate protocol redemption from DEX or CEX swap execution. The unresolved edge is slippage during stressed liquidity, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Approval path

Approval path is the decision point where public documentation must become an operating rule. In this package, it means both workflows can require wallet approvals or contract calls. The practical action is to read the wallet request and avoid blind approvals for helper contracts. The unresolved edge is front-end spoofing or wrong-chain prompts, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Evidence log

Evidence log is the decision point where public documentation must become an operating rule. In this package, it means debug evidence should prove the route without exposing wallet secrets. The practical action is to record official URL, chain, transaction hash, non-secret status and stop rule. The unresolved edge is private wallet recovery details, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Stop rule

Stop rule is the decision point where public documentation must become an operating rule. In this package, it means exit should pause when route, queue, collateral or price outcome is unclear. The practical action is to stop before signing if health factor, unstETH status or output token cannot be verified. The unresolved edge is manual override governance under volatility, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• wallets that aggregate both positions into one balance
• future price movement after the preview
• future Ethereum validator exit congestion
• slippage during stressed liquidity
• front-end spoofing or wrong-chain prompts
• private wallet recovery details
• manual override governance under volatility

Practical Takeaway

Aave and Lido expose very different exit controls even when both involve Ethereum assets. Aave documentation frames withdrawal around supplied assets, collateral use, health-factor impact and wallet transaction approval. Lido documentation frames protocol-level stETH exit through a FIFO withdrawal queue, an unstETH NFT and later claim, while its risk disclosure separates protocol withdrawals from secondary-market swaps. The decision outcome is to map whether the user is reducing lending collateral or unstaking liquid-staking tokens, then document queue timing, health-factor effect, approval path, secondary-market slippage and the stop condition before moving funds. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.