DEFINITIVE.
  • What is Definitive
  • Getting Started
  • Platform
    • Advanced Trading
      • Market Order
      • Limit Order
      • TWAP Order
      • Stop Order
      • Degen Mode
      • Bridging
      • Post-Trade Report
      • Pre-Trade Compliance
    • EDGE Token
      • Claim
      • Staking
      • Airdrop
        • Airdrop Announcements
    • Other Products
      • cbBTC Hub
      • Advanced Yield (V1 Deprecated)
        • Hyperstaking
        • LPStaking
        • Dedicated Vaults
        • Yield API
      • EDGE.EXE Points Program (Concluded)
    • Metrics
  • USERS
  • FAQ
    • Advanced Trading
    • Yield (V1 Deprecated)
    • Fees
    • Referrals
  • Guides
    • Mobile PWA
    • TWAP
    • Manual Smart Contract Interaction
      • Etherscan Withdraw
    • How to Send Tokens Directly to Your Trading Vault
    • Centralized Exchange Onboarding
      • From Coinbase
    • Fireblocks Solana (Solana WalletConnect) Tutorial
    • Using Squads Wallet with Definitive
    • Using Safe Wallet with Definitive
  • Institutions & Funds
  • DEVELOPERS
    • Trading API
  • References
    • Audits
      • Zellic - Smart Contract Security Assessment #1
      • Zellic - Smart Contract Security Assessment #2
      • Zellic - Smart Contract Security Assessment #3
      • Zellic - Smart Contract Security Assessment #4
      • Ottersec - Smart Contract Security Assessment #5
    • Media
    • Logos & Media Kit
Powered by GitBook
On this page
  1. DEVELOPERS
  2. Technical Overview

Core

The Definitive Core uses an event-driven architecture to handle high throughput on-chain events at scale. The core is responsible for receiving and publishing events onto a single source-of-truth stream to be consumed and acted upon by components. The core is off-chain and proprietary to Definitive.

Components - As events are published to the core, components with various responsibilities will subscribe and react to these events. Components manage all sorts of positions and react to market or on-chain events to effectively manage those positions.

Feeders - Components require data from 3rd party sources to execute on strategies. Data may include trades (market makers), market data (price feeds), and on-chain events (mempool and confirmations). Feeders will decode and translate events across multiple chains and data sources.

Performers/Keepers - Components may require actions to be taken on 3rd party services, such as interacting with liquidity providers, lending pools, or bridges. Performers are responsible for reliably executing the desired action, optimizing transactions for speed, gas efficiency — employing different techniques for MEV resistance.

Engines - A group of components that form the “brain” of the computation. Grouping components allow for breaking down complex tasks into composable building blocks.

Last updated 9 months ago