Deposit
Move funds into a protocol, account, or position.
A deposit is a transfer of assets into an account, exchange, smart contract, vault, or financial position. In crypto, depositing may credit a custodial balance or place tokens under protocol rules. The user should understand who controls the assets afterward and what must happen to withdraw them.
On a centralized exchange, a user sends funds to an address assigned by the provider. After enough network confirmations, the company credits its internal ledger. The exchange controls the private keys and withdrawal process. Deposits made through the wrong network, missing memo, or unsupported token can be delayed or permanently lost.
In DeFi, a deposit transaction transfers tokens to a contract. A lending market may issue receipt tokens that represent supplied assets plus accumulated interest. A liquidity pool issues LP tokens representing a proportional share. A vault may invest deposits in several underlying protocols. The receipt token can be necessary for withdrawal and may itself carry transfer or collateral value.
Deposits matter because they change custody and risk. Funds in a wallet are exposed mainly to the user's keys and approvals. Funds in a protocol also depend on its code, administrators, oracles, strategy, and liquidity. A displayed APY does not guarantee that principal can be withdrawn at the same value or at any moment.
Before depositing, verify the network, official contract or provider address, token, amount, fees, lockup, caps, and withdrawal path. Read whether assets may be lent or rehypothecated. Use a small test when the destination is new, especially for exchange memos or cross-chain transfers. Keep the transaction hash and records for support and taxes.
Common mistakes include confusing an approval with a completed deposit, sending directly to a contract that requires a function call, or ignoring receipt tokens. Pauses, withdrawal queues, depegs, liquidation, and smart contract exploits can restrict access. Deposit only after evaluating the complete position, not merely the advertised return. Moving assets into a product is a security and financial decision, not just a wallet transfer.
After depositing, verify the credited amount and position through an independent explorer or contract read. Set monitoring for protocol changes and retain enough native currency to pay a future withdrawal fee.
Frequently asked questions
- The wallet approves and transfers assets to a smart contract, which records the user's position directly or issues receipt tokens representing a claim. The protocol may lend, stake, swap, or pool the assets. Receipt tokens can change value or balance as returns accrue. Depositors inherit contract, strategy, asset, oracle, governance, and withdrawal-liquidity risks.
- Network or service fees, pending confirmations, minimum deposits, conversion spreads, locked collateral, unsettled trades, and protocol accounting can reduce the available amount. A failed transaction may also consume gas without depositing. Check the correct network, transaction status, logs, receipt-token balance, and platform terms. Contact official support without ever sharing private keys or recovery words.
- Yes. Protocol administrators or governance may pause deposits during an incident, capacity limit, upgrade, or risk change. Withdrawals can have separate controls and may remain open or also stop. Immutable contracts may lack a pause function. Before depositing, inspect admin powers, caps, queues, lockups, emergency exits, and what users can do if the frontend becomes unavailable.