# Allocation

The limit is set per identifier — provided in the settings — to allow multiple allocations within the same Core Candy Machine.

if the allocation tracker count

is equal to the limit

Minting will fail

Candy Machine

Owner: Candy Machine Core Program

Candy Guard

Owner: Candy Guard Program

GuardsAllocation- id- limit...

Allocation Tracker PDA

Mint from

*Candy Guard Program*

Access Control

Mint from

*Candy Machine Program*

Mint Logic

Asset

[React Flow](https://reactflow.dev/)

### Guard Settings <a href="#guard-settings" id="guard-settings"></a>

The Allocation guard contains the following settings:

* **ID**: A unique identifier for this guard. Different identifiers will use different counters to track how many items were minted by a given wallet. This is particularly useful when using groups of guards as we may want each of them to have a different mint limit.
* **Limit**: The maximum number of mints allowed on the guard group.

Set up a Candy Machine using the Allocation guard

JavaScript

```
create(umi, {
  // ...
  guards: {
    allocation: some({ id: 1, limit: 5 }),
  },
});
```

API References: [create](https://mpl-core-candy-machine.typedoc.metaplex.com/functions/create.html), [Allocation](https://mpl-core-candy-machine.typedoc.metaplex.com/types/Allocation.html)

### Mint Settings <a href="#mint-settings" id="mint-settings"></a>

The Allocation guard contains the following Mint Settings:

* **ID**: A unique identifier for this guard.

Note that, if you’re planning on constructing instructions without the help of our SDKs, you will need to provide these Mint Settings and more as a combination of instruction arguments and remaining accounts. See the [Candy Guard’s program documentation](https://github.com/metaplex-foundation/mpl-core-candy-machine/tree/main/programs/candy-guard#allocation) for more details.

Mint with the Allocation Guard

JavaScript

You may pass the Mint Settings of the Allocation guard using the `mintArgs` argument like so.

```
mintV1(umi, {
  // ...
  mintArgs: {
    allocation: some({ id: 1 }),
  },
});
```

### Route Instruction <a href="#route-instruction" id="route-instruction"></a>

The Allocation guard route instruction supports the following features.

#### Initialize the Allocation Tracker <a href="#initialize-the-allocation-tracker" id="initialize-the-allocation-tracker"></a>

When using the Allocation guard, we must initialize the Allocation Tracker account before minting can start. This will create a PDA account derived from the id attribute of the guard's settings.

The Allocation Tracker PDA account will keep track of the number of mints in a guard group and it will block any mint within that group once the limit has been reached.

When initializing this Allocation Tracker account, we must provide the following arguments to the route instruction of the guard:

* **ID**: The id of the Allocation of the guard's settings.
* **Candy Guard Authority**: The authority of the Core Candy Guard account as a Signer.

Candy Machine

Owner: Candy Machine Core Program

Candy GuardOwner: Candy Guard ProgramGuardsAllocation...

Route from the

*Candy Guard Program*

Initialize Allocation Tracker

Allocation Tracker PDAcount = 0[React Flow](https://reactflow.dev/)

Initialize the Allocation Tracker PDA

JavaScript

To initialize the Allocation Tracker PDA for the default guards:

```
route(umi, {
  // ...
  guard: 'allocation',
  routeArgs: {
    id: 1,
    candyGuardAuthority: umi.identity,
  },
})
```

When the Allocation guard is added to a specific group, you will need to add the **group** name:

```
route(umi, {
  // ...
  guard: 'allocation',
  routeArgs: {
    id: 1,
    candyGuardAuthority: umi.identity,
  },
  group: some('GROUPA'),
})
```

API References: [route](https://mpl-core-candy-machine.typedoc.metaplex.com/functions/route.html), [AllocationRouteArgs](https://mpl-core-candy-machine.typedoc.metaplex.com/types/AllocationRouteArgs.html)


---

# Agent Instructions: 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://8bit-1.gitbook.io/solibrary/allocation.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.