base on Kaspa full-node reference implementation and related libraries in the Rust programming language <h1>Kaspa On Rust</h1> Welcome to the Rust-based implementation of the Kaspa full-node and its ancillary libraries. The contained node release serves as a drop-in replacement to the established <a href="https://github.com/kaspanet/kaspad">Golang node</a> and to date is the recommended node software for the Kaspa network, introducing developers to the possibilities of Rust in the Kaspa network's context. We invite developers and blockchain enthusiasts to collaborate, test, and optimize our Rust implementation. Each line of code here is an opportunity to contribute to the open-source blockchain movement, shaping a platform designed for scalability and speed without compromising on security and decentralization. Your feedback, contributions, and issue reports will be integral to evolving this codebase and continuing its maturity as a reliable node in the Kaspa network. The default branch of this repository is `master` and new contributions are constantly merged into it. For a stable branch corresponding to the latest stable release please pull and compile the `stable` branch. ## Installation <details> <summary>Building on Linux</summary> 1. Install general prerequisites ```bash sudo apt install curl git build-essential libssl-dev pkg-config ``` 2. Install Protobuf (required for gRPC) ```bash sudo apt install protobuf-compiler libprotobuf-dev #Required for gRPC ``` 3. Install the clang toolchain (required for RocksDB and WASM secp256k1 builds) ```bash sudo apt-get install clang-format clang-tidy \ clang-tools clang clangd libc++-dev \ libc++1 libc++abi-dev libc++abi1 \ libclang-dev libclang1 liblldb-dev \ libllvm-ocaml-dev libomp-dev libomp5 \ lld lldb llvm-dev llvm-runtime \ llvm python3-clang ``` 3. Install the [rust toolchain](https://rustup.rs/) If you already have rust installed, update it by running: `rustup update` 4. Install wasm-pack ```bash cargo install wasm-pack ``` 4. Install wasm32 target ```bash rustup target add wasm32-unknown-unknown ``` 5. Clone the repo ```bash git clone https://github.com/kaspanet/rusty-kaspa cd rusty-kaspa ``` </details> <details> <summary>Building on Windows</summary> 1. [Install Git for Windows](https://gitforwindows.org/) or an alternative Git distribution. 2. Install [Protocol Buffers](https://github.com/protocolbuffers/protobuf/releases/download/v21.10/protoc-21.10-win64.zip) and add the `bin` directory to your `Path` 3. Install [LLVM-15.0.6-win64.exe](https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.6/LLVM-15.0.6-win64.exe) Add the `bin` directory of the LLVM installation (`C:\Program Files\LLVM\bin`) to PATH set `LIBCLANG_PATH` environment variable to point to the `bin` directory as well **IMPORTANT:** Due to C++ dependency configuration issues, LLVM `AR` installation on Windows may not function correctly when switching between WASM and native C++ code compilation (native `RocksDB+secp256k1` vs WASM32 builds of `secp256k1`). Unfortunately, manually setting `AR` environment variable also confuses C++ build toolchain (it should not be set for native but should be set for WASM32 targets). Currently, the best way to address this, is as follows: after installing LLVM on Windows, go to the target `bin` installation directory and copy or rename `LLVM_AR.exe` to `AR.exe`. 4. Install the [rust toolchain](https://rustup.rs/) If you already have rust installed, update it by running: `rustup update` 5. Install wasm-pack ```bash cargo install wasm-pack ``` 6. Install wasm32 target ```bash rustup target add wasm32-unknown-unknown ``` 7. Clone the repo ```bash git clone https://github.com/kaspanet/rusty-kaspa cd rusty-kaspa ``` </details> <details> <summary>Building on Mac OS</summary> 1. Install Protobuf (required for gRPC) ```bash brew install protobuf ``` 2. Install llvm. The default XCode installation of `llvm` does not support WASM build targets. To build WASM on MacOS you need to install `llvm` from homebrew (at the time of writing, the llvm version for MacOS is 16.0.1). ```bash brew install llvm ``` **NOTE:** Homebrew can use different keg installation locations depending on your configuration. For example: - `/opt/homebrew/opt/llvm` -> `/opt/homebrew/Cellar/llvm/16.0.1` - `/usr/local/Cellar/llvm/16.0.1` To determine the installation location you can use `brew list llvm` command and then modify the paths below accordingly: ```bash % brew list llvm /usr/local/Cellar/llvm/16.0.1/bin/FileCheck /usr/local/Cellar/llvm/16.0.1/bin/UnicodeNameMappingGenerator ... ``` If you have `/opt/homebrew/Cellar`, then you should be able to use `/opt/homebrew/opt/llvm`. Add the following to your `~/.zshrc` file: ```bash export PATH="/opt/homebrew/opt/llvm/bin:$PATH" export LDFLAGS="-L/opt/homebrew/opt/llvm/lib" export CPPFLAGS="-I/opt/homebrew/opt/llvm/include" export AR=/opt/homebrew/opt/llvm/bin/llvm-ar ``` Reload the `~/.zshrc` file ```bash source ~/.zshrc ``` 3. Install the [rust toolchain](https://rustup.rs/) If you already have rust installed, update it by running: `rustup update` 4. Install wasm-pack ```bash cargo install wasm-pack ``` 4. Install wasm32 target ```bash rustup target add wasm32-unknown-unknown ``` 5. Clone the repo ```bash git clone https://github.com/kaspanet/rusty-kaspa cd rusty-kaspa ``` </details> <details> <summary>Building WASM32 SDK</summary> Rust WebAssembly (WASM) refers to the use of the Rust programming language to write code that can be compiled into WebAssembly, a binary instruction format that runs in web browsers and NodeJs. This allows for easy development using JavaScript and TypeScript programming languages while retaining the benefits of Rust. WASM SDK components can be built from sources by running: - `./build-release` - build a full release package (includes both release and debug builds for web and nodejs targets) - `./build-docs` - build TypeScript documentation - `./build-web` - release web build - `./build-web-dev` - development web build - `./build-nodejs` - release nodejs build - `./build-nodejs-dev` - development nodejs build IMPORTANT: do not use `dev` builds in production. They are significantly larger, slower and include debug symbols. ### Requirements - NodeJs (v20+): https://nodejs.org/en - TypeDoc: https://typedoc.org/ ### Builds & documentation - Release builds: https://github.com/kaspanet/rusty-kaspa/releases - Developer builds: https://kaspa.aspectron.org/nightly/downloads/ - Developer TypeScript documentation: https://kaspa.aspectron.org/docs/ </details> <details> <summary> Kaspa CLI + Wallet </summary> `kaspa-cli` crate provides a cli-driven RPC interface to the node and a terminal interface to the Rusty Kaspa Wallet runtime. These wallets are compatible with WASM SDK Wallet API and Kaspa NG projects. ```bash cd cli cargo run --release ``` </details> <details> <summary> Local Web Wallet </summary> Run an http server inside of `wallet/wasm/web` folder. If you don't have once, you can use the following: ```bash cd wallet/wasm/web cargo install basic-http-server basic-http-server ``` The *basic-http-server* will serve on port 4000 by default, so open your web browser and load http://localhost:4000 The framework is compatible with all major desktop and mobile browsers. </details> ## Running the node **Start a mainnet node** ```bash cargo run --release --bin kaspad # or with UTXO-index enabled (needed when using wallets) cargo run --release --bin kaspad -- --utxoindex ``` **Start a testnet node** ```bash cargo run --release --bin kaspad -- --testnet ``` **Testnet 11** For participation in the 10BPS test network (TN11), see the following detailed [guide](docs/testnet11.md). <details> <summary> Using a configuration file </summary> ```bash cargo run --release --bin kaspad -- --configfile /path/to/configfile.toml # or cargo run --release --bin kaspad -- -C /path/to/configfile.toml ``` - The config file should be a list of \<CLI argument\> = \<value\> separated by newlines. - Whitespace around the `=` is fine, `arg=value` and `arg = value` are both parsed correctly. - Values with special characters like `.` or `=` will require quoting the value i.e \<CLI argument\> = "\<value\>". - Arguments with multiple values should be surrounded with brackets like `addpeer = ["10.0.0.1", "1.2.3.4"]`. For example: ``` testnet = true utxoindex = false disable-upnp = true perf-metrics = true appdir = "some-dir" netsuffix = 11 addpeer = ["10.0.0.1", "1.2.3.4"] ``` Pass the `--help` flag to view all possible arguments ```bash cargo run --release --bin kaspad -- --help ``` </details> <details> <summary> wRPC </summary> wRPC subsystem is disabled by default in `kaspad` and can be enabled via: JSON protocol: ```bash --rpclisten-json = <interface:port> # or use the defaults for current network --rpclisten-json = default ``` Borsh protocol: ```bash --rpclisten-borsh = <interface:port> # or use the defaults for current network --rpclisten-borsh = default ``` **Sidenote:** Rusty Kaspa integrates an optional wRPC subsystem. wRPC is a high-performance, platform-neutral, Rust-centric, WebSocket-framed RPC implementation that can use [Borsh](https://borsh.io/) and JSON protocol encoding. JSON protocol messaging is similar to JSON-RPC 1.0, but differs from the specification due to server-side notifications. [Borsh](https://borsh.io/) encoding is meant for inter-process communication. When using [Borsh](https://borsh.io/) both client and server should be built from the same codebase. JSON protocol is based on Kaspa data structures and is data-structure-version agnostic. You can connect to the JSON endpoint using any WebSocket library. Built-in RPC clients for JavaScript and TypeScript capable of running in web browsers and Node.js are available as a part of the Kaspa WASM framework. </details> ## Benchmarking & Testing <details> <summary>Simulation framework (Simpa)</summary> The current codebase supports a full in-process network simulation, building an actual DAG over virtual time with virtual delay and benchmarking validation time (following the simulation generation). To see the available commands ```bash cargo run --release --bin simpa -- --help ``` The following command will run a simulation to produce 1000 blocks with communication delay of 2 seconds and 8 BPS (blocks per second) while attempting to fill each block with up to 200 transactions. ```bash cargo run --release --bin simpa -- -t=200 -d=2 -b=8 -n=1000 ``` </details> <details> <summary>Heap Profiling</summary> Heap-profiling in `kaspad` and `simpa` can be done by enabling `heap` feature and profile using the `--features` argument ```bash cargo run --bin kaspad --profile heap --features=heap ``` It will produce `{bin-name}-heap.json` file in the root of the workdir, that can be inspected by the [dhat-viewer](https://github.com/unofficial-mirror/valgrind/tree/master/dhat) </details> <details> <summary>Tests</summary> **Run unit and most integration tests** ```bash cd rusty-kaspa cargo test --release // or install nextest and run ``` **Using nextest** ```bash cd rusty-kaspa cargo nextest run --release ``` </details> <details> <summary>Lints</summary> ```bash cd rusty-kaspa ./check ``` </details> <details> <summary>Benchmarks</summary> ```bash cd rusty-kaspa cargo bench ``` </details> <details> <summary>Logging</summary> Logging in `kaspad` and `simpa` can be [filtered](https://docs.rs/env_logger/0.10.0/env_logger/#filtering-results) by either: 1. Defining the environment variable `RUST_LOG` 2. Adding the --loglevel argument like in the following example: ``` (cargo run --bin kaspad -- --loglevel info,kaspa_rpc_core=trace,kaspa_grpc_core=trace,consensus=trace,kaspa_core=trace) 2>&1 | tee ~/rusty-kaspa.log ``` In this command we set the `loglevel` to `INFO`. </details> ", Assign "at most 3 tags" to the expected json: {"id":"5235","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"