SEDA’s Modular Data Network facilitates the deployment of programmable feeds for all data on any network.
Without data, blockchain builders’ innovation is stifled. Blockchains cannot access data outside their native execution environments — no data from real-world feeds other blockchains or protocols. As the industry looks towards an interoperable chain abstracted future focused on app-specificity, the importance of custom data feeds has never been so crucial. Modules revolutionize developers’ flexibility by enabling the permissionless deployment of custom programmable feeds for any data type across all networks.
What Are Data Modules?
Data modules are like SEDA’s protocol recipes, instructions, or blueprints for executing data requests according to preset protocol parameters. Modules are similar to custom itineraries designed by a travel agency. The travel agency has access to all the necessary resources: flights, hotels, tours, and restaurants. You provide your preferences, including destinations, activities, and travel dates. The agency then creates a custom itinerary that meets your needs and desires.
In the same way, data modules on SEDA provide a high degree of flexibility. They act as blueprints for executing data requests, allowing the system to fetch, filter, and present data according to a protocol’s unique requirements.
Builders in Web3 require day-one access to data, and even more so, they require day-one access to configurable data. By deploying a data module on SEDA, protocols can define the data type they need, the sources they do or do not want to query, and how data should be filtered, cleaned, and aggregated. Similarly to how Raas projects allow projects to configure their rollup via an SDK, SEDA could be viewed as ‘Data feeds as a service (DaaS).’ Customize the feed to your needs and deploy it to the network. Once a data module is live on the SEDA network, it can be accessed and leveraged by other protocols requiring similar data requests, facilitating an open developer environment that aligns with the network’s mission.
Why Are Data Modules So Important?
New on-chain use cases have flooded the industry this year, with projects across real-world assets, AI, IP gaming, and complex DeFi. As the industry continues to benefit from modular expansion, driving a new era of developer optionality, more niche products have begun development. In what CTO and Co-Founder Jasper De Gooijer has coined ‘The Era of Hyper-Specialization,’ Web3 will deliver on highly specific projects with rigid data needs.
Data modules are fundamental in the permissionless deployment of programmable feeds. They allow SEDA to query, filter, and return data exactly as a protocol requires. Different projects have different requirements, and finding traditional oracle designs that can service all their data needs is nearly impossible. This is because typical oracle designs focus on specific data, such as price feeds or bridging pathways designed for typical defi use cases. SEDA offers a more flexible approach for builders who require customized, hyper-specific, or industry-wide interoperability feed options.
Exploring Data Module Use Cases | Interoperability
Initial integration partners are set to begin building the first interoperability modules on the network. Interoperability modules will serve interop projects in querying any data type from other blockchains, including RPC data, account states, indexers, or even Zklite clients. Where traditional bridges require deploying smart contracts on each new network that interacts with an oracle and relayer, SEDA allows them to communicate with all networks instantly.
The industry has begun collaborating to build frameworks for chain abstraction with initiatives such as CAKE or MagicSpend++. SEDA’s interoperability modules will allow key chain abstraction projects to communicate between all networks. The modules will likely consist of the blockchains and their data sources, such as specific RPCs that interoperability projects wish to query. Other configurations could include specific data aggregation or filtration, such as the time of transaction settlements or which data points not to include in an aggregated result.
State verification is the crucial fundamental element for chain abstraction and interoperability. As Web3 becomes an intent-centric framework where solvers and paymasters execute user transactions, industry-wide state verification and proof are paramount. SEDA natively serves 250+ (and any future) blockchains with one contract deployment. As data modules are permissionless to deploy, any developer can create a chain abstraction module to communicate, verify, and issue execution proofs of transaction states on any chain. This is vital for value unlocks common in noval account abstracted frameworks.
Where a lack of composability and customization has traditionally restricted the industry, SEDA is built to offer a new era of specialization, flexibility, and configuration for any data type on all networks.
