Why does my address need funds to activate?

How to do it

1. Choose the wallet you want to receive into, open Receive and select the correct asset and network.
2. If an activation notice appears below the address, read its network and amount. It concerns this address on this network, not every wallet in Oath.
3. Use the address shown in Receive to fund your own account on that same network. Follow the relevant network section below; sending a token may not activate the native account.
4. Check the sender’s review before confirming. Allow for any sender fee or exchange withdrawal fee so the amount actually received meets the requirement.
5. After the transfer confirms, reopen Receive to check again. On Gram (TON), funding and deploying the wallet contract are separate steps, so funding alone can leave a deployment notice.

Why a new address can need funding

Creating or importing a wallet gives you an address before that address necessarily exists as an account on the blockchain. Some networks require a reserve, some require funds for storage, and some deploy a wallet contract. These rules help limit spam and pay for maintaining or processing on-chain data. They are network rules, not an Oath subscription.

Oath does not charge or collect an activation fee. Fund the receiving address in your own wallet, not an address supplied by someone claiming to activate it for you. Network transaction fees, network account-creation charges, storage costs and an exchange’s withdrawal fees can still apply. Oath cannot waive these charges or change a network’s reserve.

A reserve or storage deposit is different from a fee: it may stay in an account while being unavailable to spend. A network fee is consumed under that network’s rules. Do not assume that every amount called activation is refundable.

Stellar (XLM): a minimum account balance

An ordinary new Stellar account needs two base reserves. At the time of this update, one base reserve is 0.5 XLM, so a basic account needs 1 XLM. Oath reads the current ledger reserve for its notice. The sender must use a transfer flow that creates a new Stellar account; an ordinary payment to a nonexistent account is not enough.

The reserve remains in your Stellar account; Oath does not receive it. It normally cannot be spent while the account requires it. Trustlines and other ledger entries can increase the minimum, commonly by another base reserve each. For example, holding an issued token can require a trustline in addition to activation. Sponsored reserves can change who supplies the balance. Keep extra XLM available for transaction fees; sending an issued token alone does not create an ordinary new account.

Source: https://developers.stellar.org/docs/learn/fundamentals/lumens

XRP Ledger (XRP): the base reserve

A new XRP Ledger address becomes an account when it receives enough XRP to meet the base reserve. The published Mainnet base reserve is currently 1 XRP; Oath uses the validated ledger’s current value. Additional owned objects can raise the reserve, currently generally 0.2 XRP per item, with exceptions and sponsorship rules.

Reserved XRP stays in the account and is normally unavailable for ordinary payments. It is not paid to Oath. Network transaction costs are separate and can consume XRP even below the reserve. Qualifying account deletion can recover part of a reserve, but has its own network rules and cost; removing a wallet from Oath does not delete its on-chain account. Activate with XRP first, not an issued token. An already existing account can receive smaller XRP payments.

Source: https://xrpl.org/docs/concepts/accounts/reserves

Solana (SOL): account funding and token-account deposits

Solana accounts need enough SOL for their rent-exempt balance, which depends on the space they use. For an address that does not yet have a native account, Oath asks the network for the current minimum for a basic account rather than assuming every account needs the same amount. The SOL remains in that account; it is not an Oath activation payment. Keep additional SOL for future transaction fees.

USDC, USDT and other Solana tokens live in separate token accounts. A sender can create the required token account and fund its deposit while transferring a token, even if the wallet owner has no SOL balance. Receiving tokens therefore does not prove the owner’s native SOL account is funded. A token-account deposit is separate from the transaction fee; eligible token accounts can be closed to reclaim their remaining SOL under the token program’s rules. Account size and token extensions can change the deposit.

Source: https://solana.com/docs/core/accounts/account-structure

Source: https://solana.com/docs/tokens/basics/create-token-account

Source: https://solana.com/docs/tokens/basics/close-account

TRON (TRX): account creation paid by the sender

A newly generated TRON address is activated by receiving TRX or a TRC-10 transfer from an existing account, or by an account-creation operation. Receiving only a TRC-20 token such as USDT does not perform that native-account activation.

For standard activation, the sender pays the network account-creation charge: currently 1 TRX, plus a possible 0.1 TRX creation Bandwidth charge when staked or delegated Bandwidth is insufficient. Parameters can change. Contract-based activation follows different Energy and Bandwidth rules. These are consumed network charges, not a minimum TRX balance held by the recipient and not an Oath fee. The amount sent to the recipient remains theirs. After activation, TRX or sufficient network resources are still needed to send, especially for TRC-20 tokens. A token transfer’s cost is not fixed by this activation example.

Source: https://developers.tron.network/docs/account

NEAR: creating an implicit account and covering storage

Oath’s generated NEAR address is a 64-character implicit account ID. A native NEAR transfer creates that account on chain and credits the transferred balance. The warning applies to this implicit-address flow; it is not a way to register an arbitrary missing name ending in .near.

Keep enough NEAR for the account’s storage requirements and later transaction fees. Storage usage, account configuration and token-contract registration can affect the required amount, so this guide does not promise one universal activation deposit. NEAR reserved for storage is unavailable for other uses while that storage is required. Token registration can require a separate storage deposit with a token contract, and sending a token does not substitute for creating the native account. Oath does not collect these balances. Any storage refund depends on the account or contract’s supported rules; deleting the wallet in the app does not refund on-chain storage.

Source: https://github.com/near/nearcore/blob/master/docs/DataStructures/Account.md

Source: https://docs.near.org/protocol/storage/storage-staking

Gram (TON): fund, then deploy the wallet contract

Oath displays this network as Gram and its native coin as GRAM. TON wallets are smart contracts. A new address can first receive funds while its contract is still uninitialized. The initial native-coin transfer should be non-bounceable; use the receiving address supplied by Oath and a sender that supports this network.

Funding the address and deploying the contract are different steps. Oath includes the wallet’s deployment data with its first outgoing transaction when required. Until the contract is active, the notice can remain even when the balance is positive. You do not need to repeatedly deposit just because deployment is still pending.

There is no single fixed deposit that guarantees every deployment or transfer. Keep enough native coin for the estimated deployment, transaction and storage costs. The unused balance remains in your account; actual network charges are consumed. Jettons such as USDT do not replace native coin for these costs. Oath does not take an activation fee.

Source: https://docs.ton.org/foundations/status

Source: https://docs.ton.org/foundations/fees

What about the other supported networks?

Oath does not show this account-activation notice for ordinary wallet receipts on Bitcoin-family networks, EVM networks, Sui, Aptos or THORChain. This does not mean transactions are free. Sender fees, minimum transfer or dust rules, token-specific requirements and funds needed for a later outgoing transaction are different questions.

Why the notice appears, disappears or stays visible

Oath checks the selected receiving address in the background. It shows this notice only when the network check confirms an absent or undeployed account. It does not block copying or sharing the address. An account already reported active does not get this activation notice, even if it later needs more funds for fees or other reserves.

A failed or unavailable network check is not proof that an account is inactive, so Oath does not show an activation warning for an unknown result. The absence of this notice is therefore not a guarantee that a transfer will succeed. Check the correct network, address, amount and sender review. Each address and network has its own state; activating one does not activate all your wallets.