# What should an Algorand wallet explain before a newcomer’s first transaction? **URL:** \ **Category:** General\ **Created:** [September 25, 2026, 11:42am UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486 "2026-09-25T11:42:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Anzus\_GemWallet](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/anzus_gemwallet/32/4059_2.png) [@Anzus\_GemWallet](https://forum.algorand.co/u/Anzus_GemWallet)\ **Post date:** [September 25, 2026, 11:42am UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486/1 "2026-09-25T11:42:49Z")
Algorand is fast and inexpensive to use, but some wallet behavior may not be obvious to someone using it for the first time. A newcomer may see ALGO in their account without realizing that part of it must remain because of minimum-balance requirements. Receiving an Algorand Standard Asset may require an opt-in, which also affects that minimum balance. Assets can have similar names, so checking the correct asset ID matters. Rekeying is another useful feature that can be misunderstood if it is presented like a normal password change. If you were helping someone use an Algorand wallet for the first time, which concept would you explain first? Is there anything else wallets should explain at the moment it becomes relevant instead of leaving users to find it in documentation? For transparency, I work in BD and support with [Gem Wallet](https://gemwallet.com/), an open-source self-custody wallet that supports ALGO and Algorand Standard Assets. I’m interested in what guidance could prevent avoidable mistakes for newcomers. What surprised or confused you when you first started using an Algorand wallet? ---
**Author:** ![scholtz](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/scholtz/32/864_2.png) [@scholtz](https://forum.algorand.co/u/scholtz)\ **Post date:** [September 25, 2026, 1:19pm UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486/2 "2026-09-25T13:19:24Z")
i dont think the users should be worried with specific algorand requirements like minimum balance or opting to the assets.. its not the wallet role to solve this.. it is the dApp role to solve this.. and best dApps will use tools like biatec gas station, so that the user does not even notice that he has to have some mbr.. its really by the use case that dApp is solving.. if the use case is profitable enough so that the business owner can take the super low algoran network fees and mbr up to him self and just present user to do the business with him, it is quite undesirable from the wallet side to block or complicate any onboarding process that is the reason why in the Biatec wallet, the first account is created right away when the user just enters his password which is used to encrypt the data.. and he can connect the dApp with empty account.. yes, he can do all additional stuff like asset optin later, but the onboarding to algorand should be done in the dApp, not in the wallet itself ---
**Author:** ![Anzus\_GemWallet](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/anzus_gemwallet/32/4059_2.png) [@Anzus\_GemWallet](https://forum.algorand.co/u/Anzus_GemWallet)\ **Post date:** [September 26, 2026, 3:18am UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486/3 "2026-09-26T03:18:00Z")
Thanks, that’s a useful distinction. I agree that onboarding should not overwhelm users with protocol details when a dApp can handle them in the background. I was thinking more about cases where someone manages ALGO or ASAs directly in the wallet and encounters an unavailable portion of their balance or an opt-in requirement. In those moments, would a short explanation from the wallet be helpful, or do you think that should still be left entirely to the dApp? ---
**Author:** ![scholtz](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/scholtz/32/864_2.png) [@scholtz](https://forum.algorand.co/u/scholtz)\ **Post date:** [September 26, 2026, 8:29pm UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486/4 "2026-09-26T20:29:37Z")
Biatec Wallet does have the FAQ section where users can find more about the algorand ecosystem and processes if you are looking for this type of answer 🙂 > **[Community Algorand Wallet - Biatec Wallet](https://wallet.biatec.io/faq)** > > Free open source algorand wallet created by community for community. ---
**Author:** ![Anzus\_GemWallet](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/anzus_gemwallet/32/4059_2.png) [@Anzus\_GemWallet](https://forum.algorand.co/u/Anzus_GemWallet)\ **Post date:** [September 27, 2026, 1:34am UTC](https://forum.algorand.co/t/what-should-an-algorand-wallet-explain-before-a-newcomer-s-first-transaction/15486/5 "2026-09-27T01:34:07Z")
Thanks, I’ll take a look. Keeping detailed explanations in an optional FAQ, while showing only a short message when a user encounters an issue, sounds like a reasonable balance between simple onboarding and clear guidance.