project-robius / project-robius/robrix

[TSP] Support the WebVH DID kind

Open
#597 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tsp
Dominant language
Rust
Stars
487
Forks
68
Avg merge
1h 22m
Merged PRs (30d)
54

Description

This is needed to meet the Second stage TSP Milestone.

Currently Robrix only supports the basic "Web" DID type, which does not come with any verifiable history guarantees.

Implementation Notes

  • The CreateDidModal already offers a radio button to select which DID type. Currently, WebVH is disabled, so we'd need to enable that.
  • SDK-level support for WebVH used to be gated behind a webvh feature, but now it is apparently included under the resolve feature, which we already enable, so we should just be able to use it.
  • There is a create_webvh() function here that we could likely use.
  • For republishing a DID, we'll also need to support determining if an existing DID is Web or WebVH, and then republishing the correct version of it, along with whatever other DID "documents" are required when re-publishing a WebVH DID>

References

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the CreateDidModal entry point and inspect how the existing Web DID creation and republishing paths use the TSP SDK. Read the SDK create_webvh() function and the linked CLI example first, then determine how existing DID kinds and required documents are handled. Done means WebVH can be selected, created, identified, and republished correctly alongside Web DIDs.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.