AIP - 155 Informational: Planned Implementation Process

Introduction: is proud to support the ApeCoin community in facilitating an ongoing bug bounty program for all AIPs. Given our experience with leading the audit for the ApeCoin DAO marketplace, as well as our deep expertise in end-to-end web3 solutions, we, as fellow apes and ApeCoin holders, look forward to serving this critically needed role as a proactive preventative measure.

As our community’s holders are often targets for social engineering, exploits, and hacks, we know that security is critical to enable the growth of ApeCoin usage and holders.

We know that AIP 134 was an effort at a fix for this, however, we were disappointed in how limited it was in scope (specific to staking only) and the lack of access for other AIPs to receive funding and resourcing to run key preventative security programs to protect their software infrastructure and communities. We believe our role can help enable efficiencies to operationalize the bug bounty program in terms of onboarding, bug identification, bug remediation, bug reward payout, and ultimately return of unused pooled funds across all existing and future AIPs.

Key Roles and Responsibilities

This Bug Bounty Program is a shared responsibility between AIP authors, Immunefi,, white hat hackers, and the broader ApeCoin community. will be responsible for the following:

  1. Initial setup of the program and coordination between AIP authors onboarded, Immunefi, and the community
  2. Onboarding of future ApeCoin DAO-approved AIP authors
  3. Monthly communication (via Twitter Space or similar) on example bugs, latest bug findings, and general bug bounty program Q&A
  4. Coordination of quarterly reporting, which includes bug status, findings, and payouts.
  5. Review bug payouts prior to communication with white hat hackers, to ensure a balanced view of technical severity (as defined by Immunefi and standards) and community impact. has the final decision on payouts.

AIP authors will be responsible for:

  1. Self-identifying and requesting onboarding via the website contact form. (A specific page will be added to the site in Q1 with information on BBP applications)
  2. Definition, Scope, and Program oversight of bug bounty program specific to their AIP.
  3. Time availability with for onboarding, including walkthrough and review of AIP-specific program(s).
  4. Onboarding (with guidance) to the Immunefi platform, including “targets” for bug bounty
  5. Review of all identified bugs for associated applicable AIPs and facilitate timely remediation
  6. SLA requirement of 48-hour response to any questions or requests raised by or Immunefi.
  7. SLA requirement of 72-hour lead time to provide status updates for monthly updates and quarterly reporting
  8. Failure to align to #6 and #7 SLAs will result in removal from the bug bounty program. AIP authors can request to be re-onboarding with a trial period.

Immunefi is responsible for:

  1. Bug Bounty platform to facilitate the metadata and data capture for program criteria, targets, and impact.
  2. Consumption of targets from AIP authors
  3. Definitions and standards for impact based on existing standards defined by Immunefi (with opportunity for input from to adjust) and provide clear communication to community on types of bugs and rewards
  4. Management of 1M $APE funds
  5. Providing timely and relevant information to the team prior to any reward communication
  6. Acceptance of decision to override or adjust payout with reasonable reasoning and commentary provided.
  7. SLA requirement of 72-hour lead time to provide bug bounty program reporting for monthly updates and quarterly reporting to ApeCoin DAO community. Ideally, if there are major bugs found, Immunefi, AIP authors, and Solidity will collaborate to provide clear and concise communications to the community.

Who can participate:

Overall, anyone is able to participate in the bug bounty program. Those interested in participating will need to set up an account on Immunefi. Individual AIP owners will provide a framework that allows for participation by all, but also the ability to protect IP, proprietary processes, and non-public code blocks. will report on any instances where access is limited and provide recommendations for either formal audit (excluded from bug bounty funding) or for recommendations on white hat hackers willing to test under NDA.

Link to AIP 155: AIP-155: Should we fund an ongoing bug bounty program for all AIP’s that introduce security risk?


Great context and a great plan. Thank you!


Sounds like a sensible and common sense idea!


Big fan of the SLAs. This is much needed and well thought out context, thank you


Thanks for making this AIP clear and concise. I could go back through it a few times to digest the info without hating my life.

As an approved AIP owner (AIP-88) I like the idea and would be interested in participating and helping to build this process out. If approved AIPs can get this kind of support, it’ll help keep the ApeCoin reputation strong by preventing issues that can be caught and remedied sooner + help us move faster with our ideas and innovation.


Proven track record. Important. Useful.

I like it…



Hi everyone,

As I’m reviewing the AIPs for this week, I think it’s worth highlighting the importance of clearly setting expectations, deliverables, AND mandated moderation/reporting for the ongoing program. @alexmccurry and the Solidity team, including @8uddha, have been participating in the DAO long enough to understand some of the difficulties we’re facing - and continue to push solutions forward. The concept of “progress > perfection” has come up frequently in recent discussions about ApeCoin. If our community values security and inviting new developers to our ecosystem, then a bug bounty will surely create a meaningful impact during its course.

Thank you,


Sharing context around my decision-making process and vote in favor of AIP-155 in case it’s useful for anyone else.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.