From eb839b5f937596c0114d0ef50d3bb137e51fc412 Mon Sep 17 00:00:00 2001 From: Oskar Thoren Date: Tue, 31 Mar 2020 12:25:05 +0800 Subject: [PATCH] Fix more links --- docs/draft/7-group-chat.md | 2 +- docs/stable/5-secure-transport.md | 7 ++++--- docs/stable/6-payloads.md | 2 +- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/draft/7-group-chat.md b/docs/draft/7-group-chat.md index bec0850..b142f8e 100644 --- a/docs/draft/7-group-chat.md +++ b/docs/draft/7-group-chat.md @@ -35,7 +35,7 @@ This documents describes the group chat protocol used by the status application. ## Membership updates -Membership updates messages are used to propagate group chat membership changes. The protobuf format is described in the [Status Payload Specs](status-payload-specs.md). Here we will be describing each specific field. +Membership updates messages are used to propagate group chat membership changes. The protobuf format is described in the [6/PAYLOADS](https://specs.status.im/spec/6). Here we will be describing each specific field. The protobuf messages are: diff --git a/docs/stable/5-secure-transport.md b/docs/stable/5-secure-transport.md index 2c3e7f8..ff42d4c 100644 --- a/docs/stable/5-secure-transport.md +++ b/docs/stable/5-secure-transport.md @@ -10,7 +10,7 @@ title: 5/SECURE-TRANSPORT > > Status: Stable > -> Authors: Andrea Piana , Pedro Pombeiro , Corey Petty , Oskar Thorén , Dean Eigenmann Authors: Andrea Piana , Pedro Pombeiro , Corey Petty , Oskar Thorén , Dean Eigenmann ## Abstract @@ -130,13 +130,14 @@ Every client initially generates some key material which is stored locally: - A signed prekey based on secp256k1 - `SPK` - A prekey signature - `Sig(IK, Encode(SPK))` -More details can be found in the `X3DH Prekey bundle creation` section of [Account specification](./status-account-spec.md#x3dh-prekey-bundle-creation). +More details can be found in the `X3DH Prekey bundle creation` section of [2/ACCOUNT](https://specs.status.im/spec/2#x3dh-prekey-bundles). Prekey bundles can be extracted from any user's messages, or found via searching for their specific topic, `{IK}-contact-code`. TODO: See below on bundle retrieval, this seems like enhancement and parameter for recommendation ### Bundle retrieval + X3DH works by having client apps create and make available a bundle of prekeys (the X3DH bundle) that can later be requested by other interlocutors when they wish to start a conversation with a given user. @@ -161,7 +162,7 @@ There are two phases in the initial negotiation of a 1:1 chat: 1. **Identity verification** (e.g., face-to-face contact exchange through QR code, Identicon matching). A QR code serves two purposes simultaneously - identity verification and initial bundle retrieval; 1. **Asynchronous initial key exchange**, using X3DH. -For more information on account generation and trust establishment, see [Status Account Specification](status-account-spec.md) +For more information on account generation and trust establishment, see [2/ACCOUNT](https://specs.status.im/spec/2) #### Initial key exchange flow (X3DH) diff --git a/docs/stable/6-payloads.md b/docs/stable/6-payloads.md index c83f37c..20331d9 100644 --- a/docs/stable/6-payloads.md +++ b/docs/stable/6-payloads.md @@ -175,7 +175,7 @@ message StickerMessage { #### Message types -Message types are required to decide how a particular message is encrypted and what metadata needs to be attached when passing a message to the transport layer. For more on this, see [Status Whisper Usage Specification](./status-whisper-usage-spec.md). +Message types are required to decide how a particular message is encrypted and what metadata needs to be attached when passing a message to the transport layer. For more on this, see [3/WHISPER-USAGE](https://specs.status.im/spec/3).