> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/guides/deploy-policy/allowlist.md).

# allowlist-destinations

This policy restricts what a dWallet can sign for: only transactions whose destination program is on a whitelist are approved. Everything else is rejected on-chain, regardless of what the API does.

Program address (Solana devnet): `91hycWu3sTbRELUDBTkqbyaEse1fVFDX3RmW9uPNQqFx`.

## What it enforces

For each signing request, the policy checks the destination program(s) involved against the allowlist. If anything is not on the list, the signature does not go through.

## Configuration

* **Allowlist**: the set of destination program addresses the dWallet is permitted to interact with.

Updating the allowlist follows the [policy lifecycle](/hub/andromeda/guides/deploy-policy.md): a challenge-based admin action (request a challenge, the owner signs it, submit), with the change typically staged as pending so it is reviewable before it takes effect.

## Combine it

`allowlist-destinations` pairs naturally with [`velocity-guard`](/hub/andromeda/guides/deploy-policy/velocity-guard.md): "only these programs, and at most N times per slot window". It also pairs with [`time-lock`](/hub/andromeda/guides/deploy-policy/time-lock.md) for "only these programs, only during this window".

## On-chain guarantees

* The check runs in the program that holds the dWallet authority. The API cannot bypass it.
* The PDA is seeded with an init-authority hash, so the address cannot be front-run.
* Replay-nonced admin actions for configuration changes.

## When to use it

* DAO and protocol treasuries that should only ever touch known programs.
* Operational wallets that interact with a fixed, audited set of contracts.
* Any wallet where "where can the funds go" is the thing you most want to constrain.


---

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

```
GET https://shinkalabs.gitbook.io/hub/andromeda/guides/deploy-policy/allowlist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.