> 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/sign-transaction-as-staking-proxy.md).

# Sign Transaction as Staking Proxy

How to sign staking-related transactions from a staking proxy

This guide assumes that an account that you have imported into Nova Wallet has been set as a Staking Proxy (Delegated Authority).

1. Open the Nova Wallet application.
2. `Select` the identicon at the top right of the Assets screen.
3. `Select` the account which is Delegated To You as a Staking proxy.
4. You will now see that the identicon at the top right of the screen has a new icon next to it, this indicates that you are controlling a delegated account.
5. You can now carry out staking operations on behalf of that account.


---

# 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/sign-transaction-as-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.