From bbc897c352161b8909a6f099e727904e6b1b9516 Mon Sep 17 00:00:00 2001 From: oskarth Date: Thu, 6 Oct 2022 18:50:42 +0000 Subject: [PATCH] deploy: 44d8a2026dc31a37e181043ceb67e2822376dc03 --- docs/tutorial/rln-chat-cross-client.md | 31 +++++++++++++++++++ .../vendor/libbacktrace-upstream/libtool | 2 +- 2 files changed, 32 insertions(+), 1 deletion(-) create mode 100644 docs/tutorial/rln-chat-cross-client.md diff --git a/docs/tutorial/rln-chat-cross-client.md b/docs/tutorial/rln-chat-cross-client.md new file mode 100644 index 000000000..2bae8cea0 --- /dev/null +++ b/docs/tutorial/rln-chat-cross-client.md @@ -0,0 +1,31 @@ +# Waku-RLN-Relay Testnet2: Cross-Client + +In this tutorial, the aim is to test the interoperability of the 3 available Waku v2 clients namely, Nim, Go, and JS over the Waku network in the spam-protected mode. +Spam protection is done by rate limiting each message publisher. +At the time of this tutorial, the messaging rate is set to `1` per Epoch where Epoch duration is set to `10` seconds. +You will find more about the details of spam protection in the chat clients tutorial provided below. +Messaging rate/spam protection is enabled through [Waku-RLN-Relay protocol](https://rfc.vac.dev/spec/17/) that is mounted on the routing hops. +For ease of demonstration, we make use of Nim-chat, Go-chat, and JS-chat applications that are developed on top of their respective Waku v2 clients. +You will need to set up one instance of each chat client in spam-protected mode and then start messaging with them. +As for the setup, please follow the tutorials below: +- [Nim-chat](./onchain-rln-relay-chat2.md) +- [Go-chat](https://github.com/status-im/go-waku/blob/master/docs/tutorials/rln.md) +- [JS-chat](https://examples.waku.org/rln-js/) + +Once you set up your chat clients, they will all be connected to the Waku v2 test fleets as their first hop. +Messages generated by all the chat clients are set to be published on a specific combination of pubsub and content topic i.e., the default pubsub topic of `/waku/2/default-waku/proto` and the content topic of `/toy-chat/2/luzhou/proto`. +The test fleets also run Waku-RLN-Relay over the same pubsub topic and content topic. +Test fleets act as routers and enforce the message rate limit. +As such, any spam messages published by the chat clients on the said combination of topics will be caught by the Waku v2 test fleet nodes and will not be routed. +Note that spam protection does not rely on the presence of the test fleets. +In fact, all the chat clients (except js-chat as it is in progress) are also capable of catching and dropping spam messages if they receive any. +You can test it by connecting two chat clients (running Waku-RLN-Relay) directly to each other and see if they can spot each other's spam activities. + +Note: JS-chat will use the [WAKU2-LIGHTPUSH protocol](https://rfc.vac.dev/spec/19/) to push its messages to the Waku v2 test fleets. +Waku v2 test fleets will act according to the WAKU2-LIGHTPUSH specifications and push that message to the network without any further verification. +That is, they do not enforce spam protection in that specific protocol but rather act merely as a message publisher (this behavior may change in the future though). +As such, you can expect to receive spam messages published by the JS-chat clients from other connecting chat clients i.e., Go-chat and Nim-chat. +However, you will see that such messages will be immediately identified as spam on those clients and a proper message will be displayed on the console. + + +You can also find a recorded demo of this testnet in the following [video](https://drive.proton.me/urls/EC4G8SY2J8#ie92Wtje1f4O). \ No newline at end of file diff --git a/vendor/nim-libbacktrace/vendor/libbacktrace-upstream/libtool b/vendor/nim-libbacktrace/vendor/libbacktrace-upstream/libtool index d3463649f..36a983f13 100755 --- a/vendor/nim-libbacktrace/vendor/libbacktrace-upstream/libtool +++ b/vendor/nim-libbacktrace/vendor/libbacktrace-upstream/libtool @@ -2,7 +2,7 @@ # libtool - Provide generalized library-building support services. # Generated automatically by config.status (libbacktrace) version-unused -# Libtool was configured on host fv-az421-801: +# Libtool was configured on host fv-az348-255: # NOTE: Changes made to this file will be lost: look at ltmain.sh. # # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2003, 2004, 2005,