SEDA is built to empower developers to build anywhere, access everywhere.
Building onchain has become an obstacle course for developers. Where Web2 enables developers to focus on their product, Web3 requires navigating chain-specific requirements and gaining access to infra fundamentals. To bring more app developers onchain, the web3 landscape needs to be an attractive DevX compared to traditional building environments. SEDA’s north star is to give any builder the freedom of unrestricted onchain development.
Build anywhere → access everywhere.
Navigating Chain-Specific Requirements
When you build a traditional app, you look for the servers and tools optimized for developing the application experience. Building in Web3, however, requires developers to start by selecting what chain they will deploy to. This involves a host of chain-specific considerations, such as:
→ How many active users
→ Which tools can I access
→ What liquidity services exist
→ What fees will I need to pay
These chain-specific requirements represent a massive blocker for developers building consumer-facing app experiences. SEDA’s vision is that builders should focus on what they want to build, including being able to build on chains optimized to their use case. For gaming applications, build on Skale, Avax, or Immutable. DeFi projects should consider optimized networks like Unichain, Sei or Ink.
Instead, builders must continue deploying on outdated networks because they cannot access fundamentals on newer optimized chains. To build great apps on the right networks, developers need open access to users, tools, and liquidity without exorbitant fees or proof of traction models.
Better DevX → Better Apps → Better Onboarding → More Users
Accessing Fundamental Infra: Data
An extension to Chain-Specific requirements is ensuring developers can access fundamental infrastructure no matter which chain they build. Where projects like Particle Network give users access to the network from a single entry point, SEDA gives developers access to any data type from a single entry point. Where users on one wallet for one chain only get one experience, developers with access to one data set can only produce the same experiences over and over.
Restricting onchain development by restricting access to data restricts the app types users can expect onchain — stifling industry growth. SEDA is built to break the app repetition cycle by allowing developers to connect any data type from any network on day one. Achieved by a single prover contract integration monitored by a network of Solvers, devs can ship new feeds in 97 seconds. Requests are then relayed to SEDA for processing, and results are returned to any destination chain.
TLDR: Build on any chain — Access any data — From day one.
SEDA | Build Anywhere, Access Everywhere
By allowing developers to select chains optimized to their use case with day-one access to the tools they need, SEDA removes developer shackles for an unrestricted onchain DevX. The end goal for Web3 is clear: apps. But building apps on inferior infrastructure has its clear message: Apps don’t get built.
SEDA was built from first-hand experience with legacy oracles and their restrictions on the industry growth by restricting data access, requiring month-long delays, and, in many cases, unacceptably high integration fees.
Builders on the SEDA network can ship great apps, enjoying: → Permissionless access to the data they need. → Day-one feed deployment for any data type. → Zero network integration fees, zero delays. → Unrestricted Onchain development
Devs: Build on SEDA → https://Github.com/sedaprotocol
Community: Join The Rebellion → https://discord.com/invite/seda
