> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/chain-abstraction-mobile-application-user-guide.md).
# Chain Abstraction: Mobile Application User Guide
## Overview:
The Qubetics chain abstraction module in the Qubetics mobile app allows users to access and move multiple assets from different blockchains via a single interface, making it simple to move assets between blockchains. For example, the user can convert TICS to BTC or BTC to TICS directly within the app.
This guide walks you through setting up your abstraction wallet, funding it, and making your first transaction.
### Step 1: Opening the Chain Abstraction Module
When you open the Qubetics app, you’ll land on the home screen. At the bottom right corner, you’ll see the Chain Abstraction option. Tap it to get started.
### Step 2: Generating Your Abstracted Addresses
The first time you enter the module, you’ll see a short introduction explaining that your abstracted wallet isn’t set up yet. To move forward, tap “Generate Addresses.”
\
### Step 3: Wallet Setup Completed
The app will now create two unique addresses for you:
* A TICS address (for Qubetics).
* A BTC address (for Bitcoin).
These addresses are the foundation of your cross-chain activity. Once they are generated, select Continue.
Note: Copy and save your addresses. You’ll need them to receive funds later.
### Step 4: Adding Funds to Your Abstracted Wallet
Before making any transfers, your abstracted wallet needs to be funded. You can do this in two ways:
* Internal Transfer: Move tokens from your existing Qubetics wallet.
* External Transfer: Copy your TICS or BTC address and send tokens from another wallet or an exchange.
### Step 5: Setting Up Your First Transaction
Once your wallet is funded, you can create your first transaction.
1. Choose the token you want to send (e.g., TICS).
2. Enter the amount.
3. Select the destination token and chain (e.g., BTC).
4. Confirm the receiving address — you can edit it if needed.
### Step 6: Confirming the Details
Before sending, the app will show you a summary of the transaction:
* Amount you’re transferring.
* Platform fee (5%).
* Solver fee (5%).
* Network fee.
Review everything carefully. If it looks correct, tap Confirm.
### Step 7: Transaction in Progress
After confirmation, the system gets to work. It will first validate your transaction, then broadcast it to the Solvers Network. You’ll see a progress screen showing each step.
***Note***: **Depending on network congestion, this may take a few minutes.**
### Step 8: Transaction Hash and Completion
When the transaction is successfully processed, you’ll see a final screen with:
* The transaction hash.
* Status (Pending or Completed).
* Network fee details.
You can copy the hash or tap View on Explorer to track it directly.
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://qubetics.gitbook.io/qubetics-docs/chain-abstraction-mobile-application-user-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.