Skip to content

fix(spec): correct header version to 1.2.1 #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrishooooo-netizen merged 1 commit into from
May 28, 2026
Merged

fix(spec): correct header version to 1.2.1 #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions spec/did-method-trail-v1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# did:trail Method Specification

**Version:** 1.2.0-draft
**Version:** 1.2.1
**Status:** Draft
**Authors:** Christian Hommrich (TRAIL Protocol Initiative)
**Contact:** christian.hommrich@trailprotocol.org
**Repository:** https://github.com/trailprotocol/trail-did-method
**Date:** 2026-03-04
**Date:** 2026-04-22
**License:** CC BY 4.0

---
Expand Down Expand Up @@ -2238,6 +2238,14 @@ The `OutputAttestationVC` is protocol-agnostic. It can be issued regardless of h

## 16. Changelog

### v1.2.1 (2026-04-22)

Editorial patch release. No behavioral change for implementations.

| # | Change | Sections Affected |
|---|--------|-------------------|
| 1 | **Aligned trail-hash reference in §6.3 with the normative definition in §4.5.2** — §6.3 (Hash and Key Rotation Semantics) still referenced `[0:12]`, a leftover from v1.1.0-draft before the 48-bit to 64-bit change. The normative definition in §4.5.2 already used `[0:16]` (16 hex characters, 64 bits) correctly. This patch removes the stale reference. | §6.3 |

### v1.2.0 (2026-04-21)

This release adds normative support for platform-hosted AI agent deployments (Managed Agents). It addresses the structural gap identified in v1.1.0-draft: the assumption that an agent has a persistent identity and can directly interact with the TRAIL Registry does not hold for agents dynamically provisioned per session by third-party platforms.
Expand Down
Loading