Simulacrum
  • Overview
  • Existential Attestation
    • Validators
  • Synthetic Blockchain
    • Organization
      • Indexer
        • Sources
          • X
          • Telegram
          • TBD
      • Blocks
      • Mempool
      • Commands
        • Wallet
        • Metaprotocols
        • Modifiers
        • Arguments
        • Keyword Arguments
      • Effects
    • Roadmap
  • Metaprotocols
    • The Drops
      • Modules
        • Tokens
          • Token Deployment
          • Airdrops
          • Trading
          • Liquidity
        • Trading
        • Vaults
      • Points
    • MiniGame (TBD)
    • Sportsbook (TBD)
    • Lottery (TBD)
  • Revenue
    • $EMP Staking
  • Fair Witness API
    • Integration
  • FAQ
  • Guides
  • Website
  • X
  • Empyreal
  • Empyreal Docs
Powered by GitBook
On this page

Metaprotocols

PreviousRoadmapNextThe Drops

Last updated 7 months ago

A MetaProtocol is a protocol built on top of the synthetic blockchain, that can be organized into a set of modules and/or commands. The first MetaProtocol will be , but additional metaprotocols are being developed. We will start by only allowing whitelisted protocols to be introduced, but eventually the registering of protocols will be permissionless. A MetaProtocol has a variety of customizations within the Synthetic Blockchain. For example, a MetaProtocol can decide to only accept from certain sources. This helps to limit risks associated with introducing experimental sources at a later point in time.

The benefit of building a MetaProtocol on top of Simulacrum is, it allows for users to focus on implementation logic for arbitrary . Developers can applications that leverage any or all Sources that are supported by The Simulacrum. For example, once a telegram source is introduced, we will be able to allow applications to be developed (such as trading bots) where a user can use a platform like Twitter or Telegram, and no longer has to trust Centralized Execution.

The Drops
Commands
Commands