From 2e39bf8b9268d1ce8ea94d508316888dd5fb1b9f Mon Sep 17 00:00:00 2001
From: librelois <elois@ifee.fr>
Date: Tue, 30 Jan 2018 14:56:05 +0100
Subject: [PATCH] [fix] ws2p v1 does not handle sync
---
rfc/0004_ws2p_v1.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/rfc/0004_ws2p_v1.md b/rfc/0004_ws2p_v1.md
index 6a0244c..57cf3ea 100644
--- a/rfc/0004_ws2p_v1.md
+++ b/rfc/0004_ws2p_v1.md
@@ -52,9 +52,8 @@ Any WS2P endpoint must match this regexp : `/^WS2P (?:[1-9][0-9]* )?([a-f0-9]{8}
### Getting endpoints from other Duniter nodes
Initially, Duniter is totally endpoint agnostic and don't know any node.
-The endpoints of other nodes are obtained during the synchronization step.
-Currently, the synchronization process is fully managed by the BMA module,
-this synchronization process adds peer cards* of others nodes to Duniter-ts's database.
+The ws2p module requires that at least one or more peer cards are already stored in the database when launching the node,
+it's up to the Duniter sync command to handle this (ws2p does not handle this).
_*peer card : Signed document declaring all the access points of a peer._
--
GitLab