Update Waku Links

status/raw/simple-scaling.md

@@ -63,14 +63,14 @@ efficient way will be part of a future document.
 Sharding the [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md)
 network is an integral part of scaling the Status app.
 
-[51/WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)
+[WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
 specifies shards clusters, which are sets of `1024` shards
 (separate pubsub mesh networks).
 Content topics specified by application protocols can be distributed over these shards.
 The Status app protocols are assigned to shard cluster `16`,
-as defined in [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/waku-RFC/informational/relay-static-shard-alloc.md).
+as defined in [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/master/informational/relay-static-shard-alloc.md).
 
-[WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)
+[WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
 specifies three sharding methods.
 This document uses *static sharding*,
 which leaves the distribution of content topics to application protocols,
@@ -88,7 +88,7 @@ The 1024 shards within the main Status shard cluster are allocated as follows.
 |    768 - 895  |   1:1 chat                       |
 |   896 - 1023  |   media and control msgs         |
 
-Shard indices are mapped to pubsub topic names as follows (specified in [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)).
+Shard indices are mapped to pubsub topic names as follows (specified in [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)).
 
 `/waku/2/rs/<cluster_id>/<shard_number>`
 
@@ -154,7 +154,7 @@ message CommunityDescription {
 }
 ```
 
-> *Note*: Currently, Status app has allocated shared cluster `16` in [52/WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/waku-RFC/informational/relay-static-shard-alloc.md).
+> *Note*: Currently, Status app has allocated shared cluster `16` in [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/master/informational/relay-static-shard-alloc.md).
 Status app could allocate more shard clusters, for instance to establish a test net.
 We could add the shard cluster index to the community description as well.
 The recommendation for now,
@@ -168,7 +168,7 @@ Status communities can be mapped to shards in two ways: static, and owner-based.
 
 With static mapping,
 communities are assigned a specific shard index within the Status shard cluster.
-This mapping is similar in nature to the shard cluster allocation in [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/waku-RFC/informational/relay-static-shard-alloc.md).
+This mapping is similar in nature to the shard cluster allocation in [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/master/informational/relay-static-shard-alloc.md).
 Shard indices allocated in that way are in the range `16 - 127`.
 The Status CC community uses index `16`
 (not to confuse with shard cluster index `16`, which is the Status shard cluster).
@@ -310,7 +310,7 @@ Light protocols comprise
 * [19/WAKU2-LIGHTPUSH](../../waku/standards/core/19/lightpush.md) for sending messages
 * [12/WAKU2-FILTER](../../waku/standards/core/12/filter.md)
 for requesting messages with specific attributes
-* [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/peer-exchange/peer-exchange.md)
+* [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/master/standards/core/peer-exchange.md)
 for discovering peers
 
 ## Waku Archive
@@ -333,7 +333,7 @@ In fact, the archive service can be offered by infrastructure nodes.
 
 ## Discovery
 
-Shard discovery is covered by [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md).
+Shard discovery is covered by [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md).
 This allows the Status app to abstract from the discovery process and
 simply address shards by their index.
 
@@ -344,7 +344,7 @@ this document suggests using [libp2p rendezvous](https://github.com/libp2p/specs
 Nodes can check whether they are behind a restrictive NAT using the
 [libp2p AutoNAT protocol](https://github.com/libp2p/specs/blob/master/autonat/README.md).
 
-> *Note:* The following will move into [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md),
+> *Note:* The following will move into [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md),
 or [33/WAKU2-DISCV5](../../waku/standards/core/33/discv5.md):
 Nodes behind restrictive NATs SHOULD not announce their publicly unreachable address
 via [33/WAKU2-DISCV5](../../waku/standards/core/33/discv5.md) discovery.
@@ -369,9 +369,9 @@ functionality offered by the libp2p circuit relay protocols, and
 to upgrade to a direct connection.
 
 Nodes that do not announce themselves at all and only plan to use light protocols,
-MAY use rendezvous discovery instead of or along-side [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/peer-exchange/peer-exchange.md).
+MAY use rendezvous discovery instead of or along-side [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/master/standards/core/peer-exchange.md).
 For these nodes, rendezvous and
-[WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/peer-exchange/peer-exchange.md)
+[WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/master/standards/core/peer-exchange.md)
 offer the same functionality,
 but return node sets sampled in different ways.
 Using both can help increasing connectivity.
@@ -401,7 +401,7 @@ The string conversion SHOULD remove leading zeros.
 field is of type string, a more efficient byte encoding is not utilized.
 
 Registering shard 2 in the Status shard cluster (with shard cluster index 16,
-see [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/waku-RFC/informational/relay-static-shard-alloc.md),
+see [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/master/informational/relay-static-shard-alloc.md),
 the register query would look like
 
 ```rs
@@ -601,7 +601,7 @@ It could be rate-limited with RLN.
 
 This document makes several trade-offs to privacy and anonymity.
 Todo: elaborate.
-See [WAKU2-ADVERSARIAL-MODELS](https://github.com/waku-org/specs/blob/waku-RFC/informational/adversarial-models.md)
+See [WAKU2-ADVERSARIAL-MODELS](https://github.com/waku-org/specs/blob/master/informational/adversarial-models.md)
 for information on Waku Anonymity.
 
 ## Copyright
@@ -614,12 +614,12 @@ Copyright and related rights waived via [CC0](https://creativecommons.org/public
 * [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
 * [23/WAKU2-TOPICS](../../waku/informational/23/topics.md)
 * [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md)
-* [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)
-* [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/waku-RFC/informational/relay-static-shard-alloc.md)
+* [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
+* [WAKU2-RELAY-STATIC-SHARD-ALLOC](https://github.com/waku-org/specs/blob/master/informational/relay-static-shard-alloc.md)
 * [30/ADAPTIVE-NODES](../../waku/informational/30/adaptive-nodes.md)
 * [19/WAKU2-LIGHTPUSH](../../waku/standards/core/19/lightpush.md)
 * [12/WAKU2-FILTER](../../waku/standards/core/12/filter.md)
-* [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/peer-exchange/peer-exchange.md)
+* [WAKU2-PEER-EXCHANGE](https://github.com/waku-org/specs/blob/master/standards/core/peer-exchange.md)
 * [13/WAKU2-STORE](../../waku/standards/core/13/store.md)
 * [libp2p rendezvous](https://github.com/libp2p/specs/blob/master/rendezvous/README.md)
 * [libp2p AutoNAT protocol](https://github.com/libp2p/specs/blob/master/autonat/README.md)
@@ -629,9 +629,9 @@ Copyright and related rights waived via [CC0](https://creativecommons.org/public
 * [DCUtR](https://github.com/libp2p/specs/blob/master/relay/DCUtR.md)
 * [scoring](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#extended-validators)
 * [Circuit Relay](https://docs.libp2p.io/concepts/nat/circuit-relay/)
-* [WAKU2-ADVERSARIAL-MODELS](https://github.com/waku-org/specs/blob/waku-RFC/informational/adversarial-models.md)
+* [WAKU2-ADVERSARIAL-MODELS](https://github.com/waku-org/specs/blob/master/informational/adversarial-models.md)
 
 ## Informative
 
 * [Circuit Relay](https://docs.libp2p.io/concepts/nat/circuit-relay/)
-* [WAKU2-ENR](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/enr.md)
+* [WAKU2-ENR](https://github.com/waku-org/specs/blob/master/standards/core/enr.md)

status/raw/status-waku-usage.md

@@ -15,12 +15,12 @@
 Status is a chat application which has several features,
 including, but not limited to -
 
-- Private 1:1 chats, described by [55/STATUS-1TO1-CHAT](/spec/55)
-- Large scale group chats, described by [56/STATUS-COMMUNITIES](/spec/56)
+- Private 1:1 chats, described by [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
+- Large scale group chats, described by [56/STATUS-COMMUNITIES](../56/communities.md)
 
 This specification describes how a Status implementation will make use of
 the underlying infrastructure, Waku,
-which is described in [10/WAKU2](/spec/10).
+which is described in [10/WAKU2](../../waku/standards/core/10/waku2.md).
 
 ## Background
 
@@ -38,13 +38,13 @@
 
 | Name  | Description |
 | --------------- | --------- |
-| `RELAY`| This refers to the Waku Relay protocol, described in [11/WAKU2-RELAY](/spec/11) |
-| `FILTER` | This refers to the Waku Filter protocol, described in [12/WAKU2-FILTER](/spec/12) |
-| `STORE` | This refers to the Waku Store protocol, described in [13/WAKU2-STORE](/spec/13) |
-| `MESSAGE` | This refers to the Waku Message format, described in [14/WAKU2-MESSAGE](/spec/14) |
-| `LIGHTPUSH` | This refers to the Waku Lightpush protocol, described in [19/WAKU2-LIGHTPUSH](/spec/19) |
+| `RELAY`| This refers to the Waku Relay protocol, described in [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md) |
+| `FILTER` | This refers to the Waku Filter protocol, described in [12/WAKU2-FILTER](../../waku/standards/core/12/filter.md) |
+| `STORE` | This refers to the Waku Store protocol, described in [13/WAKU2-STORE](../../waku/standards/core/13/store.md) |
+| `MESSAGE` | This refers to the Waku Message format, described in [14/WAKU2-MESSAGE](../../waku/standards/core/14/message.md) |
+| `LIGHTPUSH` | This refers to the Waku Lightpush protocol, described in [19/WAKU2-LIGHTPUSH](../../waku/standards/core/19/lightpush.md) |
 | Discovery | This refers to a peer discovery method used by a Waku node. |
-| `Pubsub Topic` / `Content Topic` | This refers to the routing of messages within the Waku network, described in [23/WAKU2-TOPICS](/spec/23/) |
+| `Pubsub Topic` / `Content Topic` | This refers to the routing of messages within the Waku network, described in [23/WAKU2-TOPICS](../../waku/informational/23/topics.md) |
 
 ### Waku Node
 
@@ -71,10 +71,10 @@
 
 The `RELAY` MUST NOT be used by Status light clients.
 The `RELAY` is used to broadcast messages between Status clients.
-All Status messages are transformed into [14/WAKU2-MESSAGE](/spec/14),
+All Status messages are transformed into [14/WAKU2-MESSAGE](../../waku/standards/core/14/message.md),
 which are sent over the wire.
 
-All Status message types are described in [62/STATUS-PAYLOAD](/spec/62).
+All Status message types are described in [62/STATUS-PAYLOADS](../62/payloads.md).
 Status Clients MUST transform the following object into a `MESSAGE`
 as described below -
 
@@ -110,7 +110,7 @@
 This protocol MUST remain optional according to the user's preferences,
 it MAY be enabled on Light clients as well.
 
-Messages received via [11/WAKU2-RELAY](/spec/11), are stored in a database.
+Messages received via [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md), are stored in a database.
 When Waku node running this protocol is service node,
 it MUST provide the complete list of network messages.
 Status clients SHOULD request historical messages from this service node.
@@ -146,16 +146,16 @@
 Status clients SHOULD apply a filter for all the `Content Topic`
 they are interested in, such as `Content Topic` derived from -
 
-1. 1:1 chats with other users, described in [55/STATUS-1TO1-CHAT](/spec/55)
+1. 1:1 chats with other users, described in [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
 2. Group chats
-3. Community Channels, described in [56/STATUS-COMMUNITIES](/spec/56)
+3. Community Channels, described in [56/STATUS-COMMUNITIES](../56/communities.md)
 
 ### 4. `LIGHTPUSH`
 
 The `LIGHTPUSH` protocol MUST be enabled on Status light clients.
 A Status `RELAY` node MAY implement `LIGHTPUSH` to support light clients.
 Peers will be able to publish messages,
-without running a full-fledged [11/WAKU2-RELAY](/spec/11) protocol.
+without running a full-fledged [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md) protocol.
 
 When a Status client is publishing a message,
 it MUST check if Light mode is enabled,
@@ -169,9 +169,9 @@
 that are provided by Waku, such as -
 
 1. [EIP-1459: DNS-Based Discovery](https://eips.ethereum.org/EIPS/eip-1459)
-2. [33/WAKU2-DISCV5](/spec/33): A node discovery protocol to
+2. [33/WAKU2-DISCV5](../../waku/standards/core/33/discv5.md): A node discovery protocol to
 create decentralized network of interconnected Waku nodes.
-3. [34/WAKU2-PEER-EXCHANGE](/spec/34):
+3. [34/WAKU2-PEER-EXCHANGE](../../waku/standards/core/34/peer-exchange.md):
 A peer discovery protocol for resource restricted devices.
 
 Status clients MAY use any combination of the above peer discovery methods,
@@ -182,37 +182,37 @@
 This specification inherits the security and
 privacy considerations from the following specifications -
 
-1. [10/WAKU2](/spec/10)
-2. [11/WAKU2-RELAY](/spec/11)
-3. [12/WAKU2-FILTER](/spec/12)
-4. [13/WAKU2-STORE](/spec/13)
-5. [14/WAKU2-MESSAGE](/spec/14)
-6. [23/WAKU2-TOPICS](/spec/23)
-7. [19/WAKU2-LIGHTPUSH](/spec/19)
-8. [55/STATUS-1TO1-CHAT](/spec/55)
-9. [56/STATUS-COMMUNITIES](/spec/56)
-10. [62/STATUS-PAYLOAD](/spec/62)
+1. [10/WAKU2](../../waku/standards/core/10/waku2.md)
+2. [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md)
+3. [12/WAKU2-FILTER](../../waku/standards/core/12/filter.md)
+4. [13/WAKU2-STORE](../../waku/standards/core/13/store.md)
+5. [14/WAKU2-MESSAGE](../../waku/standards/core/14/message.md)
+6. [23/WAKU2-TOPICS](../../waku/informational/23/topics.md)
+7. [19/WAKU2-LIGHTPUSH](../../waku/standards/core/19/lightpush.md)
+8. [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
+9. [56/STATUS-COMMUNITIES](../56/communities.md)
+10. [62/STATUS-PAYLOADS](../62/payloads.md)
 11. [EIP-1459: DNS-Based Discovery](https://eips.ethereum.org/EIPS/eip-1459)
-12. [33/WAKU2-DISCV5](/spec/33)
-13. [34/WAKU2-PEER-EXCHANGE](/spec/34)
+12. [33/WAKU2-DISCV5](../../waku/standards/core/33/discv5.md)
+13. [34/WAKU2-PEER-EXCHANGE](../../waku/standards/core/34/peer-exchange.md)
 
 ## Copyright
 
 Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
 
 ## References
 
-1. [55/STATUS-1TO1-CHAT](/spec/55)
-2. [56/STATUS-COMMUNITIES](/spec/56)
-3. [10/WAKU2](/spec/10)
-4. [11/WAKU2-RELAY](/spec/11)
-5. [12/WAKU2-FILTER](/spec/12)
-6. [13/WAKU2-STORE](/spec/13)
-7. [14/WAKU2-MESSAGE](/spec/14)
-8. [23/WAKU2-TOPICS](/spec/23)
-9. [19/WAKU2-LIGHTPUSH](/spec/19)
-10. [64/WAKU2-NETWORK](/spec/64)
-11. [62/STATUS-PAYLOAD](/spec/62)
+1. [55/STATUS-1TO1-CHAT](../55/1to1-chat.md)
+2. [56/STATUS-COMMUNITIES](../56/communities.md)
+3. [10/WAKU2](../../waku/standards/core/10/waku2.md)
+4. [11/WAKU2-RELAY](../../waku/standards/core/11/relay.md)
+5. [12/WAKU2-FILTER](../../waku/standards/core/12/filter.md)
+6. [13/WAKU2-STORE](../../waku/standards/core/13/store.md)
+7. [14/WAKU2-MESSAGE](../../waku/standards/core/14/message.md)
+8. [23/WAKU2-TOPICS](../../waku/informational/23/topics.md)
+9. [19/WAKU2-LIGHTPUSH](../../waku/standards/core/19/lightpush.md)
+10. [64/WAKU2-NETWORK](../../waku/standards/core/64/network.md)
+11. [62/STATUS-PAYLOADS](../62/payloads.md)
 12. [EIP-1459: DNS-Based Discovery](https://eips.ethereum.org/EIPS/eip-1459)
-13. [33/WAKU2-DISCV5](/spec/33)
-14. [34/WAKU2-PEER-EXCHANGE](/spec/34)
+13. [33/WAKU2-DISCV5](../../waku/standards/core/33/discv5.md)
+14. [34/WAKU2-PEER-EXCHANGE](../../waku/standards/core/34/peer-exchange.md)

status/raw/url-data.md

@@ -26,7 +26,7 @@ this specification proposes a standard method for encoding data within URLs.
 - Community: Refer to [STATUS-COMMUNITIES](../56/communities.md)
 - Channel: Refer to terminology in [STATUS-COMMUNITIES](../56/communities.md)
 - User: Refer to terminology in [STATUS-COMMUNITIES](../56/communities.md)
-- Shard Refer to terminology in [51/WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
+- Shard Refer to terminology in [WAKU2-RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
 
 ## Wire Format
 

vac/template.md

@@ -1,9 +1,9 @@
 ---
 slug: XX
-title: XX/(WAKU2|LOGOS|CODEX|*)-TEMPLATE
-name: (Waku v2 | Logos | Codex) RFC Template
-status: (raw|draft|stable)
-category: (Standards Track|Informational|Best Current Practice)
+title: TEMPLATE
+name: RFC Template
+status: raw/draft/stable/deprecated
+category: Standards Track/Informational/Best Current Practice
 tags: an optional list of tags, not standard
 editor: Daniel Kaiser <[email protected]>
 contributors:

waku/informational/23/topics.md

@@ -19,9 +19,9 @@ In [10/WAKU2 spec](../../standards/core/10/waku2.md) there are two types of topi
 ## Pubsub Topics
 
 Pubsub topics are used for routing of messages (see [11/WAKU2-RELAY](../../standards/core/11/relay.md)),
-and can be named implicitly by Waku sharding (see [RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)).
+and can be named implicitly by Waku sharding (see [RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)).
 This document comprises recommendations for explicitly naming pubsub topics
-(e.g. when choosing *named sharding* as specified in [RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)).
+(e.g. when choosing *named sharding* as specified in [RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)).
 
 ### Pubsub Topic Format
 
@@ -80,7 +80,7 @@ but for different domains completely.
 
 ### Named Topic Sharding Example
 
-The following is an example of named sharding, as specified in [RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md).
+The following is an example of named sharding, as specified in [RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md).
 
 ```text
 waku/2/waku-9_shard-0/
@@ -175,7 +175,7 @@ Copyright and related rights waived via
 
 - [10/WAKU2 spec](../../standards/core/10/waku2.md)
 - [11/WAKU2-RELAY](../../standards/core/11/relay.md)
-- [RELAY-SHARDING](https://github.com/waku-org/specs/blob/waku-RFC/standards/core/relay-sharding.md)
+- [RELAY-SHARDING](https://github.com/waku-org/specs/blob/master/standards/core/relay-sharding.md)
 - [Ethereum 2 P2P spec](https://github.com/ethereum/eth2.0-specs/blob/dev/specs/phase0/p2p-interface.md#topics-and-messages)
 - [14/WAKU2-MESSAGE](../../standards/core/14/message.md)
 - [12/WAKU2-FILTER](../../standards/core/12/filter.md)