mirror of
https://github.com/vacp2p/rfc-index.git
synced 2026-01-08 21:37:59 -05:00
Chore/fix headers (#239)
This commit is contained in:
fbarbu15
2
.github/workflows/.markdownlint.json
vendored
2
.github/workflows/.markdownlint.json
vendored
@@ -3,4 +3,4 @@
|
||||
"MD024": false,
|
||||
"MD025": false,
|
||||
"MD033": false
|
||||
}
|
||||
}
|
||||
|
||||
61
custom.css
61
custom.css
@@ -75,30 +75,12 @@ main h1, main h2, main h3, main h4 {
|
||||
margin-bottom: 0.6em;
|
||||
}
|
||||
|
||||
.rfc-meta {
|
||||
main h1 + table {
|
||||
margin: 1rem 0 1.5rem 0;
|
||||
padding: 0.75rem 1rem;
|
||||
border: 1px solid var(--table-border-color);
|
||||
background: var(--bg);
|
||||
}
|
||||
|
||||
.rfc-meta table {
|
||||
margin: 0;
|
||||
border: none;
|
||||
}
|
||||
|
||||
.rfc-meta th,
|
||||
.rfc-meta td {
|
||||
border: none;
|
||||
padding: 0.2rem 0.4rem 0.2rem 0;
|
||||
text-align: left;
|
||||
vertical-align: top;
|
||||
}
|
||||
|
||||
.rfc-meta th {
|
||||
main h1 + table th {
|
||||
width: 10rem;
|
||||
color: var(--sidebar-fg);
|
||||
font-weight: 600;
|
||||
}
|
||||
|
||||
main p, main li {
|
||||
@@ -311,3 +293,42 @@ main h1 {
|
||||
min-width: 0;
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
.menu-title-link {
|
||||
position: absolute;
|
||||
left: 50%;
|
||||
transform: translateX(-50%);
|
||||
text-decoration: none;
|
||||
color: inherit;
|
||||
}
|
||||
|
||||
.menu-title-link .menu-title {
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
.chapter-item > .chapter-link-wrapper > a {
|
||||
display: flex;
|
||||
align-items: center;
|
||||
gap: 0.4rem;
|
||||
}
|
||||
|
||||
.section-toggle::before {
|
||||
content: "▸";
|
||||
display: inline-block;
|
||||
font-size: 0.9em;
|
||||
line-height: 1;
|
||||
transition: transform 0.15s ease;
|
||||
}
|
||||
|
||||
.chapter-item:not(.collapsed) > a .section-toggle::before {
|
||||
transform: rotate(90deg);
|
||||
}
|
||||
|
||||
.chapter-item.collapsed > ol.section {
|
||||
display: none;
|
||||
}
|
||||
|
||||
.chapter-item.collapsed > .chapter-link-wrapper > a .section-toggle::before {
|
||||
transform: rotate(0deg);
|
||||
}
|
||||
|
||||
@@ -24,14 +24,6 @@ An IETF-style index of Vac-managed RFCs across Waku, Nomos, Codex, and Status. U
|
||||
<span class="chip" data-project="codex" data-label="Codex">Codex</span>
|
||||
</div>
|
||||
</div>
|
||||
<div class="quick-links">
|
||||
<a href="./vac/1/coss.html">1/COSS (Process)</a>
|
||||
<a href="./vac/README.html">Vac index</a>
|
||||
<a href="./waku/README.html">Waku index</a>
|
||||
<a href="./status/README.html">Status index</a>
|
||||
<a href="./nomos/README.html">Nomos index</a>
|
||||
<a href="./codex/README.html">Codex index</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="results-row">
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# CODEX-BLOCK-EXCHANGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Codex Block Exchange Protocol</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Codex Team</td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Codex Block Exchange Protocol |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Codex Team |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Specification Status
|
||||
|
||||
This specification contains a mix of:
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# CODEX-MARKETPLACE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Codex Storage Marketplace</td></tr>
|
||||
<tr><th>Slug</th><td>codex-marketplace</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Codex Team and Dmitriy Ryajov <dryajov@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Mark Spanbroek <mark@codex.storage><br>Adam Uhlíř <adam@codex.storage><br>Eric Mastro <eric@codex.storage><br>Jimmy Debe <jimmy@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Codex Storage Marketplace |
|
||||
| Slug | codex-marketplace |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Codex Team and Dmitriy Ryajov <dryajov@status.im> |
|
||||
| Contributors | Mark Spanbroek <mark@codex.storage>, Adam Uhlíř <adam@codex.storage>, Eric Mastro <eric@codex.storage>, Jimmy Debe <jimmy@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Codex Marketplace and its interactions are defined by a smart contract deployed on an EVM-compatible blockchain. This specification describes these interactions for the various roles within the network.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# CONSENSUS-CLARO
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Claro Consensus Protocol</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Corey Petty <corey@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Álvaro Castro-Castilla<br>Mark Evenson</td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Claro Consensus Protocol |
|
||||
| Status | deprecated |
|
||||
| Category | Standards Track |
|
||||
| Editor | Corey Petty <corey@status.im> |
|
||||
| Contributors | Álvaro Castro-Castilla, Mark Evenson |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document specifies Claro: a Byzantine, fault-tolerant, binary decision
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# NOMOSDA-ENCODING
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>NomosDA Encoding Protocol</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Sanchez-Quiros <danielsq@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Daniel Kashepava <danielkashepava@status.im><br>Álvaro Castro-Castilla <alvaro@status.im><br>Filip Dimitrijevic <filip@status.im><br>Thomas Lavaur <thomaslavaur@status.im><br>Mehmet Gonen <mehmet@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | NomosDA Encoding Protocol |
|
||||
| Status | raw |
|
||||
| Editor | Daniel Sanchez-Quiros <danielsq@status.im> |
|
||||
| Contributors | Daniel Kashepava <danielkashepava@status.im>, Álvaro Castro-Castilla <alvaro@status.im>, Filip Dimitrijevic <filip@status.im>, Thomas Lavaur <thomaslavaur@status.im>, Mehmet Gonen <mehmet@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
This document describes the encoding and verification processes of NomosDA, which is the data availability (DA) solution used by the Nomos blockchain. NomosDA provides an assurance that all data from Nomos blobs are accessible and verifiable by every network participant.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# NOMOS-DA-NETWORK
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>NomosDA Network</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Sanchez Quiros <danielsq@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Álvaro Castro-Castilla <alvaro@status.im><br>Daniel Kashepava <danielkashepava@status.im><br>Gusto Bacvinka <augustinas@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | NomosDA Network |
|
||||
| Status | raw |
|
||||
| Editor | Daniel Sanchez Quiros <danielsq@status.im> |
|
||||
| Contributors | Álvaro Castro-Castilla <alvaro@status.im>, Daniel Kashepava <danielkashepava@status.im>, Gusto Bacvinka <augustinas@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
NomosDA is the scalability solution protocol for data availability within the Nomos network.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# P2P-HARDWARE-REQUIREMENTS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Nomos p2p Network Hardware Requirements Specification</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>infrastructure</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Sanchez-Quiros <danielsq@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Nomos p2p Network Hardware Requirements Specification |
|
||||
| Status | raw |
|
||||
| Category | infrastructure |
|
||||
| Editor | Daniel Sanchez-Quiros <danielsq@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification defines the hardware requirements for running various types of Nomos blockchain nodes. Hardware needs vary significantly based on the node's role, from lightweight verification nodes to high-performance Zone Executors. The requirements are designed to support diverse participation levels while ensuring network security and performance.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# P2P-NAT-SOLUTION
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Nomos P2P Network NAT Solution Specification</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>networking</td></tr>
|
||||
<tr><th>Editor</th><td>Antonio Antonino <antonio@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Álvaro Castro-Castilla <alvaro@status.im><br>Daniel Sanchez-Quiros <danielsq@status.im><br>Petar Radovic <petar@status.im><br>Gusto Bacvinka <augustinas@status.im><br>Youngjoon Lee <youngjoon@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Nomos P2P Network NAT Solution Specification |
|
||||
| Status | raw |
|
||||
| Category | networking |
|
||||
| Editor | Antonio Antonino <antonio@status.im> |
|
||||
| Contributors | Álvaro Castro-Castilla <alvaro@status.im>, Daniel Sanchez-Quiros <danielsq@status.im>, Petar Radovic <petar@status.im>, Gusto Bacvinka <augustinas@status.im>, Youngjoon Lee <youngjoon@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification defines a comprehensive NAT (Network Address Translation) traversal solution for the Nomos P2P network. The solution enables nodes to automatically determine their NAT status and establish both outbound and inbound connections regardless of network configuration. The strategy combines [AutoNAT](https://github.com/libp2p/specs/blob/master/autonat/autonat-v2.md), dynamic port mapping protocols, and continuous verification to maximize public reachability while maintaining decentralized operation.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# P2P-NETWORK-BOOTSTRAPPING
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Nomos P2P Network Bootstrapping Specification</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>networking</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Sanchez-Quiros <danielsq@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Álvaro Castro-Castilla <alvaro@status.im><br>Petar Radovic <petar@status.im><br>Gusto Bacvinka <augustinas@status.im><br>Antonio Antonino <antonio@status.im><br>Youngjoon Lee <youngjoon@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Nomos P2P Network Bootstrapping Specification |
|
||||
| Status | raw |
|
||||
| Category | networking |
|
||||
| Editor | Daniel Sanchez-Quiros <danielsq@status.im> |
|
||||
| Contributors | Álvaro Castro-Castilla <alvaro@status.im>, Petar Radovic <petar@status.im>, Gusto Bacvinka <augustinas@status.im>, Antonio Antonino <antonio@status.im>, Youngjoon Lee <youngjoon@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
Nomos network bootstrapping is the process by which a new node discovers peers and synchronizes with the existing decentralized network. It ensures that a node can:
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# NOMOS-P2P-NETWORK
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Nomos P2P Network Specification</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>networking</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Sanchez-Quiros <danielsq@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Nomos P2P Network Specification |
|
||||
| Status | draft |
|
||||
| Category | networking |
|
||||
| Editor | Daniel Sanchez-Quiros <danielsq@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification defines the peer-to-peer (P2P) network layer for Nomos blockchain nodes. The network serves as the comprehensive communication infrastructure enabling transaction dissemination through mempool and block propagation. The specification leverages established libp2p protocols to ensure robust, scalable performance with low bandwidth requirements and minimal latency while maintaining accessibility for diverse hardware configurations and network environments.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# NOMOS-SDP
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Nomos Service Declaration Protocol Specification</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Marcin Pawlowski <marcin@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Mehmet <mehmet@status.im><br>Daniel Sanchez Quiros <danielsq@status.im><br>Álvaro Castro-Castilla <alvaro@status.im><br>Thomas Lavaur <thomaslavaur@status.im><br>Filip Dimitrijevic <filip@status.im><br>Gusto Bacvinka <augustinas@status.im><br>David Rusu <davidrusu@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Nomos Service Declaration Protocol Specification |
|
||||
| Status | raw |
|
||||
| Editor | Marcin Pawlowski <marcin@status.im> |
|
||||
| Contributors | Mehmet <mehmet@status.im>, Daniel Sanchez Quiros <danielsq@status.im>, Álvaro Castro-Castilla <alvaro@status.im>, Thomas Lavaur <thomaslavaur@status.im>, Filip Dimitrijevic <filip@status.im>, Gusto Bacvinka <augustinas@status.im>, David Rusu <davidrusu@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
This document defines a mechanism enabling validators to declare their participation in specific protocols that require a known and agreed-upon list of participants. Some examples of this are Data Availability and the Blend Network. We create a single repository of identifiers which is used to establish secure communication between validators and provide services. Before being admitted to the repository, the validator proves that it locked at least a minimum stake.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 24/STATUS-CURATION
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Community Directory Curation Voting using Waku v2</td></tr>
|
||||
<tr><th>Slug</th><td>24</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Szymon Szlachtowicz <szymon.s@ethworks.io></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Community Directory Curation Voting using Waku v2 |
|
||||
| Slug | 24 |
|
||||
| Status | draft |
|
||||
| Editor | Szymon Szlachtowicz <szymon.s@ethworks.io> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification is a voting protocol for peers to submit votes to a smart contract.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 28/STATUS-FEATURING
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status community featuring using waku v2</td></tr>
|
||||
<tr><th>Slug</th><td>28</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Szymon Szlachtowicz <szymon.s@ethworks.io></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status community featuring using waku v2 |
|
||||
| Slug | 28 |
|
||||
| Status | draft |
|
||||
| Editor | Szymon Szlachtowicz <szymon.s@ethworks.io> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes a voting method to feature different active Status Communities.
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 55/STATUS-1TO1-CHAT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status 1-to-1 Chat</td></tr>
|
||||
<tr><th>Slug</th><td>55</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Piana <andreap@status.im><br>Pedro Pombeiro <pedro@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Dean Eigenmann <dean@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status 1-to-1 Chat |
|
||||
| Slug | 55 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Andrea Piana <andreap@status.im>, Pedro Pombeiro <pedro@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Dean Eigenmann <dean@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how the Status 1-to-1 chat protocol is implemented
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 56/STATUS-COMMUNITIES
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Communities that run over Waku v2</td></tr>
|
||||
<tr><th>Slug</th><td>56</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Piana <andreap@status.im><br>Prem Chaitanya Prathi <prem@waku.org></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Communities that run over Waku v2 |
|
||||
| Slug | 56 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Andrea Piana <andreap@status.im>, Prem Chaitanya Prathi <prem@waku.org> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes the design of Status Communities over Waku v2,
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 61/STATUS-Community-History-Service
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Community History Service</td></tr>
|
||||
<tr><th>Slug</th><td>61</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>r4bbit <r4bbit@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Sanaz Taheri <sanaz@status.im><br>John Lea <john@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Community History Service |
|
||||
| Slug | 61 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | r4bbit <r4bbit@status.im> |
|
||||
| Contributors | Sanaz Taheri <sanaz@status.im>, John Lea <john@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Messages are stored permanently by store nodes
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 62/STATUS-PAYLOADS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Message Payloads</td></tr>
|
||||
<tr><th>Slug</th><td>62</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>r4bbit <r4bbit@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Maria Piana <andreap@status.im><br>Oskar Thoren <oskarth@titanproxy.com><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Message Payloads |
|
||||
| Slug | 62 |
|
||||
| Status | draft |
|
||||
| Editor | r4bbit <r4bbit@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Oskar Thoren <oskarth@titanproxy.com>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how the payload of each message in Status looks
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 63/STATUS-Keycard-Usage
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Keycard Usage</td></tr>
|
||||
<tr><th>Slug</th><td>63</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Jimmy Debe <jimmy@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Keycard Usage |
|
||||
| Slug | 63 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Jimmy Debe <jimmy@status.im> |
|
||||
|
||||
## Terminology
|
||||
|
||||
- **Account**: A valid
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 65/STATUS-ACCOUNT-ADDRESS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Account Address</td></tr>
|
||||
<tr><th>Slug</th><td>65</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Corey Petty <corey@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Account Address |
|
||||
| Slug | 65 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Corey Petty <corey@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification details what a Status account address is and
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 71/STATUS-PUSH-NOTIFICATION-SERVER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Push Notification Server</td></tr>
|
||||
<tr><th>Slug</th><td>71</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Jimmy Debe <jimmy@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Maria Piana <andreap@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Push Notification Server |
|
||||
| Slug | 71 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Jimmy Debe <jimmy@status.im> |
|
||||
| Contributors | Andrea Maria Piana <andreap@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
A push notification server implementation for IOS devices and Android devices.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 3RD-PARTY
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>3rd party</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Volodymyr Kozieiev <volodymyr@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | 3rd party |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Volodymyr Kozieiev <volodymyr@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification discusses 3rd party APIs that Status relies on.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# IPFS-gateway-for-Sticker-Pack
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>IPFS gateway for Sticker Pack</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Gheorghe Pinzaru <gheorghe@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | IPFS gateway for Sticker Pack |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Gheorghe Pinzaru <gheorghe@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how Status uses the IPFS gateway
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# ACCOUNT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Account</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Corey Petty <corey@status.im><br>Oskar Thorén <oskar@status.im><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Account |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification explains what a Status account is,
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# CLIENT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Client</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Maria Piana <andreap@status.im><br>Dean Eigenmann <dean@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskar@status.im><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Client |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Dean Eigenmann <dean@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how to write a Status client for communicating
|
||||
|
||||
@@ -1,12 +1,11 @@
|
||||
# Dapp browser API usage
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Dapp browser API usage</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Dapp browser API usage |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes requirements that an application must fulfill in order to provide a proper environment for Dapps running inside a browser.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# EIPS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>EIPS</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Ricardo Guilherme Schmidt <ricardo3@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>None</td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | EIPS |
|
||||
| Status | deprecated |
|
||||
| Editor | Ricardo Guilherme Schmidt <ricardo3@status.im> |
|
||||
| Contributors | None |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how Status relates with EIPs.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# ETHEREUM-USAGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status interactions with the Ethereum blockchain</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Maria Piana <andreap@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status interactions with the Ethereum blockchain |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Andrea Maria Piana <andreap@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification documents all the interactions that the Status client has
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# GROUP-CHAT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Group Chat</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Piana <andreap@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Group Chat |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Andrea Piana <andreap@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes the group chat protocol used by the Status application.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# Keycard Usage for Wallet and Chat Keys
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Keycard Usage for Wallet and Chat Keys</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Roman Volosovskyi <roman@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Keycard Usage for Wallet and Chat Keys |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Roman Volosovskyi <roman@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
In this specification, we describe how Status communicates with Keycard to create, store and use multiaccount.
|
||||
|
||||
@@ -1,13 +1,11 @@
|
||||
# NOTIFICATIONS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Notifications</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Eric Dvorsak <eric@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Notifications |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Eric Dvorsak <eric@status.im> |
|
||||
|
||||
## Local Notifications
|
||||
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# PAYLOADS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Payloads</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Maria Piana <andreap@status.im><br>Oskar Thorén <oskar@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Payloads |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Oskar Thorén <oskar@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how the payload of each message in Status looks like.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# PUSH-NOTIFICATION-SERVER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Push notification server</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Maria Piana <andreap@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Push notification server |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Andrea Maria Piana <andreap@status.im> |
|
||||
|
||||
## Reason
|
||||
|
||||
Push notifications for iOS devices and some Android devices can only be implemented by relying on [APN service](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/APNSOverview.html#//apple_ref/doc/uid/TP40008194-CH8-SW1) for iOS or [Firebase](https://firebase.google.com/).
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# SECURE-TRANSPORT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Secure Transport</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Maria Piana <andreap@status.im><br>Corey Petty <corey@status.im><br>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskar@status.im><br>Pedro Pombeiro <pedro@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Secure Transport |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Andrea Maria Piana <andreap@status.im>, Corey Petty <corey@status.im>, Dean Eigenmann <dean@status.im>, Oskar Thorén <oskar@status.im>, Pedro Pombeiro <pedro@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes how Status provides a secure channel between two peers,
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# WAKU-MAILSERVER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Mailserver</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Oskar Thorén <oskar@status.im><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Mailserver |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Oskar Thorén <oskar@status.im>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Being mostly offline is an intrinsic property of mobile clients.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# WAKU-USAGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Usage</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskar@status.im><br>Samuel Hawksby-Robinson <samuel@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Usage |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im>, Samuel Hawksby-Robinson <samuel@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Status uses [Waku](/waku/standards/legacy/6/waku1.md) to provide privacy-preserving routing
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# WHISPER-MAILSERVER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Whisper mailserver</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Oskar Thorén <oskar@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Whisper mailserver |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Oskar Thorén <oskar@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Being mostly offline is an intrinsic property of mobile clients.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# WHISPER-USAGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Whisper Usage</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Piana <andreap@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskar@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Whisper Usage |
|
||||
| Status | deprecated |
|
||||
| Editor | Filip Dimitrijevic <filip@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Piana <andreap@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
Status uses [Whisper](https://eips.ethereum.org/EIPS/eip-627) to provide
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# STATUS-SIMPLE-SCALING
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Simple Scaling</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Informational</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Alvaro Revuelta <alrevuelta@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Simple Scaling |
|
||||
| Status | raw |
|
||||
| Category | Informational |
|
||||
| Editor | Daniel Kaiser <danielkaiser@status.im> |
|
||||
| Contributors | Alvaro Revuelta <alrevuelta@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes how to scale
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# STATUS-PROTOCOLS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status Protocol Stack</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Jimmy Debe <jimmy@status.im><br>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status Protocol Stack |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Jimmy Debe <jimmy@status.im>, Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes the Status Application protocol stack.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# STATUS-MVDS-USAGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>MVDS Usage in Status</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Best Current Practice</td></tr>
|
||||
<tr><th>Editor</th><td>Kaichao Sun <kaichao@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | MVDS Usage in Status |
|
||||
| Status | raw |
|
||||
| Category | Best Current Practice |
|
||||
| Editor | Kaichao Sun <kaichao@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document lists the types of messages that are using [MVDS](/vac/2/mvds.md)
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# STATUS-URL-DATA
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status URL Data</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Felicio Mununga <felicio@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Aaryamann Challani <aaryamann@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status URL Data |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Felicio Mununga <felicio@status.im> |
|
||||
| Contributors | Aaryamann Challani <aaryamann@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document specifies serialization, compression, and
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# STATUS-URL-SCHEME
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Status URL Scheme</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Felicio Mununga <felicio@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Status URL Scheme |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Felicio Mununga <felicio@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes URL scheme for previewing and
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 1/COSS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Consensus-Oriented Specification System</td></tr>
|
||||
<tr><th>Slug</th><td>1</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Best Current Practice</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Oskar Thoren <oskarth@titanproxy.com><br>Pieter Hintjens <ph@imatix.com><br>André Rebentisch <andre@openstandards.de><br>Alberto Barrionuevo <abarrio@opentia.es><br>Chris Puttick <chris.puttick@thehumanjourney.net><br>Yurii Rashkovskii <yrashk@gmail.com><br>Jimmy Debe <jimmy@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Consensus-Oriented Specification System |
|
||||
| Slug | 1 |
|
||||
| Status | draft |
|
||||
| Category | Best Current Practice |
|
||||
| Editor | Daniel Kaiser <danielkaiser@status.im> |
|
||||
| Contributors | Oskar Thoren <oskarth@titanproxy.com>, Pieter Hintjens <ph@imatix.com>, André Rebentisch <andre@openstandards.de>, Alberto Barrionuevo <abarrio@opentia.es>, Chris Puttick <chris.puttick@thehumanjourney.net>, Yurii Rashkovskii <yrashk@gmail.com>, Jimmy Debe <jimmy@status.im> |
|
||||
|
||||
This document describes a consensus-oriented specification system (COSS)
|
||||
for building interoperable technical specifications.
|
||||
COSS is based on a lightweight editorial process that
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 2/MVDS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Minimum Viable Data Synchronization</td></tr>
|
||||
<tr><th>Slug</th><td>2</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Sanaz Taheri <sanaz@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Minimum Viable Data Synchronization |
|
||||
| Slug | 2 |
|
||||
| Status | stable |
|
||||
| Editor | Sanaz Taheri <sanaz@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
In this specification, we describe a minimum viable protocol for
|
||||
data synchronization inspired by the Bramble Synchronization Protocol ([BSP](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md)).
|
||||
This protocol is designed to ensure reliable messaging
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 25/LIBP2P-DNS-DISCOVERY
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Libp2p Peer Discovery via DNS</td></tr>
|
||||
<tr><th>Slug</th><td>25</td></tr>
|
||||
<tr><th>Status</th><td>deleted</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Libp2p Peer Discovery via DNS |
|
||||
| Slug | 25 |
|
||||
| Status | deleted |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
`25/LIBP2P-DNS-DISCOVERY` specifies a scheme to implement [`libp2p`](https://libp2p.io/)
|
||||
peer discovery via DNS for Waku v2.
|
||||
The generalised purpose is to retrieve an arbitrarily long, authenticated,
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 3/REMOTE-LOG
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Remote log specification</td></tr>
|
||||
<tr><th>Slug</th><td>3</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Remote log specification |
|
||||
| Slug | 3 |
|
||||
| Status | draft |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im> |
|
||||
|
||||
A remote log is a replication of a local log.
|
||||
This means a node can read data that originally came from a node that is offline.
|
||||
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 32/RLN-V1
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Rate Limit Nullifier</td></tr>
|
||||
<tr><th>Slug</th><td>32</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Barry Whitehat <barrywhitehat@protonmail.com><br>Sanaz Taheri <sanaz@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Onur Kilic <onurkilic1004@gmail.com><br>Blagoj Dimovski <blagoj.dimovski@yandex.com><br>Rasul Ibragimov <curryrasul@gmail.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Rate Limit Nullifier |
|
||||
| Slug | 32 |
|
||||
| Status | draft |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Barry Whitehat <barrywhitehat@protonmail.com>, Sanaz Taheri <sanaz@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Onur Kilic <onurkilic1004@gmail.com>, Blagoj Dimovski <blagoj.dimovski@yandex.com>, Rasul Ibragimov <curryrasul@gmail.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
The following specification covers the RLN construct
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 4/MVDS-META
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>MVDS Metadata Field</td></tr>
|
||||
<tr><th>Slug</th><td>4</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Sanaz Taheri <sanaz@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Andrea Maria Piana <andreap@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | MVDS Metadata Field |
|
||||
| Slug | 4 |
|
||||
| Status | draft |
|
||||
| Editor | Sanaz Taheri <sanaz@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Andrea Maria Piana <andreap@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
In this specification, we describe a method to construct message history that
|
||||
will aid the consistency guarantees of [2/MVDS](../2/mvds.md).
|
||||
Additionally,
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# HASHGRAPHLIKE CONSENSUS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Hashgraphlike Consensus Protocol</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Ugur Sen [ugur@status.im](mailto:ugur@status.im)</td></tr>
|
||||
<tr><th>Contributors</th><td>s<br>e<br>e<br>m<br>e<br>n<br>k<br>i<br>n<br>a<br> <br>[<br>e<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>]<br>(<br>m<br>a<br>i<br>l<br>t<br>o<br>:<br>e<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>)</td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Hashgraphlike Consensus Protocol |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Ugur Sen [ugur@status.im](mailto:ugur@status.im) |
|
||||
| Contributors | seemenkina [ekaterina@status.im](mailto:ekaterina@status.im) |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document specifies a scalable, decentralized, and Byzantine Fault Tolerant (BFT)
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# ETH-DCGKA
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Decentralized Key and Session Setup for Secure Messaging over Ethereum</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>informational</td></tr>
|
||||
<tr><th>Editor</th><td>Ramses Fernandez-Valencia <ramses@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Decentralized Key and Session Setup for Secure Messaging over Ethereum |
|
||||
| Status | raw |
|
||||
| Category | informational |
|
||||
| Editor | Ramses Fernandez-Valencia <ramses@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document introduces a decentralized group messaging protocol
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# ETH-SECPM
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Secure channel setup using Ethereum accounts</td></tr>
|
||||
<tr><th>Status</th><td>deleted</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Ramses Fernandez <ramses@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Secure channel setup using Ethereum accounts |
|
||||
| Status | deleted |
|
||||
| Category | Standards Track |
|
||||
| Editor | Ramses Fernandez <ramses@status.im> |
|
||||
|
||||
## NOTE
|
||||
|
||||
The content of this specification has been split between
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# ETH-MLS-OFFCHAIN
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Secure channel setup using decentralized MLS and Ethereum accounts</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Ugur Sen [ugur@status.im](mailto:ugur@status.im)</td></tr>
|
||||
<tr><th>Contributors</th><td>s<br>e<br>e<br>m<br>e<br>n<br>k<br>i<br>n<br>a<br> <br>[<br>e<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>]<br>(<br>m<br>a<br>i<br>l<br>t<br>o<br>:<br>e<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>)</td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Secure channel setup using decentralized MLS and Ethereum accounts |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Ugur Sen [ugur@status.im](mailto:ugur@status.im) |
|
||||
| Contributors | seemenkina [ekaterina@status.im](mailto:ekaterina@status.im) |
|
||||
|
||||
## Abstract
|
||||
|
||||
The following document specifies Ethereum authenticated scalable
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# ETH-MLS-ONCHAIN
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Secure channel setup using decentralized MLS and Ethereum accounts</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Ramses Fernandez <ramses@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>A<br>a<br>r<br>y<br>a<br>m<br>a<br>n<br>n<br> <br>C<br>h<br>a<br>l<br>l<br>a<br>n<br>i<br> <br><<br>a<br>a<br>r<br>y<br>a<br>m<br>a<br>n<br>n<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>><br>,<br> <br>E<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br> <br>B<br>r<br>o<br>s<br>l<br>a<br>v<br>s<br>k<br>a<br>y<br>a<br> <br><<br>e<br>k<br>a<br>t<br>e<br>r<br>i<br>n<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>><br>,<br> <br>U<br>g<br>u<br>r<br> <br>S<br>e<br>n<br> <br><<br>u<br>g<br>u<br>r<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>><br>,<br> <br>K<br>s<br>r<br> <br><<br>k<br>s<br>r<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Secure channel setup using decentralized MLS and Ethereum accounts |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Ramses Fernandez <ramses@status.im> |
|
||||
| Contributors | Aaryamann Challani <aaryamann@status.im>, Ekaterina Broslavskaya <ekaterina@status.im>, Ugur Sen <ugur@status.im>, Ksr <ksr@status.im> |
|
||||
|
||||
## Motivation
|
||||
|
||||
The need for secure communications has become paramount.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# GOSSIPSUB-TOR-PUSH
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Gossipsub Tor Push</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Gossipsub Tor Push |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Daniel Kaiser <danielkaiser@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document extends the [libp2p gossipsub specification](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/README.md)
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# LOGOS-CAPABILITY-DISCOVERY
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Logos Capability Discovery Protocol</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Arunima Chaudhuri [arunima@status.im](mailto:arunima@status.im)</td></tr>
|
||||
<tr><th>Contributors</th><td>U<br>g<br>u<br>r<br> <br>S<br>e<br>n<br> <br>[<br>u<br>g<br>u<br>r<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>]<br>(<br>m<br>a<br>i<br>l<br>t<br>o<br>:<br>u<br>g<br>u<br>r<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>)</td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Logos Capability Discovery Protocol |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Arunima Chaudhuri [arunima@status.im](mailto:arunima@status.im) |
|
||||
| Contributors | Ugur Sen [ugur@status.im](mailto:ugur@status.im) |
|
||||
|
||||
> **Note:** This specification is currently a WIP and undergoing a high rate of changes.
|
||||
|
||||
## Abstract
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# LIBP2P-MIX
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Libp2p Mix Protocol</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Prem Prathi <premprathi@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>A<br>k<br>s<br>h<br>a<br>y<br>a<br> <br>M<br>a<br>n<br>i<br> <br><<br>a<br>k<br>s<br>h<br>a<br>y<br>a<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>><br>,<br> <br>D<br>a<br>n<br>i<br>e<br>l<br> <br>K<br>a<br>i<br>s<br>e<br>r<br> <br><<br>d<br>a<br>n<br>i<br>e<br>l<br>k<br>a<br>i<br>s<br>e<br>r<br>@<br>s<br>t<br>a<br>t<br>u<br>s<br>.<br>i<br>m<br>></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Libp2p Mix Protocol |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Prem Prathi <premprathi@proton.me> |
|
||||
| Contributors | Akshaya Mani <akshaya@status.im>, Daniel Kaiser <danielkaiser@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
The Mix Protocol defines a decentralized anonymous message routing layer for libp2p networks.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# NOISE-X3DH-DOUBLE-RATCHET
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Secure 1-to-1 channel setup using X3DH and the double ratchet</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Ramses Fernandez <ramses@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Secure 1-to-1 channel setup using X3DH and the double ratchet |
|
||||
| Status | raw |
|
||||
| Category | Standards Track |
|
||||
| Editor | Ramses Fernandez <ramses@status.im> |
|
||||
|
||||
## Motivation
|
||||
|
||||
The need for secure communications has become paramount.
|
||||
|
||||
@@ -1,12 +1,11 @@
|
||||
# RLN-INTEREP-SPEC
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Interep as group management for RLN</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Interep as group management for RLN |
|
||||
| Status | raw |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This spec integrates [Interep](https://interep.link)
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# RLN-STEALTH-COMMITMENTS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>RLN Stealth Commitment Usage</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Jimmy Debe <jimmy@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | RLN Stealth Commitment Usage |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Jimmy Debe <jimmy@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes the usage of stealth commitments
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# RLN-V2
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Rate Limit Nullifier V2</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Rasul Ibragimov <curryrasul@gmail.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Lev Soukhanov <0xdeadfae@gmail.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Rate Limit Nullifier V2 |
|
||||
| Status | raw |
|
||||
| Editor | Rasul Ibragimov <curryrasul@gmail.com> |
|
||||
| Contributors | Lev Soukhanov <0xdeadfae@gmail.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
The protocol specified in this document is an improvement of [32/RLN-V1](../32/rln-v1.md),
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# SDS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Scalable Data Sync protocol for distributed logs</td></tr>
|
||||
<tr><th>Status</th><td>raw</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Akhil Peddireddy <akhil@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Scalable Data Sync protocol for distributed logs |
|
||||
| Status | raw |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Akhil Peddireddy <akhil@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification introduces the Scalable Data Sync (SDS) protocol
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# TEMPLATE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>RFC Template</td></tr>
|
||||
<tr><th>Slug</th><td>XX</td></tr>
|
||||
<tr><th>Status</th><td>raw/draft/stable/deprecated</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track/Informational/Best Current Practice</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | RFC Template |
|
||||
| Slug | XX |
|
||||
| Status | raw/draft/stable/deprecated |
|
||||
| Category | Standards Track/Informational/Best Current Practice |
|
||||
| Editor | Daniel Kaiser <danielkaiser@status.im> |
|
||||
|
||||
## (Info, remove this section)
|
||||
|
||||
This section contains meta info about writing RFCs.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 16/WAKU2-RPC
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 RPC API</td></tr>
|
||||
<tr><th>Slug</th><td>16</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 RPC API |
|
||||
| Slug | 16 |
|
||||
| Status | deprecated |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
This specification describes the JSON-RPC API that Waku v2 nodes MAY adhere to.
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 18/WAKU2-SWAP
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku SWAP Accounting</td></tr>
|
||||
<tr><th>Slug</th><td>18</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku SWAP Accounting |
|
||||
| Slug | 18 |
|
||||
| Status | deprecated |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification outlines how we do accounting and settlement based on the provision
|
||||
@@ -56,10 +55,10 @@ where `b>c`.
|
||||
|
||||
From A's point of view:
|
||||
|
||||
A/B | Cooperate | Defect
|
||||
-----|----------|-------
|
||||
Cooperate | b-c | -c
|
||||
Defect | b | 0
|
||||
| A/B | Cooperate | Defect |
|
||||
| --- | --- | --- |
|
||||
| Cooperate | b-c | -c |
|
||||
| Defect | b | 0 |
|
||||
|
||||
What this means is that if A and B cooperates,
|
||||
A gets some benefit `b` minus a cost `c`.
|
||||
@@ -69,10 +68,10 @@ If both defect they get neither benefit nor cost.
|
||||
|
||||
The generalized form of PD is:
|
||||
|
||||
A/B | Cooperate | Defect
|
||||
-----|----------|-------
|
||||
Cooperate | R | S
|
||||
Defect | T | P
|
||||
| A/B | Cooperate | Defect |
|
||||
| --- | --- | --- |
|
||||
| Cooperate | R | S |
|
||||
| Defect | T | P |
|
||||
|
||||
With R=reward, S=Sucker's payoff, T=temptation, P=punishment
|
||||
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 5/WAKU0
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v0</td></tr>
|
||||
<tr><th>Slug</th><td>5</td></tr>
|
||||
<tr><th>Status</th><td>deprecated</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Maria Piana <andreap@status.im><br>Dean Eigenmann <dean@status.im><br>Kim De Mey <kimdemey@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v0 |
|
||||
| Slug | 5 |
|
||||
| Status | deprecated |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Dean Eigenmann <dean@status.im>, Kim De Mey <kimdemey@status.im> |
|
||||
|
||||
This specification describes the format of Waku messages within the ÐΞVp2p Wire Protocol.
|
||||
This spec substitutes [EIP-627](https://eips.ethereum.org/EIPS/eip-627).
|
||||
Waku is a fork of the original Whisper protocol that enables better usability
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 21/WAKU2-FAULT-TOLERANT-STORE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Fault-Tolerant Store</td></tr>
|
||||
<tr><th>Slug</th><td>21</td></tr>
|
||||
<tr><th>Status</th><td>deleted</td></tr>
|
||||
<tr><th>Editor</th><td>Sanaz Taheri <sanaz@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Fault-Tolerant Store |
|
||||
| Slug | 21 |
|
||||
| Status | deleted |
|
||||
| Editor | Sanaz Taheri <sanaz@status.im> |
|
||||
|
||||
The reliability of [13/WAKU2-STORE](../../core/13/store.md)
|
||||
protocol heavily relies on the fact that full nodes i.e.,
|
||||
those who persist messages have high availability and
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 22/TOY-CHAT
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Toy Chat</td></tr>
|
||||
<tr><th>Slug</th><td>22</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Franck Royer <franck@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Toy Chat |
|
||||
| Slug | 22 |
|
||||
| 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.
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 23/WAKU2-TOPICS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Topic Usage Recommendations</td></tr>
|
||||
<tr><th>Slug</th><td>23</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Informational</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thoren <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Hanno Cornelius <hanno@status.im><br>Daniel Kaiser <danielkaiser@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Topic Usage Recommendations |
|
||||
| Slug | 23 |
|
||||
| Status | draft |
|
||||
| Category | Informational |
|
||||
| Editor | Oskar Thoren <oskarth@titanproxy.com> |
|
||||
| Contributors | Hanno Cornelius <hanno@status.im>, Daniel Kaiser <danielkaiser@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
This document outlines recommended usage of topic names in Waku v2.
|
||||
In [10/WAKU2 spec](/waku/standards/core/10/waku2.md) there are two types of topics:
|
||||
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 27/WAKU2-PEERS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Client Peer Management Recommendations</td></tr>
|
||||
<tr><th>Slug</th><td>27</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Client Peer Management Recommendations |
|
||||
| Slug | 27 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
`27/WAKU2-PEERS` describes a recommended minimal set of peer storage and
|
||||
peer management features to be implemented by Waku v2 clients.
|
||||
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 29/WAKU2-CONFIG
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Client Parameter Configuration Recommendations</td></tr>
|
||||
<tr><th>Slug</th><td>29</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Client Parameter Configuration Recommendations |
|
||||
| Slug | 29 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
`29/WAKU2-CONFIG` describes the RECOMMENDED values
|
||||
to assign to configurable parameters for Waku v2 clients.
|
||||
Since Waku v2 is built on [libp2p](https://github.com/libp2p/specs),
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 30/ADAPTIVE-NODES
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Adaptive nodes</td></tr>
|
||||
<tr><th>Slug</th><td>30</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Adaptive nodes |
|
||||
| Slug | 30 |
|
||||
| Status | draft |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
This is an informational spec that show cases the concept of adaptive nodes.
|
||||
|
||||
## Node types - a continuum
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 20/TOY-ETH-PM
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Toy Ethereum Private Message</td></tr>
|
||||
<tr><th>Slug</th><td>20</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Franck Royer <franck@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Toy Ethereum Private Message |
|
||||
| Slug | 20 |
|
||||
| Status | draft |
|
||||
| Editor | Franck Royer <franck@status.im> |
|
||||
|
||||
**Content Topics**:
|
||||
|
||||
- Public Key Broadcast: `/eth-pm/1/public-key/proto`
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 26/WAKU2-PAYLOAD
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Message Payload Encryption</td></tr>
|
||||
<tr><th>Slug</th><td>26</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thoren <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Oskar Thoren <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Message Payload Encryption |
|
||||
| Slug | 26 |
|
||||
| Status | draft |
|
||||
| Editor | Oskar Thoren <oskarth@titanproxy.com> |
|
||||
| Contributors | Oskar Thoren <oskarth@titanproxy.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how Waku provides confidentiality, authenticity, and
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 53/WAKU2-X3DH
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>X3DH usage for Waku payload encryption</td></tr>
|
||||
<tr><th>Slug</th><td>53</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Piana <andreap@status.im><br>Pedro Pombeiro <pedro@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Dean Eigenmann <dean@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | X3DH usage for Waku payload encryption |
|
||||
| Slug | 53 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Andrea Piana <andreap@status.im>, Pedro Pombeiro <pedro@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Dean Eigenmann <dean@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document describes a method that can be used to provide a secure channel
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 54/WAKU2-X3DH-SESSIONS
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Session management for Waku X3DH</td></tr>
|
||||
<tr><th>Slug</th><td>54</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Aaryamann Challani <p1ge0nh8er@proton.me></td></tr>
|
||||
<tr><th>Contributors</th><td>Andrea Piana <andreap@status.im><br>Pedro Pombeiro <pedro@status.im><br>Corey Petty <corey@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Dean Eigenmann <dean@status.im><br>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Session management for Waku X3DH |
|
||||
| Slug | 54 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Aaryamann Challani <p1ge0nh8er@proton.me> |
|
||||
| Contributors | Andrea Piana <andreap@status.im>, Pedro Pombeiro <pedro@status.im>, Corey Petty <corey@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Dean Eigenmann <dean@status.im>, Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document specifies how to manage sessions based on an X3DH key exchange.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 10/WAKU2
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2</td></tr>
|
||||
<tr><th>Slug</th><td>10</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Sanaz Taheri <sanaz@status.im><br>Hanno Cornelius <hanno@status.im><br>Reeshav Khan <reeshav@status.im><br>Daniel Kaiser <danielkaiser@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 |
|
||||
| Slug | 10 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Sanaz Taheri <sanaz@status.im>, Hanno Cornelius <hanno@status.im>, Reeshav Khan <reeshav@status.im>, Daniel Kaiser <danielkaiser@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
<!-- timeline:start -->
|
||||
|
||||
## Timeline
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 11/WAKU2-RELAY
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Relay</td></tr>
|
||||
<tr><th>Slug</th><td>11</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Oskar Thorén <oskarth@titanproxy.com><br>Sanaz Taheri <sanaz@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Relay |
|
||||
| Slug | 11 |
|
||||
| Status | stable |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Oskar Thorén <oskarth@titanproxy.com>, Sanaz Taheri <sanaz@status.im> |
|
||||
|
||||
`11/WAKU2-RELAY` specifies a [Publish/Subscribe approach](https://docs.libp2p.io/concepts/publish-subscribe/)
|
||||
to peer-to-peer messaging with a strong focus on privacy,
|
||||
censorship-resistance, security and scalability.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 12/WAKU2-FILTER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Filter</td></tr>
|
||||
<tr><th>Slug</th><td>12</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskar@status.im><br>Sanaz Taheri <sanaz@status.im><br>Ebube Ud <ebube@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Filter |
|
||||
| Slug | 12 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskar@status.im>, Sanaz Taheri <sanaz@status.im>, Ebube Ud <ebube@status.im> |
|
||||
|
||||
previous versions: [00](/waku/standards/core/12/previous-versions/00/filter.md)
|
||||
|
||||
**Protocol identifiers**:
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 12/WAKU2-FILTER
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Filter</td></tr>
|
||||
<tr><th>Slug</th><td>12</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Sanaz Taheri <sanaz@status.im><br>Ebube Ud <ebube@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Filter |
|
||||
| Slug | 12 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Sanaz Taheri <sanaz@status.im>, Ebube Ud <ebube@status.im> |
|
||||
|
||||
`WakuFilter` is a protocol that enables subscribing to messages that a peer receives.
|
||||
This is a more lightweight version of `WakuRelay`
|
||||
specifically designed for bandwidth restricted devices.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 13/WAKU2-STORE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Store</td></tr>
|
||||
<tr><th>Slug</th><td>13</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Simon-Pierre Vivier <simvivier@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Aaryamann Challani <p1ge0nh8er@proton.me><br>Sanaz Taheri <sanaz@status.im><br>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Store |
|
||||
| Slug | 13 |
|
||||
| Status | draft |
|
||||
| Editor | Simon-Pierre Vivier <simvivier@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Aaryamann Challani <p1ge0nh8er@proton.me>, Sanaz Taheri <sanaz@status.im>, Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification explains the `13/WAKU2-STORE` protocol
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 13/WAKU2-STORE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Store Query</td></tr>
|
||||
<tr><th>Slug</th><td>13</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com><br>Aaryamann Challani <p1ge0nh8er@proton.me><br>Sanaz Taheri <sanaz@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Store Query |
|
||||
| Slug | 13 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com>, Aaryamann Challani <p1ge0nh8er@proton.me>, Sanaz Taheri <sanaz@status.im> |
|
||||
|
||||
Previous version: [00](/waku/standards/core/13/previous-versions/00/store.md)
|
||||
|
||||
## Abstract
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 14/WAKU2-MESSAGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Message</td></tr>
|
||||
<tr><th>Slug</th><td>14</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Sanaz Taheri <sanaz@status.im><br>Aaryamann Challani <p1ge0nh8er@proton.me><br>Lorenzo Delgado <lorenzo@status.im><br>Abhimanyu Rawat <abhi@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Message |
|
||||
| Slug | 14 |
|
||||
| Status | stable |
|
||||
| Category | Standards Track |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Sanaz Taheri <sanaz@status.im>, Aaryamann Challani <p1ge0nh8er@proton.me>, Lorenzo Delgado <lorenzo@status.im>, Abhimanyu Rawat <abhi@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
[10/WAKU2](/waku/standards/core/10/waku2.md) is a family of modular peer-to-peer protocols
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 15/WAKU-BRIDGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Bridge</td></tr>
|
||||
<tr><th>Slug</th><td>15</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Bridge |
|
||||
| Slug | 15 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes how [6/WAKU1](/waku/standards/legacy/6/waku1.md)
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 17/WAKU2-RLN-RELAY
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 RLN Relay</td></tr>
|
||||
<tr><th>Slug</th><td>17</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Alvaro Revuelta <alvaro@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Oskar Thorén <oskarth@titanproxy.com><br>Aaryamann Challani <p1ge0nh8er@proton.me><br>Sanaz Taheri <sanaz@status.im><br>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 RLN Relay |
|
||||
| Slug | 17 |
|
||||
| Status | draft |
|
||||
| Editor | Alvaro Revuelta <alvaro@status.im> |
|
||||
| Contributors | Oskar Thorén <oskarth@titanproxy.com>, Aaryamann Challani <p1ge0nh8er@proton.me>, Sanaz Taheri <sanaz@status.im>, Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes the `17/WAKU2-RLN-RELAY` protocol,
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 19/WAKU2-LIGHTPUSH
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Light Push</td></tr>
|
||||
<tr><th>Slug</th><td>19</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Daniel Kaiser <danielkaiser@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Light Push |
|
||||
| Slug | 19 |
|
||||
| Status | draft |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Daniel Kaiser <danielkaiser@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
**Protocol identifier**: `/vac/waku/lightpush/2.0.0-beta1`
|
||||
|
||||
## Motivation and Goals
|
||||
|
||||
@@ -1,13 +1,12 @@
|
||||
# 31/WAKU2-ENR
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 usage of ENR</td></tr>
|
||||
<tr><th>Slug</th><td>31</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Franck Royer <franck@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 usage of ENR |
|
||||
| Slug | 31 |
|
||||
| Status | draft |
|
||||
| Editor | Franck Royer <franck@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes the usage of the ENR (Ethereum Node Records)
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 33/WAKU2-DISCV5
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Discv5 Ambient Peer Discovery</td></tr>
|
||||
<tr><th>Slug</th><td>33</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Discv5 Ambient Peer Discovery |
|
||||
| Slug | 33 |
|
||||
| Status | draft |
|
||||
| Editor | Daniel Kaiser <danielkaiser@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
`33/WAKU2-DISCV5` specifies a modified version of
|
||||
|
||||
@@ -1,15 +1,14 @@
|
||||
# 34/WAKU2-PEER-EXCHANGE
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku2 Peer Exchange</td></tr>
|
||||
<tr><th>Slug</th><td>34</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Standards Track</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Daniel Kaiser <danielkaiser@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku2 Peer Exchange |
|
||||
| Slug | 34 |
|
||||
| Status | draft |
|
||||
| Category | Standards Track |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
| Contributors | Daniel Kaiser <danielkaiser@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This document specifies a simple request-response peer exchange protocol.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 36/WAKU2-BINDINGS-API
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 C Bindings API</td></tr>
|
||||
<tr><th>Slug</th><td>36</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Richard Ramos <richard@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Franck Royer <franck@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 C Bindings API |
|
||||
| Slug | 36 |
|
||||
| Status | draft |
|
||||
| Editor | Richard Ramos <richard@status.im> |
|
||||
| Contributors | Franck Royer <franck@status.im> |
|
||||
|
||||
## Introduction
|
||||
|
||||
Native applications that wish to integrate Waku may not be able to use nwaku and
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 64/WAKU2-NETWORK
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v2 Network</td></tr>
|
||||
<tr><th>Slug</th><td>64</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Category</th><td>Best Current Practice</td></tr>
|
||||
<tr><th>Editor</th><td>Hanno Cornelius <hanno@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v2 Network |
|
||||
| Slug | 64 |
|
||||
| Status | draft |
|
||||
| Category | Best Current Practice |
|
||||
| Editor | Hanno Cornelius <hanno@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes an opinionated deployment of [10/WAKU2](../10/waku2.md)
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 66/WAKU2-METADATA
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Metadata Protocol</td></tr>
|
||||
<tr><th>Slug</th><td>66</td></tr>
|
||||
<tr><th>Status</th><td>draft</td></tr>
|
||||
<tr><th>Editor</th><td>Franck Royer <franck@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Filip Dimitrijevic <filip@status.im><br>Alvaro Revuelta <alrevuelta@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Metadata Protocol |
|
||||
| Slug | 66 |
|
||||
| Status | draft |
|
||||
| Editor | Franck Royer <franck@status.im> |
|
||||
| Contributors | Filip Dimitrijevic <filip@status.im>, Alvaro Revuelta <alrevuelta@status.im> |
|
||||
|
||||
## Abstract
|
||||
|
||||
This specification describes the metadata
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 6/WAKU1
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku v1</td></tr>
|
||||
<tr><th>Slug</th><td>6</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Andrea Maria Piana <andreap@status.im><br>Dean Eigenmann <dean@status.im><br>Kim De Mey <kimdemey@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku v1 |
|
||||
| Slug | 6 |
|
||||
| Status | stable |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Dean Eigenmann <dean@status.im>, Kim De Mey <kimdemey@status.im> |
|
||||
|
||||
This specification describes the format of Waku packets within the ÐΞVp2p Wire Protocol.
|
||||
This spec substitutes [EIP-627](https://eips.ethereum.org/EIPS/eip-627).
|
||||
Waku is a fork of the original Whisper protocol
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 7/WAKU-DATA
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Envelope data field</td></tr>
|
||||
<tr><th>Slug</th><td>7</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Kim De Mey <kimdemey@status.im></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Envelope data field |
|
||||
| Slug | 7 |
|
||||
| Status | stable |
|
||||
| Editor | Oskar Thorén <oskarth@titanproxy.com> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Kim De Mey <kimdemey@status.im> |
|
||||
|
||||
This specification describes the encryption,
|
||||
decryption and signing of the content in the [data field used in Waku](../6/waku1.md/#abnf-specification).
|
||||
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 8/WAKU-MAIL
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku Mailserver</td></tr>
|
||||
<tr><th>Slug</th><td>8</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Andrea Maria Piana <andreap@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Adam Babik <adam@status.im><br>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku Mailserver |
|
||||
| Slug | 8 |
|
||||
| Status | stable |
|
||||
| Editor | Andrea Maria Piana <andreap@status.im> |
|
||||
| Contributors | Adam Babik <adam@status.im>, Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
## Abstract
|
||||
|
||||
In this specification, we describe Mailservers.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
# 9/WAKU-RPC
|
||||
|
||||
<div class="rfc-meta">
|
||||
<table>
|
||||
<tr><th>Name</th><td>Waku RPC API</td></tr>
|
||||
<tr><th>Slug</th><td>9</td></tr>
|
||||
<tr><th>Status</th><td>stable</td></tr>
|
||||
<tr><th>Editor</th><td>Andrea Maria Piana <andreap@status.im></td></tr>
|
||||
<tr><th>Contributors</th><td>Dean Eigenmann <dean@status.im><br>Oskar Thorén <oskarth@titanproxy.com></td></tr>
|
||||
</table>
|
||||
</div>
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Name | Waku RPC API |
|
||||
| Slug | 9 |
|
||||
| Status | stable |
|
||||
| Editor | Andrea Maria Piana <andreap@status.im> |
|
||||
| Contributors | Dean Eigenmann <dean@status.im>, Oskar Thorén <oskarth@titanproxy.com> |
|
||||
|
||||
This specification describes the RPC API that Waku nodes MAY adhere to.
|
||||
The unified API allows clients to easily
|
||||
be able to connect to any node implementation.
|
||||
|
||||
@@ -21,38 +21,27 @@ EXCLUDE_FILES = {"README.md", "SUMMARY.md"}
|
||||
EXCLUDE_PARTS = {"previous-versions"}
|
||||
|
||||
|
||||
def parse_meta_from_html(text: str) -> Optional[Dict[str, str]]:
|
||||
if '<div class="rfc-meta">' not in text:
|
||||
return None
|
||||
|
||||
def parse_meta_from_markdown_table(text: str) -> Optional[Dict[str, str]]:
|
||||
lines = text.splitlines()
|
||||
meta: Dict[str, str] = {}
|
||||
for match in re.findall(r"<tr><th>([^<]+)</th><td>(.*?)</td></tr>", text, flags=re.DOTALL):
|
||||
key = match[0].strip().lower()
|
||||
value = match[1].replace("<br>", "\n").strip()
|
||||
value = html.unescape(value)
|
||||
meta[key] = value
|
||||
|
||||
return meta or None
|
||||
|
||||
|
||||
def parse_front_matter(text: str) -> Optional[Dict[str, str]]:
|
||||
if not text.startswith("---"):
|
||||
return None
|
||||
|
||||
end = text.find("\n---", 3)
|
||||
if end == -1:
|
||||
return None
|
||||
|
||||
front = text[3:end].strip().splitlines()
|
||||
meta: Dict[str, str] = {}
|
||||
for line in front:
|
||||
if ":" not in line:
|
||||
for i in range(len(lines) - 2):
|
||||
line = lines[i].strip()
|
||||
next_line = lines[i + 1].strip()
|
||||
if not (line.startswith('|') and next_line.startswith('|') and '---' in next_line):
|
||||
continue
|
||||
key, value = line.split(":", 1)
|
||||
key = key.strip().lower()
|
||||
value = value.strip().strip('"').strip("'")
|
||||
if key and value:
|
||||
meta[key] = value
|
||||
|
||||
# Simple two-column table parsing
|
||||
j = i + 2
|
||||
while j < len(lines) and lines[j].strip().startswith('|'):
|
||||
parts = [p.strip() for p in lines[j].strip().strip('|').split('|')]
|
||||
if len(parts) >= 2:
|
||||
key = parts[0].lower()
|
||||
value = html.unescape(parts[1])
|
||||
if key and value:
|
||||
meta[key] = value
|
||||
j += 1
|
||||
break
|
||||
|
||||
return meta or None
|
||||
|
||||
|
||||
@@ -75,9 +64,7 @@ def collect() -> List[Dict[str, str]]:
|
||||
|
||||
text = path.read_text(encoding="utf-8", errors="ignore")
|
||||
|
||||
meta = parse_front_matter(text)
|
||||
if meta is None:
|
||||
meta = parse_meta_from_html(text) or {}
|
||||
meta = parse_meta_from_markdown_table(text) or {}
|
||||
|
||||
slug = meta.get("slug")
|
||||
title = meta.get("title") or meta.get("name") or parse_title_from_h1(text) or rel.stem
|
||||
|
||||
@@ -1,4 +1,93 @@
|
||||
(() => {
|
||||
function linkMenuTitle() {
|
||||
const menuTitle = document.querySelector(".menu-title");
|
||||
if (!menuTitle || menuTitle.dataset.linked === "true") {
|
||||
return;
|
||||
}
|
||||
|
||||
const existingLink = menuTitle.closest("a");
|
||||
if (existingLink) {
|
||||
menuTitle.dataset.linked = "true";
|
||||
return;
|
||||
}
|
||||
|
||||
const root = (typeof path_to_root !== "undefined" && path_to_root) ? path_to_root : "";
|
||||
const link = document.createElement("a");
|
||||
link.href = `${root}index.html`;
|
||||
link.className = "menu-title-link";
|
||||
link.setAttribute("aria-label", "Back to home");
|
||||
|
||||
const parent = menuTitle.parentNode;
|
||||
parent.replaceChild(link, menuTitle);
|
||||
link.appendChild(menuTitle);
|
||||
menuTitle.dataset.linked = "true";
|
||||
}
|
||||
|
||||
document.addEventListener("DOMContentLoaded", linkMenuTitle);
|
||||
|
||||
document.addEventListener("DOMContentLoaded", () => {
|
||||
const printLink = document.querySelector("a[href$='print.html']");
|
||||
if (!printLink) return;
|
||||
printLink.addEventListener("click", (event) => {
|
||||
event.preventDefault();
|
||||
window.print();
|
||||
});
|
||||
});
|
||||
|
||||
function initSidebarCollapsible(root) {
|
||||
if (!root) return;
|
||||
const items = root.querySelectorAll("li.chapter-item");
|
||||
items.forEach((item) => {
|
||||
const section = item.querySelector(":scope > ol.section");
|
||||
const link = item.querySelector(":scope > .chapter-link-wrapper > a");
|
||||
if (!section || !link) return;
|
||||
|
||||
if (!link.querySelector(".section-toggle")) {
|
||||
const toggle = document.createElement("span");
|
||||
toggle.className = "section-toggle";
|
||||
toggle.setAttribute("role", "button");
|
||||
toggle.setAttribute("aria-label", "Toggle section");
|
||||
toggle.addEventListener("click", (event) => {
|
||||
event.preventDefault();
|
||||
event.stopPropagation();
|
||||
item.classList.toggle("collapsed");
|
||||
});
|
||||
link.prepend(toggle);
|
||||
}
|
||||
|
||||
const hasActive = item.querySelector(".active");
|
||||
if (!hasActive) {
|
||||
item.classList.add("collapsed");
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function bindSidebarCollapsible() {
|
||||
const sidebar = document.querySelector("#mdbook-sidebar .sidebar-scrollbox");
|
||||
if (sidebar) {
|
||||
initSidebarCollapsible(sidebar);
|
||||
}
|
||||
|
||||
const iframe = document.querySelector(".sidebar-iframe-outer");
|
||||
if (iframe) {
|
||||
const onLoad = () => {
|
||||
try {
|
||||
initSidebarCollapsible(iframe.contentDocument);
|
||||
} catch (e) {
|
||||
// ignore access errors
|
||||
}
|
||||
};
|
||||
iframe.addEventListener("load", onLoad);
|
||||
onLoad();
|
||||
}
|
||||
}
|
||||
|
||||
document.addEventListener("DOMContentLoaded", () => {
|
||||
bindSidebarCollapsible();
|
||||
// toc.js may inject the sidebar after load
|
||||
setTimeout(bindSidebarCollapsible, 100);
|
||||
});
|
||||
|
||||
const searchInput = document.getElementById("rfc-search");
|
||||
const resultsCount = document.getElementById("results-count");
|
||||
const tableContainer = document.getElementById("rfc-table-container");
|
||||
|
||||
Reference in New Issue
Block a user