Skip to content

feat: resolve did:webs (VTI-KEY-003) - #40

Merged
stormer78 merged 1 commit into
mainfrom
feat/resolve-did-webs
Nov 12, 2026
Merged

stormer78 merged 1 commit into
mainfrom
feat/resolve-did-webs

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

The VTI spec is making did:webs a method every VTI party resolves (trustoverip/dtgwg-vti-spec#123, VTI-KEY-003), so a VTA or device can use did:webvh, did:scid or did:webs as its DID and still reach the gateway.

  • affinidi-did-resolver-cache-sdk 0.8.43 [network] → 0.8.52 [network, did-webs]. There is one copy in the lockfile, so the proof verifier, the TSP self-check and the DIDComm listener all get the feature.
  • No LMDB or other system library (cargo tree -i heed is empty). The dev-dependency affinidi-did-webs with create is for tests only.
  • tests/did_webs.rs (offline): resolves a did:webs that a local server hosts, and the default public-only policy refuses a private-host did:webs without connecting.
  • README updated.

fmt, clippy -D warnings, cargo test --all-targets and cargo deny check all pass locally.

Note: rust-version = "1.85" is already stale. The cache-sdk has needed 1.95 since 0.8.43. That's unchanged here.

Every VTI node must resolve did:webs (VTI-KEY-003), so that each party can
choose its own DID method and still interoperate. The gateway's resolver had
no did:webs, so a VTA or device whose DID is a did:webs could not be resolved.

Take affinidi-did-resolver-cache-sdk 0.8.52 with `did-webs`. The graph holds
one copy of the crate, so the feature reaches every resolver the gateway
builds: the proof verifier's, the TSP self-check's and the DIDComm listener's
TDKConfig. did:webs resolution runs under the same host policy as
did:web/did:webvh/did:scid (public hosts only unless
GATEWAY_DID_ALLOW_PRIVATE_HOSTS). The resolver side of affinidi-did-webs 0.13
needs no affinidi-keri, so no LMDB or other native library enters the build.

tests/did_webs.rs creates a did:webs for a local fixture server (dev-dependency
affinidi-did-webs with `create`, on affinidi-keri without default features),
serves its keri.cesr and did.json, and resolves it through ResolverTuning; a
second test checks the default policy refuses a private-host did:webs without
connecting.

Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
@stormer78
stormer78 merged commit 525ee6e into main Nov 12, 2026
3 checks passed
@stormer78
stormer78 deleted the feat/resolve-did-webs branch November 12, 2026 04:10
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