updated module path

removed cflag import for test
updated module path.. again
2024-05-31 15:19:34 +02:00 · 2024-05-31 15:14:54 +02:00 · 2024-05-31 15:07:16 +02:00 · 2024-05-31 14:54:14 +02:00 · 2024-05-31 14:49:29 +02:00 · 2024-05-31 14:43:13 +02:00
143 changed files with 946 additions and 957 deletions
@@ -102,6 +102,18 @@ jobs:
            nym-wallet/target/release/bundle/dmg/*.dmg
            nym-wallet/target/release/bundle/macos/*.app.tar.gz*

+      - name: Deploy artifacts to CI www
+        continue-on-error: true
+        uses: easingthemes/ssh-deploy@main
+        env:
+          SSH_PRIVATE_KEY: ${{ secrets.CI_WWW_SSH_PRIVATE_KEY }}
+          ARGS: "-avzr"
+          SOURCE: "nym-wallet/target/release/bundle/macos/nym-wallet.app.tar.gz"
+          REMOTE_HOST: ${{ secrets.CI_WWW_REMOTE_HOST }}
+          REMOTE_USER: ${{ secrets.CI_WWW_REMOTE_USER }}
+          TARGET: ${{ secrets.CI_WWW_REMOTE_TARGET }}/builds/${{ github.ref_name }}/nym-wallet
+          EXCLUDE: "/dist/, /node_modules/"            
+
  push-release-data:
    if: ${{ (startsWith(github.ref, 'refs/tags/nym-wallet-') && github.event_name == 'release') || github.event_name == 'workflow_dispatch' }}
    uses: ./.github/workflows/release-calculate-hash.yml
@@ -77,6 +77,18 @@ jobs:
            nym-wallet/target/release/bundle/appimage/*.AppImage
            nym-wallet/target/release/bundle/appimage/*.AppImage.tar.gz*

+      - name: Deploy artifacts to CI www
+        continue-on-error: true
+        uses: easingthemes/ssh-deploy@main
+        env:
+          SSH_PRIVATE_KEY: ${{ secrets.CI_WWW_SSH_PRIVATE_KEY }}
+          ARGS: "-avzr"
+          SOURCE: "nym-wallet/target/release/bundle/appimage/nym-wallet*.AppImage.tar.gz"
+          REMOTE_HOST: ${{ secrets.CI_WWW_REMOTE_HOST }}
+          REMOTE_USER: ${{ secrets.CI_WWW_REMOTE_USER }}
+          TARGET: ${{ secrets.CI_WWW_REMOTE_TARGET }}/builds/${{ github.ref_name }}/nym-wallet
+          EXCLUDE: "/dist/, /node_modules/"               
+
  push-release-data:
    if: ${{ (startsWith(github.ref, 'refs/tags/nym-wallet-') && github.event_name == 'release') || github.event_name == 'workflow_dispatch' }}
    uses: ./.github/workflows/release-calculate-hash.yml
@@ -97,6 +97,18 @@ jobs:
            nym-wallet/target/release/bundle/msi/*.msi
            nym-wallet/target/release/bundle/msi/*.msi.zip*

+      - name: Deploy artifacts to CI www
+        continue-on-error: true
+        uses: easingthemes/ssh-deploy@main
+        env:
+          SSH_PRIVATE_KEY: ${{ secrets.CI_WWW_SSH_PRIVATE_KEY }}
+          ARGS: "-avzr"
+          SOURCE: "nym-wallet/target/release/bundle/msi/nym-wallet_1.*.msi"
+          REMOTE_HOST: ${{ secrets.CI_WWW_REMOTE_HOST }}
+          REMOTE_USER: ${{ secrets.CI_WWW_REMOTE_USER }}
+          TARGET: ${{ secrets.CI_WWW_REMOTE_TARGET }}/builds/${{ github.ref_name }}/nym-wallet
+          EXCLUDE: "/dist/, /node_modules/"            
+
  push-release-data:
    if: ${{ (startsWith(github.ref, 'refs/tags/nym-wallet-') && github.event_name == 'release') || github.event_name == 'workflow_dispatch' }}
    uses: ./.github/workflows/release-calculate-hash.yml
@@ -4,6 +4,16 @@ Post 1.0.0 release, the changelog format is based on [Keep a Changelog](https://

 ## [Unreleased]

+## [2024.4-nutella] (2024-05-08)
+
+- [fix] apply disable_poisson_rate from internal NR/IPR cfgs ([#4579])
+- updating sign commands to include nym-node ([#4578])
+- changed nym-node redirects from 308 'Permanent Redirect' to 303: 'See Other' ([#4572])
+
+[#4579]: https://github.com/nymtech/nym/pull/4579
+[#4578]: https://github.com/nymtech/nym/pull/4578
+[#4572]: https://github.com/nymtech/nym/pull/4572
+
 ## [2024.3-eclipse] (2024-04-22)

 - Initial release of the first iteration of the Nym Node
@@ -5684,7 +5684,7 @@ dependencies = [

 [[package]]
 name = "nym-gateway"
-version = "1.1.35"
+version = "1.1.36"
 dependencies = [
 "anyhow",
 "async-trait",
@@ -6098,7 +6098,7 @@ dependencies = [

 [[package]]
 name = "nym-network-requester"
-version = "1.1.34"
+version = "1.1.35"
 dependencies = [
 "addr",
 "anyhow",
@@ -6167,7 +6167,7 @@ dependencies = [

 [[package]]
 name = "nym-node"
-version = "1.1.0"
+version = "1.1.1"
 dependencies = [
 "anyhow",
 "bip39",
@@ -8,3 +8,12 @@ use thiserror::Error;
 pub struct ConfigUpgradeFailure {
    pub current_version: String,
 }
+
+#[derive(Error, Debug)]
+pub enum InvalidTrafficModeFailure {
+    #[error("attempted to set medium toggle traffic mode with fast mode flag")]
+    MediumToggleWithFastMode,
+
+    #[error("attempted to set medium toggle traffic mode with no cover flag")]
+    MediumToggleWithNoCover,
+}
@@ -56,6 +56,7 @@ const DEFAULT_MAXIMUM_REPLY_SURB_AGE: Duration = Duration::from_secs(12 * 60 * 6
 // 24 hours
 const DEFAULT_MAXIMUM_REPLY_KEY_AGE: Duration = Duration::from_secs(24 * 60 * 60);

+use crate::error::InvalidTrafficModeFailure;
 pub use nym_country_group::CountryGroup;

 #[derive(Debug, Clone, Deserialize, PartialEq, Serialize)]
@@ -127,6 +128,56 @@ impl Config {
        self
    }

+    // TODO: this should be refactored properly
+    // as of 12.09.23 the below is true (not sure how this comment will rot in the future)
+    // medium_toggle:
+    // - sets secondary packet size to 16kb
+    // - disables poisson distribution of the main traffic stream
+    // - sets the cover traffic stream to 1 packet / 5s (on average)
+    // - disables per hop delay
+    //
+    // fastmode (to be renamed to `fast-poisson`):
+    // - sets average per hop delay to 10ms
+    // - sets the cover traffic stream to 1 packet / 2000s (on average); for all intents and purposes it disables the stream
+    // - sets the poisson distribution of the main traffic stream to 4ms, i.e. 250 packets / s on average
+    //
+    // no_cover:
+    // - disables poisson distribution of the main traffic stream
+    // - disables the secondary cover traffic stream
+    #[doc(hidden)]
+    pub fn try_apply_traffic_modes(
+        &mut self,
+        disable_poisson_process: bool,
+        medium_toggle: bool,
+        fast_mode: bool,
+        no_cover: bool,
+    ) -> Result<(), InvalidTrafficModeFailure> {
+        if disable_poisson_process {
+            self.set_no_poisson_process()
+        }
+
+        if medium_toggle {
+            if fast_mode {
+                return Err(InvalidTrafficModeFailure::MediumToggleWithFastMode);
+            }
+            if no_cover {
+                return Err(InvalidTrafficModeFailure::MediumToggleWithNoCover);
+            }
+
+            self.set_experimental_medium_toggle();
+        }
+
+        if fast_mode {
+            self.set_high_default_traffic_volume()
+        }
+
+        if no_cover {
+            self.set_no_cover_traffic();
+        }
+
+        Ok(())
+    }
+
    pub fn set_high_default_traffic_volume(&mut self) {
        self.debug.traffic.average_packet_delay = Duration::from_millis(10);
        // basically don't really send cover messages
@@ -136,6 +187,15 @@ impl Config {
        self.debug.traffic.message_sending_average_delay = Duration::from_millis(4);
    }

+    /// Enable medium mixnet traffic, for experiments only.
+    /// This includes things like disabling cover traffic, no per hop delays, etc.
+    #[doc(hidden)]
+    pub fn set_experimental_medium_toggle(&mut self) {
+        self.set_no_cover_traffic_with_keepalive();
+        self.set_no_per_hop_delays();
+        self.debug.traffic.secondary_packet_size = Some(PacketSize::ExtendedPacket16);
+    }
+
    pub fn with_disabled_poisson_process(mut self, disabled: bool) -> Self {
        if disabled {
            self.set_no_poisson_process()
@@ -442,7 +442,7 @@ impl<C, St> GatewayClient<C, St> {
        }

        debug_assert!(self.connection.is_available());
-        log::trace!("Registering gateway");
+        log::debug!("Registering gateway");

        // it's fine to instantiate it here as it's only used once (during authentication or registration)
        // and putting it into the GatewayClient struct would be a hassle
@@ -494,6 +494,7 @@ impl<C, St> GatewayClient<C, St> {
        if !self.connection.is_established() {
            return Err(GatewayClientError::ConnectionNotEstablished);
        }
+        log::debug!("Authenticating with gateway");

        // it's fine to instantiate it here as it's only used once (during authentication or registration)
        // and putting it into the GatewayClient struct would be a hassle
@@ -529,6 +530,7 @@ impl<C, St> GatewayClient<C, St> {
                self.authenticated = status;
                self.bandwidth_remaining = bandwidth_remaining;
                self.negotiated_protocol = protocol_version;
+                log::debug!("authenticated: {status}, bandwidth remaining: {bandwidth_remaining}");
                Ok(())
            }
            ServerResponse::Error { message } => Err(GatewayClientError::GatewayError(message)),
@@ -541,10 +543,11 @@ impl<C, St> GatewayClient<C, St> {
        &mut self,
    ) -> Result<Arc<SharedKeys>, GatewayClientError> {
        if self.authenticated {
+            debug!("Already authenticated");
            return if let Some(shared_key) = &self.shared_key {
                Ok(Arc::clone(shared_key))
            } else {
-                Err(GatewayClientError::AuthenticationFailure)
+                Err(GatewayClientError::AuthenticationFailureWithPreexistingSharedKey)
            };
        }

@@ -71,6 +71,9 @@ pub enum GatewayClientError {
    #[error("Authentication failure")]
    AuthenticationFailure,

+    #[error("Authentication failure with preexisting shared key")]
+    AuthenticationFailureWithPreexistingSharedKey,
+
    #[error("Timed out")]
    Timeout,

@@ -159,7 +159,7 @@ impl TunDevice {
                "add",
                &format!("{}/{}", ipv6, netmaskv6),
                "dev",
-                &tun.name(),
+                (tun.name()),
            ])
            .output()?;
        Ok(tun)
@@ -50,7 +50,7 @@ pub struct DelegationWithEverything {
    pub accumulated_by_delegates: Option<DecCoin>,
    pub accumulated_by_operator: Option<DecCoin>,
    pub block_height: u64,
-    pub delegated_on_iso_datetime: String,
+    pub delegated_on_iso_datetime: Option<String>,
    pub cost_params: Option<MixNodeCostParams>,
    pub avg_uptime_percent: Option<u8>,

@@ -60,6 +60,8 @@ pub struct DelegationWithEverything {
    pub uses_vesting_contract_tokens: bool,
    pub unclaimed_rewards: Option<DecCoin>,

+    pub errors: Option<String>,
+
    // DEPRECATED, IF POSSIBLE TRY TO DISCONTINUE USE OF IT!
    pub pending_events: Vec<DelegationEvent>,
    pub mixnode_is_unbonding: Option<bool>,
@@ -1,93 +1,96 @@
+[//]: # (TODO change the URLs in the top handlebars)
 #
-# Summary
-
+# Start Here
 - [Introduction](introduction.md)

-# Infrastructure
+[//]: # (this is where you pull in some stuff from the infrastructure section as well as a general approach to how to start )
+- [Development Overview](dev-overview.md)

- [What is Nym?](infrastructure/nym.md)
- [Nym vs Other Systems](infrastructure/nym-vs-others.md)
- [Node Types](infrastructure/node-types.md)
+[//]: # (TODO see what you can take from here and put in the intro file )
+  [//]: # (# Infrastructure)
+  [//]: # ()
+  [//]: # (- [What is Nym?]&#40;infrastructure/nym.md&#41;)
+  [//]: # (- [Nym vs Other Systems]&#40;infrastructure/nym-vs-others.md&#41;)
+  [//]: # (- [Node Types]&#40;infrastructure/node-types.md&#41;)

-# Quickstart
+[//]: # (TODO change this to something like 'where to get started' and extensively rewrite)
+# Integrations
+- [Integration Options](integrations/integration-options.md)
+- [Payment Integration](integrations/payment-integration.md)

- [Overview](quickstart/overview.md)
- [Chat demo (webapp)](quickstart/chat-demo.md)
- [Coconut Credential Playground (webapp)](quickstart/cred-playground.md)
- [SOCKS Proxy (CLI)](quickstart/socks-proxy.md)
- [NymConnect Beta (GUI)](quickstart/nymconnect-gui.md)
+# SDKs
+- [Rust SDK](sdk/rust/rust.md)
+  - [Interacting with Clients - Read First!](sdk/rust/readfirst.md)
+  - [Message Types](sdk/rust/message-types.md)
+  - [Message Helpers](sdk/rust/message-helpers.md)
+  - [Troubleshooting](sdk/rust/troubleshooting.md)
+  - [Examples](sdk/rust/examples.md)
+      - [Simple Send](sdk/rust/examples/simple.md)
+      - [Create and Store Keys](sdk/rust/examples/keys.md)
+      - [Manual Storage](sdk/rust/examples/storage.md)
+      - [Anonymous Replies](sdk/rust/examples/surbs.md)
+      - [Use Custom Network Topology](sdk/rust/examples/custom-network.md)
+      - [Socks Proxy](sdk/rust/examples/socks.md)
+      - [Split Send and Receive](sdk/rust/examples/split-send.md)
+      - [Testnet Bandwidth Cred](sdk/rust/examples/credential.md)
+      - [Example Cargo file](sdk/rust/examples/cargo.md)
+- [Typescript SDK](sdk/typescript.md)

+# Clients
+- [Client Binaries](clients/client-binaries.md)
+  - [Building Nym](clients/building-nym.md)
+  - [Prebuilt Binaries](clients/pre-built-binaries.md)
+- [Clients Overview](clients/overview.md)
+- [Websocket Client](clients/websocket-client.md)
+  - [Setup & Run](clients/websocket/setup.md)
+  - [Configuration](clients/websocket/config.md)
+  - [Using Your Client](clients/websocket/usage.md)
+  - [Examples](clients/websocket/examples.md)
+  - [Command Documentation (Autogenerated)](clients/websocket/nym-client-commands.md)
+- [Socks5 Client](clients/socks5-client.md)
+  - [Setup Guide](clients/socks5/setup.md)
+  - [Command Documentation (Autogenerated)](clients/socks5/nym-socks5-client-commands)
+- [Webassembly Client](clients/webassembly-client.md)
+- [Addressing System](clients/addressing-system.md)
+
+# Nyx Blockchain
+- [Interacting with Nyx Chain and Smart Contracts](nyx/interacting-with-chain.md)
+- [Smart Contracts](nyx/smart-contracts.md)
+    - [Mixnet Contract](nyx/mixnet-contract.md)
+    - [Vesting Contract](nyx/vesting-contract.md)
+- [RPC Nodes](nyx/rpc-node.md)
+- [Ledger Live Support](nyx/ledger-live.md)
+
+# Tools
+- [NymCLI](tools/nym-cli.md)
+- [Command Documentation (Autogenerated)](tools/nym-cli-commands.md)
+   
 # User Manuals
-
 - [NymVPN alpha](nymvpn/intro.md)
    - [CLI](nymvpn/cli.md)

-<!-- OUTDATED STUFF:
- [NymConnect X Monero](tutorials/monero.md)
- [NymConnect X Matrix](tutorials/matrix.md)
- [NymConnect X Telegram](tutorials/telegram.md)
- [NymConnect X Electrum](tutorials/electrum.md)
- [NymConnect X Firo wallet](tutorials/firo.md)
-->
-
 # Code Examples
-
 - [Custom Service Providers](examples/custom-services.md)
 - [Apps Using Network Requesters](examples/using-nrs.md)
 - [Browser only](examples/browser-only.md)
 - [Monorepo examples](examples/monorepo-examples.md)

-# Integrations
-
- [Integration Options](integrations/integration-options.md)
-[//]: # (- [Mixnet Integration]&#40;integrations/mixnet-integration.md&#41;)
- [Payment Integration](integrations/payment-integration.md)
-
 # Tutorials
+- [Under Construction](tutorials/comingsoon.md)

- [Rust SDK](tutorials/rust-sdk.md)
-	- [Blockchain Service pt1](tutorials/cosmos-service/intro.md)
-		- [Tutorial Overview](tutorials/cosmos-service/overview.md)
-		- [Preparing Your Environment](tutorials/cosmos-service/preparing-env.md)
-		- [Preparing Your Lib](tutorials/cosmos-service/lib.md)
-		- [Preparing Your Client](tutorials/cosmos-service/client.md)
-		- [Preparing Your Client pt2](tutorials/cosmos-service/client-src.md)
-		- [Preparing Your Service](tutorials/cosmos-service/service.md)
-		- [Preparing Your Service pt2](tutorials/cosmos-service/service-src.md)
-		- [Querying the Chain](tutorials/cosmos-service/querying.md)
-
- [Typescript](tutorials/typescript.md)
-    - [Simple Service Provider](tutorials/simple-service-provider/simple-service-provider.md)
-      	- [Tutorial Overview](tutorials/simple-service-provider/overview.md)
-      	- [Preparing Your User Client Environment](tutorials/simple-service-provider/preparating-env.md)
-      	- [Building Your User Client](tutorials/simple-service-provider/user-client.md)
-      	- [Preparing Your Service Provider Environment](tutorials/simple-service-provider/preparating-env2.md)
-      	- [Building Your Service Provider](tutorials/simple-service-provider/service-provider.md)
-      	- [Sending a Message Through the Mixnet](tutorials/simple-service-provider/sending-message.md)
-
-[//]: # (TODO make generic )
-[//]: # (# Shipyard Builders Hackathon 2023 )
-[//]: # (- [General Info & Resources]&#40;shipyard/general.md&#41;)
-[//]: # (- [Hackathon Challenges]&#40;shipyard/challenges-overview.md&#41;)
-[//]: # (- [A Note on Infrastructure]&#40;shipyard/infra.md&#41;)
-[//]: # (- [Submission Guidelines]&#40;shipyard/guidelines.md&#41;)
-
-# Events
-
+# Previous Events
 - [Web3Privacy Now](./events/web3-privacy.md)
 - [HCPP23-serinko](./events/hcpp23-serinko.md)
 - [HCPP23-max](./events/hcpp23-max.md)

+[//]: # (Maybe we can get rid of these?)
 # FAQ
 - [General](faq/general-faq.md)
 - [Integrations](faq/integrations-faq.md)
 - [Rewards & Token](faq/rewards-faq.md)

 # Community Resources
-
- [Nym DevRel AMAs](community-resources/ama.md)
 - [Community Applications and Guides](community-resources/community-applications-and-guides.md)
- [Change Service Grantee Information](info-request.md)

 ---
 # Misc.
@@ -8,7 +8,7 @@ Nym has two main codebases:
 - the [Nym platform](https://github.com/nymtech/nym), written in Rust. This contains all of our code _except_ for the validators.
 - the [Nym validators](https://github.com/nymtech/nyxd), written in Go.

-> This page details how to build the main Nym platform code. **If you want to build and run a validator, [go here](../nodes/validator.md) instead.**
+> This page details how to build the main Nym platform code. **If you want to build and run a validator, [go here](https://nymtech.net/operators/nodes/validator.md) instead.**

 ## Prerequisites
 - Debian/Ubuntu: `pkg-config`, `build-essential`, `libssl-dev`, `curl`, `jq`, `git`
@@ -54,19 +54,18 @@ cargo build --release # build your binaries with **mainnet** configuration

 Quite a bit of stuff gets built. The key working parts are:

-* [mix node](../nodes/mixnode.md): `nym-mixnode`
-* [gateway node](../nodes/gateway.md): `nym-gateway`
+* [mix node](https://nymtech.net/operators/nodes/mixnode.md): `nym-mixnode`
+* [gateway node](https://nymtech.net/operators/nodes/gateway.md): `nym-gateway`
 * [websocket client](../clients/websocket-client.md): `nym-client`
 * [socks5 client](../clients/socks5-client.md): `nym-socks5-client`
-* [network requester](../nodes/network-requester.md): `nym-network-requester`
+* [network requester](https://nymtech.net/operators/nodes/network-requester.md): `nym-network-requester`
 * [nym-cli tool](../tools/nym-cli.md): `nym-cli`
 * [nym-api](https://nymtech.net/operators/nodes/nym-api.html): `nym-api`
+* [nymvisor](https://nymtech.net/operators/nodes/nymvisor-upgrade.html): `nymvisor`

-[//]: # (* [nymvisor]&#40;https://nymtech.net/operators/nodes/nymvisor-upgrade.html&#41;: `nymvisor`)
-
-The repository also contains Typescript applications which aren't built in this process. These can be built by following the instructions on their respective docs pages.
-* [Nym Wallet](../wallet/desktop-wallet.md)
-* [Nym Connect](https://nymtech.net/developers/quickstart/nymconnect-gui.html)
-* [Network Explorer UI](../explorers/mixnet-explorer.md)
+[//]: # (The repository also contains Typescript applications which aren't built in this process. These can be built by following the instructions on their respective docs pages.)
+[//]: # (* [Nym Wallet]&#40;../../../docs/src/wallet/desktop-wallet.md&#41;)
+[//]: # (* [Nym Connect]&#40;https://nymtech.net/developers/quickstart/nymconnect-gui.html&#41;)
+[//]: # (* [Network Explorer UI]&#40;../../../docs/src/explorers/mixnet-explorer.md&#41;)

 > You cannot build from GitHub's .zip or .tar.gz archive files on the releases page - the Nym build scripts automatically include the current git commit hash in the built binary during compilation, so the build will fail if you use the archive code (which isn't a Git repository). Check the code out from github using `git clone` instead.
@@ -0,0 +1,5 @@
+# Client Binaries
+
+The Nym codebase is written primarily in Rust. There are two methods to getting access to the different client and node binaries: 
+* [build them yourself](building-nym.md)
+* [download pre-compiled binaries from github](pre-built-binaries.md)
@@ -0,0 +1,66 @@
+# Socks5 Client
+
+> The Nym socks5 client was built in the [building nym](./building-nym.md) section. If you haven't yet built Nym and want to run the code on this page, go there first.
+
+## Current version
+```
+<!-- cmdrun ../../../../target/release/nym-socks5-client --version | grep "Build Version" | cut -b 21-26  -->
+```
+
+## What is this client for?
+Many existing applications are able to use either the SOCKS4, SOCKS4A, or SOCKS5 proxy protocols. If you want to send such an application's traffic through the mixnet, you can use the `nym-socks5-client` to bounce network traffic through the Nym network, like this:
+
+```
+                                                                              External Systems:
+                                                                                     +--------------------+
+                                                                             |------>| Monero blockchain  |
+                                                                             |       +--------------------+
+                                                                             |       +--------------------+
+                                                                             |------>|    Email server    |
+                                                                             |       +--------------------+
+                                                                             |       +--------------------+
+                                                                             |------>|    RPC endpoint    |
+                                                                             |       +--------------------+
+                                                                             |       +--------------------+
+                                                                             |------>|       Website      |
+                                                                             |       +--------------------+
+                                                                             |       +--------------------+
+  +----------------------------------+                                       |------>|       etc...       |
+  | Mixnet:                          |                                       |       +--------------------+
+  |       * Gateway your client is   |                                       |
+  |       connected to               |          +--------------------+       |
+  |       * Mix nodes 1 -> 3         |<-------->| Network requester  |<------+
+  |       * Gateway that network     |          +--------------------+
+  |       requester is connected to  |
+  +----------------------------------+
+           ^
+           |
+           |
+           |
+           |
+           v
+ +-------------------+
+ | +---------------+ |
+ | |  Nym client   | |
+ | +---------------+ |
+ |         ^         |
+ |         |         |
+ |         |         |
+ |         |         |
+ |         v         |
+ | +---------------+ |
+ | | Your app code | |
+ | +---------------+ |
+ +-------------------+
+  Your Local Machine
+```
+
+There are 2 pieces of software that work together to send SOCKS traffic through the mixnet: the `nym-socks5-client`, and the `nym-network-requester`.
+
+The `nym-socks5-client` allows you to do the following from your local machine:
+* Take a TCP data stream from a application that can send traffic via SOCKS5.
+* Chop up the TCP stream into multiple Sphinx packets, assigning sequence numbers to them, while leaving the TCP connection open for more data
+* Send the Sphinx packets through the mixnet to a [network requester](https://nymtech.net/operators/nodes/network-requester.md). Packets are shuffled and mixed as they transit the mixnet.
+
+The `nym-network-requester` then reassembles the original TCP stream using the packets' sequence numbers, and make the intended request. It will then chop up the response into Sphinx packets and send them back through the mixnet to your  `nym-socks5-client`. The application will then receive its data, without even noticing that it wasn't talking to a "normal" SOCKS5 proxy!
+
@@ -0,0 +1 @@
+# Command Documentation (Autogenerated)
@@ -0,0 +1 @@
+# Command Documentation (Autogenerated)
@@ -0,0 +1 @@
+# Command Documentation
@@ -1,69 +1,4 @@
-# Socks5 Client
-
-> The Nym socks5 client was built in the [building nym](../binaries/building-nym.md) section. If you haven't yet built Nym and want to run the code on this page, go there first.
-
-## Current version
-```
-<!-- cmdrun ../../../../target/release/nym-socks5-client --version | grep "Build Version" | cut -b 21-26  -->
-```
-
-## What is this client for?
-Many existing applications are able to use either the SOCKS4, SOCKS4A, or SOCKS5 proxy protocols. If you want to send such an application's traffic through the mixnet, you can use the `nym-socks5-client` to bounce network traffic through the Nym network, like this:
-
-```
-                                                                              External Systems:
-                                                                                     +--------------------+
-                                                                             |------>| Monero blockchain  |
-                                                                             |       +--------------------+
-                                                                             |       +--------------------+
-                                                                             |------>|    Email server    |
-                                                                             |       +--------------------+
-                                                                             |       +--------------------+
-                                                                             |------>|    RPC endpoint    |
-                                                                             |       +--------------------+
-                                                                             |       +--------------------+
-                                                                             |------>|       Website      |
-                                                                             |       +--------------------+
-                                                                             |       +--------------------+
-  +----------------------------------+                                       |------>|       etc...       |
-  | Mixnet:                          |                                       |       +--------------------+
-  |       * Gateway your client is   |                                       |
-  |       connected to               |          +--------------------+       |
-  |       * Mix nodes 1 -> 3         |<-------->| Network requester  |<------+
-  |       * Gateway that network     |          +--------------------+
-  |       requester is connected to  |
-  +----------------------------------+
-           ^
-           |
-           |
-           |
-           |
-           v
- +-------------------+
- | +---------------+ |
- | |  Nym client   | |
- | +---------------+ |
- |         ^         |
- |         |         |
- |         |         |
- |         |         |
- |         v         |
- | +---------------+ |
- | | Your app code | |
- | +---------------+ |
- +-------------------+
-  Your Local Machine
-```
-
-There are 2 pieces of software that work together to send SOCKS traffic through the mixnet: the `nym-socks5-client`, and the `nym-network-requester`.
-
-The `nym-socks5-client` allows you to do the following from your local machine:
-* Take a TCP data stream from a application that can send traffic via SOCKS5.
-* Chop up the TCP stream into multiple Sphinx packets, assigning sequence numbers to them, while leaving the TCP connection open for more data
-* Send the Sphinx packets through the mixnet to a [network requester](../nodes/network-requester.md). Packets are shuffled and mixed as they transit the mixnet.
-
-The `nym-network-requester` then reassembles the original TCP stream using the packets' sequence numbers, and make the intended request. It will then chop up the response into Sphinx packets and send them back through the mixnet to your  `nym-socks5-client`. The application will then receive its data, without even noticing that it wasn't talking to a "normal" SOCKS5 proxy!
-
+# Setup Guide
 ## Client setup
 ### Viewing command help

@@ -84,6 +19,7 @@ You can check the necessary parameters for the available commands by running:
 ```
 ./nym-client <COMMAND> --help
 ```
+or check the autogenerated command documentation on the [next page](./nym-socks5-client-commands). 

 ### Initialising a new client instance
 Before you can use the client, you need to initalise a new instance of it, which can be done with the following command:
@@ -100,11 +36,9 @@ Before you can use the client, you need to initalise a new instance of it, which

 The `--id` in the example above is a local identifier so that you can name your clients and keep track of them on your local system; it is **never** transmitted over the network.

-The `--use-reply-surbs` field denotes whether you wish to send [SURBs](../architecture/traffic-flow.md#private-replies-using-surbs) along with your request. It defaults to `false`, we are explicitly setting it as `true`. It defaults to `false` for compatibility with older versions of the [Network Requester](../nodes/network-requester.md).
+The `--use-reply-surbs` field denotes whether you wish to send [SURBs](https://nymtech.net/docs/architecture/traffic-flow.md#private-replies-using-surbs) along with your request. It defaults to `false`, we are explicitly setting it as `true`. It defaults to `false` for compatibility with older versions of the [Network Requester](https://nymtech.net/operators/nodes/network-requester.md).

-The `--provider` field needs to be filled with the Nym address of a Network Requester that can make network requests on your behalf. If you don't want to [run your own](../nodes/network-requester.md) you can select one from the [mixnet explorer](https://explorer.nymtech.net/network-components/service-providers) by copying its `Client ID` and using this as the value of the `--provider` flag. Alternatively, you could use [this list](https://harbourmaster.nymtech.net/).
-
-Since the nodes on this list are the infrastructure for [Nymconnect](https://nymtech.net/developers/quickstart/nymconnect-gui.html) they will support all apps on the [default whitelist](../nodes/network-requester.md#network-requester-whitelist): Keybase, Telegram, Electrum, Blockstream Green, and Helios.
+The `--provider` field needs to be filled with the Nym address of a Network Requester that can make network requests on your behalf. If you don't want to [run your own](https://nymtech.net/operators/nodes/network-requester.md) you can select one from the [mixnet explorer](https://explorer.nymtech.net/network-components/service-providers) by copying its `Client ID` and using this as the value of the `--provider` flag. Alternatively, you could use [this list](https://harbourmaster.nymtech.net/).

 #### Choosing a Gateway
 By default - as in the example above - your client will choose a random gateway to connect to.
@@ -112,9 +46,9 @@ By default - as in the example above - your client will choose a random gateway
 However, there are several options for choosing a gateway, if you do not want one that is randomly assigned to your client:
 * If you wish to connect to a specific gateway, you can specify this with the `--gateway` flag when running `init`.
 * You can also choose a gateway based on its location relative to your client. This can be done by appending the `--latency-based-selection` flag to your `init` command. This command means that to select a gateway, your client will:
-	* fetch a list of all availiable gateways
-	* send few ping messages to all of them, and measure response times.
-	* create a weighted distribution to randomly choose one, favouring ones with lower latency.
+    * fetch a list of all available gateways
+    * send few ping messages to all of them, and measure response times.
+    * create a weighted distribution to randomly choose one, favouring ones with lower latency.

 > Note this doesn't mean that your client will pick the closest gateway to you, but it will be far more likely to connect to gateway with a 20ms ping rather than 200ms

@@ -195,7 +129,7 @@ When trying to connect your app, generally the proxy settings are found in `sett

 Here is an example of setting the proxy connecting in Blockstream Green:

-![Blockstream Green settings](../images/wallet-proxy-settings/blockstream-green.gif)
+![Blockstream Green settings](../../images/blockstream-green.gif)

 Most wallets and other applications will work basically the same way: find the network proxy settings, enter the proxy url (host: **localhost**, port: **1080**).

@@ -1,6 +1,6 @@
 # Websocket Client

-> The Nym Websocket Client was built in the [building nym](../binaries/building-nym.md) section. If you haven't yet built Nym and want to run the code on this page, go there first.
+> The Nym Websocket Client was built in the [building nym](./building-nym.md) section. If you haven't yet built Nym and want to run the code on this page, go there first.

 ## Current version
 ```
@@ -0,0 +1 @@
+# Setup Guide
@@ -0,0 +1 @@
+# Command Documentation (Autogenerated)
@@ -25,6 +25,8 @@ You can check the necessary parameters for the available commands by running:
 ./nym-client <command> --help
 ```

+Or check the autogenerated command documentation on the [next page](./nym-client-commands.md).
+
 ## Initialising your client

 Before you can use the client, you need to initalise a new instance of it. Each instance of the client has its own public/private keypair, and connects to its own gateway node. Taken together, these 3 things (public/private keypair + gateway node identity key) make up an app's identity.
@@ -58,7 +58,7 @@ In some applications, e.g. where people are chatting with friends who they know,

 **If that fits your security model, good. However, will probably be the case that you want to send anonymous replies using Single Use Reply Blocks (SURBs)**.

-You can read more about SURBs [here](../../architecture/traffic-flow.md#private-replies-using-surbs) but in short they are ways for the receiver of this message to anonymously reply to you - the sender - **without them having to know your client address**.
+You can read more about SURBs [here](https://nymtech.net/docs/architecture/traffic-flow.md#private-replies-using-surbs) but in short they are ways for the receiver of this message to anonymously reply to you - the sender - **without them having to know your client address**.

 Your client will send along a number of `replySurbs` to the recipient of the message. These are pre-addressed Sphinx packets that the recipient can write to the payload of (i.e. write response data to), but not view the final destination of. If the recipient is unable to fit the response data into the bucket of SURBs sent to it, it will use a SURB to request more SURBs be sent to it from your client.

@@ -1,7 +0,0 @@
-# DevRel AMAs
-
-The Nym Technology Developer Relations AMA (Ask Me Anything) is an event organised by the Nym team to engage and connect with the developer community as well as answer any questions that they may have.
-
-> ⚠️ Hosted every fortnight on Wednesday @ 4pm UTC
-
-Archives of these calls can be found [here](https://www.youtube.com/watch?v=0kVXR7aNOyg&list=PLoc3wV2YJYwohgwzf5IinyebV4GGYsa9K).
@@ -1,6 +0,0 @@
-# Forums
-
-Welcome to our page dedicated to providing you with links to open forums discussing privacy-enhancing technologies, as well as general privacy topics. These forums are a great place to learn more about the latest developments in privacy technology, as well as to connect with other individuals who are passionate about protecting their online privacy. Whether you're new to the world of privacy or an experienced user, you're sure to find valuable information and resources on these forums.
-
-
-🚧 coming soon 🚧
@@ -0,0 +1 @@
+# Development Overview
@@ -1,7 +1,5 @@
 # Nym General FAQ

-> If you have questions which are not answered below, please share them at our [DevRel AMAs](../community-resources/ama.md) or seek support in [Nym's community](https://nymtech.net/community)
-
 ### What is Nym? 

 Nym is a privacy platform that secures user data and protects against surveillance at the network level. 
@@ -198,7 +198,7 @@ For the moment then yes, the mixnet is free to use. There are no limits on the a
 No, although we do recommend that apps that wish to integrate look into running some of their own infrastructure such as gateways in order to assure uptime. 

 ### How can I find out if an application is already supported by network requester services? 
-You can check the [default allowed list](https://nymtech.net/.wellknown/network-requester/standard-allowed-list.txt) file to see which application traffic is whitelisted by default. If the domain is present on that list, it means that existing [network requesters](https://nymtech.net/docs/nodes/network-requester.html) can be used to privacy-protect your application traffic. Simply use [NymConnect](../quickstart/nymconnect-gui.md) to connect to this service through the mixnet.
+You can check the [default allowed list](https://nymtech.net/.wellknown/network-requester/standard-allowed-list.txt) file to see which application traffic is whitelisted by default. If the domain is present on that list, it means that existing [network requesters](https://nymtech.net/docs/nodes/network-requester.html) can be used to privacy-protect your application traffic. 

 Currently we are undergoing changes on this policy under the name [Project Smoosh](https://nymtech.net/operators/faq/smoosh-faq.html) where a new type of node [Exit Gateway](https://nymtech.net/operators/legal/exit-gateway.html) will allow users to connect to much wider range of domains, restricted by our new [exit policy](https://nymtech.net/.wellknown/network-requester/exit-policy.txt). Follow the changes [here](https://nymtech.net/operators/faq/smoosh-faq.html#what-are-the-changes).

@@ -1,106 +0,0 @@
-# Glossary
-
-__Familiarise yourself with Nym's specific terms and jargon through our glossary, making your understanding of Nym technology more enjoyable and educational.__
-
-## A
-**[Address](https://nymtech.net/docs/stable/integrations/addresses-in-nym/)** - A unique string of characters generated from a client keypair. Used to identify clients in the mixnet.
-
-**[Ack](https://nymtech.net/docs/architecture/traffic-flow.html#acks--package-retransmission)** - Short for "acknowledgement". Whenever a hop is completed, the recieving node will send back an 'ack', so that the sending node knows that the packet was recieved.
-
-**Attacker** - A person or entity who attempts to gain unauthorised access to a computer system, network, or other information resource.
-
-## B
-**Binary** - Is a type of computer file that contains machine code, which is a set of instructions that a computer can execute directly. The file consists of a series of 1s and 0s, which are the two digits used in the binary number system.
-
-**Blockchain** - A distributed database that maintains a continuously growing list of ordered records, called blocks.
-
-## C
-**[Coconut](https://nymtech.net/docs/stable/coconut/)** - A distributed cryptographic signing scheme providing a high degree of privacy for its users.
-
-**[CLI](https://nymtech.net/docs/stable/nym-cli/)** - A command-line interface (CLI) is a text-based user interface (UI) used to run programs, manage computer files and interact with the computer.
-
-**Credentials** - Unique values that prove the legitimacy of a user or individual.
-
-**Centralisation** - Refers to the concentration of control of an activity or organisation under a single authority, or small group of authorities.
-
-**[CosmWasm](https://cosmwasm.com)** - Cosmos WebAssembly is a WebAssembly (Wasm) interpreter that is used in the Cosmos SDK, a framework for building decentralised applications (dApps) on the Cosmos network. It allows us to write smart contracts in Rust and then compile them to webassembly to be uploaded on the blockchain.
-
-## D
-**DAO** - Stands for Decentralised Autonomous Organisation. A type of organisation made up of smart contracts on a blockchain. It operates on a set of rules encoded in a computer program, and is governed by the people who use it, rather than by a central authority.
-
-**[Delegating NYM](https://medium.com/coinmonks/what-you-have-to-know-about-staking-and-delegating-458b6d2300a5)** - Similar to bonding but by non-operators and as proof of their trust in a node operator providing a good quality of service. 
-
-**Decentralisation** - Refers to the transfer of control and decision-making from a centralised entity (individual, organization, or group thereof) to a distributed network.
-
-## E
-**Encryption** - The process of encoding information.
-
-## G
-**[Gateways](https://blog.nymtech.net/gateways-to-privacy-51196005bf5)** - The entrance to the mixnet that encrypted packets must pass through before being forwarded to mix nodes. They also act as a sort of mailbox for messages.
-
-**[Gateway Bonding](https://nymtech.net/docs/stable/run-nym-nodes/nodes/gateways/#bonding-your-gateway)** - The action of node operators to bond their stake (in the form of NYM tokens) to a Gateway in order to join the network topology and begin routing traffic through.
-
-## I
-**IPFS** - Stands for InterPlanetary File System. It's a decentralised, peer-to-peer protocol for sharing and storing files. It is designed to make it easier to share and access large amounts of data in a distributed manner, without the need for a central server or authority
-
-## M
-**[Metadata](https://www.opendatasoft.com/en/blog/what-is-metadata-and-why-is-it-important-data)** - A set of data that describes and gives information about other data such as IP addresses, device types, geolocations etc.
-
-**[Mixnet](https://nymtech.net/docs/architecture/traffic-flow.html#mixnet-traffic-flow-1)** - A routing protocol which encrypts and mixes Sphinx packet traffic so that it cannot be determined who is communicating with whom. 
-
-**[Mix Nodes](https://blog.nymtech.net/nym-mixnodes-deep-dive-d2b91917f097)** - The backbone of the Nym infrastructure, that are organised in a three-layer network referred to as the mixnet that network traffic passes through. It mixes, hides and reorders traffic and are rewarded in NYM tokens for their quality of service.
-
-**[Mix node Bonding](https://nymtech.net/docs/stable/run-nym-nodes/nodes/mixnodes/#bonding-your-mix-node)** - The action of node operators bonding their stake (in the form of NYM tokens) to a Mix node in order to join the network topology and begin routing traffic through.
-
-## N
-**[Network Requester](https://nymtech.net/docs/stable/run-nym-nodes/nodes/requester)** - Is a binary that can be ran alongside a Nym Client on a VPS, which allows for private network requests to be made outside the mixnet from you local Nym client
-
-**Nym** - The in-text name of the organisation.
-
-**[Nym Typescript SDK](https://nymtech.net/docs/stable/sdk/overview)** - A Typescript software development kit which allows developers to build browser-based Mixnet application.
-
-**[NYM](https://nymtech.net/docs/stable/nym-cli/#send-tokens-to-an-account)** - Natively distributed token. 
-
-**[Nym Wallet](https://nymtech.net/docs/stable/wallet/)** - The Nym Wallet handles all things regarding handling Nym Tokens about your Nym Node. It is a GUI application that can be downloaded and run on your machine.
-
-**[Nym Technologies SA](https://nymtech.net)** - The official company name.
-
-**[Nyx](https://nymtech.net/docs/stable/integrations/payment-integration-overview/)** - A CosmWasm-enabled blockchain smart contracts platform that functions as the backbone of the Nym network, used to keep track and provide the history of the NYM token's transactions.
-
-## P
-**Payload** - The carrying capacity of a packet or other transmission data unit.
-
-**Pledge** - The number of tokens that are put up by node operators on their nodes as their commitment to provide good quality of service and insure against future bad behaviour.
-
-**Private Key** - A large numerical value that is used to decrypt data.
-
-**Proof-of-Mixing** - The reward of NYM tokens is based on the good quality of service carried out by node operators.
-
-**POC** - Stands for Proof of Concept. It's a demonstration that a proposed product, system, or service can be built and will work as intended. It is a way of testing whether an idea is feasible and likely to succeed.
-
-**Public Key** - A large numerical value that is used to encrypt data.
-
-## S
-**Sphinx** - A cryptographic message format used to relay anonymised messages within the mixnet, also used by the Lightning Network or something similar.
-
-**[Socks5](https://en.wikipedia.org/wiki/SOCKS)** - An proxy protocol that exchanges network packets between a client and server through a proxy server.
-
-**[Service Provider](https://nymtech.net/docs/stable/tutorials/nym-simple-websocket-tutorial/)** - Any type of app that can communicate with the mixnet via a Nym Client.
-
-**[SURBs](https://nymtech.net/docs/architecture/traffic-flow.html#private-replies-using-surbs)** - Stands for 'Single Use Reply Blocks'. They are a type of crytographic construct used to facilitate secure communication between parties and are designed to allow a sender to send a message to a recipient in sucha a way that the message can only be read by the intended recipient, and cannot be read by anyone else.
-
-**Sybil** - In the context of computer networks, a Sybil attach is a type of security attack in which an attacker creates multiple fake identities or "sybils" and uses them to manipulate a network thus gaining control of a network by overwhelming it.
-
-## T
-**Tokenomics** - Is the study of the economic and financial aspects of a cryptocurrency or blockchain-based project. It involves the creation, distribution, and management of tokens, which are digital assets that represent a certain value of utility whithin a particular ecosystem.
-
-## V
-**[Validators](https://nymtech.net/docs/stable/run-nym-nodes/nodes/validators/)** - Secures the Nyx blockchain with a staking token, defending the network from attacks.
-
-**[VPS](https://en.wikipedia.org/wiki/Virtual_private_server)** - Stands for Virtual Private Server. Its a virtual machine that acts as an isolated virtual environment on a physical server operated by a cloud, web or internet hosting provider.
-
-## W
-**Websocket** - A computer communications protocol that provides a full-duplex channel over a single TCP connection. It is designed to be used as a base for real-time, two-way communication between a client and a server over the web.
-
-## Z
-**Zero Knowledge Proofs** - Cryptographic techniques that make it possible to prove something to be true without having to reveal the evidence. 
@@ -1,14 +0,0 @@
-# Change Service Grantee Information
-
-If you wish to update any of the following information: 
- - `Email Address`
- - `NYM address`
- - `Network Requester`
- - `Gateway ID Key` 
- - `Gateway Address`
- - `Service`
- - `Payment Address` 
-
-Please reach out either in the `#service-grantees` channel on Discord or on [Matrix](https://matrix.to/#/#nym-community:nymtech.chat). 
-
-
@@ -11,4 +11,4 @@ For more in-depth information on the network architecture, head to the [Network
 If you would like to concentrate on building an application that uses the mixnet:
 * Explore the [Quickstart](../quickstart/overview.md) options.
 * Check out examples of [Community Apps](../community-resources/community-applications-and-guides.md). 
-* Run through the [Rust SDK](../tutorials/rust-sdk.md) or [Typescript](../tutorials/typescript.md) tutorials. 
+* Run through the [Rust SDK](../tutorials/archive/setups/rust-sdk.md) or [Typescript](../tutorials/archive/setups/typescript.md) tutorials. 
@@ -1,13 +1,11 @@
 # Integration Options
-If you've already gone through the different [Quick Start](../quickstart/overview.md) options and had a look at the tutorials, you have seen the possibilities available to you for quickly connecting existing application code to another Nym process. 
-
 Below are a resources that will be useful for either beginning to integrate mixnet functionality into existing application code or build a new app using Nym.  

 - **We suggest you begin with this [integration decision tree](https://sdk.nymtech.net/integrations)**. This will give you a better idea of what pieces of software (SDKs, standalone clients, service providers) your integration might involve, and what is currently possible to do with as little custom code as possible. 

 - The [integrations FAQ](../faq/integrations-faq.md) has a list of common questions regarding integrating with Nym and Nyx, as well as commonly required links. 

- To get an idea of what is possible / has already been built, check the [community applications and resources](../community-resources/community-applications-and-guides.md) page, as well as the [developer tutorials codebase](https://github.com/nymtech/developer-tutorials). 
+- To get an idea of what is possible / has already been built, check the [community applications and resources](../community-resources/community-applications-and-guides.md) page. 

 > If you wish to integrate with the Nyx blockchain to use `NYM` for payments, start with the [payment integration](./payment-integration.md) page.

@@ -2,7 +2,7 @@

 If you want to integrate with Nym in order to send `NYM` tokens (for instance, if running a `NYM` <-> `BTC` swap application, or using `NYM` for payments), then you will need to interact with the Nyx blockchain. 

-Nyx is the blockchain supporting the Nym network, hosting both the `NYM` and `NYX` cryptocurrencies, the CosmWasm smart contracts keeping track of the network, and (coming soon) facilitating zk-Nym credential generation. It is built with the [Cosmos SDK](https://tendermint.com/sdk/).
+Nyx is the blockchain supporting the Nym network, hosting both the `NYM` and `NYX` cryptocurrencies, the CosmWasm smart contracts keeping track of the network, and facilitating zk-Nym credential generation. It is built with the [Cosmos SDK](https://tendermint.com/sdk/).

 ### Interacting with the Nyx blockchain 
 Check out the integration options in the [Integration FAQ](../faq/integrations-faq.md#how-can-i-use-json-rpc-methods-to-interact-with-the-nyx-blockchain). 
@@ -3,7 +3,7 @@
 The Nyx blockchain is based on [CosmWasm](https://cosmwasm.com/). It allows users to code smart contracts in a safe subset of the Rust programming language, easily export them to WebAssembly, and upload them to the blockchain. Information about the chain can be found on the [Nyx blockchain explorer](https://nym.explorers.guru/). 

 There are currently two smart contracts on the Nyx chain: 
-* the [Mixnet contract](./mixnet-contract.md) which manages the network topology of the mixnet, tracking delegations and rewarding. 
-* the [Vesting contract](./vesting-contract.md) which manages `NYM` token vesting functionality.  
+* the [Mixnet contract](mixnet-contract.md) which manages the network topology of the mixnet, tracking delegations and rewarding. 
+* the [Vesting contract](vesting-contract.md) which manages `NYM` token vesting functionality.  

 > Users will soon be able to create and upload their own CosmWasm smart contracts to Nyx and take advantage of applications such as the Coconut Credential Scheme - more to be announced regarding this very soon.
@@ -1,5 +0,0 @@
-# Chat demo (webapp)
-
-You can find a browser-based 'hello world' chat app [here](https://chat-demo.nymtech.net).
-
-Either open in two browser windows and send messages to yourself, or share with a friend and send messages to each other through the mixnet.
@@ -1,5 +0,0 @@
-# Coconut Credential Playground (webapp)
-
-There is a coconut-scheme based Credential Library playground [here](https://coco-demo.nymtech.net/). This is a WASM implementation of our Coconut libraries which generate raw Coconut credentials. Test it to create and re-randomize your own credentials.
-
-For more information on what is happening here check out the [Coconut docs](https://nymtech.net/docs/coconut.html).
@@ -1,22 +0,0 @@
-# NymConnect Beta (GUI)
-
-NymConnect is a one-button GUI application that wraps around the `nym-socks5-client` for proxying application traffic through the Mixnet. 
-
-You can watch our video on getting started with NymConnect: 
-
-<iframe width="700" height="400" src="https://www.youtube.com/embed/quj8H2qeOwY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
-
-Install NymConnect and select an application that you want to privacy-enhance from the dropdown menu. For now, NymConnect can be used with Electrum Wallet, Keybase, desktop Telegram and Blockstream Green. Configure these to run via a SOCKS5 proxy and send their data through the Nym mixnet!
-
-**Please note that NymConnect is currently released in beta. Please report bugs via Github**. 
-
-## Usage instuctions 
-* [Download](https://github.com/nymtech/nym/releases/) and install NymConnect.
-* Select your service provider from the dropdown menu.
-* Click `connect` - NymConnect will connect to a service provider and its SOCKS Proxy (IP) and Port will be displayed.
-* Click on IP or Port to copy their values to the clipboard.
-* Go to your app settings and look for the network/proxy settings. Select `running via SOCKS5 proxy` and paste the IP and Port values given by NymConnect.
-
-Your traffic from that application will now run through the mixnet for privacy and unlinkability!
-
-
@@ -1,7 +0,0 @@
-# Overview
-
-There are multiple options to quickly connect to Nym and play with both the mixnet and credentials on the Sandbox testnet.
-
-At most, these involve running Nym as a second process alongside an existing application in order to send traffic through the mixnet, most are either interact webpages or a standalone app.
-
-If you've already covered the information in this section, or want to jump straight into integrating/ a Nym connection into an existing application, head to the [Integrations](../integrations/integration-options.md) section.
@@ -1,45 +0,0 @@
-# SOCKS Proxy (CLI)
-
->The `socks5` client now also supports SOCKS4 and SOCKS4A protocols as well as SOCKS5.
-
-The Nym socks5 client allows you to proxy traffic from a desktop application through the mixnet, meaning you can send and receive information from remote application servers without leaking metadata which can be used to deanonymise you, even if you're using an encrypted application such as Signal.
-
-### Download or compile socks5 client
-
-If you are using OSX or a Debian-based operating system, you can download the `nym-socks5-client` binary from our [Github releases page](https://github.com/nymtech/nym/releases).
-
-If you are using a different operating system, head over to the [Building from Source](https://nymtech.net/docs/binaries/building-nym.html) page for instructions on how to build the repository from source.
-
-### Initialise your socks5 client
-
-Use the following command to initialise your socks5 client with the address of a Nym-operated [Network Requester](https://nymtech.net/docs/nodes/network-requester.html) as a provider (the endpoint that will be proxying your traffic out of the mixnet) for ease:
-
-```
-./nym-socks5-client init --id quickstart --provider Entztfv6Uaz2hpYHQJ6JKoaCTpDL5dja18SuQWVJAmmx.Cvhn9rBJw5Ay9wgHcbgCnVg89MPSV5s2muPV2YF1BXYu@Fo4f4SQLdoyoGkFae5TpVhRVoXCF8UiypLVGtGjujVPf
-```
-
-You can always check out the list of endpoints you can use otherwise on the [mixnet service provider explorer page](https://explorer.nymtech.net/network-components/service-providers).
-
-### Start your socks5 client
-Now your client is initialised, start it with the following:
-
-```
-./nym-socks5-client run --id quickstart
-```
-
-### Proxying traffic
-After completing the steps above, your local socks5 Client will be listening on `localhost:1080` ready to proxy traffic to the Network Requester set as the `--provider` when initialising.
-
-When trying to connect your app, generally the proxy settings are found in `settings->advanced` or `settings->connection`.
-
-Here is an example of setting the proxy connecting in Blockstream Green:
-
-![Blockstream Green settings](../images/blockstream-green.gif)
-
-Most wallets and other applications will work basically the same way: find the network proxy settings, enter the proxy url (host: **localhost**, port: **1080**).
-
-In some other applications, this might be written as **localhost:1080** if there's only one proxy entry field.
-
-## Further reading
-
-If you want to dig more into the architecture and use of the socks5 client check out its documentation [here](https://nymtech.net/docs/clients/socks5-client.html).
@@ -1,9 +1,9 @@
 # Coconut credential generation
-The following code shows how you can use the SDK to create and use a [credential](../../../bandwidth-credentials.md) representing paid bandwidth on the Sandbox testnet.
+The following code shows how you can use the SDK to create and use a [credential](https://nymtech.net/docs/bandwidth-credentials.md) representing paid bandwidth on the Sandbox testnet.

 ```rust,noplayground
 {{#include ../../../../../../sdk/rust/nym-sdk/examples/bandwidth.rs}}
 ```

-You can read more about Coconut credentials (also referred to as `zk-Nym`) [here](../../../coconut.md).
+You can read more about Coconut credentials (also referred to as `zk-Nym`) [here](https://nymtech.net/docs/coconut.md).

@@ -1,13 +1,11 @@
 # Anonymous Replies with SURBs (Single Use Reply Blocks)
 Both functions used to send messages through the mixnet (`send_message` and `send_plain_message`) send a pre-determined number of SURBs along with their messages by default.

-The number of SURBs is set [here](https://github.com/nymtech/nym/blob/master/sdk/rust/nym-sdk/src/mixnet/client.rs#L33).
-
 ```rust,noplayground
 {{#include ../../../../../../sdk/rust/nym-sdk/src/mixnet/client.rs:33}}
 ```

-You can read more about how SURBs function under the hood [here](../../../architecture/traffic-flow.md#private-replies-using-surbs).
+You can read more about how SURBs function under the hood [here](https://nymtech.net/docs/architecture/traffic-flow.md#private-replies-using-surbs).

 In order to reply to an incoming message using SURBs, you can construct a `recipient` from the `sender_tag` sent along with the message you wish to reply to:

@@ -1,7 +1,7 @@
 # Message Helpers

 ## Handling incoming messages
-As seen in the [Chain querier tutorial](https://github.com/nymtech/developer-tutorials/blob/0130ee5a61cd6801bdcfc84608b2a520b5392714/rust/chain-query-service/) when listening out for a response to a sent message (e.g. if you have sent a request to a service, and are awaiting the response) you will want to await [non-empty messages (if you don't know why, read the info on this here)](troubleshooting.md#client-receives-empty-messages-when-listening-for-response). This can be done with something like the helper functions [here](https://github.com/nymtech/developer-tutorials/blob/0130ee5a61cd6801bdcfc84608b2a520b5392714/rust/chain-query-service/src/lib.rs#L71): 
+When listening out for a response to a sent message (e.g. if you have sent a request to a service, and are awaiting the response) you will want to await non-empty messages [(if you don't know why, read the info on this here)](troubleshooting.md#client-receives-empty-messages-when-listening-for-response). This can be done with something like the helper functions [here](https://github.com/nymtech/developer-tutorials/blob/0130ee5a61cd6801bdcfc84608b2a520b5392714/rust/chain-query-service/src/lib.rs#L71): 

 ```rust
 use nym_sdk::mixnet::ReconstructedMessage; 
@@ -0,0 +1 @@
+# Interacting with Clients - Read First!
@@ -1,53 +0,0 @@
-# Hackathon Challenges
-There are a few different challenges to choose from, each with different approaches. It is also recommended to check out the _**Examples**_ directory above for inspiration. 
-
-## Tooling challenge
-The tooling challenge involves creating tooling for users, operators, or developers of Nym.
-
-### Examples of user-centric tools:
- Facilitate onboarding new users more easily to staking their Nym, and understanding the pros and cons, as well as finding a good node to stake on. Examples of tools like this:
-    - [ExploreNym dashboard](https://explorenym.net/)
-
- Show information on a dashboard about the network. NOTE due to the amount of dashboards currently available, we expect a good justification for why / something to set this apart from existing ones e.g. it is presenting information that is not already presented, or it is presented in a different manner, such as a TUI or CLI app instead of a web dashboard - maybe an onion service, or no-JS site for those who do not wish to enable Javascript in their day-to-day browsing. Examples of tools like this:
-    - [NTV's node dashboard](https://status.notrustverify.ch/d/CW3L7dVVk/nym-mixnet?orgId=1)
-    - [IsNymUp dashboard](https://isnymup.com/)
-
-### Examples of operator-centric tooling:
- An APY calculator for determining different financial outcomes of running a node in different situations. 
-    
- Scripting for updating and maintaining nodes. Examples of tools like this:
-    - [ExploreNym's bash scripts](https://github.com/ExploreNYM/bash-tool) 
-
- Scripting for packaging node binaries for different OSes.
-
-### Examples of developer-centric tooling:
- Tooling for use in development: are there pain points you’ve found when developing apps with Nym that you have created scripts/hacks/workarounds for? Is there a pain point that you’ve thought ‘oh it would be great if I could just do X’? These are often the best places to start for building out developer tooling - if you’ve run into this issue, it's very likely someone else already has, or will!
-
- Interacting with one of the SDKs via FFI: perhaps you’re a Go developer who would love to have the functionality of one of the Nym SDKs. Building an FFI tool might be something that would make your life easier, and can be shared with other developers in your situation. 
-
-## Integrations challenge
-Integration options for Nym are currently relatively restrictive due to the manner in which Nym handles sending and receiving traffic (as unordered Sphinx packets). This challenge will involve (most likely) implementing custom logic for handling Nym traffic for an existing application.
-
-There are several potential avenues developers can take here:
- If your application (or the application you wish to modify) is written in either Javascript or Typescript, and relies on the `fetch` library to make API calls, then you can use its drop-in replacement: [`mixfetch`](). Perhaps you wish to interact with Coingecko, or a private search engine like Kagi without leaking your IP and metadata, or an RPC endpoint.
-    - Example with [NTV’s privacy-preserving Coingecko API](https://github.com/notrustverify/mixfetch-examples)
-    - [Mixfetch docs examples](https://github.com/nymtech/nym/tree/develop/sdk/typescript/examples)
-
- If you instead have an application that is able to use any of the SOCKS5, 4a, or 4 protocols (a rule of thumb: if it can communicate over Tor, it will) then you can experiment with using Nym as the transport layer. 
-  - For Rustaceans, check out our [socks5 rust sdk example](https://nymtech.net/docs/sdk/rust.html#socks-client-example).  
-  - For those of you who aren’t Crustaceans, then you will have to run the [Socks Client]() alongside your application as a separate process. _NOTE If you are taking this route, please make sure to include detailed documentation on how you expect users to do this, as well as including any process management tools, scripts, and configs (e.g. if you use systemd then include the configuration file for the client, as well as initialisation logic) that may streamline this process._
-    - [NTV's PasteNym backend](https://github.com/notrustverify/pastenym) is a great example of an application with this architecture. 
-
- Nym is not only useful for blockchain-related apps, but for anything that requires network level privacy! Email clients, messaging clients, and decentralised storage are all key elements of the privacy-enabled web. Several of these sorts of apps can be found in the [community apps page](../community-resources/community-applications-and-guides.md). 
-
- There is currently a proof of concept using Rust Libp2p with Nym as a transport layer. Perhaps you can think of an app that uses Gossipsub for p2p communication could benefit from network-level privacy. 
-  - [GossipSub chat example](https://github.com/nymtech/nym/tree/develop/sdk/rust/nym-sdk/examples/libp2p_chat) 
-  - [Chainsafe's Lighthouse Nym PoC](https://github.com/ChainSafe/lighthouse/blob/nym/USE_NYM.md#usage)
-
- Alternatively if you know of an app that is written in Rust or TS and could benefit from using Nym, you could fork and modify it using the SDKs. Applications such as:
-  - Magic Wormhole (has a [rust implementation](https://github.com/magic-wormhole/magic-wormhole.rs))
-  - [Qual](https://github.com/qaul/qaul.net) (uses Rust Libp2p)
-  - [Syncthing](https://github.com/syncthing/syncthing)
-
-### MiniApp challenge 
-Write an app, either using one of the SDKs or a standalone client (harder). Think of what you can ‘nymify’ e.g. a version of the [TorBirdy](https://support.torproject.org/glossary/torbirdy/) extension that uses Nym instead of Tor. This is very similar to the Integration challenge in terms of the different potential _architectures_ and approaches, but just for new applications. 
@@ -1,16 +0,0 @@
-# General Info & Resources 
-Discussions and announcements will be taking place in the [builders channel on Matrix](https://matrix.to/#/#shipyardbuilders:nymtech.chat). This channel can be used for all discussions. 
-
-There will be daily office horse between 12-14:00 CET. 
-
-This is an open call and questions will be answered on a first come first serve basis. 
-
-The timetable can be found on the [Shipyard website](https://nymtech.net/learn/shipyard). 
-
-## Links 
- You can find **code examples**, **tutorials**, & **quickstart** information here, on the Developer Portal. 
- [Rust SDK docs](https://nymtech.net/docs/sdk/rust.html)
- [Typescript SDK docs](https://sdk.nymtech.net)
- [Platform docs](https://nymtech.net/docs)
- [NoTrustVerify's Awesome Nym list](https://github.com/notrustverify/awesome-nym)
- [Builders channel Matrix](https://matrix.to/#/#shipyardbuilders:nymtech.chat)
@@ -1,15 +0,0 @@
-# Submission Guidelines
-We expect to see the following for submissions: 
- Working code demos hosted publicly (Gitlab, Github, some other git instance).
- Quality > quantity here: we’d prefer to see a contained, working, and well documented Proof of Concept over a sprawling and messy app that does more but is poorly explained and presented. _The repo must be open source and able to be used and modified by others. The license is up to you._
- If you already have existing apps / projects you are more than welcome to extend them, instead of starting from scratch - we will only be looking at the NEW additions to make this fair. If you are doing this, make sure to write a detailed account of what it is you;ve added to the existing project, preferably with the possibility to see the ‘old’ version as well as the new one.
- Proper documentation:
-  - If an app / tool:
-    - How do you install and run the code? How is it to be used? 
-    - An overview of the application architecture: what is it doing? Is it relying on other services? 
-  - If a UI-based solution:
-    - How to run it locally? We are happy to also accept staging deployments as part of the submission (e.g. via Vercel) but this does not replace being able to run it locally.
- Please make sure that your application works on commonly reproducible system environments (e.g. if you’re developing on Artix Linux please check for the necessary dependencies for more common-place OSes such as Debian, or Arch). If you are developing on Windows please make sure that it works on non-Windows machines also. Where possible please try to include build and install instructions for a variety of OSes. 
-
-## How to submit? 
-Please follow the instructions [here](https://github.com/nymtech/nym/discussions/4143). 
@@ -1,12 +0,0 @@
-# A Note on Infrastructure
-If you are writing an application that requires sending messages through the mixnet, then you will either be relying on existing infrastructure nodes (network requesters), or writing your own custom service (for example, the service written as part of the Rust SDK tutorial).
-
-If you are relying on network requesters then chances are that the IPs or domains your app relies on will not already be on the whitelist. Ideally, you would [run your own,](https://nymtech.net/operators/nodes/network-requester-setup.html) but we will also run a few nodes in ‘open proxy’ mode and share the addresses so that you can use them when beginning to develop. 
-
-## Node Details:
- NR1
-  - Location: Singapore
-  - Nym Address: `FDeWfd8q686PWLXJDCqNJTCbydTk1KSux5HVftimsPyx.9XyThN4yh92eTMuLp1NvWicRZob8Ei5xpba9dvcMLxcN@9Byd9VAtyYMnbVAcqdoQxJnq76XEg2dbxbiF5Aa5Jj9J`
- NR2
-  - Location: Frankfurt
-  - Nym Address: `BNypKaGiGY8GNRN4gpV95GcaVS8n7CrHuoZNgQ2ezqv2.ACpaixzuaSzuMajVQj6aR7cbpbvp676tm21MiLbX1gni@678qVUJ21uwxZBhp3r56z7GRf6gMh3NYDHruTegPtgMf`
@@ -0,0 +1 @@
+# Command Documentation (Autogenerated)
@@ -68,6 +68,8 @@ subcommands:
 ```
 ~~~

+Or check the autogenerated command documentation on the [next page](./nym-cli-commands.md).
+
 ## Example Usage
 Below we have listed some example commands for some of the features listed above.

@@ -304,7 +306,7 @@ Verify a signature.

 ### Create a Vesting Schedule

-Creates a vesting schedule for an account in the [vesting smart contract](../nyx/vesting-contract.md).
+Creates a vesting schedule for an account in the [vesting smart contract](../../../dev-portal/src/nyx/vesting-contract.md).

 ```
 ./nym-cli vesting-schedule create --mnemonic <mnemonic> --address <ADDRESS> --amount <AMOUNT>
@@ -312,7 +314,7 @@ Creates a vesting schedule for an account in the [vesting smart contract](../nyx

 ### Query a Vesting Schedule

-Query for vesting schedule in the [vesting smart contract](../nyx/vesting-contract.md).
+Query for vesting schedule in the [vesting smart contract](../../../dev-portal/src/nyx/vesting-contract.md).

 ```
 ./nym-cli vesting-schedule query --mnemonic <mnemonic>
@@ -27,10 +27,10 @@ chmod +x ./nym-connect_<VERSION>

 To download Electrum visit the [official webpage](https://electrum.org/#download). To connect to the Mixnet follow these steps:

-7. Start and connect [NymConnect](./electrum.md#nymconnect-installation) (or [`nym-socks5-client`](https://nymtech.net/docs/clients/socks5-client.html))
+7. Start and connect [NymConnect](electrum.mdymconnect-installation) (or [`nym-socks5-client`](https://nymtech.net/docs/clients/socks5-client.html))
 2. Start your Electrum Bitcoin wallet
 3. Go to: *Tools* -> *Network* -> *Proxy*
 4. Set *Use proxy* to ✅, choose `SOCKS5` from the drop-down and add the values from your NymConnect application
 5. Now your Electrum Bitcoin wallet runs through the Mixnet and it will be connected only if your NymConnect or `nym-socks5-client` are connected.

-![Electrum Bitcoin wallet setup](../images/electrum_tutorial/electrum.gif)
+![Electrum Bitcoin wallet setup](../../../images/electrum_tutorial/electrum.gif)
@@ -27,10 +27,10 @@ chmod +x ./nym-connect_<VERSION>

 To download Firo Electrum wallet visit the [Firo's repository](https://github.com/firoorg/firo) or [Github release page](https://github.com/firoorg/electrum-firo/releases/tag/4.1.5.2). To connect to the Mixnet follow these steps:

-7. Start and connect [NymConnect](./firo.md#nymconnect-installation) (or [`nym-socks5-client`](https://nymtech.net/docs/clients/socks5-client.html))
+7. Start and connect [NymConnect](firo.mdymconnect-installation) (or [`nym-socks5-client`](https://nymtech.net/docs/clients/socks5-client.html))
 8. Start your Firo Electrum wallet
 9. Go to: *Tools* -> *Network* -> *Proxy*
 10. Set *Use proxy* to ✅, choose `SOCKS5` from the drop-down and add the values from your NymConnect application
 11. Now your Firo Electrum wallet runs through the Mixnet and it will be connected only if your NymConnect or `nym-socks5-client` are connected.

-![Firo Electrum wallet setup](../images/firo_tutorial/firo.png)
+![Firo Electrum wallet setup](../../../images/firo_tutorial/firo.png)
@@ -37,7 +37,7 @@ Make sure your `Shortcut` isn't already taken by something else in the menu.

 An example can look like this.

-![](../images/element_nym_keybind.png)
+![](../../../images/element_nym_keybind.png)

 Alternatively you can add a keybinding via the CLI, using whatever config files you edit for your given desktop environment / window manager.

@@ -2,7 +2,7 @@

 *New Nym mixnet integration launched for Monero desktop to secure the right to financial privacy and censorship-resistance*

-![](../images/monero_tutorial/monero.png)
+![](../../../images/monero_tutorial/monero.png)

 Financial privacy is an important component of digital currencies and the use of Nym will provide users with the highest level of privacy at the infrastructure level. All users of digital currencies should be afforded equal rights to protection from financial surveillance.

@@ -2,11 +2,11 @@

 *This is a shortened version of a [Nym Community post](https://blog.nymtech.net/how-to-use-telegram-in-iraq-with-nymconnect-106a3b8dd050) written by Saliveja.*

-![](../images/telegram.png)
+![](../../../images/telegram.png)

 The purpose of the following manual is not to promote Telegram but so people can use it with the Nym mixnet if they wish to, should a situation ask for that. This privacy-enhances Telegram at the network level and allows users to access the application from locations like where the application was banned.  

-See also: [Element (Matrix) over the Nym mixnet](./matrix.md): private, decentralised and secure messaging.
+See also: [Element (Matrix) over the Nym mixnet](matrix.md): private, decentralised and secure messaging.

 ## Setup & Run

@@ -10,9 +10,9 @@ You should have the following set up:

 Simply fill in the fields in your browser and click `Send`. In your browser you will see the message sent to the SP, followed by the response from the SP. In your console you will see the logged incoming message from the UC, and the reply message to itfrom the SP.  

-<img src="../../images/tutorial_image_5.png"/>
+<img src="../../../images/tutorial_image_5.png"/>

-This small project can be used as a template to start conceptualizing and developing more complex PEApps. Stay tuned for more soon, and if you're searching for inspiration check out the [community apps](../../community-resources/community-applications-and-guides.md) list! 
+This small project can be used as a template to start conceptualizing and developing more complex PEApps. Stay tuned for more soon, and if you're searching for inspiration check out the [community apps](../../../community-resources/community-applications-and-guides.md) list! 



@@ -248,7 +248,7 @@ npm start

 Return to [localhost:1234](http://localhost:1234/)) and you should see an updated UI.  

-<img src="../../images/tutorial_image_2.png"/>
+<img src="../../../images/tutorial_image_2.png"/>

 ## Connecting to your Nym Client

@@ -256,7 +256,7 @@ Follow instructions in the [Nym websocket client documentation](https://nymtech.

 Your User Client application code is connected to a Nym websocket client, and ready to send messages through the mixnet! 

-<img src="../../images/tutorial_image_1.png"/>
+<img src="../../../images/tutorial_image_1.png"/>

 In the next section, you will build the Service application you will send these messages to. 
 
@@ -0,0 +1,7 @@
+# Under Construction 
+
+Development on the Nym SDKs is currently paused - focus for the moment is on the NymVPN product and the deeper network modifications that it relies on. 
+
+As such, the tutorials that were previously here are now both fairly out of date and underpowered. Future tutorials looking at drop in replacements for `Fetch`, using the mixnet from C/C++ and Go via FFI and a few others will be coming in the future. 
+
+Although they have been removed, you can still find the [`developer tutorials repo`]() and the Markdown archives [here](). 
@@ -5,14 +5,6 @@
 # Architecture
 - [Network Overview](architecture/network-overview.md)
 - [Mixnet Traffic Flow](architecture/traffic-flow.md)
-<!-- TODO reintroduce this with themed images  -->
-<!-- - [Network Rewards](architecture/network-rewards.md) -->
-
-# Binaries
- [Pre-built Binaries](binaries/pre-built-binaries.md)
-    - [Binary Initialisation and Configuration](binaries/init-and-config.md)
- [Building from Source](binaries/building-nym.md)
-<!-- - [Version Compatibility Table](binaries/version-compatiblity.md) -->

 # Nodes
 - [Node Types (Previously Setup Guides)](nodes/overview.md)
@@ -21,34 +13,6 @@
    - [Network Requester](nodes/network-requester.md)
    - [Validator](nodes/validator.md)

-# Clients
- [Clients Overview](clients/overview.md)
- [Websocket Client](clients/websocket-client.md)
-  - [Setup & Run](clients/websocket/setup.md)
-  - [Configuration](clients/websocket/config.md)
-  - [Using Your Client](clients/websocket/usage.md)
-  - [Examples](clients/websocket/examples.md)
- [Socks5 Client](clients/socks5-client.md)
- [Webassembly Client](clients/webassembly-client.md)
- [Addressing System](clients/addressing-system.md)
-
-# SDK
- [Typescript SDK](sdk/typescript.md)
- [Rust SDK](sdk/rust/rust.md)
-  - [Message Types](sdk/rust/message-types.md)
-  - [Message Helpers](sdk/rust/message-helpers.md)
-  - [Troubleshooting](sdk/rust/troubleshooting.md)
-  - [Examples](sdk/rust/examples.md)
-    - [Simple Send](sdk/rust/examples/simple.md)
-    - [Create and Store Keys](sdk/rust/examples/keys.md)
-    - [Manual Storage](sdk/rust/examples/storage.md)
-    - [Anonymous Replies](sdk/rust/examples/surbs.md)
-    - [Use Custom Network Topology](sdk/rust/examples/custom-network.md)
-    - [Socks Proxy](sdk/rust/examples/socks.md)
-    - [Split Send and Receive](sdk/rust/examples/split-send.md)
-    - [Testnet Bandwidth Cred](sdk/rust/examples/credential.md)
-    - [Example Cargo file](sdk/rust/examples/cargo.md)
-
 # Wallet
 - [Desktop Wallet](wallet/desktop-wallet.md)
 - [CLI Wallet](wallet/cli-wallet.md)
@@ -56,21 +20,10 @@
 # Explorers
 - [Mixnet Explorer](explorers/mixnet-explorer.md)

-# Nyx Blockchain
- [Interacting with Nyx Chain and Smart Contracts](nyx/interacting-with-chain.md)
- [Smart Contracts](nyx/smart-contracts.md)
-    - [Mixnet Contract](nyx/mixnet-contract.md)
-    - [Vesting Contract](nyx/vesting-contract.md)
- [RPC Nodes](nyx/rpc-node.md)
- [Ledger Live Support](nyx/ledger-live.md)
-
 # Coconut
 - [Coconut](coconut.md)
 - [Bandwidth Credentials](bandwidth-credentials.md)

-# Tools
- [NymCLI](tools/nym-cli.md)
-
 ---
 # Misc.
 - [Code of Conduct](coc.md)
@@ -1,20 +0,0 @@
-# Binary Initialisation and Configuration
-
-All Nym binaries must first be made executable and initialised with `init` before being `run`. 
-
-To make a binary executable, open terminal in the same directory and run:
-
-```sh
-chmod +x <BINARY_NAME> 
-# for example: chmod +x nym-mixnode
-```
-
-The `init` command is usually where you pass flags specifying configuration arguments such as the gateway you wish to communicate with, the ports you wish your binary to listen on, etc. 
-
-The `init` command will also create the necessary keypairs and configuration files at `~/.nym/<BINARY_TYPE>/<BINARY_ID>/` if these files do not already exist. **It will not overwrite existing keypairs if they are present.** 
-
-You can reconfigure your binaries at any time by editing the config file located at `~/.nym/<BINARY_TYPE>/<BINARY_ID>/config/config.toml` and restarting the binary process. 
-
-Once you have run `init`, you can start your binary with the `run` command, usually only accompanied by the `id` of the binary that you specified. 
-
-This `id` is **never** transmitted over the network, and is used to select which local config and key files to use for startup. 
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
mfahampshire	e8ead6aadf	updated module path	2024-05-31 15:19:34 +02:00
mfahampshire	91f75fd360	removed cflag import for test	2024-05-31 15:14:54 +02:00
mfahampshire	472e389d9d	updated module path.. again	2024-05-31 15:07:16 +02:00
mfahampshire	04bfb6a658	updated module path	2024-05-31 14:54:14 +02:00
mfahampshire	2900a63c21	updated module path	2024-05-31 14:49:29 +02:00
mfahampshire	9641e5f9dd	updated go mod import	2024-05-31 14:43:13 +02:00
mfahampshire	bcdc548289	added nym-cli-tool autogen	2024-05-14 16:55:09 +02:00
mfahampshire	e59ef01400	more reorg and dead links	2024-05-14 16:29:35 +02:00
mfahampshire	098155f6b9	fixed broken links in dev portal + moved a bunch of files from docs -> dev portal	2024-05-14 15:54:15 +02:00
mfahampshire	5ef17a506b	cont. with restructure	2024-05-13 22:45:59 +02:00
mfahampshire	46e858a097	reorg of files and SUMMARY files	2024-05-13 22:36:31 +02:00
benedetta davico	0902539332	Merge pull request #4583 from nymtech/release/2024.4-nutella Release 2024.4-nutella to master	2024-05-13 10:27:08 +02:00
benedettadavico	f0a4350e83	pruning version bump and changelog updates	2024-05-08 11:01:50 +02:00
import this	d5c2a01a34	[DOCs/operators]: 2024.4 nutella release changelog & mixnode ipv6 clarification (#4581 ) * edit IPv6 mixnode info * add mixnode ipv6 info and nuttela changelog * syntax edit	2024-05-07 15:49:29 +00:00
benedetta davico	b1c58b36fe	Merge pull request #4578 from nymtech/update-sign-nym-node updating sign commands to include nym-node	2024-05-07 14:50:51 +02:00
benedettadavico	dfbcc781db	extra space..	2024-05-07 14:36:43 +02:00
benedettadavico	5026960169	linting	2024-05-07 14:10:57 +02:00
benedetta davico	7c2710b61a	Merge pull request #4579 from nymtech/bugfix/exit-poisson [fix] apply disable_poisson_rate from internal NR/IPR cfgs	2024-05-07 14:09:44 +02:00
Jędrzej Stuczyński	bf9fc2d537	external clippy	2024-05-07 11:49:25 +01:00
Jędrzej Stuczyński	4182af9199	[fix] apply disable_poisson_rate from internal NR/IPR cfgs	2024-05-07 11:41:57 +01:00
benedettadavico	408d803344	adding both options	2024-05-07 12:34:26 +02:00
benedettadavico	c2a5d6c035	updating sign commands to nym-node	2024-05-07 12:20:55 +02:00
Tommy Verrall	1136901daf	Merge pull request #4572 from nymtech/bugfix/change-redirects changed nym-node redirects from 308 'Permanent Redirect' to 303: 'See Other'	2024-05-07 09:29:41 +01:00
Tommy Verrall	593a1da0ff	Merge pull request #4565 from nymtech/bugfix/delegations Bug fix: wallet delegations list is empty when RPC node doesn't hold block	2024-05-07 09:07:04 +01:00
Tommy Verrall	9c17b7c269	Merge pull request #4571 from nymtech/operators/ipv6-troubleshooting [DOC/operators]: More troubleshooting for IPv6 & install dependencies guides	2024-05-07 08:50:55 +01:00
serinko	df398dbe05	add mixnode IPv6 setup	2024-05-06 13:00:51 +02:00
Tommy Verrall	effd03b2f5	Merge pull request #4567 from nymtech/dependabot/npm_and_yarn/ejs-3.1.10 Bump ejs from 3.1.9 to 3.1.10	2024-05-06 11:49:46 +01:00
Sachin Kamath	e00db6adb9	docs: fix links to archive (#4576 )	2024-05-06 09:08:21 +00:00
Jędrzej Stuczyński	fd207d4699	changed nym-node redirects from 308 'Permanent Redirect' to 303: 'See Other'	2024-05-03 15:43:49 +01:00
serinko	b9126dfc0e	add troubleshooting for IPv6 & install dependencies	2024-05-03 13:19:59 +02:00
Jon Häggblad	7bbe153b8f	Add AuthenticationFailureWithPreexistingSharedKey and a few log statements (#4568 )	2024-05-03 09:53:53 +02:00
import this	36e1e73ed2	[DOCs]/operators: Create changelog page & add more nym-node troubleshooting (#4570 ) * add note to binary download * initialise changelog page * finalise changelog draft * add local ID rename guide * remove old id * syntax edit * syntax edit * syntax edit	2024-05-02 19:11:02 +02:00
Mark Sinclair	6e23322ac4	Update nym-wallet/src/components/Delegation/DelegationList.tsx	2024-05-02 14:57:00 +01:00
Mark Sinclair	729eedc960	Update publish-nym-wallet-win10.yml	2024-05-02 13:45:51 +01:00
Mark Sinclair	025cbf5231	Update publish-nym-wallet-ubuntu.yml	2024-05-02 13:45:46 +01:00
Mark Sinclair	3db3959a74	Update publish-nym-wallet-macos.yml	2024-05-02 13:45:39 +01:00
fmtabbara	3ba83795d4	add error dialog	2024-05-02 11:22:34 +01:00
dependabot[bot]	39b01d10bd	Bump ejs from 3.1.9 to 3.1.10 Bumps [ejs](https://github.com/mde/ejs) from 3.1.9 to 3.1.10. - [Release notes](https://github.com/mde/ejs/releases) - [Commits](https://github.com/mde/ejs/compare/v3.1.9...v3.1.10) --- updated-dependencies: - dependency-name: ejs dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>	2024-05-02 07:02:37 +00:00
fmtabbara	6060ce5fb8	fix error tooltip overflow	2024-05-01 23:38:06 +01:00
Mark Sinclair	8fbad9cad8	Remove test errors	2024-05-01 19:33:10 +01:00
Mark Sinclair	650865e59a	Wallet delegations: slow refresh from 1 min to 5 mins	2024-05-01 18:02:34 +01:00
Mark Sinclair	08e580ec8b	Wallet delegations list - add an error to each row, and display as a tooltip if present	2024-05-01 17:59:46 +01:00
Mark Sinclair	ad86ec9315	Wallet delegations: add more error information	2024-05-01 15:59:45 +01:00
Mark Sinclair	53ab4c8ec9	Wallet delegations: tap errors in requests per delegation. Return an error with strings of all sub errors.	2024-05-01 15:24:29 +01:00