➖Developing

Queryloop Ecosystem - Developing

The Queryloop ecosystem's demand side consists of developers. Subquerys are created by developers and published to The Queryloop Network. They then use QL to query live subgraphs to power their apps.

Subquery Lifecycle

Subquerys deployed to the network have a defined lifecycle.

Build locally

It begins with local development and testing, as with any subquery development. When creating a subquery for The Queryloop Network, the hosted service, or a local Queryloop Node, developers may use the same local configuration by combining Queryloop-cli and Queryloop-ts. To increase the robustness of their subqueries, developers are urged to use tools like Matchstick for unit testing.

The Queryloop Network is subject to specific feature and network support limitations. Only subqueries on compatible networks will get indexing rewards; IPFS-fetching subqueries are similarly ineligible.

Deploy to the Subgraph Studio

The subquery may be constructed and deployed to the Subquery Studio once it has been specified. A sandbox environment called the Subquery Studio will index the deployed subquery and make it accessible for rate-limited testing and development. Developers can use this chance to confirm that their subquery performs as intended and has no indexing issues.

Publish to the Network

The developer can upload their finished subquery to The Queryloop Network after they are satisfied with it. The subquery is registered in this on-chain operation so that Indexers may find it. The appropriate NFT for published subqueries is then readily transferrable. The related metadata for the published subquery offers helpful context and details to other network users.

Signal to Encourage Indexing

Without the inclusion of a signal, published subqueries are unlikely to be indexed. A locked QUERYLOOP signal linked with a certain subquery informs indexers that it will get a certain amount of query traffic and also increases the indexing rewards available for processing it. To encourage indexing, subquery developers typically add a signal to their subquery. If they believe a certain subquery will likely generate query volume, third-party curators may additionally signal on the subquery in question.

Querying & Application Development

Developers can begin using a subquery in their applications after it has been processed by the indexers and is ready for querying. Developers use a gateway to submit subqueries for processing, and the Indexer processes the subquery after receiving payment from the developer in QUERYLOOP.

Developers must create an API key in the Subquery Studio before they may run queries. To cover query costs, this API key has to be financed using QUERYLOOP. In order to manage their charges, developers can establish a maximum query fee and restrict the use of their API key to a certain subquery or origin domain. Developers may access information on their API key usage history using the Subquery Studio.

Developers can also tell the gateway which Indexers they prefer, such as those whose query responses are quicker or whose data is most recent. The Subquery Studio is where these controls are configured.

Developers and Network Economics

Developers are a significant economic player in the network, locking up QUERYLOOP to promote indexing and, critically, querying subqueries, which is the main value exchange in the network. When a subquery is modified, subquery developers also burn QUERYLOOP.