From af20379925443c7b15e8c9311c5539152faad42d Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Mon, 20 May 2024 11:01:28 -0400
Subject: [PATCH] Delete standards/core/metadata.md

---
 standards/core/metadata.md | 37 -------------------------------------
 1 file changed, 37 deletions(-)
 delete mode 100644 standards/core/metadata.md

diff --git a/standards/core/metadata.md b/standards/core/metadata.md
deleted file mode 100644
index 0bd9660..0000000
--- a/standards/core/metadata.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: WAKU2-METADATA
-name: Waku Metadata Protocol
-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;
-}
-```