Two parts. A quiz you can be wrong on with no consequences, and a practical task that puts you in front of the real network.
Recall
Which role is the only one that operates infrastructure and can be slashed for provable misbehaviour?
Indexers run the machines and put their own stake at risk. Curators and delegators put capital at risk in other ways, but neither operates a service and neither is slashed for the Subgraph Service today.
Signal from curators exists mainly to:
Signal is a forward-looking bet on demand. Its job is to route indexing capacity towards data that will be wanted, which is exactly the information nobody has yet at the moment a new subgraph is published.
Which statement about issuance is correct?
That property is the point. It pays for an index to exist ahead of demand, which is the deadlock query fees alone cannot break. Delegators are paid out of what their indexer earns, not directly by the protocol.
You find a 2022 tutorial telling you to deploy your subgraph to the Hosted Service. You should:
The Hosted Service is gone. A page recommending it does not know about Arbitrum One or Horizon either, which means everything economic in it is also wrong. Date the material before trusting it.
The protocol contracts and stakeable GRT live on:
Arbitrum One. Frequent small operations, allocations, proofs, signal changes and voucher redemptions, are only sensible at L2 costs. Sending GRT to a protocol address on the wrong network is the most common expensive newcomer mistake.
0 of 5 answered
Practical task
Nothing here costs money or requires a wallet connection. The aim is to see that the things you have been reading about are real, named, and countable.
Ticks are stored in this browser only. No account, no server, nothing sent anywhere.
Pick your path
You have the shape of it. Where you go next depends on what you actually want to do:
- You have GRT and want it working: Delegators.
- You want to back specific data rather than specific operators: Curators.
- You want to run the infrastructure: Indexers.
- You want to publish data for others to query: Developers.
- You want to consume data in an application: App builders.
- You want to understand how the rules get changed: Governance.