Room Version 3

This room version builds on version 2 with an improved event format.

1   Client considerations

This room version changes the format for event IDs sent to clients. Clients should be aware that these event IDs may contain slashes and other potentially problematic characters. Clients should be treating event IDs as opaque identifiers and should not be attempting to parse them into a usable form, just like with other room versions.

Clients should expect to see event IDs changed from the format of $randomstring:example.org to something like $acR1l0raoZnm60CBwAVgqbZqoO/mYU81xysh1u7XcJk (note the lack of domain and the potentially problematic slash).

2   Server implementation components

Warning

The information contained in this section is strictly for server implementors. Applications which use the Client-Server API are generally unaffected by the intricacies contained here. The section above regarding client considerations is the resource that Client-Server API use cases should reference.

Room version 3 uses the state resolution algorithm defined in room version 2, and the event format defined here.

2.1   Event IDs

Rationale

In other room versions (namely version 1 and 2) the event ID is a distinct field from the remainder of the event, which must be tracked as such. This leads to complications where servers receive multiple events with the same ID in either the same or different rooms where the server cannot easily keep track of which event it should be using. By removing the use of a dedicated event ID, servers are required to track the hashes on an event to determine its ID.

The event ID is the reference hash of the event encoded using Unpadded Base64, prefixed with $. A resulting event ID using this approach should look similar to $CD66HAED5npg6074c6pDtLKalHjVfYb2q4Q3LZgrW6o.

Event IDs should not be sent over federation to servers when the room uses this room version. On the receiving end of an event, the server should compute the relevant event ID for itself.

Additionally, the auth_events and prev_events have had a format change compared to other room versions to make it easier to handle. Instead of a tuple of values, they are now plain lists of events.

2.1.1   Persistent Data Unit schema

A persistent data unit (event) for room version 3 and beyond.

Persistent Data Unit

Parameter Type Description
room_id string Required. Room identifier.
sender string Required. The ID of the user sending the event.
origin string Required. The server_name of the homeserver that created this event.
origin_server_ts integer Required. Timestamp in milliseconds on origin homeserver when this event was created.
type string Required. Event type
state_key string If this key is present, the event is a state event, and it will replace previous events with the same type and state_key in the room state.
content object Required. The content of the event.
prev_events [string] Required. Event IDs for the most recent events in the room that the homeserver was aware of when it made this event.
depth integer Required. The maximum depth of the prev_events, plus one. Must be less than the maximum value for an integer (2^63 - 1). If the room's depth is already at the limit, the depth must be set to the limit.
auth_events [string] Required. Event IDs for the authorization events that would allow this event to be in the room.
redacts string For redaction events, the ID of the event being redacted.
unsigned Example Unsigned Data Additional data added by the origin server but not covered by the signatures. More keys than those defined here may be used.
hashes Event Hash Required. Content hashes of the PDU, following the algorithm specified in Signing Events.
signatures {string: {string: string}} Required. Signatures for the PDU, following the algorithm specified in Signing Events.

Example Unsigned Data

Parameter Type Description
age integer The number of milliseconds that have passed since this message was sent.
replaces_state string The event ID of the state event this event replaces.
prev_sender string The sender of the replaced state event.
prev_content object The content of the replaced state event.
redacted_because string A reason for why the event was redacted.

Event Hash

Parameter Type Description
sha256 string Required. The hash.

Example:

{
    "auth_events": [
        "$base64EncodedHash",
        "$AnotherEvent"
    ],
    "content": {
        "key": "value"
    },
    "depth": 12,
    "hashes": {
        "sha256": "ThisHashCoversAllFieldsInCaseThisIsRedacted"
    },
    "origin": "matrix.org",
    "origin_server_ts": 1234567890,
    "prev_events": [
        "$base64EncodedHash",
        "$AnotherEvent"
    ],
    "redacts": "$def456:matrix.org",
    "room_id": "!abc123:matrix.org",
    "sender": "@someone:matrix.org",
    "signatures": {
        "example.com": {
            "ed25519:key_version:": "86BytesOfSignatureOfTheRedactedEvent"
        }
    },
    "state_key": "my_key",
    "type": "m.room.message",
    "unsigned": {
        "key": "value"
    }
}

2.2   Changes to APIs

Due to the event ID being removed from the event, some APIs need to change. All APIs which currently accept an event ID must do so with the new format. Servers must append the calculated event ID to all events sent to clients where an event ID would normally be expected.

Because the format of events has changed, servers must be aware of the room version where the event resides so that the server may parse and handle the event. The federation API has taken this concern into consideration by ensuring that servers are aware of (or can find) the room version during a request.

2.3   Authorization rules for events

The authorization rules for a given event have changed in this room version due to the change in event format:

  • The event no longer needs to be signed by the domain of the event ID (as there is no domain in the event ID), but still needs to be signed by the sender's domain.
  • In past room versions, redactions were only permitted to enter the DAG if the sender's domain matched the domain in the event ID being redacted, or the sender had appropriate permissions per the power levels. Due to servers now not being able to determine where an event came from during event authorization, redaction events are always accepted (provided the event is allowed by events and events_default in the power levels). However, servers should not apply or send redactions to clients until both the redaction event and original event have been seen, and are valid. Servers should only apply redactions to events where the sender's domains match, or the sender of the redaction has the appropriate permissions per the power levels.

The remaining rules are the same as room version 1.