Skip to content

feat: advertise TSP alongside DIDComm across all four components - #24

Closed
vthwang wants to merge 1 commit into
mainfrom
feat/tsp-transport
Closed

feat: advertise TSP alongside DIDComm across all four components#24
vthwang wants to merge 1 commit into
mainfrom
feat/tsp-transport

Conversation

@vthwang

@vthwang vthwang commented Aug 12, 2026

Copy link
Copy Markdown
Member

No description provided.

The images are built with TSP; the recipes were not. Turn it on in the four
places that have to agree, and fix one that was already wrong.

`services.tsp = true` in both VTA recipes publishes a `#tsp` `TSPTransport`
entry from DID log v1, pointing at the same mediator as the DIDComm entry.
`[messaging]` deliberately gains no `protocols` key — omitted, setup derives
the minted mediator's transports from `[services]`, which is the only value
that keeps the two in step.

The VTC's `messaging.transports` is a repair, not an addition: it is required,
so `vtc setup --from` had no chance of parsing this recipe on any vtc image
from #929 onward, TSP or no TSP. `identity.transport` in the webvh recipe was
likewise not neutral by absence — the daemon reads absent as `both`, so a
TSP-carrying build has been advertising `TSPTransport` against a mediator whose
recipe said `["didcomm"]`. The mediator's own `protocols` has no runtime effect
on a prebuilt image; it records which image the session expects.

Two things to know before this ships:

- The VTA image must be built `--features tsp`. Setup refuses the flag
  otherwise, so an image predating TSP no longer builds a session.
- `vta_only` points at the platform stack's mediator via `kind = "existing"`,
  and nothing upstream verifies that mediator carries TSP. Rebuild the platform
  stack on a TSP-enabled mediator image first: `#tsp` is first in the
  preference order, so peers pick it and fail rather than fall back to DIDComm.

Signed-off-by: vthwang <vthwang.work@gmail.com>
@vthwang vthwang closed this Aug 12, 2026
@vthwang
vthwang deleted the feat/tsp-transport branch August 12, 2026 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant