Wallets
Which wallets can hold Trump Digital Gold
There is no TDGOLD wallet. The asset lives on the Stellar ledger, so the question is never whether a wallet supports TDGOLD but whether it does the three things below, and the table further down records which vendors document each of them.
- 1
It has to speak Stellar
A Stellar account is an Ed25519 key pair whose public address is 56 characters long and starts with G. A wallet built for another network has no field that will accept one. The question is never whether a wallet supports TDGOLD, it is whether it supports Stellar at all.
- 2
It has to let you name the issuer yourself
TDGOLD is six characters, which makes it a credit_alphanum12 asset, and asset codes on Stellar are not unique. The issuing account is the only thing that tells one TDGOLD from another, so a wallet offering a curated asset list and no field for an issuer cannot hold this one.
- 3
It has to reach the order book or a swap
The Stellar order book is part of the protocol rather than a contract deployed on top of it, so a wallet either exposes it or it does not. Without that, or a swap that routes through it, you can receive and hold TDGOLD but you will have to leave the wallet to trade it.
One number applies whichever you pick. A Stellar account has to keep (2 + subentries) times 0.5 XLM on hand, so an empty account reserves 1 XLM and every trustline reserves another 0.5 XLM. That XLM is reserved rather than spent, and it comes back when you remove the trustline.
This is why the funding step in the buying guide asks for more than the bare minimum. An account holding exactly 1 XLM is perfectly valid and cannot afford a single trustline.
The comparison table
| Wallet | Platforms | Custody | Custom trustline | Built in DEX | Hardware | Open source |
|---|---|---|---|---|---|---|
| LOBSTR source | iOS, Android, Web | Self custody | Yes | Yes | not documented | not documented |
| Freighter source | Chrome, Firefox, Brave, iOS, Android | Self custody | Yes | Yes | not documented | Yes |
| xBull source | Chrome | Self custody | Yes | Yes | not documented | Yes |
| Rabet source | Chrome, Firefox, Edge, Brave, Desktop, Mobile | Self custody | not documented | not documented | not documented | Yes |
| Albedo source | Web, Browser extension | Self custody | Yes | Yes | not documented | Yes |
| StellarTerm source | Web | not documented | not documented | Yes | not documented | Yes |
| StellarX source | Web | not documented | not documented | Yes | not documented | not documented |
Every cell was read off the page linked under the wallet name, and the oldest row was checked on 2026-08-29. Where a vendor does not state the answer the cell reads not documented, which is a gap in the documentation and never a no.
None of these projects has any connection to TDGOLD. They are here because their own documentation describes behaviour the asset needs, which is a far weaker claim than saying they are good.
Mobile wallets
LOBSTR runs on iOS, Android and the web, states plainly that you control your keys, and publishes a help article on adding custom assets. That article says an asset can be found by its domain, by its asset code, or by the issuer public key, and the last of those is what lets you point a wallet at an issuing account directly.
The 0.5 XLM that adding an asset costs is not the wallet charging you. It is the network reserve every trustline holds, so the same 0.5 XLM applies whichever of these you install. It turns up again among the questions people ask before buying, next to the 0.00001 XLM network fee per operation.
Freighter, better known as an extension, also ships iOS and Android apps. Beans is a real Stellar wallet on both stores and calls itself fully non-custodial, but nothing on its site documents adding an asset by code and issuer, so it is not in the table: absence of evidence, not a verdict.
Browser extensions
Freighter comes from the Stellar Development Foundation, runs on Chrome, Firefox and Brave, and calls itself open source and free to use. Its front page claims both things this asset needs: control over exactly which assets you hold and the trustlines behind them, plus trading Stellar assets without leaving the wallet.
xBull is a Chrome extension under AGPL-3.0, and its repository lists the operations it can build. Change Trust and Set Trust Line Flags are both there, alongside manage buy offer and manage sell offer, which covers adding TDGOLD and then trading it. Rabet is open source too and reaches Chrome, Firefox, Edge and Brave, but its site describes encrypted local storage rather than asset handling, so most of its row is blank.
Albedo is the odd one out. It is MIT licensed and describes itself as a delegated signer and keystore for the Stellar network rather than a wallet with a balance screen. Applications reach it through a fixed list of intents, two of which matter here: trust, which requests a new trustline, and exchange, which requests trading on the Stellar DEX.
Web clients and the built in exchange
StellarTerm calls itself a web based trading client for the Stellar network and is Apache-2.0 licensed. StellarX calls itself a DEX trading platform with access to automated market makers. Both leave the custody column blank on purpose: they are clients you connect an existing key or wallet to, so who holds the key is answered somewhere else.
That distinction explains what a built in exchange really is. Stellar puts the order book in the protocol itself, so no wallet has to build one. A wallet advertising trading is exposing a ledger feature that was already there.
Stellar Lab, at lab.stellar.org, simulates, saves and submits transactions and puts Horizon endpoints behind a web interface. It is a development tool rather than a wallet, which is why it has no row in the table even though it can send a changeTrust operation.
Hardware wallets and how they connect
A hardware wallet is not a separate kind of Stellar account. The device holds the Ed25519 private key and produces the signature, while a software client builds the transaction and submits it. That is why the hardware column belongs to the software rather than to the asset, and it is why that column is empty right down the table: none of these seven vendors states the answer on the page linked under its name.
None of this removes a protocol requirement. An account signed by a device still needs its 1 XLM base reserve, still needs a trustline before TDGOLD can reach it, and that trustline still reserves 0.5 XLM.
The habit worth keeping is reading the signing screen. A Stellar address is 56 base32 characters, and the base32 alphabet runs A to Z plus 2 to 7, so the digits 0, 1, 8 and 9 never appear in one. An address containing any of them is wrong before you compare a single other character.
Custodial accounts: why an exchange account cannot hold TDGOLD
An account on a centralised exchange is not a Stellar account. Your balance there is a row in the exchange database, and the Stellar accounts belong to the exchange, usually a small number of pooled ones. That is why a deposit asks for a memo: the memo is how one account tells its customers apart. You never hold a key, so there is nothing for a trustline to attach to.
Even if the exchange were willing, the payment would fail. Stellar rejects a payment of an asset to an account with no trustline for it, and an exchange opens one only for assets it has deliberately listed.
The reverse direction has its own trap. A brand new Stellar address does not exist on the ledger until something funds it, and a withdrawal to an address that does not exist yet bounces. Fund a new wallet from an account you already control first.
Wallets that will not work
MetaMask cannot do this, and no setting or added network changes it. Its accounts are secp256k1 key pairs for EVM chains, whereas a Stellar account is an Ed25519 key pair with an address in a different format entirely. There is no key to import.
That gives you a quick test for anything else you are offered: if the wallet cannot show you a Stellar address beginning with G, it will not hold a Stellar asset.
The subtler failure is a wallet that does support Stellar but ships a fixed asset list. It shows XLM and a few stablecoins, with no field for an issuing account anywhere. It is not broken, it simply cannot be pointed at an asset its authors did not add.
Install from the vendor site linked in the table, and check the asset before you trade. The four checks that prove an issuer is genuine all read from the Stellar network or from a third-party explorer, so none of them requires trusting this page.
You picked one. Now add the trustline
Whichever you installed, what lets your account hold TDGOLD is a single
changeTrust operation naming the asset code
TDGOLD
and the issuing account. It costs one base fee of 100 stroops, which is
0.00001 XLM, plus the 0.5 XLM the trustline reserves.
Two things are worth knowing before you confirm. A trustline carries a limit, and setting one by hand below the amount arriving makes the payment bounce, so leave it at the default unless you have a reason. And TDGOLD sent back to the issuing account is destroyed rather than returned.
Removing a trustline you no longer want, and getting the 0.5 XLM back, is covered in the selling guide.
Wallet installed? Add the TDGOLD trustline
Then one operation stands between you and a TDGOLD balance. Add the trustline, verify the issuer, trade.