Update TAIP statuses and add navigation links

pelle · claude · pelle · commit 63a69cafba15 · 2025-06-25T09:22:42.000+02:00
- Advanced TAIP-1 to Final status - Advanced TAIPs 2-10 to Last Call status - Advanced TAIPs 15-16 from Draft to Review status - Added Developer Resources and Changelog to navigation - Updated changelog with status changes for 2025-06-25 - Bumped TypeScript package version 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -14,6 +14,25 @@ This changelog focuses on:
 - Protocol structural changes
 - Breaking changes
 
+## [2025-06-25]
+
+### Changed
+- **TAIP Status Updates**:
+  - TAIP-1: Transaction Authorization Improvement Proposals - Advanced to **Final** status
+  - TAIPs 2-10 - Advanced to **Last Call** status:
+    - TAIP-2: Messaging
+    - TAIP-3: Virtual Asset Transfer
+    - TAIP-4: Transaction Authorization Protocol
+    - TAIP-5: Transaction Agents
+    - TAIP-6: Transaction Parties
+    - TAIP-7: Agent Policies
+    - TAIP-8: Selective Disclosure
+    - TAIP-9: Proof of Relationship
+    - TAIP-10: IVMS101 for Travel Rule
+  - TAIPs 15-16 - Advanced from **Draft** to **Review** status:
+    - TAIP-15: Agent Connection Protocol
+    - TAIP-16: Invoices
+
 ## [2025-06-24]
 
 ### Added
diff --git a/TAIPs/taip-1.md b/TAIPs/taip-1.md
@@ -1,7 +1,7 @@
 ---
 taip: 1
 title: TAP and TAIP Purpose and Guidelines
-status: Review
+status: Final
 type: Meta
 author: Pelle Braendgaard <pelle@notabene.id>
 created: 2024-01-09
@@ -22,7 +22,7 @@ The TAIP should provide a concise technical specification of the feature and a r
 
 ## TAIP Rationale
 
-Blockchain development is still under very rapid pace. Adding authorization support to new technologies requires a decentralized approach to authoring this. 
+Blockchain development is still under very rapid pace. Adding authorization support to new technologies requires a decentralized approach to authoring this.
 
 TAIPs allows authors to focus on specific aspects of authorization and interactions with new protocols, technologies, and workflows.
 
@@ -163,7 +163,7 @@ The editors don't pass judgment on TAIPs. We merely do the administrative & edit
 
 ## History
 
-This document was derived heavily from [CAIP-1] written by Ligi, which was derived by [Bitcoin's BIP-0001] written by Amir Taaki, which in turn was derived from [Python's PEP-0001]. In many places text was simply copied and modified. Although the PEP-0001 text was written by Barry Warsaw, Jeremy Hylton, and David Goodger, they are not responsible for its use in Transaction Authorization Improvement Proposals, and should not be bothered with technical questions specific to TAIPs. Please direct all comments to the TAIP editors. 
+This document was derived heavily from [CAIP-1] written by Ligi, which was derived by [Bitcoin's BIP-0001] written by Amir Taaki, which in turn was derived from [Python's PEP-0001]. In many places text was simply copied and modified. Although the PEP-0001 text was written by Barry Warsaw, Jeremy Hylton, and David Goodger, they are not responsible for its use in Transaction Authorization Improvement Proposals, and should not be bothered with technical questions specific to TAIPs. Please direct all comments to the TAIP editors.
 
 ### References
 
@@ -177,4 +177,4 @@ This document was derived heavily from [CAIP-1] written by Ligi, which was deriv
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](../LICENSE).
+Copyright and related rights waived via [CC0](../LICENSE).
diff --git a/TAIPs/taip-10.md b/TAIPs/taip-10.md
@@ -1,7 +1,7 @@
 ---
 taip: 10
 title: IVMS101 for Travel Rule Identity Verification in TAP
-status: Review
+status: Last Call
 type: Standard
 author: Pelle Braendgaard <pelle@notabene.id>
 created: 2024-01-24
diff --git a/TAIPs/taip-15.md b/TAIPs/taip-15.md
@@ -1,7 +1,7 @@
 ---
 taip: 15
 title: Agent Connection Protocol
-status: Draft
+status: Review
 type: Standard
 author: Pelle Braendgaard <pelle@notabene.id>
 created: 2024-03-21
diff --git a/TAIPs/taip-16.md b/TAIPs/taip-16.md
@@ -1,7 +1,7 @@
 ---
 taip: 16
 title: Invoices
-status: Draft
+status: Review
 type: Standard
 author: Pelle Braendgaard <pelle@notabene.id>
 created: 2025-04-22
diff --git a/TAIPs/taip-2.md b/TAIPs/taip-2.md
@@ -1,7 +1,7 @@
 ---
 taip: 2
 title: Messaging
-status: Review
+status: Last Call
 type: Standard
 author: Pelle Braendgaard <pelle@notabene.id>, Richard Crosby <richard@notabene.id>
 created: 2024-01-09
diff --git a/TAIPs/taip-3.md b/TAIPs/taip-3.md
@@ -1,7 +1,7 @@
 ---
 taip: 3
 title: Asset Transfer
-status: Review
+status: Last Call
 type: Standard
 author: Pelle Braendgaard <pelle@notabene.id>
 created: 2024-01-12
diff --git a/TAIPs/taip-4.md b/TAIPs/taip-4.md
@@ -2,7 +2,7 @@
 taip: 4
 title: Transaction Authorization Protocol
 author: Pelle Braendgaard <pelle@notabene.id>, Andrés Junge <andres@notabene.id>, Richard Crosby <richard@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-12
 updated: 2025-06-23
diff --git a/TAIPs/taip-5.md b/TAIPs/taip-5.md
@@ -2,7 +2,7 @@
 taip: 5
 title: Transaction Agents
 author: Pelle Braendgaard <pelle@notabene.id>, Andrés Junge <andres@notabene.id>, Richard Crosby <richard@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-22
 updated: 2025-06-13
diff --git a/TAIPs/taip-6.md b/TAIPs/taip-6.md
@@ -2,7 +2,7 @@
 taip: 6
 title: Transaction Parties
 author: Pelle Braendgaard <pelle@notabene.id>, Andrés Junge <andres@notabene.id>, Richard Crosby <richard@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-22
 updated: 2025-05-31
@@ -91,7 +91,7 @@ Future TAIPs can define additional types of parties. Examples.
 * `issuer` of a real world asset
 * `trustee`, `grantor`, `beneficiary` for a trust
 * `customer`, `merchant` for a sales contract
- 
+
 ### Agents for Parties
 
 Any Agent can add a `for` attibute to their Agent object (see [TAIP-5]). This specifies that the agent is an agent for the [DID] or [IRI] for a particular party.
diff --git a/TAIPs/taip-7.md b/TAIPs/taip-7.md
@@ -2,7 +2,7 @@
 taip: 7
 title: Agent Policies
 author: Pelle Braendgaard <pelle@notabene.id>, Andrés Junge <andres@notabene.id>, Richard Crosby <richard@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-23
 updated: 2025-05-31
diff --git a/TAIPs/taip-8.md b/TAIPs/taip-8.md
@@ -2,7 +2,7 @@
 taip: 8
 title: Selective Disclosure
 author: Pelle Braendgaard <pelle@notabene.id>, Andrés Junge <andres@notabene.id>, Richard Crosby <richard@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-24
 updated: 2025-05-31
@@ -41,8 +41,8 @@ In the context of the [W3C Verifiable Credential Model][VCModel] the following p
 * **Subject** - An entity about which claims are made. In the context of [TAIP-4] this MUST be a [Party][TAIP-6] or [Agent][TAIP-5] to the transaction.
 * **Issuer** - A role of an entity that asserts claims about the **Subject** into [VC]. In the context of [TAIP-4] this could be an [Agent][TAIP-5] to the transaction, but as portable KYC becomes more prevalent it doesn't have to be.
 * **Verifier** - A role of an entity that requests and receives [Verifiable Presentations][VP] containing [Verifiable Credentials][VC] for a particular purpose. In the context of [TAIP-4] this MUST be an [Agent][TAIP-5] to the transaction.
-* **Holder** - A role for an entity that holds a combination of [Verifiable Credentials][VC] and generate [Verifiable Presentations][VP] based on requests from **Verifiers**.  In the context of [TAIP-4] this MUST be an [Agent][TAIP-5] to the transaction. 
- 
+* **Holder** - A role for an entity that holds a combination of [Verifiable Credentials][VC] and generate [Verifiable Presentations][VP] based on requests from **Verifiers**.  In the context of [TAIP-4] this MUST be an [Agent][TAIP-5] to the transaction.
+
 Within TAP the **Holder** and **Issuer** are often the same.
 
 ### `RequirePresentation` policy
@@ -244,7 +244,7 @@ In analyzing Personally Identifiable Information (PII) to comply with the Financ
 * [VC] Verifiable Credentials
 * [VP] Verifiable Presentation
 * [IVMS-101] interVASP Messaging Standard 101 (IVMS 101)
-  
+
 [TAIP-2]: ./taip-2
 [TAIP-3]: ./taip-3
 [TAIP-4]: ./taip-4
diff --git a/TAIPs/taip-9.md b/TAIPs/taip-9.md
@@ -2,7 +2,7 @@
 taip: 9
 title: Proof of Relationship
 author: Pelle Braendgaard <pelle@notabene.id>
-status: Review
+status: Last Call
 type: Standard
 created: 2024-01-25
 updated: 2025-05-31
@@ -252,7 +252,7 @@ The following case the beneficiary vasp confirms that the settlement address act
   ]
 }
 ```
-In addition to this, they 
+In addition to this, they
 
 The following case the beneficiary vasp confirms that they are acting on behalf of the beneficiary customer:
 
@@ -307,7 +307,7 @@ The following case the beneficiary vasp confirms that they are acting on behalf
 * [VCModel] W3C Verifiable Credentials Data Model
 * [VC] Verifiable Credentials
 * [VP] Verifiable Presentation
-  
+
 [TAIP-2]: ./taip-2
 [TAIP-3]: ./taip-3
 [TAIP-4]: ./taip-4
diff --git a/packages/typescript/package.json b/packages/typescript/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@taprsvp/types",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "TypeScript types and interfaces for the Transaction Authorization Protocol (TAP)",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
