Coming: the BZPX airdrop, a bug bounty, and a paid improvement-proposal programme
BlazePhoenix Engineering · updated 2026-07-27 · 5 min · written from the deployed bytecode
By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.
Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص
English — 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.
Português — Três programas em preparação: um airdrop BZPX a partir da alocação pública de 40.000.000, um bug bounty de segurança, e bounties pagos por propostas de melhoria aceites. Ainda sem datas nem valores prometidos.
Español — Tres programas en preparación: un airdrop de BZPX desde la asignación pública de 40.000.000, un bug bounty de seguridad y bounties pagados por propuestas de mejora aceptadas. Aún sin fechas ni importes prometidos.
Français — Trois programmes en préparation : un airdrop BZPX issu de l'allocation publique de 40 000 000, un bug bounty de sécurité, et des primes payées pour les propositions d'amélioration acceptées. Aucune date ni montant promis pour l'instant.
Deutsch — Drei Programme in Vorbereitung: ein BZPX-Airdrop aus der öffentlichen 40.000.000-Zuteilung, ein Security-Bug-Bounty und bezahlte Prämien für angenommene Entwickler-Verbesserungsvorschläge. Noch keine Termine oder Beträge zugesagt.
Русский — Три программы в подготовке: аirdrop BZPX из публичной аллокации 40 000 000, баг-баунти по безопасности и оплачиваемые награды за принятые предложения по улучшению. Даты и суммы пока не обещаны.
Türkçe — Hazırlıktaki üç program: kamuya açık 40.000.000 tahsisten bir BZPX airdrop'u, bir güvenlik ödül programı ve kabul edilen geliştirici iyileştirme önerileri için ödenen ödüller. Henüz tarih veya tutar taahhüdü yok.
العربية — ثلاثة برامج قيد الإعداد: توزيع BZPX من المخصّص العلني البالغ 40,000,000، ومكافآت للثغرات الأمنية، ومكافآت مدفوعة لمقترحات التطوير المقبولة. لا مواعيد ولا مبالغ موعودة بعد.
हिन्दी — तीन कार्यक्रम तैयारी में: सार्वजनिक 40,000,000 आवंटन से BZPX एयरड्रॉप, एक सुरक्षा बग बाउंटी, और स्वीकृत डेवलपर सुधार प्रस्तावों के लिए भुगतान वाली बाउंटी। अभी कोई तारीख या राशि का वादा नहीं।
日本語 — 準備中の三つのプログラム：公開済み40,000,000枠からのBZPXエアドロップ、セキュリティのバグバウンティ、そして採用された開発者改善提案への報奨金。日付も金額もまだ約束していません。
中文 — 三项计划正在筹备：来自公开的 40,000,000 配额的 BZPX 空投、安全漏洞赏金，以及对被采纳的开发者改进提案的付费赏金。目前不承诺任何日期或金额。
한국어 — 준비 중인 세 가지 프로그램: 공개된 40,000,000 배정에서 나오는 BZPX 에어드랍, 보안 버그 바운티, 그리고 채택된 개발자 개선 제안에 대한 유상 바운티. 날짜나 금액은 아직 약속하지 않습니다.
Bahasa Indonesia — Tiga program dalam persiapan: airdrop BZPX dari alokasi publik 40.000.000, bug bounty keamanan, dan bounty berbayar untuk proposal perbaikan pengembang yang diterima. Belum ada tanggal atau jumlah yang dijanjikan.
বাংলা — প্রস্তুতিতে তিনটি কর্মসূচি: প্রকাশ্য ৪০,০০০,০০০ বরাদ্দ থেকে BZPX এয়ারড্রপ, নিরাপত্তা বাগ বাউন্টি, এবং গৃহীত ডেভেলপার উন্নতি প্রস্তাবের জন্য অর্থপ্রদত্ত বাউন্টি। এখনও কোনো তারিখ বা অঙ্ক প্রতিশ্রুত নয়।
Filipino — Tatlong programa ang inihahanda: airdrop ng BZPX mula sa pampublikong 40,000,000 alokasyon, bug bounty sa seguridad, at bayad na bounty para sa tinanggap na mungkahi ng developer. Wala pang ipinangakong petsa o halaga.
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.
Do not trust this page — reproduce it
Every claim above is checkable against the chain. Start here:
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 pointContracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).
Share this article · join the discussion