Skip to content
SHC Docs

Re-measurement transcript, 2026-08-10 ~20:12 UTC (lane V-A, second session)

The first session built the lab and captured the unknown1-* / unknown3-* logs, then was killed. This session re-measured every claim against the still-running lab before writing the appendix. All tokens compared by sha256 prefix only; none printed.

  • containers: valab-synapse (matrixdotorg/synapse:v1.158.0, SQLite), valab-hookshot (ghcr.io/matrix-org/matrix-hookshot:7.4.4), valab-stub (phase-A instrument, stub.py), docker network valab
  • room: !QyJFZldCjkbUTJxoBN:valab.local (name: “alerts”)
  • static hook stateKey: 513d8011-6d0d-44f6-b65f-7b6845caa5c4
  • registration: sender_localpart: _shc_appservice, users namespace @_shc_[a-z0-9._=+/-]*: (exclusive: false), as_token sha256:4a8db67b937a, hs_token sha256:5cd134947ba6

Token cross-tie (which token does Synapse present?)

Section titled “Token cross-tie (which token does Synapse present?)”
.as_token sha256:4a8db67b937a
.hs_token sha256:5cd134947ba6
appservice-shc.yaml as_token sha256:4a8db67b937a
appservice-shc.yaml hs_token sha256:5cd134947ba6
stub observed Authorization: Bearer(sha256:5cd134947ba6)

Synapse authenticates its transaction pushes with the hs_token. The same registration (same token pair) served both the stub phase and the hookshot phase; only url: changed between the two loads (Synapse log shows both Loaded application service lines, 19:27:35 url=valab-stub, 19:29:29 url=valab-hookshot).

Room state enumeration (unknown 3: no connection state event exists)

Section titled “Room state enumeration (unknown 3: no connection state event exists)”

GET /_matrix/client/v3/rooms/<room>/state as @admin, event types counted:

1 m.room.create ''
1 m.room.guest_access ''
1 m.room.history_visibility ''
1 m.room.join_rules ''
1 m.room.member '@_shc_appservice:valab.local'
1 m.room.member '@admin:valab.local'
1 m.room.name ''
1 m.room.power_levels ''

Zero uk.half-shot.* state events. The connection exists only in config.yml’s connections: block.

Room timeline (messages actually landed, Synapse-side view)

Section titled “Room timeline (messages actually landed, Synapse-side view)”

GET /_matrix/client/v3/rooms/<room>/messages?dir=b as @admin:

m.room.message @_shc_appservice:valab.local "unknown-3 post-restart persistence check" (m.notice)
m.room.message @_shc_appservice:valab.local "unknown-3 static connection measurement" (m.notice)
m.room.member @_shc_appservice:valab.local join
m.room.message @admin:valab.local "unknown-1 measurement message" (m.text)
m.room.member @_shc_appservice:valab.local join
m.room.member @admin:valab.local invite
POST http://127.0.0.1:59000/webhook/513d8011-6d0d-44f6-b65f-7b6845caa5c4
{"text":"lane V-A re-measure 2026-08-10T20:1x"}
-> HTTP 202 {"ok":true}
POST http://127.0.0.1:59000/webhook/deadbeef-dead-beef-dead-beefdeadbeef
{"text":"bogus"}
-> HTTP 404 {"ok":false,"error":"Webhook not found"}

Timeline re-read confirms the 202 message arrived in the room as @_shc_appservice before the bogus-hook check returned:

@_shc_appservice:valab.local lane V-A re-measure 2026-08-10T20:1x
@_shc_appservice:valab.local unknown-3 post-restart persistence check

Note the success code is 202 Accepted, not 200; waitForComplete: false returns before the Matrix send completes. The §10 row’s “expect 200 not 404” resolves to the success arm.