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

Keepers

Keepers are infrastructure that triggers automated actions on the Superform Protocol to fulfill cross-chain transactions. Same-chain transactions are atomic and do not require any off-chain activity.

Keepers cannot change the original user intent, serving only to update values within user-specified parameters to fulfill a powerful UX.

There are 4 core functions Keepers perform on the Superform protocol:

  1. Updating amounts and transaction data on deposits and withdrawals respectively, done by CoreStateRegistryUpdater

  2. Processing payloads after quorum is reached on deposits and withdrawals, done by CoreStateRegistryProcessor

  3. Rescuing failed deposits if the price of a token to be received falls below the user intent, done by CoreStateRegistryRescuer

  4. Swapping tokens on deposits if needed on the destination chain, done by DstSwapper

You can read more about roles in the Superform protocol here: SuperRBAC

Last updated 1 year ago

Was this helpful?