feat(join): build the subject-linkage proof to join under a fresh DID (#1b)#131
Merged
Conversation
… (#1b) Completes the dual-control / fresh-DID join path. When the presenting persona differs from the loaded invitation's subject, OpenVTC now builds a subject- linkage proof — the invited persona authorizes the presenter — so the VTC admits the fresh DID while honoring an invite bound to another. - openvtc-core: `sign_subject_linkage` signs `TAG‖vic_id‖presenter` via the TDK Ed25519 routine (affinidi_crypto::jose::signing), not a hand-rolled signer. - Config::build_subject_linkage resolves the subject persona's signing key (BIP32 / imported / VTA-managed) + its assertionMethod VM and produces the proof. - Join flow: a loaded invitation bound to one of our personas now opens the identity choice with that persona pre-selected — Enter joins as the invited identity (#1a, no linkage); choosing a different identity builds the linkage proof (#1b). Best-effort: if the subject's key isn't held, no proof is sent and the VTC refuses the mismatched binding. Tests: sign_subject_linkage round-trips against the TDK verify routine; join helper suite green; binary builds against tdk 0.8 / 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
Completes the dual-control / fresh-DID join path (#1b). When the presenting persona differs from the loaded invitation's subject, OpenVTC builds a subject-linkage proof — the invited persona authorizes the presenter — so the VTC admits the fresh DID while honoring an invite bound to another DID. The VTC verify side merged in verifiable-trust-infrastructure #526.
What's included
sign_subject_linkage— signsTAG‖vic_id‖presentervia the TDK Ed25519 routine (affinidi_tdk::affinidi_crypto::jose::signing::sign), not a hand-rolled signer. Unit-tested (round-trips against the TDK verify routine; wrong presenter fails).Config::build_subject_linkage— resolves the subject persona's signing key (BIP32-derived / imported / VTA-managed) + its assertionMethod verification method and produces the proof.Notes
This is the last open item from the VIC follow-ups. It's a privacy-niche path (the default presents the invited persona); the linkage trades the per-community unlinkability of a fresh DID for honoring an invite to your main identity.
Tests
openvtc-corejoin suite green; binary builds against tdk 0.8 / vta-sdk 0.17; fmt clean.🤖 Generated with Claude Code