bitpontInspect the account
Inspect the Safe and its available USDC.
Supply Safe USDC to Aave on Ethereum
The Safe receives the lending position. Its signing owner authorizes the operation and pays gas from a separate balance. This operation uses the Safe on Ethereum.
EthereumSafe 1.4.1 multisigOne reviewed Safe operation
Set up your operation ↓Ethereum · ETH for network fees
← All multisig lending actions on Ethereum
- 01Inspect Safe
- 02Prepare proposal
- 03Collect approvals
- 04Review execution
Inspect your Safe
Choose the network and enter your Safe address to read owners, balances and approval requirements.
Capabilities depend on the selected network.
Connect an owner wallet and enter your existing Safe. Funds belong to the Safe; the connected owner pays network gas.
USDC on Aave V3
Supply Safe USDC to Aave
Other networks and operations remain available in the complete Treasury history.
Payment runs
Up to 500 recipients, split into transactions of at most 50 payments. Each transaction needs its own Safe approvals and gas. Completed batches stay recorded; an unresolved batch blocks the next one.
Other networks and operations remain available in the complete Treasury history.
Saved proposals
Saved on this device. A saved proposal is not proof of approval or execution. Refresh its nonce and onchain status before acting.
Transactions & recovery
A clear path from intent to result.
Review the operation
Enter the exact USDC deposit and review the allowance and supply calls.
Verify the result
Collect owner approvals, execute and refresh the supplied balance.
Supply Safe USDC to Aave explained.
Who owns the lending position?
The Safe receives aUSDC; the connected owner does not receive the deposit.
Can I withdraw it later?
Use the withdrawal action. Available reserve liquidity and the Safe’s collateral obligations determine what can be withdrawn.
Keep the exit available.
Withdraw supplied USDC or reduce variable debt from the same Safe. Withdrawals depend on available liquidity and the Safe’s collateral health. Lending supports the existing USDC reserves on Ethereum and Base.
Streams keep paying until they are stopped or the protocol terminates them. Keep sufficient USDCx for ongoing payments and protocol buffers. Safe owner approvals take time; do not wait for the balance to run out.
Stop a direct payment stream or pool stream, then unwrap the available USDCx balance. Claimed distribution funds remain in the Safe until a separate payment or unwrap is approved.
New pools use nontransferable units and admin-only distribution. Pool ownership, balances, units and fees are read again before execution. Safe modules and guards can impose additional behavior or permissions.
These tools use your selected wallet. Safe assets require a Safe-approved operation; the owner wallet and Safe have separate balances.
Account, asset and execution
The Safe receives the lending position. Its signing owner authorizes the operation and pays gas from a separate balance. This operation uses the Safe on Ethereum.
- Funds are held by
- Safe 1.4.1 multisig
- Network fees are paid in
- ETH
- Native USDC contract
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
Balances and execution conditions are checked again before signing. A saved page is not a balance or liquidity quote.
Continue on Ethereum
All Ethereum tools →
EthereumWithdraw Safe USDC from Aave
Safe 1.4.1 multisigThe withdrawal returns USDC to the Safe. Supplied value and immediately withdrawable value can differ when liquidity or collateral requirements limit the exit.
USDCOpen toolEthereumRepay Safe USDC debt
Safe 1.4.1 multisigDebt can accrue interest between preparation and execution. A full repayment uses a maximum spend; insufficient limits cause the operation to revert.
USDCOpen toolEthereumRepay debt with supplied USDC
Safe 1.4.1 multisigThis repayment consumes the Safe’s aUSDC instead of spending USDC from its wallet. Supplied assets and variable debt are checked separately.
USDCOpen tool