base on Rust implementation of Namada, a Proof-of-Stake L1 for interchain asset-agnostic privacy # Namada [![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](./LICENSE) ![CI Status](https://github.com/anoma/namada/actions/workflows/ci.yml/badge.svg?branch=main) ## Overview [Namada](http://namada.net) is a Proof-of-Stake L1 for multichain asset-agnostic data protection. Namada uses CometBFT consensus and enables multi-asset shielded transfers for any native or non-native asset. Namada features full IBC protocol support, a modern proof-of-stake system with cubic slashing, and a stake-weighted on-chain governance mechanism. Users of Namada's MASP (Multi-Asset Shielded Pool) are rewarded for their contributions to the shielded set in the form of native protocol tokens. A multi-asset shielded transfer wallet is provided in order to facilitate safe user interaction with the protocol. * Blogpost: [Introducing Namada: Multichain Asset-agnostic Data Protection](https://namada.net/blog/introducing-namada-multichain-asset-agnostic-data-protection) ## ๐Ÿ““ Docs * [User guides](https://docs.namada.net/) * [Specs](https://specs.namada.net/) * Rust docs can be built with `cargo doc --open` (add `--no-deps` to only build docs for local crates) ## Warning > Here lay dragons: this codebase is still experimental, try at your own risk! ## ๐Ÿ’พ Installing There is a single command to build and install Namada executables from source (the node, the client and the wallet). This command will also verify that a compatible version of [CometBFT](#dependencies) is available and if not, attempt to install it. Note that currently at least 16GB RAM is needed to build from source. ```shell make install ``` After installation, the main `namada` executable will be available on path. To find how to use it, check out the [User Guide section of the docs](https://docs.namada.net/users). For more detailed instructions and more install options, see the [Install section](https://docs.namada.net/introduction/install) of the User Guide. ## โš™๏ธ Development ```shell # Build the provided validity predicate and transaction wasm modules make build-wasm-scripts-docker ``` ### Before submitting a PR, please make sure to run the following ```shell # Format the code make fmt # Lint the code make clippy ``` ## ๐Ÿงพ Logging To change the log level, set `NAMADA_LOG` environment variable to one of: * `error` * `warn` * `info` * `debug` * `trace` The default is set to `info` for all the modules, except for CometBFT ABCI, which has a lot of `debug` logging. For more fine-grained logging levels settings, please refer to the [tracing subscriber docs](https://docs.rs/tracing-subscriber/0.2.18/tracing_subscriber/struct.EnvFilter.html#directives) for more information. To switch on logging in tests that use `#[test]` macro from `test_log::test`, use `RUST_LOG` with e.g. `RUST_LOG=info cargo test -- --nocapture`. ## How to contribute Please see the [contributing page](./CONTRIBUTING.md). ### Dependencies The ledger currently requires [CometBFT v0.37.15](https://github.com/cometbft/cometbft/releases/tag/v0.37.15) is installed and available on path. This can be achieved through following [these instructions](https://github.com/cometbft/cometbft/blob/main/docs/tutorials/install.md). #### Hermes We maintain a fork of [hermes](https://github.com/heliaxdev/hermes) that adds support for Namada. Compatibility table with Namada: | Namada binaries | Hermes | | ----------- | ----------- | | v101.0.0 | [1.13.0](https://github.com/informalsystems/hermes/releases/tag/v1.13.0) | | v1.1.1 | [1.11.0](https://github.com/informalsystems/hermes/releases/tag/v1.11.0) | | v1.1.0 | [1.10.5-namada-beta18](https://github.com/heliaxdev/hermes/releases/tag/v1.10.5-namada-beta18) | | v1.0.0 | [1.10.4-namada-beta17-rc2](https://github.com/heliaxdev/hermes/releases/tag/v1.10.4-namada-beta17-rc2) | ", Assign "at most 3 tags" to the expected json: {"id":"3900","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"