BTCBTC$64,966-0.08%|
ETHETH$1,819.18-0.17%|
USDTUSDT$0.99951+0.00%|
BNBBNB$591.2700-0.65%|
USDCUSDC$0.99972+0.01%|
XRPXRP$0.95377-0.76%|
SOLSOL$71.3500-0.69%|
TRXTRX$0.30545+0.29%|
FIGR_HELOCFIGR_HELOC$1.0490+0.00%|
HYPEHYPE$68.5000+1.20%|
ZECZEC$893.7200-1.56%|
DOGEDOGE$0.05924+0.36%|
XMRXMR$491.5500-1.55%|
LEOLEO$9.2100-0.20%|
USDSUSDS$0.99990+0.01%|
WBTWBT$62.7500-0.32%|
LINKLINK$9.1100-1.45%|
ADAADA$0.15295-0.97%|
USDEUSDE$0.99957+0.01%|
XLMXLM$0.13691-2.11%|
RAINRAIN$0.00644168+82.09%|
DAIDAI$0.99980+0.04%|
BCHBCH$207.6800-0.64%|
NEARNEAR$3.1700-0.93%|
LTCLTC$44.7900-1.39%|
CCCC$0.08260-1.10%|
AVAXAVAX$7.1300-1.97%|
UNIUNI$5.1300-0.78%|
XAUTXAUT$3,835-0.13%|
USD1USD1$0.99871+0.05%|
BTCBTC$64,966-0.08%|
ETHETH$1,819.18-0.17%|
USDTUSDT$0.99951+0.00%|
BNBBNB$591.2700-0.65%|
USDCUSDC$0.99972+0.01%|
XRPXRP$0.95377-0.76%|
SOLSOL$71.3500-0.69%|
TRXTRX$0.30545+0.29%|
FIGR_HELOCFIGR_HELOC$1.0490+0.00%|
HYPEHYPE$68.5000+1.20%|
ZECZEC$893.7200-1.56%|
DOGEDOGE$0.05924+0.36%|
XMRXMR$491.5500-1.55%|
LEOLEO$9.2100-0.20%|
USDSUSDS$0.99990+0.01%|
WBTWBT$62.7500-0.32%|
LINKLINK$9.1100-1.45%|
ADAADA$0.15295-0.97%|
USDEUSDE$0.99957+0.01%|
XLMXLM$0.13691-2.11%|
RAINRAIN$0.00644168+82.09%|
DAIDAI$0.99980+0.04%|
BCHBCH$207.6800-0.64%|
NEARNEAR$3.1700-0.93%|
LTCLTC$44.7900-1.39%|
CCCC$0.08260-1.10%|
AVAXAVAX$7.1300-1.97%|
UNIUNI$5.1300-0.78%|
XAUTXAUT$3,835-0.13%|
USD1USD1$0.99871+0.05%|
SEDA (tool)
Tool / APITier-3Oracle / data infrastructureVerified

SEDA (tool)

Programmable oracle infrastructure for builders: feeds drawn from sources including Polymarket and Kalshi, and a resolution layer that turns any definable outcome into a settled market.

Visit website

Key Facts

CategoryOracle / data infrastructure
AccessCommercial access is sales-led. The site offers a trial request and a contact form rather than self-serve plans, no price list is published, and the documentation carries a section on bespoke pricing methodologies instead of tiers — which in practice means terms are negotiated per integration and depend on the data sources and latency you need. The documentation, software development kits and a testnet wallet setup are open to anyone, so the network can be evaluated without a commercial conversation, and fees for work that actually runs use the network's own token. In other words: free to read, free to test on the test network, priced by negotiation once you deploy something real.
Venues CoveredPrediction markets appear on both sides of the stack rather than as a single venue. Polymarket, Kalshi and the prediction market data firm PM Insights are named among the data providers behind SEDA's feeds, and the resolution layer is designed for outcome markets of any kind — sports, elections, weather, corporate actions, equities and on-chain state — for builders creating their own markets. It does not resolve Polymarket's markets, which settle through Polymarket's own oracle on Polygon.
Data ConfidenceVerified
Last Reviewed1 Oct 2026

What It Does

SEDA is oracle infrastructure that a developer integrates rather than a place to read odds. It comes in two halves. The builder half is a layer-one network where you deploy Oracle Programs — verifiable code that fetches data from any public or private source, applies your own logic and returns a result, either on chain or through a low-latency API. The commercial half is a set of packaged products built on that network: composite data feeds for assets that trade around the clock, bundle feeds with configurable weighting, pre-IPO data on thousands of private companies, and an Outcomes product that resolves custom market outcomes programmatically, with no human reporters. For prediction markets specifically, SEDA plays two roles: prediction market venues including Polymarket and Kalshi appear among the data providers behind its feeds, and its resolution layer is what a builder would use to create and settle their own outcome markets — not what settles Polymarket's, which resolves through its own oracle on Polygon. Access is a trial request or a conversation with the team; there is no public price list.

Overview

What it is, in two halves

SEDA presents itself in two ways that are worth keeping apart. The commercial site sells four packaged products under the banner of powering markets that never close: composite data feeds, bundled feeds, pre-IPO data, and an outcome resolution layer. The documentation describes something more fundamental underneath them — a layer-one blockchain whose purpose is to run verifiable programs that fetch data, and to move that data into contracts or APIs.

Both descriptions are accurate, and the difference matters to a reader. If you are a venue or a product team, you are being sold a data and resolution service. If you are a developer, you are being handed a network where you write the oracle yourself — what data to pull, from which sources, filtered and aggregated how, delivered where.

Why it appears in this directory

Most entries here let you look at prediction markets. SEDA is one of the few that let you build one, and the only one in the directory whose job is to decide what happens when a market ends.

Its role splits in two directions. Inbound, it consumes prediction market data: the venues Polymarket and Kalshi are listed among the providers whose data is aggregated into SEDA feeds, which is how prediction market prices become inputs to products elsewhere. Outbound, it resolves outcomes: a builder defines a market and its resolution logic, and SEDA's infrastructure fetches the qualifying data and settles it programmatically.

What it does not do

One distinction prevents a common misunderstanding. SEDA does not resolve Polymarket's markets. Polymarket's own documentation is explicit that its resolution runs through the UMA optimistic oracle: anyone may propose an outcome by posting a bond — typically around $750 — after which a two-hour challenge period runs, and a dispute escalates to a token-holder vote that can take the timeline to somewhere between four and six days. Those resolution calls land on Polygon through adapter contracts that are visible on the public explorer, and they are Polymarket's own path to settlement.

SEDA offers an alternative resolution layer for markets you build yourself — the same category of function, a different dependency. Reading the two as one thing would be a mistake, and the directory record previously implied as much, which is why this page states it plainly.

The resolution layer: Outcomes

Outcomes is the product that matters most here. Its premise is that if you can define an outcome, the infrastructure can resolve it: a price above or below a level, whether a team won, whether a temperature threshold was breached, whether a governance vote passed. Four families of source are supported — public market data across equities, commodities, crypto and foreign exchange; private data such as corporate actions, earnings and bilateral quotes; real-world events including sports, weather, elections and policy decisions; and on-chain state such as protocol metrics or lending positions.

The vendor's own pages show the intent with demonstrations rather than prose: a resolver view where each example outcome carries the source that decided it and the milliseconds it took, and a status block listing a production version, a median resolution latency, a count of markets resolved over the past thirty days and an uptime figure. Those figures are worth reading with the caveats below, because SEDA's own disclaimer defines them narrowly — the latency claim, for instance, describes endpoint query behaviour rather than end-to-end settlement time.

Feeding data in: Signal and Bundles

Signal is the data product: continuously updated composite feeds for assets that trade around the clock, assembled from multiple providers and venues so that a market can keep pricing on a weekend, a holiday or outside trading hours. The mechanism is aggregation with failover and outlier detection, plus a configurable smoothing and session-awareness layer for instruments whose reference venues close.

Latency is sold in tiers rather than as a single promise, from milliseconds for the fastest tier through sub-second tiers intended for perpetual venues and liquidation engines, to a second and beyond for index products, dashboards and settlement. Bundles sit on top: instead of one asset, you define a weighted combination — a basket, an index, a spread — with automatic rebalancing. The published example pairs a broad equity benchmark with a perpetual venue's data, which is a reasonable illustration of what bundling is for.

How the infrastructure actually works

The mechanism is worth understanding because it explains both SEDA's flexibility and its cost model. Data is fetched by Oracle Programs: deterministic, verifiable units of code that pull from an endpoint, apply your filtering and aggregation logic, and return a structured result. They are compiled to WebAssembly, deployed to the network and identified by an ID. Any public endpoint can be queried directly; for private or paid sources, a Data Proxy holds the API credential on the provider's behalf, which is how a feed can be built on data that is not openly crawlable without exposing the key.

Delivery then splits. SEDA Fast serves results as an API and a WebSocket stream, which suits off-chain products that need continuous data. SEDA Core posts requests on chain and returns results to contracts, with prover contracts deployed per EVM network and a Hardhat integration for reading them. In practice, a prediction market builder might use the on-chain path for what must be trustless and the API path for what only needs to be fast.

The token

SEDA runs on its own token with a genuinely unusual mechanic: network usage burns supply. Executing Oracle Programs, delivering data and deploying programs all cost tokens, and a defined portion is permanently removed from circulation as part of protocol process rather than sent to a treasury. Staking secures the network — validators on the main chain, and separately the node operators that serve data proxies — and holders can delegate to validators through the standard wallet interface and vote on governance proposals. Burns, staking and deployment activity are tracked on the project's own explorer trends page and by third parties including DefiLlama.

Reading the numbers on its site

SEDA's marketing pages carry prominent statistics — volume supported, data feeds in production, uptime, tokens burned — and every one of them is footnoted to a content disclaimer that defines it narrowly. The same disclaimer states that the figures are provided for information only and that SEDA makes no representation about their accuracy. That is not a criticism; it is unusually candid, and it tells you exactly how to use them: as vendor-reported scale indicators, not as audited metrics. Two of them also disagree with themselves, which is documented in the method notes below.

Where it sits in this directory

Layer the directory and the picture is clean. Polygonscan shows you what already happened on chain. DefiLlama measures venues over time. OddsPapi gives you prices across venues. SEDA sits below all of them, in the position of a supplier: it is infrastructure that a prediction market platform would adopt in order to exist, and it is priced and documented as a business-to-business service rather than a tool you open in a browser.

How It Works

Outcomes, end to end

The workflow a builder follows is deliberately narrow. Define the market and its resolution condition — a threshold, a winner, a value at a stated time. Point that condition at a source: a public market feed, a credentialed private feed, a real-world data provider or on-chain state. Let the network fetch and evaluate it, and receive either a resolved outcome on chain or a stream of values your own logic settles. The attractions are that the source and the logic are yours rather than a fixed menu, that resolution is programmatic rather than dependent on a human reporter, and that the result can be delivered to whichever chain the market actually lives on.

The examples the vendor shows span the awkward middle ground of markets that traditional oracles handle poorly: a stock price after the closing bell, a game result, an hourly weather reading, a margin of victory that is still pending. Each displayed example names its source and a millisecond figure, which is the right way to present this — a resolution is only as good as the source beneath it, and the source is the part a reader should interrogate.

Signal feeds and the latency ladder

Signal exists to solve off-hours pricing. Traditional market data stops when venues close; perpetual and 24/7 products need something continuously referenceable, so SEDA aggregates multiple providers and venues into a composite and applies session-aware rules so the feed keeps producing sensible values through closures, with configurable smoothing rather than a flat hold.

The latency tiers are sold as a choice rather than a specification: the fastest tier is aimed at high-frequency use and mentions optional co-location; the sub-second tier at perpetual venues, liquidation engines and mark price calculations; a mid tier at ordinary DeFi, lending and options pricing; and the slowest tier at index products, dashboards, analytics and settlement. That ladder is the clearest signal of what the product is actually for — nothing here is aimed at retail dashboards, which is consistent with a sales-led commercial model.

Bundles, and why they matter for prediction markets

A bundle lets one feed track a defined combination of underlying assets with configurable weights and automatic rebalancing. For prediction market work the interesting applications are not indices but spreads and conditions: relative performance, a basket versus a benchmark, or a composite that smooths the noise out of a single venue's print so that a market resolving on "the price" is not at the mercy of one exchange's wick.

Private and pre-IPO data

Two product lines exist to reach data that ordinary oracles cannot see. Data Proxies let a builder consume a credentialed API — a paid data provider, a broker feed — without the credential ever being public, which is what makes private-market and bilateral data usable in a contract. Pre-IPO coverage extends that to tick-by-tick data on thousands of private companies, which is a long-tail market that few venues can presently serve and an obvious input for markets on private valuations.

Building and deploying

Oracle Programs are the unit of work: code that fetches from endpoints, applies sorting, filtering and aggregation, and emits a structured result. Two functions do most of the practical work — the fetch that reaches the outside world, and the tally that orders and shapes what came back — and the parameters a builder sets are exactly the three questions that matter: what data, from which sources, and in what shape. Providers can be included or excluded explicitly, which is how a feed expresses its own reliability policy rather than inheriting one.

Programs are compiled to WebAssembly and deployed to the network, where they receive an identifier used when requests are posted. The software development kits are open source, which means the format is inspectable without a commercial relationship, and the documentation includes worked examples — a plain crypto price feed and a session-aware equity feed — plus notes on fetch timeouts, which is the failure mode worth designing for in any oracle that depends on somebody else's endpoint.

Two delivery paths

SEDA Fast is the API-first route: REST and WebSocket interfaces for programs executed through the network, which suits off-chain services, dashboards and any product that needs a continuous feed rather than a transaction. SEDA Core is the on-chain route: a request lifecycle on chain, results readable by contracts through prover contracts deployed per EVM network, with a Hardhat integration for posting requests and reading results. Both are documented with runnable examples, and the choice between them is essentially about who needs to trust the number — a contract or a server.

Agents as a first-class audience

Unusually for an oracle, the documentation maintains a section written for autonomous agents: a master runbook that walks through choosing a data source, deciding between the two delivery paths, deploying a program and verifying the result, alongside modules for the individual steps and a machine-readable index of the whole set. There is also material on machine-to-machine payment for oracle access, which is a coherent direction for infrastructure whose users may not be people.

Access, and what it costs to find out

There is no published price list. The route in is a trial request or a conversation with the team, and the documentation deals with commercial terms in a section on bespoke pricing methodologies — which is normal for infrastructure sold to venues and products, and simply means a buyer should expect the terms to depend on which data sources they need and how fast they need them. Everything technical is open: the documentation, the SDKs and the testnet path, so the platform can be built against before any commercial discussion happens.

Method Notes & Limitations

Where this page's facts come from

Everything here was read on 2026-10-01 from SEDA's own material: the homepage, the Signal, Outcomes, Bundles and Pre-IPO product pages, the content disclaimer that defines the footnoted statistics, the trial page, and the project documentation including its introduction, its documentation index, its oracle program pages and its token utility pages. One external source is used for a single comparison — Polymarket's own documentation of its resolution process and adapter contracts — and one SEDA social announcement covers an integration mentioned below. No account was created, no trial was requested, no token was acquired and no integration was built. The performance figures quoted are the vendor's published claims read from its pages on the review date.

Verified against primary sources

ClaimStatus
SEDA is a programmable oracle layer one where developers deploy oracle programs and data proxiesVerified — stated in the project's own documentation
Oracle programs fetch any public or private source, apply custom logic and return structured output on chain or via APIVerified — documented mechanism, including the fetch and tally functions and provider inclusion rules
Two delivery paths exist: an API-first path and an on-chain path with per-network prover contractsVerified — both documented with examples and an integration guide
Product lines: composite feeds, bundles, outcome resolution and pre-IPO dataVerified — each has its own page on the vendor's site
Polymarket and Kalshi are named among the data providers behind its feedsVerified — both appear in the provider list published on the vendor's feed pages
Prediction market resolution is offered to builders, with sub-second latency claimedVendor's published claim, expressly qualified by its own disclaimer — see below
Network usage burns tokens, staking secures the network, and holders delegate and voteVerified — documented token utility, with burns tracked on the project's explorer
Polymarket's own markets resolve through the UMA optimistic oracle, not through SEDAVerified — stated in Polymarket's documentation, which also lists the adapter contracts on Polygon
Headline statistics: volume supported, feeds in production, uptime, tokens burnedVendor-reported only — SEDA's own disclaimer states it makes no representation about their accuracy

What the vendor's own footnotes say about its numbers

This is the most useful thing on SEDA's site for a careful reader, and it is unusually honest. The content disclaimer, versioned and dated, defines each headline figure and then disclaims it. Volume supported means cumulative notional volume associated with integrations using SEDA infrastructure for the current year — not revenue, and not a settled figure. Production data feeds counts feeds configured or deployed since launch and may include inactive or test instances. Uptime refers only to historically observed availability of infrastructure components, varies by product, and is always subject to separate service-level agreements. Tokens burned reflects programmatic removals from supply based on on-chain data and is subject to change. And the latency and update-frequency figures relate solely to endpoint query behaviour, with actual latency depending on the underlying sources, network conditions and deployment — with the use cases on the pages described as illustrative examples. Each definition ends with the same sentence: SEDA makes no representation concerning the accuracy or actuality of the figure.

Two figures that do not agree with themselves

The volume figure that headlines the feed product appears as roughly $19.5bn in the page's own statistics block and as roughly $18.1bn in an explanatory section further down the same page. Separately, the homepage describes the resolution product's median latency as under 200 milliseconds while the resolution page quotes 150 milliseconds and its status block displays the same 150-millisecond figure. Neither discrepancy is dramatic, and both are consistent with numbers that are updated in one place and not another, but they illustrate the point: these are live marketing figures, and a reader should prefer the product page's measurement to the homepage's rounding, and date anything they quote.

What this page does not claim

It does not endorse SEDA or recommend its token, and nothing here should be read as investment commentary — the vendor's own disclaimer is emphatic that the token is a utility token, that SEDA does not settle financial transactions and that it is not a financial intermediary. It does not verify the accuracy, cost or reliability of any feed, and it does not test the latency claims; those are vendor figures, qualified by the vendor. It does not claim SEDA resolves Polymarket's markets, and it does not claim that the integration previously described in this directory record — publishing "Polymarket's entire market data layer on chain" — is how SEDA describes its own work; that phrasing came from third-party directory listings and has been replaced here with what SEDA itself says. And it does not imply any commercial relationship between SEDA and the venues named in its provider lists beyond the provider listing itself.

Editorial note

Bitnxt is not affiliated with SEDA, holds no position in its token, has no commercial relationship with it and receives nothing from it; the visit link carries a tracking parameter only so referrals can be counted. SEDA is infrastructure rather than a venue, so it has no stake in which prediction market wins — but its customers do, which is why the resolution logic and the source beneath each feed are the parts worth scrutinising. The integration mentioned above pairs SEDA with a prediction market data aggregator so that one endpoint can serve data across venues; it is cited from SEDA's own announcement and not independently tested. Nothing here is advice of any kind.

Venues Covered

Prediction markets appear on both sides of the stack rather than as a single venue. Polymarket, Kalshi and the prediction market data firm PM Insights are named among the data providers behind SEDA's feeds, and the resolution layer is designed for outcome markets of any kind — sports, elections, weather, corporate actions, equities and on-chain state — for builders creating their own markets. It does not resolve Polymarket's markets, which settle through Polymarket's own oracle on Polygon.

Access & Pricing

Commercial access is sales-led. The site offers a trial request and a contact form rather than self-serve plans, no price list is published, and the documentation carries a section on bespoke pricing methodologies instead of tiers — which in practice means terms are negotiated per integration and depend on the data sources and latency you need. The documentation, software development kits and a testnet wallet setup are open to anyone, so the network can be evaluated without a commercial conversation, and fees for work that actually runs use the network's own token. In other words: free to read, free to test on the test network, priced by negotiation once you deploy something real.

Frequently Asked Questions

Sources & Verification

The factual claims on this page were checked against the sources below.

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.