From b24eb78e048fad09233527cf62c6adf3628ded0d Mon Sep 17 00:00:00 2001
From: Semisol <45574030+Semisol@users.noreply.github.com>
Date: Thu, 16 Mar 2023 20:18:59 +0300
Subject: [PATCH] Revert 'add NOTICE optional subscription_id'

Reverts 88009bea8509d004672551be7346a03c373491d0
---
 01.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/01.md b/01.md
index eead9664..9f60a1d5 100644
--- a/01.md
+++ b/01.md
@@ -89,7 +89,7 @@ The `limit` property of a filter is only valid for the initial query and can be
 Relays can send 2 types of messages, which must also be JSON arrays, according to the following patterns:
 
   * `["EVENT", <subscription_id>, <event JSON as defined above>]`, used to send events requested by clients.
-  * `["NOTICE", <message>, <subscription_id>]`, used to send human-readable error messages or other things to clients. Relays might optionally send a `subscription_id` this notice was caused by.
+  * `["NOTICE", <message>]`, used to send human-readable error messages or other things to clients. 
 
 This NIP defines no rules for how `NOTICE` messages should be sent or treated.