Enable CAPTCHA on a mint

Enable protection

Supported contracts require a short-lived mint authorization issued by Aurora. When CAPTCHA is enabled, Aurora validates the challenge before issuing that authorization. Turning CAPTCHA off removes the challenge, not the contract’s authorization requirement.

1. 1

   Open Edit mint settings

   Find CAPTCHA protection in the public mint editor. It is enabled by default for new releases when the collection supports it and platform setup is complete. Saved choices are preserved, and creators can turn it off before saving and publishing.

2. 2

   Enable CAPTCHA and save

   For a compatible collection, enable the setting and save or publish the update as prompted. A CAPTCHA-only setting change does not require a new onchain transaction.

If the collection needs an updated controller

1. 1

   Read the setup explanation

   The editor describes the actions needed for that particular older contract. Setup may end old releases, withdraw proceeds and transfer collection control.

2. 2

   Start Set up updated controller

   Review each wallet action. Stay in the controller setup area and use its Continue action after confirmation; an accepted transaction can be one step of several.

3. 3

   Finish connecting the release

   Follow the final instruction to create or publish a release with CAPTCHA enabled. Refresh status if the completed setup has not yet appeared.

If CAPTCHA is still unavailable

A platform-setup message requires an administrator to finish configuration. A pending wallet operation needs to be completed or recovered. Website-only protection cannot enforce CAPTCHA on a contract that still allows an unprotected mint path. CAPTCHA reduces automated abuse; it does not guarantee a bot-free mint.