🚀 ZYRA CLI: Decentralized AI Agent & PoUW Network
A powerful, self-organizing decentralized AI network client and terminal-based Agentic AI framework powered by Proof-of-Useful-Work (PoUW).
🌟 Core Ecosystem
- ZYRA CLI (
zyra_cmd/zyra_cli.py): Interactive terminal assistant with autonomous tool-calling, multi-model support, and P2P networking. - P2P Gossip Network (
p2p/): Decentralized node communication for task broadcasting and consensus. - Proof-of-Useful-Work (PoUW): Consensus mechanism where AI Miner nodes execute tasks and Smart Judges validate trajectories deterministically.
- Blockchain Integration (
blockchain/&mythchain/): EVM tokenomics (Celo/Hardhat) and sovereign Cosmos SDK L1 roadmap (MythChain). - AI Research (
ai/): Scratch-built Transformer architecture and training framework.
📦 Installation & Setup
python -m venv venv
.\venv\Scripts\activate
pip install -e .
🚀 Running ZYRA CLI
zyra
OR
python -m zyra_cmd.zyra_cli
Client Mode: Engine, Tasks & Result Folder
Client nodes can submit tasks without installing Ollama. The first Ollama installation
answer is remembered across CLI restarts. If you choose n, subsequent launches do
not repeat the installation prompt. To install/start Ollama and select a local model later:
/engine
Set the destination for future task results before submitting:
/output "D:\Hasil ZYRA"
/submit Buat aplikasi kalkulator Python
/tasks
On Linux/macOS, for example, use /output ~/hasil-zyra. Paths with spaces are supported.
/output with no argument shows the current folder. The default is ~/ZYRA Results.
Each task remembers its absolute destination at submission time; changing /output
does not move previous or in-progress tasks.
Task IDs, progress, download status, and result locations are saved in client.db
under %APPDATA%\ZYRA AI on Windows, or ~/ZYRA AI when APPDATA is unset.
When the CLI is reopened:
- A summary shows previously downloaded results and their workspace/ZIP paths.
- Pending tasks resume tracking through P2P mempool synchronization.
- Tasks completed while the client was offline are downloaded once their completion and result CID are received from peers.
- Failed downloads are retried while the CLI is running. Successfully saved results are not downloaded again, and existing result folders are not overwritten.
/tasksshows the full local task history, destinations, and latest download errors.
Recovery requires a peer that still knows the task and an online node serving its workspace. Closing the client stops local monitoring/downloads until it is reopened. Tracking applies to tasks submitted with this version; older sessions that never saved task history cannot be reconstructed from local history automatically.
PoUW Judge Votes (prototype, local changes after v2.1.51)
The /judge command signs PASS or FAIL votes using ECDSA/secp256k1. Votes bind
the task ID, trajectory hash, workspace CID, acceptance hash, verdict and reason.
Peers check the signature and judge address and count two different judge
addresses before marking a task completed or sending failure feedback to a
miner. The miner waits for the quorum before moving to the next task; its local
ledger only records a reward once per task after approval. A failed quorum
returns structured reasons so the same miner can retry that task.
Run two independent judge nodes for end-to-end testing. Judges need a wallet
created with ecdsa installed; older simulated wallets without a real 128-hex
public key cannot submit a signed vote. This is a prototype vote quorum:
judge selection and Sybil resistance are not implemented, and local SQLite
balances are not final on-chain settlement. New ZIP content addressing is being
added locally; previously published v2.1.52 still uses opaque ZIP IDs.
P2P Artifact Integrity (local changes after v2.1.52)
New automode workspace ZIP files use sha256:<hex digest> content IDs. Nodes
verify the seeded file and verify the complete reconstructed download against
that digest before making it available to the judge or client. Invalid chunks,
oversized chunks, and artifacts larger than 256 MiB are rejected. Legacy opaque
IDs remain readable for compatibility but carry no content-integrity guarantee.
1 maintainer
Metadata
1 maintainer
Release files for zyra-network 2.1.53
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zyra_network-2.1.53.tar.gz | 110.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zyra_network-2.1.53-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 213.6 kB
Release files / zyra_network-2.1.53.tar.gz
| Download URL | zyra_network-2.1.53.tar.gz |
|---|---|
| Size | 110.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f40c91002b09881e63bf5cb409900ae670327e79fbba059cb0bd9826d53f346f
|
|
BLAKE2b-256 checksum How to use checksums |
ad6f524b9c2bf1f6ec1c6158456dbf6ff73720a77b7c775442d882f3e32beed7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Release files / zyra_network-2.1.53-py3-none-any.whl
| Download URL | zyra_network-2.1.53-py3-none-any.whl |
|---|---|
| Size | 103.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7700bfcb0dbd8117a4b2d648ea2b9f2675d2c002d264ec0e9eedd49437c8958
|
|
BLAKE2b-256 checksum How to use checksums |
d7f17b838a5af7245830b01a6c01382d55c634e7471355f60f341f8ff28c4ba7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
