What is Switchboard (SWITCH)?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
Switchboard is a decentralised oracle network on Solana (and other chains) that competes with Pyth Network by offering a permissionless, community-driven model — any developer can create their own data feed on Switchboard without needing to be a permissioned publisher, making it more accessible for custom and long-tail data use cases.
Switchboard vs Pyth — different philosophies
Pyth Network uses a first-party publisher model: only verified, institutional-grade market participants can publish data. This ensures high-quality, accurate prices but creates a permissioned entry barrier. Switchboard uses a permissionless model: anyone can create a data feed, specifying how the data should be sourced (which APIs to query) and who should run the jobs (which oracles should process it). This openness allows Switchboard to support a much wider range of data types — not just financial prices, but any on-chain or off-chain data.
In practice: for mainstream DeFi price feeds (ETH/USD, SOL/USD), Pyth has the edge in data quality and institutional backing. For custom data feeds — sports outcomes, weather data, unique asset prices, protocol-specific metrics — Switchboard's permissionless model is more accessible and faster to deploy.
SWITCH token
SWITCH is the governance token of Switchboard. It governs: oracle node parameters, fee settings, and protocol development. SWITCH also has a staking function where node operators stake tokens as collateral, economically incentivising accurate data reporting. Total supply: 500 million SWITCH.
Is SWITCH legal in India?
Yes. SWITCH qualifies as a Virtual Digital Asset (VDA) under Indian law. 30% tax on gains and 1% TDS applies. Always consult a tax professional.
🟡 A bit more detail
For when you want to go a little deeper.
Switchboard V2 — permissionless feed creation
Anyone can create a Switchboard feed by: specifying the data sources (REST APIs, websocket feeds, on-chain data), defining the aggregation method (median, mean, custom), setting the update frequency and minimum node responses, and deploying the feed configuration on Switchboard. Node operators who run Switchboard nodes pick up job configurations and process them. The quality of a feed depends on which node operators process it and the reliability of the specified data sources — lower quality control than Pyth's curated publisher model, but vastly more flexible.
Multi-chain expansion
Switchboard started on Solana but expanded to EVM chains including Ethereum, Arbitrum, Base, and others. This multi-chain presence makes Switchboard useful for cross-chain DeFi protocols that need consistent oracle infrastructure across multiple deployments. For protocols already using Switchboard on Solana, extending to EVM chains with the same oracle provider reduces vendor complexity.
Switchboard's openness is its strength and its risk. Any permissionless system can have poorly-configured feeds with low-quality data sources. Always verify a specific Switchboard feed's configuration — how many node operators process it, what data sources are used, and the update frequency — before using it as a critical price reference in a DeFi protocol. Live data: CoinGecko
🟣 The full technical picture
For the technically curious.
Key facts
- Token: SWITCH (governance + node operator staking, 500M supply)
- Function: Permissionless decentralised oracle network
- Chain: Solana (primary) + Ethereum, Arbitrum, Base
- vs Pyth: Permissionless (anyone creates feeds) vs first-party institutional publishers
- Data types: Financial prices + any custom data (sports, weather, custom metrics)
- Feed creation: Any developer can deploy a custom feed configuration
- Node operators: Stake SWITCH as collateral for data accuracy incentive
- Competitors: Pyth Network (dominant Solana oracle), Chainlink
Oracle network architecture
Switchboard oracle nodes run off-chain workers that continuously process job configurations. Each job specifies: (1) data sources to query; (2) parsing rules (how to extract the value from each source); (3) aggregation method across sources. Node operators submit results on-chain and are rewarded with SWITCH tokens per successful aggregation. A result is accepted when a minimum number of node operators agree within a confidence threshold. The on-chain result is a median or mean value with a confidence interval. Node operators who deviate significantly from the consensus can have their staked SWITCH slashed.