SoLibrary
  • Solana
  • The Meme Coin Problem and Solution
  • Developing on Solana
  • From Rust To Deployment
  • Solana Blockchain Explorer
  • Building a Solana dAPP
  • Deploying a Solana dApp
  • Deploying a Solana Memecoin using CLI
  • Solana Smart Contracts
  • Send Solana via javascript functions
  • Candy Machine
  • Pump fun APIs
  • Metaplex
  • Metaplex Program Library
  • Solana Program Library
  • UMI Framework
  • Umi and Web3js Differences
  • Fetching Accounts
  • UMI Helpers
  • HTTP Requests
  • Umi's Interfaces
  • Interface implementations
  • Kinobi
  • UMI Plugins
  • Registering Programs
  • Public keys and Signers
  • Connecting RPCS
  • Serializer
  • Storage
  • Transactions
  • Web 3.JS Adapters
  • Metaplex Umi Plugins
  • Core JS SDK v1.0
  • Local Validator
  • SolScriptions
  • FAQ
  • Initialize
  • Write Inscription Data
  • Fetch
  • Clear
  • Close
  • Authority
  • Sharding
  • Getting Started using JavaScript
  • Getting started using the Inscriptions CLI
  • Core Candy Machine
  • Getting Started using JavaScript
  • Candy Guard
  • Assets
  • Creating a Core Candy Machine
  • Inserting Items
  • Updating The Core Candy Machine
  • Guard Groups
  • Special Guard Instructions
  • Fetching a Core Candy Machine
  • Minting
  • Withdrawing a Core Candy Machine
  • Address Gate Guard
  • Allocation
  • Allowlist Guard
  • Asset Burn Guard
  • Asset Burn Multi
  • Asset Payment Guard
  • Asset Payment Multi
  • Asset Mint Limit
  • Bot Tax Guard
  • End Date Guard
  • Edition
  • Freeze Sol Payment guard
  • Freeze Token Payment Guard
  • Gatekeeper Guard
  • Mint Limit Guard
  • NFT Burn Guard
  • NFT Gate Guard
  • NFT Mint Limit Guard
  • NFT Payment Guard
  • Program Gate Guard
  • Redeemed Amount Guard
  • Sol Fixed Fee Guard
  • Sol Payment Guard
  • Start Date Guard
  • Third Party Signer Guard
  • Token Burn Guard
  • Token Gate Guard
  • Token Payment Guard
  • Token2022 Payment Guard
  • Generating Custom Guard Client for Core Candy Machine
Powered by GitBook
On this page
  • Guard Settings
  • Mint Settings
  • Route Instruction

Allocation

The Allocation guard allows specifying a limit on the number of Assets each guard group can mint.

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

Guard Settings

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 }),
  },
});

Mint Settings

The Allocation guard contains the following Mint Settings:

  • ID: A unique identifier for this guard.

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

The Allocation guard route instruction supports the following features.

Initialize the Allocation Tracker

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

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'),
})
PreviousAddress Gate GuardNextAllowlist Guard

Last updated 10 months ago

API References: ,

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 for more details.

Allocation Tracker PDAcount = 0

API References: ,

React Flow
create
Allocation
Candy Guard’s program documentation
React Flow
route
AllocationRouteArgs