IPFS ACCELERATE
This is meant to be an extension of the Huggingface accelerate library, with the intent that the method load_checkpoint_and_dispatch() is going to be overloaded with a new function which will have some modular back ends, such as Libp2p, Akash, Lilypad, Huggingface Zero, Vast AI. If the model is already listed in the ipfs_model_manager there should be an associated hw_requirements key of the manifest. In the case of libp2p the request to do inference will go out to peers if there are peers in the network available to fulfill the task, otherwise a docker container will need to be launched with one of the providers here. The docker containers will will then be loaded with the ipfs_model_manager, and will use the from_auto_download() method to download the requested model and perform inference for the user.
Method #1 Huggingface Zero
Method #2 Akash
Method #3 Lilypad
Method #4 Vast AI
IPFS Huggingface Bridge:
for huggingface transformers python library visit: https://github.com/endomorphosis/ipfs_transformers/
for huggingface datasets python library visit: https://github.com/endomorphosis/ipfs_datasets/
for faiss KNN index python library visit: https://github.com/endomorphosis/ipfs_faiss
for transformers.js visit:
https://github.com/endomorphosis/ipfs_transformers_js
for orbitdb_kit nodejs library visit: https://github.com/endomorphosis/orbitdb_kit/
for fireproof_kit nodejs library visit: https://github.com/endomorphosis/fireproof_kit
for ipfs_kit nodejs library visit: https://github.com/endomorphosis/ipfs_kit/
for python model manager library visit: https://github.com/endomorphosis/ipfs_model_manager/
for nodejs model manager library visit: https://github.com/endomorphosis/ipfs_model_manager_js/
for nodejs ipfs huggingface scraper with pinning services visit: https://github.com/endomorphosis/ipfs_huggingface_scraper/
for ipfs agents visit: https://github.com/endomorphosis/ipfs_agents/
for ipfs accelerate visit: https://github.com/endomorphosis/ipfs_accelerate/
Author - Benjamin Barber QA - Kevin De Haan
Metadata
Release files for libp2p-accelerate-py 0.0.3
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 | |
|---|---|---|---|---|
| libp2p_accelerate_py-0.0.3.tar.gz | 14.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| libp2p_accelerate_py-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.3 kB
Release files / libp2p_accelerate_py-0.0.3.tar.gz
| Download URL | libp2p_accelerate_py-0.0.3.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
382907a5e9d2a30d12d72767efd8e9b9db51700286e4cab2846963d86096c8c1
|
|
BLAKE2b-256 checksum How to use checksums |
572f18f495ff23aa3f2f2cca685ef20db9f2824e0c597b597a72bc89b9289095
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / libp2p_accelerate_py-0.0.3-py3-none-any.whl
| Download URL | libp2p_accelerate_py-0.0.3-py3-none-any.whl |
|---|---|
| Size | 14.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f036e72d1037edc06c8bb9ffa88e363811f84db25755e4ad1a95e9ddb3d734d
|
|
BLAKE2b-256 checksum How to use checksums |
0451ec22eb121d1a621259f873f1bdfe819cca55bc75c8be2a8d70dedf9bd530
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for libp2p-accelerate-py 0.0.3
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.