Metadata-Version: 2.4
Name: dexbtx-miner
Version: 0.0.0
Summary: DEXBTX miner — install via install.sh; this PyPI listing is a redirect stub.
Author: DEXBTX
License: MIT
Project-URL: Homepage, https://minebtx.com
Project-URL: Repository, https://github.com/dexbtx/minebtx
Project-URL: Install, https://minebtx.com/install.sh
Keywords: dexbtx,btx,mining,stratum,miner
Classifier: Development Status :: 7 - Inactive
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Internet
Requires-Python: >=3.10
Description-Content-Type: text/markdown

# dexbtx-miner

**This is the PyPI redirect stub.** The real DEXBTX miner is not distributed via
PyPI — it ships through an install script that also drops the matching
`btx-gbt-solve` CUDA solver binary (which pip cannot deliver).

## Install the real miner

```bash
curl -sSL https://minebtx.com/install.sh | bash
```

This script:

1. Pulls the matched `btx-gbt-solve` CUDA solver binary.
2. Runs `pip install --upgrade` against a GitHub-tagged tarball, replacing this
   stub package in-place — no manual cleanup needed.
3. Drops a starter config at `~/.dexbtx-miner/config.yaml`.

## Why a stub?

Because `pip install dexbtx-miner` is the natural first instinct for anyone
familiar with Python packaging. Without this stub, that command fails with
"package not found" and operators (or their AI agents) get stuck. The stub
gives them a clear redirect message and exits non-zero so automation halts
cleanly.

The stub is pinned at version `0.0.0` and will never be bumped — the real
miner's higher version (≥ `0.3.2`) trumps it on `pip install --upgrade`, so
the stub cannot accidentally downgrade an existing install.

## Links

- **Pool dashboard:** https://minebtx.com
- **Source:** https://github.com/dexbtx/minebtx
- **Releases:** https://github.com/dexbtx/minebtx/releases
