matrix-org / matrix-org/matrix-spec
Should `unsigned` be a required field of events?
Open
clarification
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
The spec has always considered it (and the fields which are always present) optional, but it's unclear if in practice it's treated as optional or as required.
This issue serves to untangle it: do pre-1.0 implementations treat `unsigned` as required/always present?
Contributor guide
Research direction
Start by reviewing the Matrix event specification and historical pre-1.0 implementations to determine whether unsigned is required or optional in practice. Document the evidence and update the relevant specification text once the behavior is established; the issue names no specific file or test.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100