Some protocols do not hold a user's funds in their wallet. A perps or margin venue gives each user a sub account, an on-chain object owned by their wallet, and that is where collateral and open positions actually live. Those users have two addresses, and the two are not interchangeable.
This matters more than it sounds. A trader who connects their wallet and then sees a second address they do not recognise usually assumes something has gone wrong, and support gets "why is a different address showing as connected?". Turning sub accounts on removes that question instead of answering it.
What changes when it is on
- The moment a user connects, TxID resolves their sub account and shows both addresses in the widget, each labelled, so neither is a surprise.
- Both addresses are available in full, with a copy button, not only in shortened form.
- The assistant is told about both before the user's first question, so it never has to discover the second address halfway through an answer.
- Answers name which address they mean every time, rather than printing a bare 0x and leaving the user to work it out.
Why the full address is always shown
A shortened address is not something a user can verify. Address-poisoning scams generate lookalike addresses whose first and last characters match a real one exactly, so an abbreviation confirms nothing. TxID always makes the complete address available, and tells users why.
Turning it on
Open Smart Contracts
Sub accounts has its own section on the Smart Contracts page in the dashboard.
Check the status line
It tells you whether your watched contracts actually use sub accounts. If they do, it also shows what your protocol calls them, and that is the word the widget and the assistant will use.
Switch it on
Users see their sub account from their next connection. Nothing else needs changing.
Off by default, on purpose
Most protocols keep user funds in the wallet. Showing a second address there would invent a concept your users do not have, so this stays off unless you turn it on, and it does nothing on a protocol without sub accounts.
Limits worth knowing
- Support is added per protocol, since resolving a wallet to its sub account depends on how that protocol is built. Get in touch if yours is not recognised yet.
- One sub account per wallet. If a protocol lets a single wallet hold several, tell us before enabling this, because the wording assumes one.
- If the lookup itself fails, TxID shows nothing rather than claiming the user has no account. "No sub account" is only ever said when that is genuinely the answer.