diff --git a/README.md b/README.md index 36d492b..98ad3d0 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ This repository contains specifications for the Waku suite of protocols. |[WAKU2-PEER-EXCHANGE](standards/core/peer-exchange.md)| Waku Peer Exchange | |[WAKU2-ENR](standards/core/enr.md)| Waku Usage of ENR | |[WAKU2-INCENTIVIZATION](standards/core/incentivization.md)| Waku Incentivization | -|[WAKU2-METADATA](standards/core/metadata.md)| Waku Metadata | +|[66/WAKU2-METADATA](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/66/metadata.md)| Waku Metadata | |[64/WAKU2-NETWORK](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/64/network.md)| Waku Network | |[RELAY-SHARDING](standards/core/relay-sharding.md)| Waku Relay Sharding | |[WAKU2-STORE](standards/core/store.md) | Waku Store Query | 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 -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; -} -```