Developer Docs
WebsiteGitHub
  • Protocol Architecture
    • Protocol Overview
    • Upgradability
    • Asset Configuration
    • Silo Assets
    • Bridge Assets & Bridge Pool
    • System Roles
  • Smart Contracts Overview
    • Core Protocol
      • SiloRepository
      • Silo
    • Oracle
      • PriceProvidersRepository
      • BalancerV2PriceProvider
      • UniswapV3PriceProvider
    • Ownership Tokens
      • ShareCollateralToken
      • ShareDebtToken
    • InterestRateModel
    • SiloRouter
    • SiloLens
  • SECURITY
    • Audits & Formal Verification
    • Smart Contracts
    • Bug Bounty Program
  • Silo Subgraphs
    • Subgraph Introduction
    • SILO V2 Entities
    • SILO V3 Entities
    • Querying SILO
  • Submit a Bug
  • GitHub
  • Silopedia
  • Contact Us
Powered by GitBook
On this page
  1. Protocol Architecture

Silo Assets

PreviousAsset ConfigurationNextBridge Assets & Bridge Pool

Last updated 2 years ago

For each asset in a Silo, there are three ERC-20 tokens deployed via Tokens Factory:

  • shares token that will represent a collateral

  • shares token that will represent protected collateral (cannot be borrowed)

  • debt token that will be minted to represent a debt

When the user deposits into a Silo they can decide where their deposit can be borrowed by other users to earn interest. Protected deposits are also called "collateral only" and other users cannot borrow them. Silo uses the mint and burn functions to operate these underlying tokens. Meanwhile, the transfer is still available and can be used by any third-party application (MetaMask, DEX, etc...). Underlying tokens support hooks and can notify about the basic tokens operations (mint, burn, transfer) third party smart contract if those will be configured in the Silo Repository as a notification receiver for the Silo where operation occurs. For better understanding, see basic Silo operations with assets state visualization

Underlying Silo assets state visualization