# Coming: the BZPX airdrop, a bug bounty, and a paid improvement-proposal programme

> Canonical: https://blazephoenix.xyz/learn/airdrop-and-bounties
> License: CC BY 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-07-27

Three programmes in preparation: a BZPX airdrop from the public 40,000,000 allocation, a security bug bounty, and paid bounties for accepted developer improvement proposals. No dates or amounts promised yet.

Three programmes are in preparation. This note exists so that when they open, nobody has to ask whether the announcement is genuine — the plan was published here first, from the domain, with no numbers attached that could later be quietly revised.

## A BZPX airdrop

A fixed 40,000,000 BZPX of the one-billion supply is allocated to the airdrop — 4% — and that allocation has been public in the tokenomics since before this article. What is still being finalised is the distribution mechanism and the eligibility criteria.

What we will not do: promise a value, imply a return, or run a task-farm that rewards empty engagement. An airdrop that pays for noise buys noise. When the criteria are published they will be checkable on-chain, like everything else here.

## A security bug bounty

The contracts are immutable and hold user funds during execution, so the honest position is that an external audit is pending and a bounty is the complement to it, never a substitute. Both are stated as pending on the site rather than implied as done.

The programme will cover the aggregator contracts and the staking engine, with severity tiers and a disclosure process published in full. If you have already found something, do not wait for the programme: contact@blazephoenix.xyz, and responsible disclosure will be treated as such and credited.

## A bounty for accepted improvement proposals

The third programme pays for accepted developer proposals — a concrete improvement to the protocol, the SDK, the MCP tooling or the public data surfaces, submitted as a specification or a patch, and paid on acceptance rather than on submission.

The reason to run this rather than simply hiring: the people who find the sharpest improvements in a system like this are usually the ones already using it for something we did not anticipate. Integration work has a habit of revealing what the protocol should have exposed in the first place.

## Why there are no dates here

Because a date published now is a promise made with information we do not have yet, and a missed date costs more credibility than a late launch does. Each programme will be announced when its rules are final and its funding is in place — announced here first, then in the community channels, never by direct message.

One safety note, worth repeating every time: we never message first, never ask for a seed phrase, and never ask you to connect a wallet to claim anything from a link someone sends you. Any account doing those things is not us, and an airdrop announcement is exactly the moment impersonators appear.

**Verify it yourself:** Read the 40,000,000 BZPX airdrop allocation in the published tokenomics, and the total supply directly from the token contract on Base — the allocation was public before this announcement, which is the point

Related: https://blazephoenix.xyz/learn/api-sdk-mcp · https://blazephoenix.xyz/learn/integrated-dexes · https://blazephoenix.xyz/learn/on-chain-quoting