Flashstake
  • 👋Start Here
    • Flash Facts
    • Real World Example
    • Three Components
  • ⚡Flashstake Protocol (FSP)
  • ⏳Time Vault Strategies (TVS)
    • Time Vault Examples
    • Time Vault Pools
    • Time Vault Fees
    • Time Vaults Database
      • Aave
        • AAVEv2-V1 Strategies
        • AAVEv2-V2 Strategies
        • AAVEv2-V3 Strategies
        • AAVEv3 Strategies
      • Lido Finance
        • stETH
      • GMX
        • GLP Strategy
      • Rocket Pool
        • rETH
    • Time Vault Interface
  • ⚖️Time Based Tokens (TBTs)
    • Flashstaking TBTs
    • Minting TBTs (Staking)
    • Burning TBTs (FlashBurn)
    • Swapping TBTs
    • FlashNFT
  • 🌊Liquid Stake (FlashLend)
  • 🎯FlashBack
  • 🪙Tokenomics (FLASH)
    • 🗝️Token Utility
    • 💡Time Switch
    • 🚂Flash Capacitor
    • 🏦Flashstake Treasury
    • 📃Token Distribution
  • 🔗Smart Contracts
    • Addresses and Links
    • Flashstake Protocol
      • Methods
      • Events
      • Error Messages
    • Time Vault Strategy
      • Methods
      • Events
    • Flash Protocol Proxy
    • Liquid Stake
      • Methods
      • Events
  • 🔒Security and Risks
    • Audits
    • Admin Functionality
    • Unit Tests
    • Testnet Competitions
    • Disclaimer
  • 🤔FAQ
    • 🔍Where does the yield come from?
    • 🔒What are the risks of Flashstaking?
    • 🌎What are some real-world use cases?
    • 📈How is the APY calculated?
    • 🔗Where are the old docs?
  • 🧑‍🚀Flashtronaut NFTs
  • 🎆xFLASH
  • 🖼️Frontend Changelog
    • 2023 Changelog
      • FLC-2306.13 (LIQUID Upgrade)
      • FLC-2304.18 (WEBBY Upgrade)
      • FLC-2303.28 (ARBYS Upgrade)
      • FLC-2302.15 (FLIDO Upgrade)
      • FLC-2301.26 (BOOTSTRAP Upgrade)
    • 2022 Changelog
      • FLC-2212.12 (GOERLI Upgrade)
      • FLC-2211.25 (WHISTLE Upgrade)
      • FLC-2211.17 (NAMESTAKE Upgrade)
  • 📜License
Powered by GitBook
On this page
  1. Security and Risks

Unit Tests

PreviousAdmin FunctionalityNextTestnet Competitions

Last updated 2 years ago

The Flashstake Protocol has a vast array of unit tests to ensure the protocol behaves as intended. The total code coverage is over 95%

Note: The 5% of code not covered is due code written as fail safes for logic paths that are expected to never be possible to be reached. So, it could be technically argued the code has 100% coverage.

These can be found within the .

🔒
Flash Protocol GitHub