Allow using existing `_atptoto.` records for DNS verification
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ATProto already has a way for users to verify their domains using DNS, by adding a TXT record containing the DID to an _atproto. subdomain.
Keytrace introduces a duplicate method: a TXT record on the root or a _keytrace. subdomain, containing the DID with a special prefix.
In the spirit of compatibility with the ATProto ecosystem, it would be great to support the existing verification method so people don't have to add a duplicate key just for Keytrace.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Keytrace's existing DNS verification flow and how it reads TXT records on the root and _keytrace. subdomain. Compare that behavior with ATProto's _atproto. TXT record containing a DID, then add support for recognizing the existing record without requiring a duplicate key. Done means a domain verified through the ATProto record works with Keytrace and existing verification behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100