Skip to content

Commit 18613c6

Browse files
committed
readme : add bootstrapping info
1 parent 4dad99d commit 18613c6

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

README.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,13 @@ WebPEER is a Decentralized P2P Network in the Browser. It allows developers to b
88

99
## Implementation
1010

11-
- [WebPEER.js](https://www.npmjs.com/package/webpeerjs) - JavaScript implementation of WebPEER Network designed as a minimal, essential API. It uses IPFS and the libp2p modular stack for the specific purpose of propagating messages over the network via direct WebRTC connections between browsers. As a result, these messages can arrive asynchronously depending on how many iterations they have gone through.
11+
- [WebPEER.js](https://www.npmjs.com/package/webpeerjs)
12+
13+
JavaScript implementation of WebPEER Network designed as a minimal, essential API. It uses IPFS and the libp2p modular stack for the specific purpose of propagating messages over the network via direct WebRTC connections between browsers. As a result, these messages can arrive asynchronously depending on how many iterations they have gone through.
14+
15+
## Bootstrapping
16+
17+
When a new peer is created, it doesn't know the addresses of existing peers on the network. While manually entering peer addresses is possible, it's impractical. Another strategy is to use federated media, leveraging public protocols like [Torrent](https://github.com/nuzulul/signalingserver.js) to facilitate address exchange. Once the peer addresses are obtained, the peer can establish a direct browser-to-browser connection to the WebPEER Network.
1218

1319
## Security
1420

0 commit comments

Comments
 (0)