Jon Häggblad
32e2557456
* Fix tokio error in 1.39
Fix the error generated by tokio 1.39
72 | / tokio::select! {
173 | | daemon_res = &mut fused_runner => {
174 | | warn!("the daemon has terminated by itself - was it a short lived command?");
175 | | let exit_status = daemon_res?;
... |
179 | | event = &mut self.upgrade_plan_watcher.next() => {
| | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ creates a temporary value which is freed while still in use
... |
201 | | }
202 | | }
| | -
| | |
| |_____________temporary value is freed at the end of this statement
| borrow later used here
and
62 | / select! {
63 | | connection_message = &mut mix_receiver.next() => {
| | ^^^^^^^^^^^^^^^^^^^ creates a temporary value which is freed while still in use
64 | | if let Some(connection_message) = connection_message {
65 | | if deal_with_message(connection_message, &mut writer, &local_destination_address, &remote_source_address, connection_id).await {
... |
86 | | }
87 | | }
| | -
| | |
| |_________temporary value is freed at the end of this statement
| borrow later used here
* Upgrade to tokio 1.39.1
* Simpler attempt
* Revert fixes and instead bump to tokio 1.39.2
* update
* bump msrv for nym-node-tester-wasm
The Nym Privacy Platform
The platform is composed of multiple Rust crates. Top-level executable binary crates include:
nym-node- a tool for running a node within the Nym network. Nym Nodes containing functionality such asmixnode,entry-gatewayandexit-gatewayare fundamental components of Nym Mixnet architecture. Nym Nodes are ran by decentralised node operators. Read more aboutnym-nodein Operators Guide documentation. Network functionality ofnym-node(labeled with--modeflag) can be:mixnode- shuffles Sphinx packets together to provide privacy against network-level attackers.gateway- acts sort of like a mailbox for mixnet messages, which removes the need for direct delivery to potentially offline or firewalled devices. Gateways can be further categorized asentry-gatewayandexit-gateway. The latter has an extra embedded IP packet router and Network requester to route data to the internet.
nym-client- an executable which you can build into your own applications. Use it for interacting with Nym nodes.nym-socks5-client- a Socks5 proxy you can run on your machine and use with existing applications.nym-explorer- a (projected) block explorer and (existing) mixnet viewer.nym-wallet- a desktop wallet implemented using the Tauri framework.
┌─►mix──┐ mix mix
│ │
Entry │ │ Exit
client ───► Gateway ──┘ mix │ mix ┌─►mix ───► Gateway ───► internet
│ │
│ │
mix └─►mix──┘ mix
Building
- Platform build instructions are available on Nym Operators Guide documentation.
- Wallet build instructions are available on Nym Technical docs.
Developing
There's a sandbox.env file provided which you can rename to .env if you want convenient testing environment. Read more about sandbox environment in our Operators Guide page.
References for developers:
- Developers Portal
- Typescript SDKs
- Technical Documentation - Nym network overview
- Release Cycle - git flow
Developer chat
You can chat to us in two places:
Tokenomics & Rewards
Nym network economic incentives, operator and validator rewards, and scalability of the network are determined according to the principles laid out in the section 6 of Nym Whitepaper. Initial reward pool is set to 250 million Nym, making the circulating supply 750 million Nym.
Licensing and copyright information
This is a monorepo and components that make up Nym as a system are licensed individually, so for accurate information, please check individual files.
As a general approach, licensing is as follows this pattern:
- applications and binaries are GPLv3
- libraries and components are Apache 2.0 or MIT
- documentation is Apache 2.0 or CC0-1.0
Nym Node Operators and Validators Temrs and Conditions can be found here.