LogoLogo
  • Start Here
    • Use Cases
    • Fees
    • Integrated DEXs
    • Submitting an Order
    • Available Tokens
    • Post-Order Analytics
    • Setting Up Notifications
    • Managing DeFi Strategies
    • Smart Order Router (SOR)
    • Terminology
  • Referrals
  • Order Types
    • Dexible's Order Types
      • Segmented Market
      • TWAP
      • Limit
      • Take Profit
      • Stop Loss
      • Trailing Stop
      • Stop Limit
  • DXBL
    • DXBL & Proof of Trade Litepaper
      • Proof of Trade
      • Minting Rate
      • Supply Mechanism
      • Burning $DXBL
      • DXBL Discount
      • Summary
    • DXBL Technical Paper
      • Smart Contract Architecture
      • Design Principles
      • Proxy Pattern
      • Change Process
      • Multisig Approach
      • Configuration
      • Community Vault Contract
      • Dexible Contract
      • DXBL Token Contract
      • Arbitrum Gas
    • DXBL FAQs
      • $DXBL Contract Addresses
      • $DXBL Questions
      • Protocol Mechanics
      • Trader Questions
      • Miscellaneous Questions
    • Terminology
    • Audit & Contract Addresses
  • Support
    • Changelog
    • How to Participate
    • FAQs
  • Miscellaneous
    • Dexible Press Kit
    • 🔗Resource Links
      • Blog
      • Help
      • Academy
    • 🔗Important Links
      • Terms Of Service
      • Privacy Policy
      • Dexible SDK
    • 🔗Community Links
      • Twitter
      • Telegram
      • Discord
      • Youtube
      • Medium
Powered by GitBook
On this page

Was this helpful?

  1. DXBL
  2. DXBL Technical Paper

Dexible Contract

How are execution types fuliflled? How are roles defined and determined?

PreviousCommunity Vault ContractNextDXBL Token Contract

Last updated 2 years ago

Was this helpful?

The Dexible contract is responsible for satisfying execution requests. Today it only support Swap requests. But future versions will open this up to more executions types such as lending, staking, and other primitives.

Here is the relationships for the Dexible contract:

Like the Community Vault, there are base contracts that provide configuration, storage property views, and swap functionality for protocol. Dexible is configured with whitelisted relay wallets. The relays are used to enforce the rule that only relays can submit sensitive execution requests where certain fields of the request require more control, like affiliate fees for example. Here is a breakdown of how these contracts satisfy the requirements:

Requirement
Satisfied By
Description

1,2,4

Gnosis Safe

Safe multi sig ensures multiple parties approve changes

5,6

Dexible

Restricts private swap requests to only those addresses with the "relay" role. And Dexible offers both relay and public swap submissions.

7-8

CommunityVault

By leveraging its relationship with the vault, Dexible can ask the vault for current prices of fee tokens to convert the gas fees to fee-token units. Dexible also uses the vault to determine if a fee token is allowed.