> 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/operate/protocol-bonds/getting-allowlisted-for-a-bond.md).

# Getting Allowlisted for a Bond

How bond capacity is allocated during PoX-5, what to send the Stacks Endowment, and how to check your allowlist entry once the bond is set up.

Every protocol bond registration needs an allowlist entry for that bond, on either Bitcoin leg. During PoX-5 there is no on-chain auction. The Stacks Endowment sets each bond's capacity, target yield, STX:BTC ratio and allocation off-chain, and allocates the capacity to whitelisted partners before the bond starts. About 10% of paired-bond capacity is reserved for open access, first come first served, through selected pool partners.

If you do not have an allocation of your own, the open-access route is a [bond pool](/operate/protocol-bonds/bond-pool-operator-guide.md).

## What to send the Endowment

For each bond, one row per staker:

* **Staker principal.** The Stacks address that will call `register-for-bond`.
* **Maximum BTC commitment, in sats.** Your cap for this bond. You do not send an STX amount: the STX you must pair is computed at registration from the sats you actually commit and the bond's ratio.

Your signer-manager and how you are paid are not part of the allowlist. You choose both when you register. See [Opening a Bond Position](/operate/protocol-bonds/opening-a-bond-position.md).

## What the Endowment publishes

The Endowment's `setup-bond` call puts the bond on-chain: its target yield, the STX:BTC ratio and minimum STX ratio, the early-exit subscript, and the allowlist of up to 1,000 stakers with each one's sats cap. Registration opens once it lands.

* The contract accepts `setup-bond` only within the two reward cycles before the bond starts, 4,200 Bitcoin blocks on mainnet. In practice the Endowment publishes about seven days before Day 0.
* It runs once per bond. The parameters and the allowlist are fixed from then on.

{% hint style="warning" %}
**The allowlist is fixed at `setup-bond`.** If you are not on it when the bond is set up, you cannot join that bond. The next opportunity is the next bond, two reward cycles later.
{% endhint %}

## Check your entry

Read the bond back and confirm it matches what you agreed with the Endowment, then read your cap. A missing entry means you are not allowlisted. Read the parameters from the chain each time rather than hardcoding them: they are set per bond.

```ts
import { fetchBond, fetchBondAllowance } from '@stacks/bitcoin-staking';

const network = 'mainnet';

const bond = await fetchBond({ bondIndex, network });
// Check targetRateBps, stxValueRatio, minUstxRatioBps and earlyUnlockBytes

const allowance = await fetchBondAllowance({ bondIndex, address: staker, network });
if (allowance === undefined) throw new Error(`Not allowlisted for bond ${bondIndex}`);
```

Next: [Opening a Bond Position](/operate/protocol-bonds/opening-a-bond-position.md).


---

# 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.stacks.co/operate/protocol-bonds/getting-allowlisted-for-a-bond.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.