diff --git a/rfc/0004_ws2p_v1.md b/rfc/0004_ws2p_v1.md
index 6a0244c1912cfa646df3bdcd412f14c463f62434..57cf3eaf9c25c50aa7287862a0dc96f58ef6bfed 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._