Conversation
At join time the VTA credential vault is the durable home for the holder's VIC:
- if an invitation is loaded (file / paste), persist it via cred_vault_receive;
- if none is loaded, try loading one the VTA already holds for the holder
(cred_vault_query{purpose: invite} → cred_vault_get) and present it.
Both are best-effort — the join proceeds on the in-memory VIC regardless, so a
VTA without the credential-vault surface (or vault capability) degrades cleanly.
Uses the always-on admin VTA session already threaded into run_join_sequence
and the cred_vault_* methods shipped in vta-sdk 0.17.
Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
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
1 participant
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.
Summary
Wires OpenVTC to the VTA credential vault so the holder's invitation credential (VIC) has a durable home in the VTA rather than living only in memory / a file.
At join time (
run_join_sequence):--invitation <file>or paste), persist it —admin_vta.cred_vault_receive(vic);cred_vault_query({purpose: "invite"})→cred_vault_get(id)→ present it.Both are best-effort: the join proceeds on the in-memory VIC regardless, so a VTA without the credential-vault surface (or without the vault capability on the session) degrades cleanly.
Uses the always-on admin VTA session already threaded into the join flow and the
cred_vault_*methods shipped in vta-sdk 0.17 (verifiable-trust-infrastructure #524).Remaining (this completes #2; #1b build-side still open)
The subject-linkage build side (#1b) — signing
TAG‖vic_id‖presenterwith the subject persona's key to join under a fresh DID — is still open. It's a privacy-niche path (the join-as-subject default, #1a, already auto-presents the invited persona) and needs cross-persona key access + a "present a fresh identity" choice. The VTC verify side + the OpenVTCsign-bytes/SubjectLinkagegroundwork are already merged.Tests
openvtcbuilds clean against tdk 0.8 / vta-sdk 0.17; fmt clean.🤖 Generated with Claude Code