> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/pox-5/development/advanced.md).

# Advanced

Less common flows for PoX-5 integrators — signer-key grants and other edge cases.

Topics in this section aren't part of the typical integration journey. They're here for integrators with a specific need: a custodial wrapper that calls PoX-5 on behalf of users, or an operator running signer infrastructure.

* [Signers](/pox-5/development/advanced/signers.md) — Signer-key grants and revocations for operators running signer infrastructure on behalf of stakers.
* [Eligibility Preflights](/pox-5/development/advanced/eligibility.md) — Dry-run any PoX-5 entrypoint's assert chain client-side and get back the contract's own error codes before broadcasting.

### Calling PoX-5 from another contract

PoX-5 treats the staker as `tx-sender` and does not gate the staker-facing entrypoints by caller (`register-for-bond`, `update-bond-registration`, `stake`, `stake-update`, `unstake`, `unstake-sbtc`). The staker can call these directly, or route them through another contract — a wallet's batching helper, a relayer, a custodial wrapper — with no separate pre-authorization step. When routing through another contract, that contract must carry the correct STX and sBTC post-conditions on the transaction, because `tx-sender` remains the principal whose assets move.

A few entrypoints do restrict the caller. `announce-l1-early-exit` requires the staker to call it directly, with no intermediary contract in between. `claim-rewards` and `claim-staker-rewards-for-signer` require the caller to be the signer-manager principal. The signer-key grant and revoke calls, the bond-admin call, and the pause-admin calls each require their own specific caller.


---

# 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://docs.stacks.co/pox-5/development/advanced.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.