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
  • Intro
  • Custom DNS or use our automagic one: xip.switchboard-oracles.xyz
  • Bring you own DNS name
  • Firewall and traffic
  1. Switchboard Protocol
  2. Running a Switchboard Oracle
  3. Prerequisites

Network Requirements

Networking, IPv4, IPv6, possibly DNS and more fun stuff!

Intro

Our network setup has minimal requirements:

  • 1 public static IPv4 pointing at your server

  • port 80 and 443 open and available on the IPv4

  • all the usual network requirements needed for Kubernetes

  • a DNS record pointing at your IPv4 address (more on this later)

That's it. IPv6 is supported, just not included in this guide. We plan to include it in this manual in future.

Custom DNS or use our automagic one: xip.switchboard-oracles.xyz

In our setup, we use DNS to provide a TLS certificate to encrypt communication.

While you can use your custom DNS record, that points to you IPv4 address, in order to avoid unnecessary overload, we introduced the use of SSLIP-based services to achieve the same result.

The way it works is simple: you just craft a DNS name based on your IPv4 and add xip.switchboard-oracles.xyz ... as an example if you need to resolve 127.0.0.1 just use:

127.0.0.1.xip.switchboard-oracles.xyz

this DNS record will always resolve to the IPv4 127.0.0.1 while also providing a valid DNS result.

This setup works perfectly for our setup and doesn't require you to buy and maintain a set of DNS records just for the Oracle setup.

Bring you own DNS name

If you decide to go with the solution of using your own custom DNS, before moving forward be sure to create a DNS record that points to your server public IPv4 ( and IPv6 if you have one ) address and verify that it is propagated correctly.

Firewall and traffic

As mentioned above, at the very minimum your server will need to answer incoming requests on port 80 and 443 for the Oracle to be working correctly.

For outgoing traffic, just allow all connectivity as many network ports are involved in the communication especially in the higher range (>= 30K).

PreviousSoftware RequirementsNextHardware: tested providers and setup

Last updated 2 months ago