Switchboard Documentation
  • Understanding Switchboard
    • Introduction
      • Why Switchboard Oracles?
      • Vision & mission
      • Brief History and Key Achievements to Date
      • Switchboard’s Architecture, Tech Stack and Security
        • Trusted Execution Environments (TEEs)
        • Oracle Queues
        • Node Architecture
  • Product Documentation
    • Data Feeds
      • Getting Started with Switchboard Data Feeds
      • Solana / SVM
        • Part 1: Designing and Simulating Your Feed
          • Option 1: Drag-and-Drop Feed Builder
          • Option 2: Designing a Feed in Typescript
        • Part 2: Deploying your Feed On-Chain
        • Part 3: Integrating your Feed
          • Integrating your Feed On-Chain
          • Integrating into Frontends
        • Costs
        • Integrating on Eclipse
      • EVM
        • Part 1: Prerequisites and Quick Start Guide
        • Part 2: Designing and Creating Your Feed
          • Option 1: Drag-and-Drop Feed Builder
          • Option 2: Designing a Feed in Typescript
        • Part 3: Integrating your Feed
          • Integrating your Feed On-Chain
          • Integrating your Feed with Typescript
          • Integrating into Frontends (EVM)
      • Aptos
      • Sui
      • Movement
      • Starknet
      • Optional Features
        • Switchboard Secrets
    • Aggregator
      • How to use the Switchboard Oracle Aggregator
    • Randomness
      • Why Randomness is important?
      • Switchboard's Approach to Verifiable Randomness
      • Tutorials
        • Solana / SVM
        • EVM
  • Tooling and Resources
    • Crossbar
      • Run Crossbar with Docker Compose
    • Switchboard Command Line Interface
    • Technical Resources and Documentation
      • SDKs and Documentation
      • Solana Accounts
      • EVM Identifiers
      • Code Examples (Github)
  • Switchboard Protocol
    • (Re)staking
      • What is (re)staking?
      • What are Node Consensus Networks (NCNs)?
      • What are Vault Receipt Tokens (VRTs)?
      • The Node Partner Program
      • The Switchboard NCN
    • Running a Switchboard Oracle
      • Prerequisites
        • Knowledge about Linux, containers and Self-Hosting
        • Hardware Requirements and AMD SEV SNP
        • Software Requirements
        • Network Requirements
      • Hardware: tested providers and setup
        • OVH
      • Platform: Kubernetes + AMD SEV SNP
        • Bare Metal with Kubernetes (K3s)
      • The Git Repo: Clone Our Code
        • Repo Structure
      • Configuration: Tweaking Configurations
        • cfg/00-common-vars.cfg
        • cfg/00-devnet-vars.cfg and cfg/00-mainnet-vars.cfg
      • Installation: Setup Via Scripts
        • Bare Metal with Kubernetes (K3s) + AMD SEV SNP
  • Frequently Asked Questions and Glossary
    • FAQ
    • Glossary
Powered by GitBook
On this page
  1. Frequently Asked Questions and Glossary

Glossary

Term
Definition
Pros
Cons

Oracles

A blockchain primitive for propagating real-world data on-chain to be used in the context of decentralised applications. Often used in DeFi to price assets where liquidity is fractured between on-chain and off-chain sources.

N/A

N/A

Push Oracles

Broadly used oracles that consistently watch for price movements of curated assets and pushes the responses on-chain.

- No user involvement to propagate prices.

- High cost of constant updates for all transactions, regardless of usage patterns.<br>- Cost fluctuations can lead to stale data if protocols aren't willing to pay.

Pull Oracles

Gaining popularity since 2022, pull oracles use their own data layer to stream data paired with signatures from oracles verifying this data. Protocol users then bring this data on chain themselves when needed.

Much cheaper as prices are only posted when the oracle is in use. — Lower fees, meaning more freshness and lower staleness.

User behaviours relating to data submission may alter user behaviours, which may break certain assumptions made in protocols' design decisions.

Secure Enclaves

Secure Enclaves, or TEEs (trusted execution environments), are a class of hardware that can confidentially and verifiably run a process or an entire virtual machine. Output can emit a quote that confirms that output must have been generated by the binary listed.

When running an application inside a secure enclave, the application may emit any output paired with a “quote” These quotes sign the desired output with a unique signing key from within the TEE which can then be verified by any user to confirm that the generated output must have been generated by the binary listed within the quote

N/A

Enclave Quote

A cryptographically signed message that originates from within a secure enclave. Authenticated using the certificate chain of the chip manufacturer and may include data produced by an application operating inside the enclave. Attests that a specific output was indeed generated within a secure and authenticated enclave environment.

A quote serves as a verifiable mechanism to attest that a specific output was indeed generated within a secure and authenticated enclave environment.

N/A

MR_ENCLAVE

Intel's designation for an “enclave measurement”. A signed 32-byte hash that represents the binary or runtime loaded into the trusted execution environment. It serves as a definitive fingerprint of the code executing within the enclave, proving its authenticity and integrity.

All enclave quotes include an MR_ENCLAVE value, allowing verification of the specific code that produced a give output and confirms output from an authenticated/untampered code base within a secure enclave.

N/A

PreviousFAQ

Last updated 2 months ago