feat: add homepage to service metadata - #559
Merged
Merged
Conversation
rjan90
marked this pull request as ready for review
July 29, 2026 07:22
rjan90
added a commit
that referenced
this pull request
Jul 30, 2026
rjan90
added a commit
that referenced
this pull request
Jul 31, 2026
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
3 participants
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.
Summary
homepage()toIFilecoinServiceMetadatadescription()andhomepage()at 256 UTF-8 bytes in the interface documentationContext
This is a stacked follow-up to #551 and targets its head branch directly.
After chatting with Jennifer about the intended scope of the v1 Filecoin service metadata standard, the initial version should expose:
name()— a short service labeldescription()— a concise description, capped at approximately 256 bytes and treated as untrusted display-only texthomepage()— an optional, size-capped URL for technical documentation, specifications, or the service repository