diff --git a/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (1).png b/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (1).png new file mode 100644 index 0000000..094e274 Binary files /dev/null and b/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (1).png differ diff --git a/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (2).png b/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (2).png new file mode 100644 index 0000000..094e274 Binary files /dev/null and b/.gitbook/assets/air_fold_4 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (1) (2).png differ diff --git a/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (1).png b/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (1).png new file mode 100644 index 0000000..9c3bb75 Binary files /dev/null and b/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (1).png differ diff --git a/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (2).png b/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (2).png new file mode 100644 index 0000000..9c3bb75 Binary files /dev/null and b/.gitbook/assets/air_null_6 (1) (2) (2) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (3) (1) (1) (2).png differ diff --git a/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (1).png b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (1).png new file mode 100644 index 0000000..a3364b2 Binary files /dev/null and b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (1).png differ diff --git a/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (2).png b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (2).png new file mode 100644 index 0000000..a3364b2 Binary files /dev/null and b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (2).png differ diff --git a/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (3).png b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (3).png new file mode 100644 index 0000000..a3364b2 Binary files /dev/null and b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (3).png differ diff --git a/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (4).png b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (4).png new file mode 100644 index 0000000..a3364b2 Binary files /dev/null and b/.gitbook/assets/air_sequential_2 (1) (1) (1) (1) (1) (2) (3) (4) (4) (4) (1) (4).png differ diff --git a/.gitbook/assets/image (18) (1) (1) (2) (2) (1) (1).png b/.gitbook/assets/image (18) (1) (1) (2) (2) (1) (1).png new file mode 100644 index 0000000..971b427 Binary files /dev/null and b/.gitbook/assets/image (18) (1) (1) (2) (2) (1) (1).png differ diff --git a/.gitbook/assets/image (38) (1) (1).png b/.gitbook/assets/image (38) (1) (1).png new file mode 100644 index 0000000..7f714d6 Binary files /dev/null and b/.gitbook/assets/image (38) (1) (1).png differ diff --git a/README.md b/README.md index 362d98c..6aaf24d 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Fluence provides an open Web3 protocol, framework and tooling to develop and hos The Fluence Web3 stack enables -* programmable network requests +* programmable network requests * distributed applications from composition without centralization * communication, access and transactional security as first class citizens * extensibility through adapter/wrapper services @@ -16,11 +16,11 @@ An integral component of the Fluence solution is the Aquamarine stack comprised Additional resources and support are available: -* [Youtube](https://www.youtube.com/channel/UC3b5eFyKRFlEMwSJ1BTjpbw) * [Github](https://github.com/fluencelabs) * [Discord](https://fluence.chat) * [Telegram](https://t.me/fluence\_project) * [Twitter](https://twitter.com/fluence\_project) +* [Youtube](https://www.youtube.com/channel/UC3b5eFyKRFlEMwSJ1BTjpbw) Documentation is work in progress and your feedback is extremely valuable and much appreciated. If you have suggestions or unearth errors or inaccuracies, please open an Issue or push a PR. diff --git a/quick-start/1.-browser-to-browser-1.md b/quick-start/1.-browser-to-browser-1.md index 93a7234..83553ab 100644 --- a/quick-start/1.-browser-to-browser-1.md +++ b/quick-start/1.-browser-to-browser-1.md @@ -20,14 +20,11 @@ Which opens a new tab in your browser at `http://localhost:3000`. The browser ta ![Relay Selection](<../.gitbook/assets/image (17).png>) - - The client peer is now connected to the relay and ready for business: ![Connection confirmation to network](<../.gitbook/assets/image (18).png>) -Let's follow the instructions, open another browser tab, i.e. client peer, using `http://localhost:3000` , select any one of the relays and copying the ensuing peer id and relay peer id to the first client peer, i.e. the first browser tab, and click the `say hello` button:\ - +Let's follow the instructions, open another browser tab, i.e. client peer, using `http://localhost:3000` , select any one of the relays and copying the ensuing peer id and relay peer id to the first client peer, i.e. the first browser tab, and click the `say hello` button:\\ ![Peer-to-peer communication between two browser client peers](<../.gitbook/assets/image (20).png>) @@ -57,6 +54,6 @@ The local (browser) service `HelloPeer` is also implemented in the `App.tsx` fil ![Local HelloPeer service implementation](<../.gitbook/assets/image (22).png>) -To summarize, we run an app that facilities messaging between two browsers over a peer-to-peer network. At the core of this capability is Aqua which allowed us in just a few lines of code to program both the network topology and the application workflow in barely more than a handful of lines of code. Hint: You should be excited. For more information on Aqua, see the [Aqua Book](https://app.gitbook.com/@fluence/s/aqua-book/). +To summarize, we run an app that facilities messaging between two browsers over a peer-to-peer network. At the core of this capability is Aqua which allowed us in just a few lines of code to program both the network topology and the application workflow in barely more than a handful of lines of code. Hint: You should be excited. For more information on Aqua, see the [Aqua Book](https://app.gitbook.com/o/-MWEY2QOTLOVcnoRm9S-/s/-MbmEhQUL-bljop\_DzuP/). In the next section, we develop a WebAssembly module and deploy it as a hosted service to the Fluence peer-to-peer network.