| name | allora-worker-manager |
| description | Manage multiple Allora SDK workers by topic/address with lightweight local state. Use for add/deploy/start/stop/replace and health checks. |
Allora Worker Manager
Use WorkerManager when running multiple topics and ensuring one worker per (topic_id, address).
API key — stop and confirm with the user
Workers need an ALLORA_API_KEY to submit predictions on-chain.
Do not silently use a discovered key — treat it as human-confirmed input.
- If a key exists in env/file, tell the user and ask: "Should I use this key, or a different one?"
- If no key is found, prompt: "Sign up free at https://developer.allora.network and paste
your key." Workers cannot submit without one.
- Wait for the user to respond. Do not proceed to deploy without confirmation.
Core Rules
- Unique worker key is
(topic_id, address).
- Deploy with only
topic_id + artifact will:
- reuse an existing managed address not used for that topic,
- otherwise create a new wallet and address automatically.
- Deploying to an existing
(topic_id, address) requires replace=True.
Quick Start
from pathlib import Path
from allora_forge_builder_kit import WorkerManager
wm = WorkerManager(db_path="worker_state.db", secrets_path="worker_secrets.json")
result = wm.deploy_worker(topic_id=69, artifact_path=Path("predict.pkl"))
print(result.message)
wm.start_all()
print(wm.health_all())
Key management
- Wallet mnemonics are stored as individual files in
worker_keys/ (chmod 600).
worker_secrets.json maps identity aliases to {address, key_file} — never contains raw mnemonics.- The runtime reads the key file directly via
AlloraWalletConfig(mnemonic_file=...).
- Users can inspect their mnemonic by reading the key file:
cat worker_keys/<alias>.key
Monitoring
from allora_forge_builder_kit import WorkerMonitor, AlloraSDKEventFetcher
monitor = WorkerMonitor(db_path="worker_state.db", event_fetcher=AlloraSDKEventFetcher())
wm.attach_monitor(monitor, sync_now=True)
