compute-horde
Receipts
Common django models
This library contains common Django models for the receipts.
To use them, update your INSTALLED_APPS:
INSTALLED_APPS = [
...,
'compute_horde.receipts',
...,
]
Migrations
To make new migrations after doing some changes in the model files, run:
DJANGO_SETTINGS_MODULE=compute_horde.settings uv run django-admin makemigrations
Blockchain
This library contains common logic for interacting with the blockchain (subtensor).
To use it, update your INSTALLED_APPS:
INSTALLED_APPS = [
...,
'compute_horde.blockchain',
...,
]
Block cache
This is a cheap-to-query store that stores the current block number.
Usage:
- Add
compute_horde.blockchain.tasks.update_block_cacheas a Celery Beat task with some reasonable frequency (like 6s)- Make sure to set the expires= option for the beat entry to about the same value to avoid the tasks piling up
- To get the current block number from cache, use
aget_current_block(orget_current_block).
Validators
This app contains common logic for updating validators of a given network.
To use it, update your INSTALLED_APPS:
INSTALLED_APPS = [
...,
'compute_horde.validators',
...,
]
Models
This app works with models from other projects; it doesn't define its own.
To use it, you need to specify COMPUTE_HORDE_VALIDATOR_MODEL in your settings.py,
in the form of <app_label>.<model_name>. This model must have at least two fields: public key (string) and active (bool).
Other settings are:
COMPUTE_HORDE_VALIDATOR_KEY_FIELD
COMPUTE_HORDE_VALIDATOR_ACTIVE_FIELD
COMPUTE_HORDE_VALIDATOR_DEBUG_FIELD # optional
BITTENSOR_NETUID
BITTENSOR_NETWORK
Tasks
There is a periodic task to update the validators in the database. To use it, define the settings above and add
compute_horde.validators.tasks.fetch_validators to your celery beat config.
1 maintainer
Metadata
1 maintainer
Release files for compute-horde 0.0.26
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| compute_horde-0.0.26.tar.gz | 46.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compute_horde-0.0.26-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 92.8 kB
Release files / compute_horde-0.0.26.tar.gz
| Download URL | compute_horde-0.0.26.tar.gz |
|---|---|
| Size | 46.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33d4adc3b91af65719eaf589f9bca9c8827193205598439f70c119870ef5672e
|
|
BLAKE2b-256 checksum How to use checksums |
b869ad416b371c4ce5e5a64509ccd546316f6e18cf2c4e487dc78af7d532e49e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2025.
Transparency logRelease files / compute_horde-0.0.26-py3-none-any.whl
| Download URL | compute_horde-0.0.26-py3-none-any.whl |
|---|---|
| Size | 46.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
123c15bc7ebe3b76e92c97158068bb4c9a838a86ba220ab2225e8df7263c9ba3
|
|
BLAKE2b-256 checksum How to use checksums |
820c54e4af9853125c6b2de2c78e5f5b745f932e407c6dca949a6322604706b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2025.
Transparency log
