Aim:

• Interact with state channel as less as possible. Here - StateChannel are used only as a settlement layer where the accumulated queries are presented and settled
• Scaling solution for query fee
• Fast because parallelism as queries can run in parallel and generate receipt

Components

• Query(scaler) - request by client. response - receipt with query fee

• Receipt(Scaler) - generated by gateway or client - Fault-tolerant if gateway crashes then-new receipt created and the indexer will accept this - this rolled up into state channels(vector)

        - off-chain query fee between client/gateway and indexer(indirect) 
  

• Vector transfer(Vector- here connext is used) - queries are aggregated between client and indexer. State channel created and resolved in this.

           **Working** - App(called a transfer) created for state transition - (in this case created and resolved once) - created by gateway/client and resolved by indexer{transfer of funds(in connext way) to a rebate pool of the subgraph}
  

User Flow

In the view of an indexer only one change- He will also have to deploy a vector node

Cost Models

Price sheet that lists all the queries an indexer is willing to serve and for what fee

Gateway pays a higher upfront cost to show the cost model - pay higher upfron cost to request the cost model

Query shows up from the end-user - Pay a much lower performance cost to look up the fee. Given the cost model at hand. And periodically update the cost model with time

To express the cost model by indexer - Language developed