This release is a pre-release and may not be stable for production use.
## cexbot
A bot for the cex.io cryptocurrency mining marketplace
this is a really early version, recommend you check updates frequently
## Signup
Go to [cex.io](https://cex.io/r/0/nikcub/0/)
Click signup
Fill out form, confirm etc.
Once signed up go to https://www.cex.io/trade/profile
Scroll down to API Access
Optional enter your IP address
Check all API access permission boxes
Click ‘generate’
Copy the key and secret (see Config section)
Click ‘activate’
Click the link in the activation email to confirm API access
## Install
pip install cexbot
## Dev Install
git clone –depth=0 https://github.com/nikcub/cexbot.git
pip install -r requirements.txt
## Config
cexbot needs to know your username, API key and secret.
cexbot genconfig
will generate a blank config file at cex.cnf. Edit the file and fill in username, key and secret
optionally you can store the secret in an environment variable called CEXBOT_SECRET.
## Usage
see
cexbot -h
new features being added all the time.
## Update
Update frequently, new features being added all the time.
cexbot update
1 maintainer
Metadata
1 maintainer
Release files for cexbot 0.0.1-dev-
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cexbot-0.0.1-dev-.tar.gz | 2.7 kB | Without provenance | Details for cexbot-0.0.1-dev-.tar.gz |
Release files / cexbot-0.0.1-dev-.tar.gz
| Download URL | cexbot-0.0.1-dev-.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f43d2b965415b08e8198992eb77910d49c3093cc05d41e50fdb8710238e2cab7
|
|
BLAKE2b-256 checksum How to use checksums |
5c36b19ef509c16c4fb891a134be0d90e71b998961579537416376d06a935702
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cexbot 0.0.1-dev-
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
