Skip to content

Public bug-bounty program setup + scope + disclosure policy #1030

Description

@joelpeace48-cell

Epic: Compliance & Trust

Summary

Establish a bug-bounty (e.g. via Immunefi/self-hosted) with clear scope, rewards, and safe-harbor before mainnet.

Background & Problem

A funded bounty is a strong pre-mainnet signal and surfaces issues an audit may miss; it also reassures grant reviewers.

Acceptance Criteria

  • Bounty scope + rewards published.
  • Safe-harbor + disclosure policy documented.
  • Intake process defined.

Filed as part of the mainnet-readiness & world-class roadmap. Scope is intentionally small enough for one focused PR; comment to claim.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationmainnetCritical for mainnet launchpriority: mediumMedium impactsecuritySecurity hardening and scanning

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions