> For the complete documentation index, see [llms.txt](https://docs.novawallet.io/nova-wallet-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novawallet.io/nova-wallet-wiki/staking/staking-proxy/remove-staking-proxy.md).

# Remove Staking Proxy

How to remove your Staking Proxy account

This guide assumes that you have already started staking your tokens and have already previously set a Staking Proxy (Delegated Authority).

<div align="left"><figure><img src="https://2862319636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1YRoR7fazGxiQsx9pH6m%2Fuploads%2F4gdKNOeDI7aObQHMnn0y%2FStaking%20-%20Proxies%20-%20Remove%20Staking%20Proxy.avif?alt=media&amp;token=18e881f4-e5cc-4602-9f7e-c8e5177afebf" alt=""><figcaption></figcaption></figure></div>

1. Open the Nova Wallet application.
2. `Select` the Staking screen.
3. `Select` the **network/token** on which you wish to remove your **Staking Proxy**.
4. `Select` the **Your delegations button** (Note: there should be a number next to this button).
5. `Select` the **3 horizontal dots** to the right of the account address that you want to remove.
6. `Select` **Remove access**.
7. **Confirm** the transaction and your Staking Proxy (Delegated Authority) will be removed.


---

# 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.novawallet.io/nova-wallet-wiki/staking/staking-proxy/remove-staking-proxy.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.