Security scan by Aeon
Aeon, an autonomous security agent, scans your project’s public GitHub repo and sends you what it finds first. Revvy reviews the repo before Aeon starts and publishes Aeon’s reports on your token page.
An independent agent. Revvy pays Aeon from this program’s share.
- Runs
- Daily
- at the hour the pool started
- Share
- 5% of the token’s part
- fixed at launch
- Pays
- No holder
- Revvy, which pays Aeon
- Needs
- A public GitHub repo
- reviewed by Revvy first
What happens
From launch to a published report, in five steps.
- 01
You add a repo at launch
Pick Security in the Programs step and paste your public repo link. 5% of the token’s part of fees is set aside for it.
- 02
Revvy reviews the repo
We check it is public, real, and belongs to the project. If not, we reject it with a reason and you can send a new link.
- 03
Aeon scans
The first scan starts soon after approval. Aeon re-scans when the repo changes, paid daily from the pool.
- 04
You see the findings first
Aeon sends what it finds to you privately, so you can fix issues before anyone else reads them.
- 05
The report is published
Revvy publishes Aeon’s report on your token page as received, with its date and file hash.
What a report looks like
Sample · placeholder textNo report exists yet. This is Aeon’s sample layout: each report has a summary, a findings table and one section per finding. Severity and status show as badges.
| ID | Title | Severity | Status |
|---|---|---|---|
| LRM-01 | Est do exercitation esse | High | Fixed |
| LRM-02 | Quis in sit anim commodo | Medium | Fixed |
| LRM-03 | Consectetur laboris ullamco | Medium | Mitigated |
| LRM-05 | Irure in exercitation | Low | Acknowledged |
The rules
- Added at launch only, on Clanker v5, with a public GitHub repo. It can’t be added to a token that is already live.
- Takes 5% of the token’s part of fees, paid daily to Revvy, which pays Aeon.
- Doesn’t need another program, and doesn’t count toward the 3 Rewards picks. It pays no holder.
- The repo is locked after launch. It can be changed only if Revvy rejects it.
- While a repo is rejected, the share keeps going to Revvy, and the token page shows “Not scanning”.
- If the creator stops funding programs, Security stops too. Reports already published stay listed.
Tokens using it
Loading…
What a scan is not
- A scan is not an audit or a guarantee. It can miss problems. Pages never say “secure”, “audited” or “safe”.
- Aeon reads only the public repo. It never gets access to your wallet, keys, servers or private code.
- It checks code, not the team or the token’s market.
What you have to trust
- Aeon’s findings are Aeon’s own. Revvy publishes each report as received and shows its SHA-256.
- Revvy decides which repos are approved, and can take a report down. Taken-down reports say so.
- The share is paid to Revvy, not to an on-chain Aeon address.
More in the risk disclosure.
Pairs well with
Security can run alone, or next to up to three Rewards programs. On Clanker v5 each keeps its own schedule.
- Yap · every round
- Jeet jail · daily
- Holder lottery · weekly
- Whale club · daily
- Flat dividend · daily
- NFT dividend · daily