Available Guards

Bot Tax Guard

Last updated March 10, 2026

The Bot Tax guard charges a configurable SOL penalty on invalid mint transactions to discourage bots and spam attempts against the Core Candy Machine.

Some wallets (such as Solflare, Phantom, and possibly others) currently auto-inject Lighthouse instructions into transactions. This causes the Bot Tax guard to trigger when lastInstruction is set to true.

Since wallet choice is up to the user, you cannot prevent someone from minting with Solflare or similar wallets. If you expect users to mint using these wallets, consider setting lastInstruction to false to avoid false positives.

Use the Bot Tax guard with caution.

Overview

The Bot Tax guard charges a penalty for invalid transactions to discourage bots from attempting to mint NFTs. This amount is usually small to hurt bots without affecting genuine mistakes from real users. All bot taxes will be transferred to the Candy Machine account so that, once minting is over, you can access these funds by deleting the Candy Machine account.

This guard is a bit special and affects the minting behavior of all other guards. When the Bot Tax is activated and any other guard fails to validate the mint, the transaction will pretend to succeed. This means no errors will be returned by the program but no NFT will be minted either. This is because the transaction must succeed for the funds to be transferred from the bot to the Candy Machine account.

Additionally, the Bot Tax guard enables us to ensure the mint instruction was the last instruction of the transaction. This prevents bots from adding malicious instructions after the mint and returns an error to avoid paying the tax.

Guard Settings

The Bot Tax guard contains the following settings:

  • Lamports: The amount in SOL (or lamports) to charge for an invalid transaction. We recommend setting a fairly small amount to avoid affecting real users who made a genuine mistake. Client-side validation can also help reduce affecting real users.
  • Last Instruction: Whether or not we should forbid minting and charge a bot tax when the mint instruction is not the last instruction of the transaction. We recommend setting this to true to be better protected against bots.

Set up a Candy Machine using the Bot Tax guard

create(umi, {
// ...
guards: {
botTax: some({
lamports: sol(0.01),
lastInstruction: true,
}),
},
});

API References: create, BotTax

Mint Settings

The Bot Tax guard does not need Mint Settings.

Route Instruction

The Bot Tax guard does not support the route instruction.

Notes

  • When the Bot Tax guard is active and another guard rejects a mint, the transaction still appears to succeed on-chain but no NFT is minted. This is by design so the penalty can be collected.
  • Collected bot tax funds accumulate in the Candy Machine account and can be recovered by deleting the Candy Machine after minting concludes.
  • Setting lastInstruction to true may cause false positives with wallets (such as Solflare and Phantom) that auto-inject additional instructions into transactions. Test thoroughly before enabling this option in production.
  • Keep the penalty amount small (for example, 0.01 SOL) to avoid punishing legitimate users who encounter validation errors.