SUIBROKERS DAO · field note
How to fund a Sui wallet before using an app
A practical path from a verified funding source to a Sui wallet with the intended network, asset, and gas balance.

Funding a Sui wallet is a handoff between a source service and an onchain address. The useful checkpoint is concrete: the intended asset arrived on Sui mainnet at the address you selected, and the wallet has the gas needed for the action you plan to review.
Separate purchase, transfer, and app use
Buying SUI, transferring it to a wallet, bridging an asset, and connecting that wallet to an app are four different actions. A provider can show a completed purchase while the withdrawal is pending. A bridge can deliver an asset on a network the target app does not support. A wallet connection identifies an account; it does not authorize a later transaction.
The official Sui getting-started guide provides general orientation around wallets and ways to obtain SUI. It does not select a provider or guarantee regional availability. Before paying or withdrawing, inspect the provider's current identity, custody, limits, fees, network selector, and withdrawal terms. Use a source you can independently identify and contact.
Check the destination before sending
Choose a compatible wallet and keep its recovery method private. Copy the destination address only after checking it in the wallet, then compare it again in the source service. Confirm Sui mainnet, the intended amount, and the asset type. A ticker such as SUI or USDC is not enough if the same symbol appears on another network or a bridged coin has a different full type.
For a first transfer, a small hypothetical amount can help confirm the address and network before a larger action, but it is still a real transaction with its own gas and provider terms. Do not treat a test transfer as proof that every later asset or application route is supported.
Leave room for the first action
SUI is commonly used for Sui transaction gas. The exact charge depends on the transaction's computation, storage, rebate, gas price, and budget. The Sui gas guide explains why a fixed reserve cannot be promised from a general article. Keep gas separate from an application commission or a route's price impact.
Before connecting to an app, check the wallet's current SUI balance and the action's gas details. If the app requests a transfer, swap, or package call, compare the account, network, asset, amount, recipient, and output with the signing prompt. Reject a prompt that does not match; a provider's successful withdrawal message cannot correct a wrong destination.
Follow the handoff
After the source says “sent,” use the transaction hash or provider receipt to follow the transfer until the wallet shows the expected asset. Then verify the full coin type and amount in the wallet or explorer. Only after that should you connect to an application. A route quote or provider preview is a proposal; the signed digest and resulting effects establish the network action.
For a current Sui application example, Swap can prepare a route after a compatible wallet connects, but the wallet still controls signing. The example teaches the handoff boundary; it is not a recommendation of a provider, route, or outcome.
If the transfer is missing, stop and collect the source network, destination address, asset type, amount, and transaction hash. If the asset is present but the app cannot use it, check the target's supported network and full type before sending anything else.
Related checks: wallet ownership and signing, a first Sui transaction, and USDC identity on Sui.