Security

Audits

At SNAP, we place the utmost importance on the security and integrity of our protocol and community. As a fork of Lynex, SNAP inherits a thoroughly audited and battle-tested codebase originally derived from the Solidly → Velodrome → Thena → Lynex lineage. Our approach builds on this proven foundation, adding continuous internal monitoring and review for all new contracts deployed within the TAC ecosystem.

Key Security Measures

Inherited Audit by Secure3: Lynex, the protocol SNAP is forked from, successfully completed a comprehensive security audit conducted by Secure3. This audit validated the safety and performance of the ve(3,3) architecture, including voting gauges, bribes, and emission systems that underpin SNAP’s own design. View the Secure3 Audit Report Robust Codebase Heritage: SNAP’s smart contracts descend from the same core architecture audited and deployed across Thena, Velodrome, and Solidly, all of which have maintained a strong record of security with no major reported exploits.

Related Security Audits and Practices

Thena’s Security Audit: Thena (which Lynex forks) has undergone extensive audits by OpenZeppelin and PeckShield. These audits covered the ve(3,3) framework and associated emissions mechanisms. Algebra’s Audits: Our DEX infrastructure, powered by Algebra, has been independently audited by multiple leading security firms: ABDK Consulting, Hexens, and Hacken.These audits collectively reinforce the safety of the contract infrastructure that SNAP operates upon.

⚠️ User Caution Advised While audits significantly reduce risks, they do not eliminate them entirely. Users should review our legal disclaimers before interacting with the protocol. For security-related queries or concerns, please contact the SNAP team through our verified communication channels.