diff --git a/rfc/0004_ws2p_v1.md b/rfc/0004_ws2p_v1.md index 57bf1ebe04cc57aa7aca7a8211de47532429788e..8e4995aae0d2bb000d7860ba9f75854dab2d0945 100644 --- a/rfc/0004_ws2p_v1.md +++ b/rfc/0004_ws2p_v1.md @@ -52,9 +52,11 @@ 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 first endpoints of other nodes are obtained during the synchronization step. +The endpoints of other nodes are obtained during the synchronization step. Currently, the synchronization process is fully managed by the BMA module, -but this synchronization process adds peer cards of the network nodes known by the node on which the user has chosen to synchronize to Duniter-ts's database. +this synchronization process adds peer cards* of others nodes to Duniter-ts's database. + +_*peer card : Signed document declaring all the access points of a peer._ When duniter-ts starts up, the WS2P module accesses the peer cards stored in duniter-ts's database following synchronization.