From 7cb0e77d3e87c326c8da42ace99c8f3d1dc01a57 Mon Sep 17 00:00:00 2001
From: BlowaterNostr <127284497+BlowaterNostr@users.noreply.github.com>
Date: Sat, 15 Jul 2023 19:05:05 +0800
Subject: [PATCH] Update 1078.md

---
 1078.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/1078.md b/1078.md
index 76de312f..b9edcdb6 100644
--- a/1078.md
+++ b/1078.md
@@ -7,6 +7,19 @@
 
 This NIP specifies the use of event kind `1078` which is almost identical to [30078](https://github.com/nostr-protocol/nips/blob/master/78.md) except that it's not a replacible event.
 
+### Format
+#### Private Configs
+Private config should be encrypted using Kind-4's algorithm and stored in `content`. Technically the plain text content can be in any format, but it's best to use a JSON format of the following shape
+```
+content: {
+  "client": "the client name, url for web client or NIP-89 identifier"
+  ... the rest can be whatever the client author decides to be.
+}
+```
+
+#### Public Configs
+Similar to [NIP-78](https://github.com/BlowaterNostr/nips/blob/master/78.md#nostr-event), configs should be stored in `tags` and can be anything.
+
 ## Some use cases
 The reason to not having a 30078 is that some clients want to implement local state changes as [CRDTs](https://crdt.tech/), meaning support cumulative and associative mutations