Add BlazePhoenix - #502
Open
blazephoenixxyz-crypto wants to merge 1 commit into
Open
Conversation
Paid bug bounty across an on-chain DEX aggregator and a staking engine. Full safe harbour, co-ordinated disclosure, RFC 9116 security.txt.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds BlazePhoenix to
program-list.json, re-sorted with the exact jq command from CONTRIBUTING.Paid bug bounty across two protocols — an on-chain DEX aggregator and a solvency-enforced staking engine.
safe_harbor: full— good-faith research under the policy is authorised, we will not pursue or support legal action for it, and if a third party does we will make that authorisation known publicly and in writing. The conditions are stated concretely in the policy rather than left to interpretation.offers_bounty: yes, with one thing worth flagging to anyone reading this list rather than leaving them to find it: rewards are paid in the project's own token, which is not liquid yet, and settlement begins after October 2026. Reports are accepted, triaged and acknowledged now. That is on the programme page in the first screen, not in a footnote — but if the list would rather record this aspartialuntil payouts actually start, that is a fair call and I will happily change it.