Xave Finance
Xave Finance Socials
  • Introduction
  • General FAQs
  • Guides
    • How to Connect Your Wallet
    • How to Supply Liquidity
      • How to Add Liquidity to FXPools
      • How to Remove Liquidity from Xave Liquidity Pools
    • How to Use Xave Strategies
      • How to Deposit to xSGD Thetanuts Strategy
      • How to Withdraw from xSGD Thetanuts Strategy
    • How to Swap
    • How to Lend
    • How to Borrow
    • How to Repay
    • How to Withdraw
    • How to Vote for Xave's Gauges in Balancer using veBAL
      • How to get B-80BAL-20WETH
      • How to Lock veBAL
      • How to Vote for a Liquidity Gauge for Xave's Pool
    • How to Earn BAL Rewards
      • How to Stake into a Liquidity Pool's Gauge
      • How to Unstake from a Liquidity Pool's Gauge
      • How to Claim BAL Rewards
    • How to Claim XSGD Rewards
    • How to Test PHPT:USDC on Sepolia Testnet
  • Product Overview
    • FXPools
      • Pool Operator FAQs
      • Invariant FAQs
    • Lending Market
    • Xave Strategies
      • Strategy # 1: Thetanuts
      • Strategy # 2: USDC Lending
  • Tokenomics
    • XAV
    • XAV Tokenomics
      • XAV MultiSigs
      • Claim Portal for Prior Community Supporters
    • Governance
  • Contract Addresses
  • TOKEN LAUNCH
    • XAV Launches and Exchange Listing
  • Future
    • Roadmap
    • FXMetaPool
  • Contract Audits
    • Overview
    • Price Oracles Final Audit
    • FXPool Final Audit
    • Lending Market
    • Standard Operating Procedure for Security
  • Liquidity Provider and Protocol Fees
    • Avalanche Pools
    • Ethereum Pools
    • Polygon (POS) Pools
  • List of supported Stablecoins
    • πŸ‡ΈπŸ‡¬XSGD
    • πŸ‡ΊπŸ‡ΈUSDC
    • πŸ‡ͺπŸ‡ΊEUROC
    • πŸ‡ͺπŸ‡ΊEURS
    • πŸ‡¬πŸ‡§GBPT
  • Socials
    • Twitter
    • Medium
    • Discord
    • Github
  • Branding Assets
    • Xave Finance Brand Assets
Powered by GitBook
On this page
  1. Contract Audits

Standard Operating Procedure for Security

As protocol operators, we regularly receive security or bug reports that result in minor to major security concerns. As a rule of thumb, the team prefers to be on the safe side and advise liquidity providers to remove liquidity immediately upon a bug report that requires more than 24 hours to investigate.

The team's main priority is keeping liquidity safe. There are upcoming features in development that will make this process easier but for now liquidity providers may sometimes be asked via our social channels, such as X (formerly Twitter) or Discord, to remove liquidity in the event of a bug report that requires more thorough investigation to ensure that various aspects of the protocol are not peripherally affected.

Last updated 1 year ago