Superform v1
  • Introduction
  • Components
    • Protocol
    • Keepers
    • API
    • App
  • E2E Flows
    • Same-chain Deposit
    • Cross-chain Deposit
    • Same-chain Withdrawal
    • Cross-chain Withdrawal
  • Periphery Contracts
    • SuperformRouter
      • SuperformRouterPlus
      • SuperformRouterPlusAsync
    • PayMaster
    • PaymentHelper
    • EmergencyQueue
    • SuperformFactory
    • Forms
      • ERC4626Form
      • ERC5115Form
      • ERC7540Form
    • SuperPositions
      • ERC1155A
    • RewardsDistributor
  • Core Contracts
    • State Registries
      • CoreStateRegistry
      • AsyncStateRegistry
      • PayloadHelper
    • AMB Implementations
      • LayerzeroImplementation
      • LayerzeroV2Implementation
      • WormholeARImplementation
      • HyperlaneImplementation
      • AxelarImplementation
    • Broadcasting
      • BroadcastRegistry
      • WormholeSRImplementation
    • Bridge Validators
      • LiFiValidator
      • SocketValidator
      • SocketOneInchValidator
      • DebridgeValidator (and forwarder)
      • OneInchValidator
    • DstSwapper
    • Settings
      • SuperRBAC
      • SuperRegistry
  • SuperVaults
    • SuperVaults
  • Resources
    • Deployment Addresses
    • Subgraphs
      • Protocol Level Entities
      • Form Related Entities
      • Deposits and Withdrawals
      • SuperPosition Events
      • External Entities
    • Infrastructure Integrations
    • Security & Audits
    • Protocol License
    • Glossary
    • Protocol Multisig
    • Superform Labs Socials
Powered by GitBook
On this page

Was this helpful?

  1. Components

Protocol

Last updated 1 year ago

Was this helpful?

The Superform Protocol is EVM-native and will be deployed on Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Fantom, BNB Chain, Base, zkEVM, and Gnosis. Identical Superform contracts are deployed on each chain supported by Superform and are deployed to the same addresses found here Deployment Addresses

Superform contracts are split into two categories: Core and Periphery.

  • Core contracts contain logic to move liquidity and data across chains along with maintaining roles in the protocol

  • Periphery contracts contain the main touch-points for protocols and users to interface with and include helper contracts to ease 3rd party integrations

This documentation will only cover external calls in non-abstract contracts. More information on internal functions and abstract contracts are viewable in Superform's Github repo.