Contributors & badges
Badges say what someone has done for Maya2C. They are a record, not a reward: they carry no token, no money, and no promise of either.
The badges
Section titled “The badges”| Badge | Criteria |
|---|---|
 | Ran a validator or full node on maya-testnet-1 for at least 7 consecutive days. |
 | Reported a valid vulnerability privately under SECURITY.md, with consent to be named. |
 | Had at least one pull request merged into master. |
A person can hold more than one badge.
How to claim
Section titled “How to claim”Open an issue on the
Maya2C repository and
title it Badge claim: <badge name>. Include:
- Testnet node: your node’s peer ID, the dates it ran, and a log excerpt with keys and addresses removed.
- Security finder: the advisory link, or confirmation that the report was made privately. Do not put vulnerability details in the public issue.
- Merged PR: the pull request number.
The maintainer checks the claim against the criteria and adds an entry to
contributors.json. Claims that cannot be checked
are declined with the reason given.
Where they are listed
Section titled “Where they are listed”- The machine-readable list is
contributors.json. It starts empty. - Security reporters are also named on the Security Hall of Fame.
No one is listed until a claim has been checked. Nothing here is taken from a scanner’s output or from a name without a claim.