From 228ce1694f3714da1a339863a49e900a35c3fc86 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Tue, 6 Jan 2026 21:22:06 +0000
Subject: [PATCH] docs: Add NIP-04/NIP-44 dual support policy to AGENTS.md

Update AGENTS.md to explicitly require support for both legacy NIP-04 and newer NIP-44 Direct Messages, as many users still rely on the legacy standard.
---
 AGENTS.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 823343e6..031e5aa6 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -180,6 +180,14 @@ When moving a feature to a controller, follow these steps:
 
 ---
 
+## 10. Direct Messages (NIP-04 vs NIP-44)
+
+* **Dual Support:** We must support both legacy NIP-04 and newer NIP-44 Direct Messages.
+* **Reasoning:** A significant portion of the user base still relies on NIP-04 DMs. While NIP-44 offers better security, we cannot drop NIP-04 support until adoption of the new standard is nearly universal.
+* **Implementation:** When working on DM features, ensure code paths exist for both encryption/decryption methods. Do not deprecate or remove NIP-04 handling logic. Other legacy methods can be considered for removal, but NIP-04 is critical.
+
+---
+
 ## Next
 
 Please read these documents next.