Practical overview
When it fits
Use it as a codebase reference when building a Solana burn-to-NFT reward workflow or adapting the webhook verification pattern to another event.
Who it is for
- Developers building NFT rewards around qualifying Solana token burns
- Teams exploring webhook-based on-chain event reward workflows
Documented uses
- Validate and authorize incoming Helius webhook requests.
- Check that a transaction is a token burn and that the burned amount exceeds a configured minimum.
- Request an NFT mint for the burner through Crossmint.
- Optionally send Discord notifications for the event.
Requirements & limits
- The front end for initiating token burns is separate from the webhook backend.
- The documented integration requires Helius webhook configuration and Crossmint environment values.
- Discord credentials are only needed if the optional notification bot is enabled.
- The README reports that the BURN feed excludes inner-transaction burns and BurnChecked transactions.
- The README notes serverless execution limits and a possible NFT metadata rendering issue on some platforms.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the project for a Helius burn webhook
Set up the documented project configuration and local development environment before connecting a deployed webhook.
Before you start
- The project source repository
- A Crossmint developer account for the Crossmint environment variables
- A self-generated AUTH_CODE
- Discord developer keys only if Discord notifications remain enabled
Steps
Clone the repository and rename .env.example to .env.
Set the environment variables, including AUTH_CODE and the Crossmint values; provide Discord keys if notifications are enabled.
Install dependencies with yarn and start the app with yarn dev.
After launching the server, configure a Helius webhook for the documented Enhanced Transaction BURN type and direct it to the serverless endpoint.
Expected outcome
The project is configured for local development and the documented Helius burn-webhook integration.
Guide limitations
- The README says the webhook should be deployed only after the server is launched.
- The documented BURN feed omits inner-transaction burns and BurnChecked transactions.
- Vercel execution limits and occasional timeouts are noted; the README does not establish current provider limits.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- amilz/proof-of-x · Official homepage title · retained in its source language

