Folks finance deposits on Algorand require ALGO beyond the deposit amount
Folks finance requires you to leave room for ALGO transaction fees and minimum balance requirements when making your first Algorand deposit. The amount you can deposit therefore depends on your spendable balance, the selected asset, and any setup transactions. Confirm the resulting deposit before committing more funds.
On this page
Your first Algorand lending deposit needs enough spendable ALGO to cover transaction fees and any additional account requirements.
Depositing ALGO and depositing another asset need different budgets
An ALGO deposit draws its principal and transaction costs from the same currency balance, so choosing the amount requires some subtraction. Your wallet’s total ALGO balance includes funds it may need to retain for existing account requirements. The proposed deposit must also accommodate any new setup requirements and the fees payable by your account.
With another supported deposit asset, the principal and ALGO budget are separate. Reducing that token’s deposit amount doesn’t necessarily solve an ALGO shortage because it doesn’t replenish the currency paying the fees. In either case, the relevant balance belongs to the connected Algorand account. Funds held in a different account don’t automatically cover its transactions.
Check the account and proposed deposit before signing
The connected address, available asset balance, and proposed transaction details establish whether the first deposit matches the action you intend to authorize.
The account holding the funds
Check the full connected address and network, especially when your wallet manages several accounts. Record the starting balance of the deposit asset and the account’s ALGO balance. A spendable balance already accounts for some restrictions; a total balance doesn’t necessarily do so. Avoid subtracting the same reserved amount twice when comparing wallet displays. These starting records also help explain the later balance change without treating every ALGO reduction as a fee.
The amount and authorization request
The Algorand deposit workflow lets you select an available asset, enter an amount, and authorize the operation through your wallet. Review the complete request, including transfers, fees, and any setup actions. Connecting a wallet alone doesn’t perform the deposit. An unexpected asset, amount, or account is a reason to stop before signing.
How much ALGO should remain outside the first deposit?
The required amount covers existing balance restrictions, additional setup funding, and transaction fees, with spendable ALGO left for any intended follow-up transaction.
Fees paid for the operation
A deposit can contain several transactions, so a single transaction’s base fee isn’t the complete operation cost. Algorand supports pooled fees within a transaction group. One transaction can therefore carry fees covering others in that group. Read the aggregate fee your account will pay rather than treating a zero-fee entry as a free deposit. Network conditions and the actual transaction construction also affect the required fee.
ALGO retained or supplied for setup
Minimum balance requirements restrict how much ALGO an account can spend while it maintains particular resources. They differ from transaction fees, which pay for execution. A first interaction can also include funding for protocol setup, so its ALGO requirement can exceed a later deposit’s requirement. Review where each amount goes: ALGO remaining in your wallet and ALGO transferred to fund another account won’t appear in the same balance. There isn’t one first-deposit reserve suitable for every account.
A smaller ALGO deposit versus funding the wallet first
When an intended ALGO deposit would consume the available reserve, compare reducing the deposit with adding ALGO to the same account first. For either choice, check that the deposit amount and costs fit before signing. After confirmation, verify the deposit and remaining spendable ALGO. The first choice changes the principal; the second preserves it only if the added funds cover the shortage.
- If a smaller deposit leaves enough ALGO for the displayed requirements, revise the amount before authorizing it.
- If keeping the original amount requires more ALGO, wait until the added funds appear in the connected account.
- Once the amount and costs fit, submit the deposit through the deposit control and approve the matching wallet request.
- After submission, retain the transaction identifier and compare the confirmed operation with the starting balances and resulting deposit.
- Continue only when those records agree and the remaining ALGO covers the next intended action. Wait while confirmation is unresolved; stop if the recorded asset or amount differs.
A funding transfer alone doesn’t establish that the lending deposit happened. Likewise, approving a reduced amount doesn’t establish completion until the deposit transaction confirms.
What proves the first deposit completed?
A confirmed deposit transaction and a matching deposit balance establish completion more reliably than a wallet approval message or a projected yield.
A positive confirmed-round value identifies a transaction committed to the Algorand ledger. A pending transaction remains unresolved, while a rejection supplies a different reason for investigation. The confirmed record identifies what actually executed, including transaction fees. The deposit display should correspond to the intended asset and amount, allowing for its stated units and rounding.
A slow page refresh isn’t a reason to authorize another deposit. Check the submitted transaction’s status before creating a replacement request. A displayed interest rate describes potential accrual under the pool’s terms; it doesn’t prove that your funds entered the pool. Borrowing is also a separate action, so the presence of a lending deposit doesn’t establish a new debt.
Asset opt-ins explain part of the reserved balance
Each Algorand asset opt-in increases the account’s minimum balance requirement by 0.1 ALGO. An opt-in establishes the account’s ability to hold that asset. Its reserve remains relevant even when the asset balance reaches zero, until the holding is closed out. Closing out a holding with a remaining balance transfers that balance, so removing holdings requires attention to the asset and destination.
This explains why a wallet can show ALGO while allowing less of it to move. Existing opt-ins can also make the starting requirements differ between accounts. The per-asset reserve is only one component; it doesn’t describe every application or protocol setup requirement.
Leaving spendable ALGO outside the deposit keeps it available for later transaction costs. Depositing that remainder would increase the lending principal, but it could leave the account needing fresh ALGO before another operation.
Questions and answers about Folks finance
Can ALGO in another account pay for my first deposit automatically?
ALGO in another account doesn’t automatically fund the connected account’s deposit. The transaction group determines which accounts pay its fees and supply any setup funding. A wallet containing several accounts doesn’t combine their balances into one spendable amount. Check the address authorizing the deposit rather than the wallet’s combined portfolio value.
Does selecting the maximum deposit amount reserve ALGO for a later withdrawal?
A maximum deposit amount shouldn’t be treated as confirmation that a later withdrawal’s costs are covered. The proposed transaction describes the operation you’re authorizing now. Any later operation has its own fees and account requirements. Check the ALGO expected to remain spendable instead of assuming the maximum control budgets for future actions.
Are multiple entries in the signing request evidence of duplicate deposits?
Multiple transaction entries can belong to a single deposit operation. Algorand applications use transaction groups to combine related actions, and fees can be pooled across those entries. Review their amounts and purposes together. Several entries within one request are different from approving separate deposit requests for the same intended amount.
Can a failed atomic transaction group leave a partial deposit?
An Algorand atomic transaction group executes in full or doesn’t execute. Separate setup transactions confirmed outside that group can remain completed, however. Distinguish the failed deposit group from other confirmed operations when reconciling balances; a prior setup action isn’t proof that part of the failed group succeeded.
Will closing the browser cancel a deposit I’ve already submitted?
Closing the browser doesn’t cancel a transaction already submitted to the network. Its confirmation, rejection, or expiry determines what happens next. Reopening the application and inspecting the original transaction record is safer than assuming the browser closure prevented execution. A new deposit request can create an additional deposit if both requests execute.
Is a larger first-time ALGO requirement entirely a transaction fee?
A larger first-time requirement can include setup funding as well as transaction fees. The fee fields identify execution charges, while transfers can fund resources the deposit operation needs. Compare those entries separately before describing the entire wallet reduction as a fee. Recovering setup funding depends on the relevant resource and its available removal procedure.