LogoLogo
  • Introduction
  • Parallel Protocol
    • PRL (Parallel Governance Token)
      • Issuance
      • Bridging Module
        • Specifications
        • Implementation
      • Tokenomics
        • Epoch Concept
        • Staking Mechanisms
        • ParaBoost
        • Fee Distribution
      • Governance
      • MIMO to PRL Migration
    • PAR (€ stablecoin)
      • How does PAR work?
      • Where can I get PAR ?
    • paUSD ($ stablecoin)
      • How does paUSD work?
      • Where can I get paUSD ?
    • Classic Vaults
      • Depositing
      • Borrowing
      • Fees
        • Fees Generation
      • Withdrawing
      • Repaying
      • Liquidating
    • Bridging Module
      • LayerZero Infrastructure
      • Specifications
      • Implementation
        • PAR
        • paUSD
    • Super Vaults (SV)
      • Leveraging
      • Rebalancing
      • EmptyVault
      • Automated Rebalance
      • Managed Rebalance
    • Inception Vaults (IV)
      • Borrowing
      • Liquidating
  • DAO & Governance
    • sPRL and Voting Power
    • Governance process
    • Proposal Framework
      • Parallel Integration Request (PIR)
      • Parallel Governance Proposal (PGP)
      • Parallel Improvement Protocol (PIP)
    • DAO Multisigs
      • DAO Multisigs Elections
        • Election 1
        • Election 2
        • Election 3
        • Election 4
        • Election 5
        • Election 6
      • Multisigs Transactions History
        • May 2022 Multisig History
        • June 2022 Multisig History
        • July 2022 Multisig History
        • August 2022 Multisig History
        • September 2022 Multisig History
        • October 2022 Multisig History
        • November 2022 Multisig History
        • December 2022 Multisig History
        • January 2023 Multisig History
        • February 2023 Multisig History
        • March 2023 Multisig History
        • April 2023 Multisig History
        • May 2023 Multisig History
        • June 2023 Multisig History
        • July 2023 Multisig History
        • August 2023 Multisig History
        • September 2023 Multisig History
        • October 2023 Multisig History
        • November 2023 Multisig History
        • December 2023 Multisig History
        • January 2024 Multisig History
        • February 2024 Multisig History
        • March 2024 Multisig History
        • April 2024 Multisig History
        • May 2024 Multisig History
    • Parallel Emergency Guardians
    • DAO Treasury
      • DAO Treasury Reports
  • Risk Assessments
    • Parallel's Risk framework
    • Methodology
    • Risk per Assets
      • PAR
        • Ethereum Assets
        • Polygon Assets
        • Fantom Assets
      • paUSD
        • Ethereum Assets
        • Polygon Assets
    • Risk parameters
      • PAR
        • Ethereum Risk parameters
        • Polygon Risk parameters
        • Fantom Risk parameters
      • paUSD
        • Ethereum Risk parameters
        • Polygon Risk parameters
    • Insurance Fund
  • Developers
    • Developer Guide
    • Parallel Governance Token (PRL)
    • Tokenomics
      • Key Operations Flows
      • Contracts
    • Classic Vaults
      • Architecture
      • VaultsCore
      • Opening a vault
      • Borrowing and minting PAR/paUSD
    • Bridging Module
      • Architecture
      • Sample Use Cases
    • Super Vault (SV)
      • Proxy Design
        • MIMOProxy
        • MIMOProxyGuard
        • MIMOProxyFactory
      • Action Contracts
        • MIMOEmptyVault
        • MIMOLeverage
        • MIMORebalance
        • MIMOAutoRebalance
        • MIMOManagedRebalance
        • MIMOProxyActions
        • MIMOVaultActions
      • Leverage Max Amount Derivation
    • Inception Vault (IV)
      • IV Architecture
      • InceptionVaultFactory
      • AdminInceptionVault
      • InceptionVaultCore
      • InceptionVaultsDataProvider
      • InceptionVaultPriceFeed
    • Contract Addresses
      • Parallel V3
        • Core Protocol
        • Parallel Governance Token
      • Parallel V2
        • PAR
          • Ethereum
          • Polygon PoS
          • Fantom
        • paUSD
          • Ethereum
          • Polygon PoS
      • Super Vaults (SV)
        • PAR
          • Ethereum
          • Polygon PoS
        • paUSD
          • Ethereum
          • Polygon PoS
      • Inception Vaults (IV)
        • Kovan
  • Resources
    • User Guides
      • Setting up
      • Managing Transactions on EVM blockchains
      • Troubleshooting
      • Mint PAR
      • Liquidity Providing
        • Provide PAR-USDC liquidity on Uniswap V3 (Ethereum)
        • Provide PAR-jEUR liquidity on Balancer (Polygon PoS)
        • Impermanent loss
      • How to Migrate to PRL?
      • How to Bridge Parallel Tokens?
      • How to Stake PRL?
    • Security & Audits
    • Links
    • Glossary
    • Brand Kit
Powered by GitBook
On this page
  • Summary
  • Rules
  • Insurance Fund Assets
  • Strategy Repartition

Was this helpful?

  1. Risk Assessments

Insurance Fund

PreviousPolygon Risk parametersNextDeveloper Guide

Last updated 4 months ago

Was this helpful?

Summary

Introduced with the Insurance Fund is covering losses in case of shortfall events:

  • Smart contract risk: Risk of a bug, design flaw or potential attack surfaces on the smart contract layer.

  • Liquidation risk: Risk of failure of an asset that is being used as collateral on Parallel; risk of liquidators not capturing liquidation opportunities in a timely manner, or low market liquidity of the principal asset to be repaid.

  • Oracle failure risk: Risk of the oracle system not properly updating the prices in case of extreme market downturn and network congestion; risk of the Oracle system not properly submitting prices, causing improper liquidations.

Rules

The DAO must decide, via governance votes, which deployment (PAR and/or paUSD) is covered, which chain is covered, or not, by the insurance fund, and at which % or $ value of the insurance fund the deployment & chain are covered.

Assets held in the insurance fund must be liquid under a 16 weeks period.

At least 10k PAR for PAR deployments and 10k paUSD for paUSD deployments must stay in the vaultsCore to cover very short term potential bad debts.

DAO Multisig signers will have the right to rebalance assets from the deployed insurance fund to vaultsCore contracts in order to always have enough assets to cover very short term bad debts.

The DAO approved to cover PAR & paUSD deployment on Ethereum and Polygon PoS to up to 100% of the insurance fund.

Insurance Fund Assets

Multisig
Address

Insurance Fund Multisig

VaultsCore - PAR (only PAR in the contract)

VaultsCore - paUSD (only paUSD in the contract)

Multisig
Address

Insurance Fund Multisig

VaultsCore - PAR (only PAR in the contract)

VaultsCore - paUSD (only paUSD in the contract)

Strategy Repartition

To mitigate the associated risks with holding native Parallel stablecoins (exploit that lead the PAR & paUSD prices to 0) the DAO has approved the diversification the insurance fund holdings in a way that both diversifies the fund and supports the growth of the Parallel protocol.

10k PAR → Ethereum VaultsCore

10k PAR → Polygon PoS VaultsCore

10k paUSD → Ethereum VaultsCore

10k paUSD → Polygon PoS VaultsCore

50k USD → PAR/EURA (Ethereum) → on (& staked on )

50k USD ->paUSD/GYD (Ethereum) → on (& staked on )

50k USD → PAR/EURe (Polygon PoS) → on (& staked on )

50k USD → paUSD/stataUSDCn (Polygon PoS) → on (& staked on )

214k USD (+ potential remaining PAR/paUSD accumulated in the meantime) → swapped for AURA, then locked in vlAURA for 16 weeks on

AURA tokens will be acquired via TWAP or OTC Deal, depending on the best offer received. Accumulated rewards from & deposits would be swapped every 16 weeks for AURA tokens then locked as vlAURA for 16 weeks on .

MIP-28┃Ratify the Parallel Insurance Fund
contract
contract
contract
contract
Balancer
Aura
Balancer
Aura
Balancer
Aura
Balancer
Aura
Aura
CowSwap
Aura
Balancer
Aura
0x6aF71a3723D3c0Ed69f84EE259c9De3019C2a77c
0x173ae6283a717b6cdd5491eac5f82c082a8c674b
0xE26348D30694aa7E879b9335252362Df3df93204
0x2C6A1D01057258281eFE31bB34Bc0Df24C13086e
0x0a9202c6417a7b6b166e7f7fe2719b09261b400f
0xcABAbC1Feb7C5298F69B635099D75975aD5E6e5f