From 0e2b38660a66b4b1e6ce45621e9f0a1062ed5fa9 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Tue, 30 Jan 2024 14:06:57 -0500
Subject: [PATCH] Create metadata.md

---
 standards/application/metadata.md | 39 +++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 standards/application/metadata.md

diff --git a/standards/application/metadata.md b/standards/application/metadata.md
new file mode 100644
index 0000000..e034fc9
--- /dev/null
+++ b/standards/application/metadata.md
@@ -0,0 +1,39 @@
+---
+slug: 66
+title: 66/WAKU2-METADATA
+name: Waku Metadata Protocol
+status: raw
+editor: Alvaro Revuelta <alrevuelta@status.im>
+contributors:
+---
+
+# Metadata Protocol
+
+Waku specifies a req/resp protocol that provides information about the node's medatadata. Such metadata is meant to be used
+by the node to decide if a peer is worth connecting or not. The node that makes the request, includes its metadata
+so that the receiver is aware of it, without requiring an extra interaction. The parameters are the following:
+* `clusterId`: Unique identifier of the cluster that the node is running in.
+* `shards`: Shard indexes that the node is subscribed to.
+
+
+## Protocol id
+
+`/vac/waku/metadata/1.0.0`
+
+## Request
+
+```proto
+message WakuMetadataRequest {
+  optional uint32 cluster_id = 1;
+  repeated uint32 shards = 2;
+}
+```
+
+## Response
+
+```proto
+message WakuMetadataResponse {
+  optional uint32 cluster_id = 1;
+  repeated uint32 shards = 2;
+}
+```