# Alias Chat Alias Chat is a separate conversation mode in Sealed built for stronger separation between a specific conversation and the user’s main wallet identity. It is not a public profile, not a nickname system, and not a standard wallet-to-wallet chat. It is a device-bound chat mode where both sides communicate through locally created aliases, shared hints, temporary wallets, and separate Alias Chat credits. The purpose of Alias Chat is to make the conversation harder to connect with the user’s main Sealed identity. Instead of displaying the recipient’s wallet address or nickname, the app shows a local alias chosen by the user. Under the hood, Sealed uses cryptographic information exchanged between both devices to recognize which encrypted messages belong to that Alias Chat. ### Contact setup Alias Chat can be started in two ways. The first method is a one-time invitation sent through the network. From the outside, this invitation looks like a normal Sealed message, so it does not clearly reveal that a special chat mode is being created. The second method is an offline QR code exchange, where both users scan codes from each other’s devices. One device shows a QR code, the other scans it, and then the same process happens in the opposite direction. The goal of this step is only to establish the first connection between the two devices. After this setup, both apps have the information they need to create the shared detection mechanism for the Alias Chat. ### Local alias In Alias Chat, the user does not see the other person as a wallet address or public nickname. Instead, the user creates a local alias for that conversation. This alias is only a label inside the user’s app and can be chosen freely by the user. The alias exists to make the conversation readable for the user without exposing the recipient’s real wallet identity in the interface. If someone opens the app, they see the chosen alias, not the other person’s wallet address. This is why the feature is called Alias Chat: the visible identity in the chat is local and user-defined. ### Shared hint After the initial setup, both devices create the same shared hint from the exchanged keys. This hint is used by the apps to recognize messages that belong to the Alias Chat. The shared hint replaces the need to show or use a visible recipient wallet address in the conversation interface. When the app scans incoming encrypted messages, it checks whether any of them match the Alias Chat hint. If there is a match, the app knows that the message belongs to that conversation. ### Alias Chat credits Alias Chat uses its own credit flow. From the main Sealed wallet, the user can exchange regular credits into Alias Chat credits. These credits are divided into packages of 50 messages. Each package works as a separate code, similar to a top-up code. These codes are stored locally on the device and are later used to fund Alias Chat messaging. This keeps the spending flow for Alias Chat separated from the main wallet used by the regular Sealed identity. ### Temporary wallet When an Alias Chat is started, the app creates a new local temporary wallet for that conversation. This wallet receives one package of Alias Chat credits and uses those credits to send messages within the Alias Chat. The temporary wallet exists only for this separated communication flow. It is not the user’s main Sealed wallet. When the package of credits runs out, the temporary wallet can be removed from the device and replaced with a new temporary wallet funded by a new Alias Chat code. ### Wallet rotation inside one conversation Alias Chat can continue even when the first temporary wallet is no longer used. When credits run out, the app can create another temporary wallet and fund it with another Alias Chat credit package. This means that one Alias Chat conversation does not need to rely on one long-lived wallet. Over time, the conversation can move through multiple temporary wallets, each funded by a separate credit code. This helps reduce the risk of building a long-term visible wallet trail for the conversation. ### Device-bound storage Alias Chat is bound to the device where it was created. The local alias, exchanged keys, shared hint, stored credit codes, temporary wallets, and conversation data are kept on that device. This is different from the main Sealed identity, which can be restored with a 24-word mnemonic phrase. Alias Chat is intentionally more isolated, so it does not use the same backup model. If the user loses the device or deletes the local Alias Chat data, the Alias Chat may be lost. ### Alias Chat architecture summary Alias Chat separates a specific conversation from the user’s main Sealed identity. Contact is established through a one-time network invitation or offline QR exchange. The visible identity is a local alias, message detection is based on a shared hint, and sending is handled by temporary wallets funded with Alias Chat credit packages. This design gives users a stronger separation layer for selected conversations, but it also comes with a clear trade-off: Alias Chat is device-bound and does not have the same recovery model as the main Sealed identity. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sealed.channel/architecture/alias-chat.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.