> For the complete documentation index, see [llms.txt](https://docs.varialwallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varialwallet.com/mobile-walletconnect/installation.md).

# Installation

Get up and running with WalletConnect so your dapp can connect to the Varial mobile app.

## Prerequisites

1. Sign up at [WalletConnect Dashboard](https://dashboard.walletconnect.com/) and create a project to get your **Project ID**.
2. Choose an installation method below.

## npm / yarn

```bash
npm install @walletconnect/universal-provider @reown/appkit
```

```bash
yarn add @walletconnect/universal-provider @reown/appkit
```

Then initialize the provider and modal:

```typescript
import { UniversalProvider } from "@walletconnect/universal-provider";
import { createAppKit } from "@reown/appkit/core";
import { mainnet } from "@reown/appkit/networks";

const projectId = "YOUR_PROJECT_ID";

// Provider — handles the WalletConnect protocol
const provider = await UniversalProvider.init({
  projectId,
  metadata: {
    name: "My Stellar Dapp",
    description: "A dapp that integrates with Varial",
    url: "https://my-dapp.com",
    icons: ["https://my-dapp.com/icon.png"],
  },
});

// Modal — displays the QR code and wallet list.
// AppKit requires at least one network. Stellar is not built-in,
// so we pass a placeholder. With manualWCControl the modal won't
// use it for chain switching.
const modal = createAppKit({
  projectId,
  networks: [mainnet],
  universalProvider: provider,
  manualWCControl: true,
});
```

## Next steps

| I want to...                        | Go to                                                            |
| ----------------------------------- | ---------------------------------------------------------------- |
| Connect to the Varial mobile app    | [Connecting](/mobile-walletconnect/connecting.md)                |
| Sign a transaction                  | [Signing](/mobile-walletconnect/signing.md)                      |
| Feature Varial upfront in the modal | [Featuring Varial](/mobile-walletconnect/featuring-freighter.md) |

## Alternatives

[Stellar Wallets Kit](https://stellarwalletskit.dev/) provides a multi-wallet interface that includes WalletConnect support. From v2.3.0, its `WalletConnectModule` supports all four Varial methods:

| Stellar Wallets Kit method   | WalletConnect RPC method   |
| ---------------------------- | -------------------------- |
| `signTransaction()`          | `stellar_signXDR`          |
| `signAndSubmitTransaction()` | `stellar_signAndSubmitXDR` |
| `signMessage()`              | `stellar_signMessage`      |
| `signAuthEntry()`            | `stellar_signAuthEntry`    |

Use the kit if your dapp supports several Stellar wallets. Integrate WalletConnect directly, as shown in this guide, if you want full control over the session and the modal. Kit versions before v2.3.0 only support `stellar_signXDR` and `stellar_signAndSubmitXDR`.

{% hint style="warning" %}
The kit sends `stellar:pubnet` only for the Mainnet passphrase (`Networks.PUBLIC`) and `stellar:testnet` for anything else. It uses the `networkPassphrase` you pass on the call, or else the kit's network, which is Mainnet unless you set it with `init({ network })` or `setNetwork()`. Keep it in line with the network active in the Varial mobile app, or the request is rejected.
{% endhint %}

{% hint style="info" %}
Older examples may use `@walletconnect/sign-client` directly. That approach still works, but `@walletconnect/universal-provider` is the actively documented package. For more details, see the [UniversalProvider docs](https://docs.reown.com/advanced/providers/universal) and the [AppKit modal migration guide](https://docs.reown.com/appkit/upgrade/wcm).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.varialwallet.com/mobile-walletconnect/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.