@xpr-agents/openclaw 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xpr-agents/openclaw",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "OpenClaw plugin for XPR Network Trustless Agent Registry - autonomous agent operation, escrow jobs, feedback, and validation",
5
5
  "author": "XPR Network",
6
6
  "repository": {
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: xpr-agent-operator
3
3
  description: Operate an autonomous AI agent on XPR Network's trustless registry
4
- metadata: {"openclaw":{"requires":{"env":["XPR_ACCOUNT","XPR_PRIVATE_KEY"]}}}
4
+ metadata: {"openclaw":{"requires":{"env":["XPR_ACCOUNT"],"cli":["proton"]}}}
5
5
  ---
6
6
 
7
7
  # XPR Agent Operator
@@ -152,7 +152,7 @@ Check registry stats: xpr_get_stats
152
152
  - Check task progress with `xpr_a2a_get_task`
153
153
  - Delegate sub-tasks from escrow jobs to specialized agents with `xpr_a2a_delegate_job`
154
154
  - Always verify the target agent's trust score before delegating work
155
- - All outgoing A2A requests are signed with your EOSIO key (via `XPR_PRIVATE_KEY`)
155
+ - Outgoing A2A requests are signed with a separate `A2A_SIGNING_KEY` (registered on a custom permission with no on-chain powers — limited blast radius if leaked). If unset, A2A runs receive-only.
156
156
  - Incoming A2A requests are authenticated — callers must prove account ownership via signature
157
157
  - Rate limiting and trust gating protect against abuse (configurable via `A2A_MIN_TRUST_SCORE`, `A2A_MIN_KYC_LEVEL`)
158
158
 
@@ -207,7 +207,7 @@ When a job involves token swaps, OTC deals, or any financial trade:
207
207
 
208
208
  ## Safety Rules
209
209
 
210
- 1. **Never reveal private keys** - XPR_PRIVATE_KEY must stay in environment variables only. Recommend operators use a dedicated agent account, not their personal account
210
+ 1. **Never reveal private keys** — Your blockchain key lives in the proton CLI's encrypted keychain (loaded once via `proton key:add`) and never enters this process's memory. Do not attempt to read it, dump it, or print it. Recommend operators use a dedicated agent account, not their personal account.
211
211
  2. **Always verify before accepting** - Read job details thoroughly before committing
212
212
  3. **Always provide evidence** - When delivering or disputing, include evidence URIs
213
213
  4. **Respect confirmation gates** - High-risk actions (registration, funding, disputes) require confirmation