> 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.md).

# Development

Implementation guidance for PoX-5, grouped by interaction cluster.

This section walks through PoX-5 from the integrator's perspective. Pages are grouped by the interaction shape they cover rather than by actor — most users hit more than one cluster (a partner onboards, reads their position, enrolls in a paired bond, claims rewards, then renews).

All examples use [`@stacks/bitcoin-staking`](https://github.com/hirosystems/stacks.js/tree/feat/bitcoin-staking/packages/bitcoin-staking) for the PoX-5 surface and `@stacks/transactions` for signing and broadcast. The actor-oriented overview lives at [Actors](/pox-5/actors.md); these pages assume you already know which path you're building for.

### How the flow unfolds

A typical integration moves through four stages. The second one forks based on which path your user takes — most apps support more than one.

1. **Get allowlisted and onboard** — [Onboarding](/pox-5/development/onboarding.md) Native-bond participation in PoX-5 is allowlisted. To get your users (or your platform) on a bond's allowlist, you communicate with the Stacks Endowment off-chain; the Endowment publishes the allowlist and bond parameters on-chain before each bond opens. Plan for this contact early — it is not an API call. A later, permissionless protocol version (PoX-6) is expected to remove this manual step. If you operate signer infrastructure, [Advanced › Signers](/pox-5/development/advanced/signers.md) covers signer-key grants and revocations.
2. **Open a position** — your user commits assets through one of three paths:
   * [**Paired BTC**](/pox-5/development/paired-btc.md) — L1 BTC timelock + L2 STX lock. Institutional, protocol bond tranche yield, self-custodial.
   * [**Solo STX**](/pox-5/development/solo-stx.md) — STX-only stake, no BTC commitment. Earns STX-only staking tranche residual after the protocol bond tranche, ahead of the reserve fund.
   * [**Pool**](/pox-5/development/pools.md) — sBTC + STX through a whitelisted pool operator. Lower friction, shared envelope.
3. **Receive rewards** — [Rewards](/pox-5/development/rewards.md) Distributions are pulled, not pushed. Your job is to read accumulated reward balances, show them to the user, and offer a claim path. Payout is in sBTC; an optional L1 BTC payout is handled in the signer-manager layer. The Rewards page covers the read and claim calls.
4. **Renew or exit** — [Paired BTC › Renew](/pox-5/development/paired-btc.md#renew-into-the-next-bond-period) In roughly the last week of a bond, the L1 timelock has expired but STX is still locked. Your user either constructs the next L1 timelock to roll into the next bonding period without losing continuity, or exits and lets STX unlock at the bond's end. The [Paired BTC](/pox-5/development/paired-btc.md) and [Rewards](/pox-5/development/rewards.md) pages cover this flow.


---

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