V2 Fringe Finance Platform Docs
  • What is Fringe Finance?
  • Platform Overview
    • Multi-Chain Support
    • Censorship Resistance
  • Roadmap
  • Product Versions
    • v1 (deprecating)
      • v1 Audits
    • v2 (live)
      • v2.1
      • v2.2
    • Fringe v3
  • Fringe Lending
    • Fringe Lending
    • Borrowing
    • Lending
    • Interest Rates
    • Partial Liquidations
    • Collateral Asset Parameter Modeling
      • Loan-To-Value Ratio (LVR)
      • Maximum Borrowing Capacity (MBC)
      • Liquidator Reward Percentage
    • Amplify and Margin Trade
    • Fringe Price Oracle Model
  • USB Stablecoin
    • Stablecoin Components
    • Minting
    • USB Savings
    • Interest Rates
    • Liquidations
  • Staking, Rewards and Fees
    • Fringe Staking
    • Fee Structure
  • FAQs
  • Fringe Finance Whitepaper v1.4
  • PLP Liquidation Instructions
  • User guides and use cases
    • Hedge both assets underlying an LP token - and - hedge impermanent loss
    • Hedging Exposure to the More Volatile Underlying Asset in an LP Token
    • Isolating ERC4626 yield exposure - using Superform
    • Isolating ERC4626 yield
    • Go long BTC - with Amplify
    • Trade BTC vs ETH dominance - using Margin Trade
    • New Opportunities for ERC4626 Token Holders
Powered by GitBook
On this page
  1. Platform Overview

Censorship Resistance

PreviousMulti-Chain SupportNextRoadmap

Last updated 1 year ago

Fringe Finance’s backend was initially hosted by the Fringe Finance project. However, to ensure greater decentralization and reduce the likelihood of censorship by state actors or hosting providers, Fringe Finance has now released a decentralized backend that employs subgraphs on The Graph.

The Graph records specified on-chain activity and statistics that can be rendered on the Fringe dApp, thus removing the need for a separate Fringe backend. This is part of Fringe fulfilling its aim to increase its censorship resistance.

Decentralized back-end

Fringe’s includes two crucial features designed to protect us against the risk of censorship posed to DeFi apps: a decentralized back-end and integration with decentralized indexing services.

The move to a decentralized back-end, motivated by increased security, makes the platform less vulnerable to attacks and improves transparency. now employs The Graph and this enhancement is one of our new features to continually increase the platform’s censorship resistance.

As a follow-on after v2, we will provide an open-source, free-to-download front-end that anyone can host. This includes deploying a front-end on IPFS in the near future, which will allow multiple instances of the dApp front-end to be hosted simultaneously by independent parties. By doing so, any single actor’s attempt to deactivate any single front-end instance will be rendered powerless. Additionally, we will open-source our front-end codebase, offer grants for actors to host the front-end. Fringe is also assessing distributing our frontend dApp via nostr (employing nostr's decentralised persistent storage and messaging protocol.)

To mitigate the risk of backends being deactivated by cloud service providers, we will integrate with decentralized blockchain indexing services and make API endpoints open-source and accessible. This will enable us to provide our users with a more secure and reliable experience.

To minimize the risk of centralized RPC providers, Fringe has redesigned our RPC integration to be easily reconfigured in case the need arises to change RPC providers.

v2
Fringe Lending