mirror of
https://github.com/vacp2p/rfc.vac.dev.git
synced 2026-01-07 21:33:54 -05:00
40a3a4604d
* chore: MD content updates * fix: comparison symbol parsing by groups * chore: MD content updates
1.7 KiB
1.7 KiB
title, name, status, editor, contributors
| title | name | status | editor | contributors | |
|---|---|---|---|---|---|
| 22/TOY-CHAT | Waku v2 Toy Chat | draft | Franck Royer <franck@status.im> |
|
- Status: draft
- Editor: Franck Royer <franck@status.im>
- Contributors:
- Hanno Cornelius <hanno@status.im>
Content Topic: /toy-chat/2/huilong/proto.
This specification explains a toy chat example using Waku v2. This protocol is mainly used to:
- Dogfood Waku v2,
- Show an example of how to use Waku v2.
Currently, all main Waku v2 implementations support the toy chat protocol: nim-waku, js-waku (NodeJS and web) and go-waku.
Note that this is completely separate from the protocol the Status app is using for its chat functionality.
Design
The chat protocol enables sending and receiving messages in a chat room. There is currently only one chat room, which is tied to the content topic. The messages SHOULD NOT be encrypted.
The contentTopic MUST be set to /toy-chat/2/huilong/proto.
Payloads
syntax = "proto3";
message Chat2Message {
uint64 timestamp = 1;
string nick = 2;
bytes payload = 3;
}
timestamp: The time at which the message was sent, in Unix Epoch seconds,nick: The nickname of the user sending the message,payload: The text of the messages, UTF-8 encoded.
Copyright
Copyright and related rights waived via CC0.