... | ... | @@ -24,13 +24,13 @@ The session ID is the hash of a BDF list containing the unique ID of the introdu |
|
|
|
|
|
The protocol uses six message types.
|
|
|
|
|
|
**0: REQUEST** - Sent by the introducer to each introducee. The message body is a BDF list with four elements: `messageType` (int), `previousMessageId` (unique ID or null), `contact` (list), and `message` (string or null).
|
|
|
**0: REQUEST** - Sent by the introducer to each introducee. The message body is a BDF list with four elements: `messageType` (int), `previousMessageId` (unique ID or null), `contact` (list), and `text` (string or null).
|
|
|
|
|
|
`previousMessageId` is the unique ID of the previous message sent by the sender in this session, if any, which is a dependency.
|
|
|
|
|
|
`contact` is the identity of the other introducee, which is a list with three elements: `formatVersion` (int), `nickname` (string), and `publicKey` (raw).
|
|
|
|
|
|
`message` is an optional message from the introducer to the introducee explaining the introduction.
|
|
|
`text` is an optional message from the introducer to the introducee explaining the introduction.
|
|
|
|
|
|
**1: ACCEPT** - Sent by an introducee to the introducer if the sender accepts the introduction. Forwarded by the introducer to the other introducee. The message body is a BDF list with six elements: `messageType` (int), `sessionId` (unique ID), `previousMessageId` (unique ID), `ephemeralPublicKey` (raw), `timestamp` (int), and `transportProperties` (dictionary).
|
|
|
|
... | ... | |