Open
Conversation
osmaczko
approved these changes
Feb 8, 2026
|
|
||
| | domain_id | specification repository | | ||
| |-----------|--------------------------------------| | ||
| | 0 | https://github.com/waku-org/specs | No newline at end of file |
There was a problem hiding this comment.
0 domain_id contradicts "MUST be a positive integer"
| Domains should focus on providing types unique to their service or use case. | ||
|
|
||
|
|
||
| # Appendix A: Domains |
There was a problem hiding this comment.
[Sand]
The spec describes ContentFrame as enabling "permissionless innovation" and "decentralized governance," but the registry mechanism (adding domains via pull request with no defined acceptance criteria) introduces a centralized chokepoint. Who approves? On what basis? What's the timeline?
Has any governance model been considered for the registry?
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
2 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.
This PR adds a specification which describes a method for self-describing content types.
It aims to provide interoperability between client versions while enabling developers to create types permissionlessly.