mirror of
https://github.com/nymtech/nym.git
synced 2025-12-04 16:26:07 -05:00
No description
| .github | ||
| .reuse | ||
| .wellknown/wallet | ||
| assets | ||
| clients | ||
| common | ||
| contracts | ||
| cpu-cycles | ||
| docker | ||
| documentation | ||
| envs | ||
| examples | ||
| explorer-v2 | ||
| gateway | ||
| LICENSES | ||
| nym-api | ||
| nym-authenticator-client | ||
| nym-browser-extension | ||
| nym-credential-proxy | ||
| nym-data-observatory | ||
| nym-gateway-probe | ||
| nym-ip-packet-client | ||
| nym-network-monitor | ||
| nym-node | ||
| nym-node-status-api | ||
| nym-outfox | ||
| nym-registration-client | ||
| nym-signers-monitor | ||
| nym-statistics-api | ||
| nym-validator-rewarder | ||
| nym-wallet | ||
| nyx-chain-watcher | ||
| ppa | ||
| scripts | ||
| sdk | ||
| service-providers | ||
| sqlx-pool-guard | ||
| tools | ||
| ts-packages | ||
| wasm | ||
| .dockerignore | ||
| .env.sample-dev | ||
| .gitattributes | ||
| .github_changelog_generator | ||
| .gitignore | ||
| .ruby-version | ||
| about.hbs | ||
| about.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| clippy.toml | ||
| deny.toml | ||
| lefthook.yml | ||
| lerna.json | ||
| Makefile | ||
| nym-api.dockerfile | ||
| nym-network-monitor.dockerfile | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| sonar-project.properties | ||
| yarn.lock | ||
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.nym-cli- a tool for interacting with the network from the CLI.
┌─►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 here.
Developing
References for developers:
Developer chat
You can chat to us in the #dev channel on Matrix or on the Nym Forum.
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 Terms and Conditions can be found here.
Getting Started
yarn install
yarn build