Pharo
  • 🟢Getting Started
  • 🤝Meet Pharo
    • ❔Why Pharo
    • 🌪️Use Cases
    • 📐Architecture
  • ✨Protocol
    • 🎨Product Design
    • 💰Pricing Models
    • 🏛️Capitol Provision
    • 📊Risk Assessment
  • 🛣️Roadmap
  • ⁉️FAQs
  • Market Manager
    • 💹Creating a Pharo Market
    • 👩‍💼Managing a Market
  • Liquidity Provider
    • 🎯Selecting a Market
    • 💵Provide Liquidity
  • Cover Buyer
    • 🤔What it means to buy cover
    • 🔅Buy Cover
  • Governance
    • Overview
    • Process
      • 📄Writing A Proposal
    • Glossary
    • Adversarial Circumstances
    • Governance Reference
  • PHRO Token
    • Overview
    • 🪙Tokenomics
    • Staking
    • 📄Contracts
    • 🐪PHRO Distribution Speed
  • Guides
  • Beginners Guide to Voting
  • Setting Up Your Local Environment
    • Hardhat
    • Foundry
  • API Reference
    • Start Here Developer
  • Technical Reference
    • Litepaper
    • Smart Contracts Overview
    • Pharo SDK
    • Anubis
    • Obelisk
Powered by GitBook
On this page

Was this helpful?

  1. Meet Pharo

Architecture

How we built Pharo ACM

PreviousUse CasesNextProtocol

Last updated 1 year ago

Was this helpful?

The system will consist of four layers, including:

  • User Layer, to provide the user access functions for platform users such as cover buyers, liquidity providers (investors), or market managers.

  • Operation Layer, to cover the various business or user operation scenarios interacting with the Pharo protocol and its core functions.

  • Products Layer, to build the core functions of the platform, such as product offering, liquidity pools, pricing models, governance, etc..

  • Infrastructure Layer, set up the interactions with Ethereum network as a base, and maintain interoperability with external oracles and cross-chain utilities.

🤝
📐