Blockchain Data made Useable
Skopos is a set of web2 services that analyze and index all data on an EVM blockchain. It stores the data in any format requested by the entity using the service, such as a protocol developer or an institution. It makes querying through select datasets as simple as API calls.
Any project that stores data on-chain - no matter how simple or complex - can benefit. Products such as Gallery and Ēnosys DEX already utilize Skopos.
DEX
On Ēnosys DEX, Skopos provides the data used to display real time trading charts and transaction histories. Skopos also allows for volume and TVL tracking on DEX.
Gallery
Skopos provides data to Gallery which allows for multi-asset orderbooks for NFTs and volume statistics for NFT collections.
Analytics
Skopos functions as the data backbone for transaction and fee tracking in the Ēnosys ecosystem. This allows for an in depth display of the volumes, fees, and yields that are flowing through the product suite.
Flow
In Skopos, the Flow of data is quite specific. A list of events is defined by Skopos’s users. Skopos starts with the BlockNumber service, which listens in for new incoming blocks. The Stage1 service processes that information and stores it into a database with all the relevant data such as blocks, receipts, logs and more.
Simultaneously, Stage1 looks through the list of events that was initially provided by Skopos’ users and indexes them if there's a match. If so, it sends the matched data to the parsing service. The parsing service is subsequently responsible for indexing and storing the data according to the preferences of the user. The user can subsequently query that data through an API.
Skopos for Developers
Currently, Skopos is used by all of Ēnosys’ products and all of Ēnosys’ partners’ products, upon request. Ultimately, it will be a service with free and paid tiers for developers and institutions, to help them build data-rich experiences.
Skopos will be billed per request based on the needs of the entity using it. Depending on how many RPM(requests per minute) an entity would need to perform, and how many active applications it will have, the pricing will vary.
