@agether/agether 2.6.1 → 2.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agether/agether",
-  "version": "2.6.1",
+  "version": "2.6.3",
   "description": "OpenClaw plugin for Agether — onchain credit for AI agents on Ethereum & Base",
   "main": "src/index.ts",
   "openclaw": {

package/skills/agether/SKILL.md

@@ -1,21 +1,6 @@
 ---
 name: agether
-description: On-chain credit protocol for AI a## 🔗 CHAIN RESOLUTION (CRITICAL — HARD REQUIREMENT)
-
-All on-chain tools (register, borrow, deposit, withdraw, pay, etc.) will **FAIL with an error** if chain is not configured. You MUST call `agether_set_chain` FIRST.
-
-If `agether_health` returns `chain: "?"`, the chain is NOT configured:
-
-```
-1. Ask user: "Which blockchain would you like to use? **Ethereum** or **Base**?"
-2. User chooses a chain
-3. Call `agether_set_chain(chain: "<ethereum or base>")`
-4. After set → call `agether_health` to confirm everything is working on that chain
-```
-
-`agether_set_chain` saves the chain to config permanently (survives restarts). Accepts: `ethereum`, `eth`, `1`, `base`, `8453`.
-
-**IMPORTANT:** Resolve chain BEFORE doing ANYTHING else — including `agether_register`. The agent identity is chain-specific. If you skip this step, all write tools will return an error. Morpho credit & lending, x402 payments, ERC-8004 identity.
+description: On-chain credit protocol for AI agents. Morpho credit & lending, x402 payments, ERC-8004 identity.
 ---
 
 # Agether — On-Chain Credit for AI Agents
@@ -41,11 +26,11 @@ If you don't paste it, the user sees NOTHING. An empty colon ":" with no data af
 1. **PASTE tool results into your reply.** Every tool returns JSON. Extract the key fields and write them in your message. The user cannot see tool output directly.
 2. **ALWAYS paste tx links.** Tools return `tx` field like `https://basescan.org/tx/0x...`. Copy it verbatim into your reply.
 3. **After on-chain actions, call `agether_balance` and paste the balances.**
-4. **On first message, call `agether_health`.** This is your single best "context loader" — it returns balances, positions, LTV, alerts, and headroom in one call. If `agentId` is `"?"`, see AGENT ID RESOLUTION below.
+4. **On first message, call `agether_health`.** This is your single best "context loader" — it returns balances, positions, LTV, alerts, and headroom in one call. If `chain` is `"?"`, follow the MANDATORY BOOT SEQUENCE above — set chain FIRST, then agent ID.
 5. **Be proactive** — if the user asks to call a paid API, do the full flow without asking.
 6. **Never ask for private keys** — they come from OpenClaw secrets (AGETHER_PRIVATE_KEY env var).
 7. **Max LTV is 80%** (125% collateral ratio). To borrow $X, you need $X × 1.25 in collateral value.
-8. **When user says "register" → ALWAYS call `agether_register`.** A wallet CAN have multiple ERC-8004 identities. The tool handles everything. Never refuse to register because the wallet "already has an identity". Just call the tool.
+8. **When user says "register" → ALWAYS call `agether_register`.** But ONLY after chain is set (see MANDATORY BOOT SEQUENCE). A wallet CAN have multiple ERC-8004 identities. The tool handles everything. Never refuse to register because the wallet "already has an identity". Just call the tool.
 9. **Never guess about blockchain state.** If you're unsure, call the tool. Don't tell the user something is impossible — try it first.
 10. **Your EOA wallet IS the user's wallet.** Same private key, same address. If the user says "I have WETH", call `agether_balance` — you'll see it in the `collateral` field. You already have access to those tokens.
 11. **`morpho_deposit` and `morpho_deposit_and_borrow` transfer collateral from your EOA automatically.** You do NOT need anyone to "send you" tokens. If your EOA has WETH, just call the deposit tool directly. The SDK handles EOA→Safe account→Morpho in one flow.
@@ -58,39 +43,63 @@ If you don't paste it, the user sees NOTHING. An empty colon ":" with no data af
 
 ---
 
-## 🆔 AGENT ID RESOLUTION (CRITICAL)
+## 🚫🚫🚫 MANDATORY BOOT SEQUENCE — READ THIS FIRST 🚫🚫🚫
+
+There is a **strict ordering requirement**. Violating this order WILL cause wrong-chain registration and lost funds.
+
+### STEP 1 → CHAIN (must be first, ALWAYS, no exceptions)
+
+**You MUST set the chain BEFORE you do ANYTHING else — before `agether_set_agent`, before `agether_register`, before ANY on-chain tool call.**
 
-If `agether_health` or `agether_balance` returns `agentId: "?"`, ALL Morpho tools will fail. You MUST resolve this first:
+An `agentId` is **chain-specific**. Agent 28368 on Base is a completely different account than agent 28368 on Ethereum. If you set an agentId without knowing the chain, you WILL point at the wrong contract on the wrong network.
+
+**NEVER call `agether_set_agent` before the chain is confirmed. NEVER.**
 
 ```
-1. Check your memory for a previously registered agentId
-2. IF you find an agentId in memory:
-     → Ask user: "I remember agent ID <X> from before. Should I use it, or register a new one?"
-     → IF user says yes → call `agether_set_agent(agentId: "<X>")`
-     → IF user says no  → call `agether_register(name: "<ask name>")`
-3. IF no agentId in memory:
-     → call `agether_register(name: "<ask name>")`
-4. After either path → call `agether_health` to confirm everything is working
+IF agether_health returns chain: "?"
+  → Ask user: "Which chain — Ethereum or Base?"
+  → Call agether_set_chain(chain: "<ethereum or base>")
+  → Call agether_health again to confirm chain is set (not "?")
 ```
 
-Both `agether_set_agent` and `agether_register` save the agentId to config permanently (survives restarts).
+`agether_set_chain` accepts: `ethereum`, `eth`, `1`, `base`, `8453`.
 
----
+### STEP 2 → AGENT ID (ONLY after chain is confirmed, not "?")
 
-## � CHAIN RESOLUTION (CRITICAL)
+**NEVER call `agether_set_agent` or `agether_register` until the chain is confirmed (chain ≠ "?").**
 
-If `agether_health` returns `chain: "?"`, the chain is NOT configured. You MUST resolve this before proceeding with any on-chain action:
+Even if you have an agentId cached in memory or config — that agentId belongs to a **specific chain**. Do NOT blindly reuse it. A config value like `"agentId": "28368"` might be from the old deployment or a different chain.
 
 ```
-1. Ask user: "Which blockchain would you like to use? **Ethereum** or **Base**?"
-2. User chooses a chain
-3. Call `agether_set_chain(chain: "<ethereum or base>")`
-4. After set → call `agether_health` to confirm everything is working on that chain
+IF chain is confirmed AND agentId is "?"
+  1. IF you remember an agentId AND know which chain it was for:
+       → Ask: "I remember agent <X> on <CHAIN>. Is this still correct?"
+       → IF yes AND chain matches → agether_set_agent(agentId: "<X>")
+       → IF no → agether_register(name: "<ask>")
+  2. IF no memory of agentId:
+       → agether_register(name: "<ask>")
+  3. Call agether_health to confirm
 ```
 
-`agether_set_chain` saves the chain to config permanently (survives restarts). Accepts: `ethereum`, `eth`, `1`, `base`, `8453`.
+### ⛔ FORBIDDEN (will cause bugs)
+
+- ❌ `agether_set_agent` → then `agether_set_chain` — **WRONG ORDER, agent points at wrong chain**
+- ❌ `agether_register` before chain is set — **WILL FAIL**
+- ❌ Reusing a cached agentId without confirming which chain it belongs to — **WRONG ACCOUNT**
+- ❌ Seeing `"agentId": "28368"` in config and assuming it's valid — it might be stale or from a different chain
+- ❌ Calling `agether_set_agent` just because config has an agentId — **ASK THE USER FIRST**
+
+### ✅ CORRECT SEQUENCE (always follow this)
 
-**IMPORTANT:** Resolve chain BEFORE resolving agentId — the agent registration happens on a specific chain.
+```
+1. agether_health          → check chain and agentId status
+2. agether_set_chain       → if chain is "?", ask user and set it FIRST
+3. agether_health          → confirm chain is now set
+4. agether_set_agent OR agether_register → only NOW, after chain is confirmed
+5. agether_health          → final confirmation that both chain + agentId are set
+```
+
+Both `agether_set_agent` and `agether_register` save the agentId to config permanently (survives restarts).
 
 ---
 
@@ -191,11 +200,11 @@ When `autoYield` and/or `autoDraw` are enabled, `x402_pay` automatically sources
 ```
 1. agether_health                ← ONE call for full context
 2. Check the "chain" field:
-     → If chain is "?" → go to CHAIN RESOLUTION (must resolve before anything else)
+     → If chain is "?" → STOP. Set chain first (MANDATORY BOOT SEQUENCE). Do NOT proceed until chain is confirmed.
 3. Check the "alerts" array:
      → If any 🔴 alerts → WARN user immediately (liquidation risk!)
      → If any 🟡 alerts → mention the risk casually
-     → If "agentId: ?" → go to AGENT ID RESOLUTION
+     → If "agentId: ?" → set agent ID (but only AFTER chain is confirmed — see MANDATORY BOOT SEQUENCE)
 4. Now you have full context to handle any request
 ```
 

package/src/index.ts

@@ -158,13 +158,15 @@ function resolvePrivateKey(): string {
 
 function getConfig(api: any): PluginConfig {
   const cfg = api.config?.plugins?.entries?.["agether"]?.config ?? {};
-  const rawChain = cfg.chain;
+  // chainOverride (set by agether_set_chain at runtime) takes priority over
+  // api.config which is a stale in-memory snapshot that never refreshes.
+  const rawChain = chainOverride ?? cfg.chain;
   const chainConfigured = rawChain !== undefined && rawChain !== null && rawChain !== "";
   const chainId = (rawChain as ChainId) || ChainId.Ethereum;
   activeChainId = chainId; // Update module-level for txLink
   return {
     privateKey: resolvePrivateKey(),
-    agentId: cfg.agentId,
+    agentId: cachedAgentId || cfg.agentId,
     rpcUrl: resolveRpcUrl(chainId),
     chainId,
     chainConfigured,
@@ -174,6 +176,7 @@ function getConfig(api: any): PluginConfig {
 // Module-level cache
 let cachedAgentId: string | undefined;
 let activeChainId: ChainId = ChainId.Ethereum;
+let chainOverride: ChainId | undefined; // set by agether_set_chain, survives stale api.config
 
 /**
  * Hard guardrail: refuse to proceed if chain was never explicitly configured.
@@ -225,6 +228,7 @@ function persistAgentId(agentId: string): string {
 /** Persist chain to openclaw.json so it survives restarts. */
 function persistChainId(chainId: ChainId): string {
   activeChainId = chainId;
+  chainOverride = chainId; // In-memory override so getConfig() picks it up immediately
   try {
     const home = process.env.HOME || process.env.USERPROFILE || "/root";
     const cfgPath = path.join(home, ".openclaw", "openclaw.json");