Flaunch Docs
  • For Builders
  • For Creators
  • Changelog
  • Welcome Builders
  • Builder Fund
  • Token Managers
  • Get Started
  • Implementation
  • Manager Types
    • RevenueManager
    • AddressFeeSplitManager
  • Submit your App
  • References
    • SDK
    • API
    • Solidity Cookbook
    • Subgraph
      • Graph Explorer
      • Subgraph Query Examples
      • Indexing Swaps
  • Artificial Intelligence
    • Vibe Guide
    • AgentKit
    • MCP
  • Developer Resources
    • GitHub
    • Uniswap V4 Helpers
    • Contract Addresses
  • Audits
  • Bug Bounty
  • Network
    • Flaunch.gg
    • QuickIntel
  • Flaunchy
  • Nyko
  • Terms
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  • Audit 1: Omniscia
  • Audit 2: Enigma Dark
  • Audit 3: Enigma Dark

Was this helpful?

Export as PDF

Audits

PreviousContract AddressesNextBug Bounty

Last updated 1 month ago

Was this helpful?

During the development of Flaunch we undertook three audits to ensure that the protocol is secure and functions as expected. At each audit we remediated or acknowledged all known issues.

Audit 1: Omniscia

Omniscia undertook our initial audit. Unfortunately this cannot be shared publicly, but a synopsis extract from the findings has been provided below showing their initial findings.

Audit 2: Enigma Dark

The first Enigma Dark audit followed on from the Omnisca findings and also reviewed some newly implemented zap logic including flaunch scheduling and premining.

Audit 3: Enigma Dark

After the initial Enigma Dark audit there was a small raft of changes to optimise flow which were subsequently reaudited.

805KB
2024-12_Security_Review_FlayerLabs_Flaunch.pdf
382KB
2024-12_Security_Review_Extension_FlayerLabs_Flaunch.pdf