Read the existing merge record by role
| Field or record | Meaning for this enquiry | What to check next |
|---|---|---|
| account in the merge object | The Stellar address removed by the merge | Do not use an old balance snapshot as current funding |
| into in the merge object | The account receiving the removed account’s lumens | Find the actual destination receipt |
| Operation and transaction result | Whether the intended merge completed | A submitted request alone is insufficient |
| Later exchange payment | A separate payment matching the instruction | Its own sender, recipient, amount and result |
A missing source account needs its history checked before declaring a loss
The Stellar operation reference describes AccountMerge as removing a source account and moving its lumens to a destination. An account lookup performed after that successful operation can therefore tell a different story from an older wallet screenshot. Read the merge and destination evidence before calling the original balance missing.
Consider a fictional owner who consolidated one personal account into another and later opened an old wallet profile to buy Litecoin. The profile can still identify the old address without establishing that this address now holds the spendable XLM. The relevant funding inventory belongs to the account actually credited and controlled by the intended sender.
Reconstruct what already happened without creating a new merge
- Identify the precise operation
Obtain the existing transaction reference, merge operation and result from a trusted history view. Stellar transactions can contain operations, and the operation’s source can be specified separately. Read the account named by the merge rather than assuming the transaction-level source is always the removed account.
- Locate the credited destination
Use the into field and resulting account history to establish where the lumens arrived. If the destination is a hosted account, clarify credit with that provider using the actual existing record. Do not assume a service accepts AccountMerge as an ordinary deposit payment.
- Prepare the separate payment from an available account
Once the current XLM location is established, review the sender’s actual usable amount and current exchange instruction. Keep the Litecoin receiving address independent of the old and new Stellar accounts. Save the later funding reference rather than substituting the account-consolidation record.
Two bookkeeping mistakes to exclude
- Counting both the old screenshot and the destination receipt
- The merge moves the remaining native balance; an old source screenshot is not an additional holding after a successful transfer. Reconcile the same funds once before selecting the exchange amount. Use the current destination balance, allowing for any later activity and the sender’s account requirements.
- Treating every asset as automatically consolidated
- The cited merge description concerns the account’s lumens. Do not infer from its completion that every issued asset, trustline or application position moved to the destination as well. This enquiry concerns native XLM funding; investigate other holdings through their own records and applicable operation details.
Account merge and XLM payment questions
- Does an old source screenshot show current funding after a successful merge?
- No. Reconcile the destination receipt and current account state instead of counting the old screenshot again.
- Which merge-object field identifies the recipient?
- The documented into field identifies the account receiving the removed account’s lumens.
- Does a merge reference automatically prove exchange funding?
- No. Identify any separate payment matching the exchange instruction and do not assume merge deposits are supported.
- Does this article recommend deleting an account?
- No. It concerns interpreting an existing operation and locating native XLM already moved.
Primary Stellar references
Reviewed: