Skip to content
by Unity Nodes
Education

What should a NEAR wallet explain before a user sends their first transaction?

3 posts116 views5 likesLast activity Sep 2026

  1. Anzus_GemWalletOP 2

    NEAR’s human-readable account names can make sending funds easier, but the account system can still be unfamiliar to someone arriving from another network.

    A beginner might see a name such as example.near in one place and a long address in another. They may also assume that sending NEAR and sending a token on NEAR work exactly the same way.

    Before a user confirms their first transaction, I think a wallet should clearly explain:

    • Whether the destination is a valid NEAR account.
    • Why some accounts use a readable .near name while others use a long address.
    • Whether the user is sending native NEAR or a token issued on NEAR.
    • The expected network fee and whether any additional account or token requirements apply.
    • Whether an exchange or service requires a memo or other deposit information.
    • What a failed transaction means and whether it is safe to retry.
    • Why testing with a small amount can be useful when sending to a new destination.

    From a support perspective, clear information before confirmation is usually more helpful than a technical error after something fails.

    I work with Gem Wallet in BD and support. Gem Wallet supports NEAR and NEAR tokens, including transfers to .near account names.

    Which part of sending assets on NEAR tends to confuse new users most: account names, long addresses, tokens, fees, or something else?

  2. Mayor_of_Pumpopolis 1

    Give them an option to read the actual transaction data. Include a natural language summary of the transaction if possible. Even if they don’t understand this initially, they should know that this option is available for them in the future. Ideally this would build good habits, where users become more literate over time and review their transactions before signing.

  3. Anzus_GemWallet 2

    That makes sense. A plain-language summary on the main confirmation screen, with the full transaction data available for anyone who wants to inspect it, seems like a good balance.

    It could help users understand what they are approving without overwhelming beginners, while also encouraging them to become more comfortable reviewing transaction details over time. Thanks, this is useful feedback.