# Telegram wallet (DEPRECATED)

### 🚨 <mark style="color:red;">UNFORTUNATELY, DUE TO NEW TELEGRAM RULES, IT IS NO LONGER POSSIBLE TO USE ARGENT TELEGRAM WALLET AND READY TELEGRAM SDK.</mark>

The Ready Telegram Wallet is a self-custody, embedded wallet within Telegram. By leveraging account abstraction, users benefit from a best-in-class experience while retaining ownership of their assets. The goal here is to abstract away the concept of blockchain.

To set up and use the wallet, please follow this guide: [**How to use the Argent Telegram Wallet**.](https://www.argent.xyz/blog/how-to-use-argent-telegram-wallet)

Talking about the Ready Telegram Wallet, we have to differentiate two features: the wallet and the SDK.

The wallet/bot enables end-users to:

* Send (including Gifting)
* Send with bot (including Gifting)
* Add Funds
* Unlock with biometrics

The SDK enables mini-app developers to:

* Seamlessly establish connection between the dapp and the wallet (like [StarknetKit](https://www.starknetkit.com/))
* Leverage [session keys](https://docs.argent.xyz/aa-use-cases/session-keys) to highly improve the user experience.

Under the hood, our Telegram wallet leverages the same smart-account technology that is used for other Argent wallets, like the Mobile wallet. Part of the signing process is handled by our backend. It is somewhat similar to a 2-2 multisig wallet. To make a transaction, both the Telegram wallet signature and the Argent backend signature are required. The private key of the Telegram wallet is stored on the user’s Telegram cloud space.

The private key is encrypted using your pin or secure enclave if your enable biometric.


---

# 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.ready.co/telegram-wallet-deprecated.md?ask=<question>
```

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.