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

# WalletConnect

### Introduction

WalletConnect is an open protocol to communicate securely between Tectonic and wallets. The idea is to allow users to connect their desired wallets to Tectonic on their mobile devices, without the need to install and approve on browser extensions. 

### How does it work?

The protocol establishes a remote connection using a Bridge server to relay payloads. These payloads are symmetrically encrypted through a shared key. The connection is initiated when Tectonic displays a **QR Code** or deep link with a standard WalletConnect URI and is established when the counter-party approves this connection request. It also includes an optional Push server to allow Native applications to notify the user of incoming payloads for established connections.

To know more about WalletConnect: <https://docs.walletconnect.com/>


---

# 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://tectonic.gitbook.io/docs/developer/walletconnect.md?ask=<question>&goal=<endgoal>
```

`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.