Repository navigation
feat: index indexer avatar and profile metadata - #16
Closed
MoonBoi9001 wants to merge 3 commits into
Closed
MoonBoi9001 wants to merge 3 commits into
MoonBoi9001 wants to merge 3 commits into
Conversation
An indexer record carried only its service URL, so consumers cross-queried the network subgraph for the avatar and display name. Index each account's metadata document (avatar, display name, description), pointed to on-chain and fetched from IPFS, and link it per indexer. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
An indexer's profile pointer is published on-chain with a validity deadline. Retracting the profile re-publishes the pointer with that deadline set to the current moment, so it is expired. The subgraph now drops the profile link when the deadline has passed instead of re-indexing it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Registering an indexer also links it to an account record stored under the same address, but no test covered that link. This checks the link is set once an indexer registers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
MoonBoi9001
force-pushed
the
mb9/index-indexer-profile-metadata
branch
from
June 5, 2026 13:49
77ed4ac to
2c00e0c
Compare
Member
Author
|
Closing this, if needed we can reopen. For now just going with pr 15 that has the URL. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Reading an indexing agreement now gives you the indexer's address and service URL, but not the indexer's avatar or profile, so anything that displays an indexer still cross-queries the network subgraph for those. This indexes each indexer's avatar and profile details from the same on-chain registry the network already uses and links them to the indexer, so they come back in one query.
Motivation
The indexing payments subgraph records each indexer with its on-chain address and, as of #15, its service URL. Products that display an indexer — such as Studio's indexing-progress view — also show the indexer's avatar and a short profile, and today those come only from the network subgraph, so a consumer that already reads this subgraph must make a second query elsewhere just to show a picture and a description.
Indexers publish that profile on-chain themselves: an entry in the Ethereum DID registry points at a metadata document on IPFS holding the avatar, description, and website. Indexing it here lets a consumer read an indexer's URL and profile together in one query, dropping the extra round-trip for the common case of showing who an indexer is.
Summary