meshtensor-cli 9.28.0
Meshtensor CLI
Requires Python: >=3.9

<div align="center">

# Meshtensor CLI <!-- omit in toc -->
[![Discord Chat](https://img.shields.io/discord/308323056592486420.svg)](https://discord.gg/meshtensor)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) 
[![PyPI version](https://badge.fury.io/py/meshtensor_cli.svg)](https://badge.fury.io/py/meshtensor_cli)

---

## Internet-scale Neural Networks <!-- omit in toc -->

[SDK](https://github.com/borgg-dev/meshtensor/tree/master) • [Wallet](https://github.com/borgg-dev/btwallet) • [Research](https://meshtensor.com/whitepaper)

</div>

- [Documentation](#documentation)
- [Install on macOS and Linux](#install-on-macos-and-linux)
  - [Install from source](#install-from-source)
- [Install on Windows](#install-on-windows)
- [Verify the installation](#verify-the-installation)
- [Configuration](#configuration)
  - [Example config file](#example-config-file)
- [License](#license)

---

The Meshtensor CLI, `meshcli`, is a powerful command line tool for the Meshtensor platform. You can use it on any macOS, Linux or WSL terminal to manage all common operations like creating a wallet, registering a subnet or a neuron, delegating your MESH, viewing Senate proposals and voting for them, and much more. Help information can be invoked for every command and option with `--help` option.

![meshcli screenshot](./assets/meshcli-screenshot.png)

---

## Documentation

Installation steps are described below. For a full documentation on how to use `meshcli`, see the [Meshtensor CLI section](https://docs.meshtensor.com/meshcli) on the developer documentation site.

---

## Install on macOS and Linux

You can install `meshcli` on your local machine directly from source, PyPI, or Homebrew. 
**Make sure you verify your installation after you install**.

### For macOS users
Note that the macOS preinstalled CPython installation is compiled with LibreSSL instead of OpenSSL. There are a number
of issues with LibreSSL, and as such is not fully supported by the libraries used by meshcli. Thus we highly recommend, if 
you are using a Mac, to first install Python from [Homebrew](https://brew.sh/). Additionally, the Rust FFI bindings 
[if installing from precompiled wheels (default)] require the Homebrew-installed OpenSSL pacakge. If you choose to use
the preinstalled Python version from macOS, things may not work completely.


### Install from [PyPI](https://pypi.org/project/meshtensor/)

Run 
```
pip install -U meshtensor-cli
```

Alternatively, if you prefer to use [uv](https://pypi.org/project/uv/):
```
uv pip install meshtensor-cli
```

### Install from [Homebrew](https://formulae.brew.sh/formula/meshcli#default)

```shell
brew install meshcli
```

### Install from source

1. Create and activate a virtual environment.

```bash
python3 -m venv meshcli_venv
source meshcli_venv/bin/activate
```

2. Clone the Meshtensor CLI repo.

```bash
git clone https://github.com/borgg-dev/meshcli.git
```

3. `cd` into `meshcli` directory.

```bash
cd meshcli
```

4.  Install


```bash
pip3 install .
```

### Also install meshtensor (SDK)

If you prefer to install the meshcli alongside the meshtensor SDK, you can do this in a single command with

```
pip install -U meshtensor[cli]
```

---

## Install on Windows

To install and run Meshtensor SDK on Windows you must install [**WSL 2** (Windows Subsystem for Linux)](https://learn.microsoft.com/en-us/windows/wsl/about) on Windows and select [Ubuntu Linux distribution](https://github.com/ubuntu/WSL/blob/main/docs/guides/install-ubuntu-wsl2.md). 

After you installed the above, follow the same installation steps described above in [Install on macOS and Linux](#install-on-macos-and-linux).

**ALERT**: **Limited support on Windows for Meshtensor operations**
While wallet transactions like delegating, transfer, registering, staking can be performed on a Windows machine using WSL 2, the subnet mining and subnet validating operations are not recommended and are not supported on Windows machines.

---

## Verify the installation

```bash
meshcli --version
```

The above command will show you the version of the `meshcli` you just installed.

---

## Configuration

You can set the commonly used values, such as your hotkey and coldkey names, the default chain URL or the network name you use, and more, in `config.yml`. You can override these values by explicitly passing them in the command line for any `meshcli` command.

### Example config file

The default location of the config file is: `~/.meshtensor/config.yml`. An example of a `config.yml` is shown below:

```yaml
network: local
use_cache: true
dashboard_path: null
disk_cache: true
rate_tolerance: null
safe_staking: true
wallet_hotkey: default
wallet_name: coldkey-user1
wallet_path: ~/.meshtensor/wallets
metagraph_cols:
  ACTIVE: true
  AXON: true
  COLDKEY: true
  CONSENSUS: true
  DIVIDENDS: true
  EMISSION: true
  HOTKEY: true
  INCENTIVE: true
  RANK: true
  STAKE: true
  TRUST: true
  UID: true
  UPDATED: true
  VAL: true
  VTRUST: true
```

**For more help:**

```bash
meshcli config --help
```

### ENV VARS
MeshCLI accepts a few environment variables that can alter how it works:
 - USE_TORCH (default 0): If set to 1, will use torch instead of numpy
 - DISK_CACHE (default 0, also settable in config): If set to 1 (or set in config), will use disk caching for various safe-cachable substrate
calls (such as block number to block hash mapping), which can speed up subsequent calls.
 - MeshCLI_CONFIG_PATH (default `~/.meshtensor/config.yml`): This will set the config file location, creating if it does not exist.
 - MeshCLI_DEBUG_FILE (default `~/.meshtensor/debug.txt`): The file stores the most recent's command's debug log. 

---

## Debugging
If a command is failing with an odd error, you can usually rerun the command with `--verbose` for a more detailed output
of any errors/exceptions that occur. This should be done prior to reporting the issue, as it helps us substantially in 
determining the root cause of issues. 

Additionally, you can pull a debug log.

MeshCLI will store a debug log for every command run. This file is overwritten for each new command run. The default location
of this file is `~/.meshtensor/debug.txt` and can be set with the `MeshCLI_DEBUG_FILE` env var (see above section).

The debug log will **NOT** contain any sensitive data (private keys), and is intended to be sent to the developers
for debugging. This file contains basic information about the command being run, the config, and the back and forth of requests and responses
to and from the chain.

If you encounter an issue, and would like to save the file somewhere it won't be overwritten, run `meshcli --debug`,
and set the save file location. We recommend doing this first before anything, and then starting your debugging with
us on our [Discord](https://discord.gg/meshtensor), or by opening an issue on [GitHub](https://github.com/borgg-dev/meshcli/issues/new)
(where you can also upload your debug file).


Steps:
1. Re-run the command with `--verbose` at the end, e.g. `meshcli st remove --verbose`
2. Run `meshcli --debug` to save the debug log
3. Report the issue on GitHub or Discord

---

## License
The MIT License (MIT)
Copyright © 2024 Grobb

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.