What is SEDA FAST?
At its core, SEDA FAST provides an authenticated API endpoint that enables developers to execute Oracle Programs securely without the delays associated with direct on-chain execution. Each response is cryptographically signed by SEDA FAST, attesting its integrity and enabling verification in any environment. This design allows developers to request data updates at any frequency their application demands—from real-time data feeds to high-frequency event signals.
SEDA FAST's architecture enables multi-chain data publishing, meaning the same Oracle Program execution can be verified and used across any blockchain. This makes SEDA FAST ideal for latency-sensitive applications like, for example, DeFi protocols requiring rapid price data updates, gaming applications needing real-time data, or any system where sub-second oracle responses are critical.
Key Benefits:
Ultra-Low Latency: Sub-second response times for time-critical applications
Cryptographically Signed: Every response is signed by SEDA FAST for verification
Multi-Chain Compatible: Publish data to any blockchain
Flexible Request Frequency: Request data as often as your application needs
Production-Ready: Enterprise-grade infrastructure with auto-scaling and global CDN
When to Use SEDA FAST:
Real-time data feeds for decentralized protocols
High-frequency data requirements (e.g., gaming, real-time data environments)
Applications requiring sub-second oracle latency
Multi-chain deployments needing consistent data sources
How It Works
SEDA FAST orchestrates multiple components to deliver low-latency oracle execution while maintaining security and data integrity.
The following diagram illustrates the high-level architecture and data flow:
┌─────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Client │ HTTPS │ SEDA FAST API │ │ SEDA Chain │
│ Application │◀────────▶│ (Authenticated) │◀────────▶│ (Oracle Program │
│ │ │ │ │ Repository) │
└─────────────┘ └──────────────────┘ └─────────────────┘
▲
│
▼
┌──────────────────┐
│ Oracle Program │
│ Execution │
│ (Exec + Tally) │
└──────────────────┘
▲
│
▼
┌──────────────────┐
│ Data Proxies │
│ (External Data) │
└──────────────────┘Authentication with API Keys
SEDA FAST uses bearer token authentication to secure access to the API. Each request must include an API key in the Authorization header. API keys are provided during onboarding and control access to the execution API.
Credits System
SEDA FAST operates on a pre-paid credits model:
Credits are purchased or allocated to your account in advance
Each Oracle Program execution consumes credits based on computational resources used
Credit limits can be set to control spending
Real-time credit balance and usage tracking via the /project endpoint
Credits are deducted when an execution completes, with a portion allocated to Data Proxy providers based on their fees.
Oracle Program Execution Flow
When you make a request to SEDA FAST:
Validation: Your API key is validated and your configuration is checked (credits, allow-lists, limits)
Program Fetching: The Oracle Program is retrieved from the SEDA blockchain (or from cache)
VM Execution Phase: The Oracle Program runs with your specified inputs, potentially fetching data from allow-listed Data Proxies. Results are processed through the tally program to produce the final output
Response: The signed result is returned to your application
Data Proxy Access
SEDA FAST enables access to external data through Data Proxies — independent, reliable data providers that Oracle Programs can query during execution. SEDA FAST allows access to a curated list of Data Proxies covering a wide range of data sources, enabling your Oracle Programs to retrieve the high-quality data they need.
If your application requires access to specific data sources, the SEDA team can facilitate onboarding additional Data Proxy providers. Each Data Proxy provider sets their own usage fee.
Response Signing & Verification
Every response from SEDA FAST includes a cryptographic signature that can be verified using SEDA FAST's public key (available via the /info endpoint).
This signature proves:
The response came from SEDA FAST
The data has not been tampered with and the execution results are authentic
This enables applications and smart contracts to verify oracle data without trusting the relayer.
Last updated
Was this helpful?

