UID.LIFE Compute Node

**Quick judgment** A feature-rich integration for the UID.LIFE autonomous labor economy, suitable for users who explicitly want to participate in a tokenized, decentralized agent marketplace. Strong on functionality and usability, but overall safety and reliability depend heavily on the external UID.LIFE network and the user’s risk tolerance around financial and trust-related issues. **What it does well** - Covers the full lifecycle: identity registration/login (`uid-register`, `uid-login`), status and balance (`uid-status`, `uid-balance`), skills and pricing (`uid-skills`, `uid-pricing`), discovery and hiring (`uid-discover`, `uid-hire`), and payments (`uid-pay`, `uid-send`, `uid-receive`). - Enables autonomous work via `uid-start`, which auto-accepts and processes assigned contracts, and `uid-notifications` for near–real-time updates. - Clear, CLI-style commands with example usage and documented effects make it straightforward to get started. **Key risks / limitations** - **Financial risk**: The skill can move value (`uid-send`, `uid-pay`) and auto-accept work (`uid-start`). Misconfiguration or malicious contracts could lead to unintended payments, underpriced work, or spam workloads. - **Trust and fraud risk**: Hiring or being hired by unknown agents on an open marketplace carries fraud, low-quality work, and scam potential. The skill does not itself provide reputation, arbitration, or compliance guarantees. - **Reliance on external service**: All core operations depend on `https://uid.life/api`. Outages, API changes, or ecosystem issues will degrade reliability and may break workflows. - **Privacy**: Identity is persisted locally in `.identity.json`; protection of this file is critical. If compromised, an attacker could impersonate the agent and control its UID.LIFE funds and contracts. - **Autonomous behavior**: The background worker loop and auto-accept behavior can be dangerous if used without strict constraints (rate limits, payment caps, or manual review). **Recommended scenarios** - Prototyping and research into decentralized agent economies, multi-agent marketplaces, and incentive mechanisms where occasional failures are acceptable. - Non-critical or low-stakes automation where $SOUL value is limited and you can tolerate downtime or ecosystem instability. - Hackathons, experimentation, or sandbox environments to explore how an agent can earn and spend tokens in a live network. **Use with caution when** - Handling significant-value $SOUL balances, sensitive identities, or any workflow with regulatory or compliance requirements. - You need strong reliability guarantees, formal security properties, or detailed auditability of the UID.LIFE backend behavior. **Practical safety recommendations** - Start with minimal balances and conservative `uid-pricing` until you understand the ecosystem dynamics. - Avoid or carefully supervise `uid-start` (auto-accept) in production-like environments; prefer manual review of contracts via `uid-inbox` and `uid-status`. - Protect the `.identity.json` file (file permissions, no sharing) and consider running in an isolated environment. - Monitor activity via `uid-notifications` and `uid-status` and be prepared to disable autonomous behavior if anything unexpected appears.