@wowok/agent-mcp 2.2.11 → 2.2.13

package/docs/docs/treasury.md

@@ -0,0 +1,1149 @@
+
+# Treasury Component (💰 Team Fund Vault Management)
+
+---
+
+## Component Overview
+
+The Treasury component is used to create and manage team fund vaults, set deposit/withdrawal rules, etc. Treasury supports two operation modes: permission management through Permission objects, or verification through external Guard objects.
+
+---
+
+## Function List
+
+| Function Name | Purpose | Usage Scenario | Significance |
+|---------------|---------|----------------|-------------|
+| **Create Treasury** | Establish new fund vault with access controls | Set up team budget vaults, project fund pools | Creates secure on-chain treasury with permission management |
+| **Deposit Funds** | Add assets to Treasury balance | Contribute to team funds, deposit project budgets | Fills the treasury balance pool |
+| **Withdraw Funds** | Remove assets from Treasury balance | Pay expenses, distribute bonuses, allocate funds | Releases funds from treasury to recipients |
+| **Manage Deposit Guards** | Configure external Guard verification for deposits | Allow public deposits, controlled external contributions | Enables permissionless deposits with Guard validation |
+| **Manage Withdrawal Guards** | Configure external Guard verification for withdrawals | Enable automated payouts, controlled external withdrawals | Enables permissionless withdrawals with Guard validation |
+| **Receive Assets** | Process received CoinWrapper objects | Deposit incoming payments, collect fees | Automatically adds received assets to treasury balance |
+| **Owner Receive** | Unwrap and send received assets to owner | Forward received tokens, process incoming payments | Delivers received assets to permission owner |
+
+---
+
+## Complete Tool Call Structure
+
+Treasury operations use the following top-level structure:
+
+```json
+{
+  "operation_type": "treasury",
+  "data": { ... },    // Treasury data definition
+  "env": { ... },       // Execution environment (optional)
+  "submission": { ... }  // Submission data (optional)
+}
+```
+
+---
+
+## Schema Tree
+
+```
+treasury (Treasury Object)
+├── operation_type: "treasury" (fixed value)
+├── data (Treasury data definition)
+│   ├── object (object definition, required)
+│   │   ├── name|id (reference existing object)
+│   │   └── name|tags|type_parameter|permission (create new object)
+│   ├── description (description, optional)
+│   ├── receive (receive CoinWrapper, optional)
+│   │   ├── Option 1: "recently" (string) - receive all recently received
+│   │   └── Option 2: { balance, token_type, received } - specify received balance
+│   │       ├── balance (number or string)
+│   │       ├── token_type (string) - token type like "CoinWrapper<0x2::wow::WOW>"
+│   │       └── received (array) - received CoinWrapper object records
+│   │           └── [{ id: string, balance: number, payment: string }]
+│   ├── deposit (deposit, optional)
+│   │   ├── coin (asset, required)
+│   │   │   ├── Option 1: { balance: number } - specify amount
+│   │   │   └── Option 2: { coin: string } - use specified Coin object ID
+│   │   ├── by_external_deposit_guard (string, optional) - Guard ID for external verification
+│   │   ├── payment_info (required)
+│   │   │   ├── for_object (string or null, optional) - Payment for a specific object ID
+│   │   │   ├── for_guard (string or null, optional) - Payment to satisfy verification of a Guard object
+│   │   │   ├── remark (string) - Payment record remark
+│   │   │   └── index (number or string) - Payment record index
+│   │   └── namedNewPayment (object, optional) - Create new Payment object after deposit
+│   │       └── name (string, optional) - Name for the new Payment object
+│   ├── withdraw (withdrawal, optional)
+│   │   ├── amount (amount, required)
+│   │   │   ├── Option 1: { fixed: number|string } - Fixed withdrawal amount (Permission only)
+│   │   │   └── Option 2: { by_external_withdraw_guard: string } - Guard-verified withdrawal
+│   │   ├── recipient (AccountOrMark_Address object, required) - Recipient ID
+│   │   ├── payment_info (required)
+│   │   │   ├── for_object (string or null, optional) - Payment for a specific object ID
+│   │   │   ├── for_guard (string or null, optional) - Payment to satisfy verification of a Guard object
+│   │   │   ├── remark (string) - Payment record remark
+│   │   │   └── index (number or string) - Payment record index
+│   │   └── namedNewPayment (object, optional) - Create new Payment object after withdrawal
+│   │       └── name (string, optional) - Name for the new Payment object
+│   ├── external_deposit_guard (optional)
+│   │   ├── op (string) - Operation type: "add", "set", "remove", "clear"
+│   │   └── guards (array, required for add/set/remove)
+│   │       ├── For add/set: AmountFromDepositGuard
+│   │       │   ├── guard (string) - Guard object ID or name
+│   │       │   ├── identifier (number or null, optional) - Guard Table data index for amount
+│   │       │   └── store_from_id (number or null, optional) - Guard table index for record storage
+│   │       └── For remove: NameOrAddress (string) - Guard object ID or name only
+│   ├── external_withdraw_guard (optional)
+│   │   ├── op (string) - Operation type: "add", "set", "remove", "clear"
+│   │   └── guards (array, required for add/set/remove)
+│   │       ├── For add/set: AmountFromWithdrawGuard
+│   │       │   ├── guard (string) - Guard object ID or name
+│   │       │   ├── identifier (number, required) - Guard Table data index for amount
+│   │       │   └── store_from_id (number or null, optional) - Guard table index for record storage
+│   │       └── For remove: NameOrAddress (string) - Guard object ID or name only
+│   ├── owner_receive (transfer received coins or NFT objects to owner, optional)
+│   │   ├── Option 1: "recently" (string) - receive all recent objects
+│   │   ├── Option 2: Array of received objects
+│   │   │   └── [{ id: "object_id", type: "object_type" }]
+│   │   └── Option 3: Received balance object
+│   │       ├── balance (number or string)
+│   │       ├── token_type (string)
+│   │       └── received (array of received items)
+│   └── um (Contact object, optional)
+│       ├── Option 1: NamedObject (object) - create a named Contact object
+│       │   ├── name (string, optional) - Contact object name
+│       │   ├── tags (string[], optional) - object tags
+│       │   ├── onChain (boolean, optional) - sync name to chain
+│       │   └── replaceExistName (boolean, optional) - overwrite existing
+│       └── Option 2: null (to unbind contact)
+├── env (optional, execution environment)
+│   ├── account (string, optional) - account name or address, empty string for default
+│   ├── network (string, optional) - "testnet" or "localnet"
+│   ├── permission_guard (array, optional) - list of permission guard IDs
+│   ├── no_cache (boolean, optional) - disable caching
+│   └── referrer (string, optional) - referrer ID
+└── submission (optional, submission data)
+    ├── type (string) - fixed value "submission"
+    ├── guard (array) - list of guards to verify
+    │   └── [{ object: "guard_id", impack: boolean }]
+    └── submission (array) - submission data for guards
+        └── [{ guard: "guard_id", submission: [guard_submission_items] }]
+            └── guard_submission_items
+                ├── identifier (number, 0-255) - Guard table item identifier
+                ├── b_submission (boolean) - whether this item requires submission
+                ├── value_type (number | string) - value type (e.g., 6 or "U64" for U64 type)
+                ├── **value (any) - submitted value**
+                └── name (string, optional) - item name
+```
+
+---
+
+### ⚠️ Important Note About Submission
+
+If the execution returns a `submission` field in the response, it indicates that additional Guard verification data is required. You must:
+
+1. Complete all required submission data within the `submission` structure
+2. Resubmit the operation with the completed submission data
+3. **Do not modify any other parts of the structure** - only fill in the required submission values
+
+The submission structure will specify which Guard objects need verification and what data needs to be provided for each Guard table item.
+
+**Query Value Types**: Use the `wowok_buildin_info` tool with `{ "info": "value types" }` to query all supported value types with their numeric and string representations. This helps you understand what `value_type` values are valid for submission data.
+
+---
+
+## ⚠️ Critical Constraints and Error Codes
+
+### Error Code Reference
+
+| Error Code | Constant | Description | Solution |
+|------------|----------|-------------|----------|
+| 5 | `E_IDENTIFIER_NOT_NUMBER_TYPE` | Guard identifier is not a numeric type | Ensure Guard table identifier uses U64 type, not Bool or other types |
+| 6 | `E_DEPOSIT_INSUFFICIENT_AMOUNT` | Deposit amount is less than Guard required minimum | Deposit amount must be >= Guard identifier value |
+| 7 | `E_WITHDRAW_INSUFFICIENT_AMOUNT` | Treasury balance is insufficient for withdrawal | Ensure Treasury has sufficient balance before withdrawal |
+
+### External Guard Requirements
+
+When using external Guards for deposit/withdrawal:
+
+1. **Guard Type Requirements**:
+   - Guard's table identifier **must be U64 type** (not Bool, String, etc.)
+   - The identifier value represents the **maximum allowed amount** for the operation
+
+2. **Guard Creation Example**:
+   ```json
+   {
+     "operation_type": "guard",
+     "data": {
+       "namedNew": { "name": "my_guard" },
+       "table": [{ "identifier": 0, "b_submission": false, "value_type": "U64", "value": 1000000000 }],
+       "root": { "type": "node", "node": { "type": "logic_as_u256_greater_or_equal", "nodes": [...] } }
+     }
+   }
+   ```
+
+3. **Amount Constraints**:
+   - For deposit: `deposit.coin.balance` must be **>=** Guard's identifier value
+   - For withdrawal: Guard's identifier value specifies the **exact** withdrawal amount
+
+---
+
+## Sub-feature 1: Create New Treasury
+
+### Feature Description
+
+Create a new Treasury object, can simultaneously create a new Permission object or reference an existing Permission.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | object or string | Yes | Object definition | TypedPermissionObject |
+| `data.description` | string | No | Treasury description | Max 4000 BCS characters |
+| `env.account` | string | No | Use specified account | Empty string '' uses default account |
+| `env.network` | enum | No | Network selection | "localnet" or "testnet" |
+
+### Important Notes
+
+⚠️ **Permission Object**: Treasury requires Permission to manage permissions, can create new or reference existing.
+
+⚠️ **External Guard**: Can set external verification rules through `external_deposit_guard` and `external_withdraw_guard`, allowing non-permission users to deposit/withdraw through Guard verification.
+
+---
+
+### Examples
+
+#### Example 1.1: Create Minimal Treasury (name only)
+
+**Prompt**: Create a Treasury named "team_treasury", use default account and network, no other configuration specified.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": {
+      "name": "team_treasury"
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Permission",
+      "object": "0x53ad...08e7",
+      "version": "244384",
+      "change": "created"
+    },
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "244384",
+      "change": "created"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 1.2: Create Treasury with Tags
+
+**Prompt**: Create a Treasury named "project_fund", add tags "project", "finance", and description "Project fund treasury for managing team finances".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": {
+      "name": "project_fund",
+      "tags": ["project", "finance"]
+    },
+    "description": "Project fund treasury for managing team finances"
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0x20fd...393a",
+      "version": "251892",
+      "change": "created"
+    },
+    {
+      "type": "Permission",
+      "object": "0x677f...0767",
+      "version": "251892",
+      "change": "created"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 1.3: Create Treasury and Set External Guards
+
+**Prompt**: Create a Treasury named "community_fund", set external deposit Guard and external withdrawal Guard, allowing deposit/withdrawal operations through Guard verification.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": {
+      "name": "community_fund",
+      "tags": ["community", "fund"]
+    },
+    "description": "Community fund treasury with external Guard access",
+    "external_deposit_guard": {
+      "op": "add",
+      "guards": [
+        {
+          "guard": "deposit_guard_u64",
+          "identifier": 0
+        }
+      ]
+    },
+    "external_withdraw_guard": {
+      "op": "add",
+      "guards": [
+        {
+          "guard": "withdraw_guard_u64",
+          "identifier": 0
+        }
+      ]
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Permission",
+      "object": "0x163e...c6a8",
+      "version": "258393",
+      "change": "created"
+    },
+    {
+      "type": "Treasury",
+      "object": "0x5b1a...3dbf",
+      "version": "258393",
+      "change": "created"
+    }
+  ]
+}
+```
+
+> **Important Constraints**:
+> - Guard's table identifier must be **U64 type** . Error code 5 (`E_IDENTIFIER_NOT_NUMBER_TYPE`) will be returned if using non-numeric types
+> - The identifier value in Guard table represents the **maximum allowed amount** for deposit/withdrawal
+
+---
+
+## Sub-feature 2: Deposit
+
+### Feature Description
+
+Deposit assets into Treasury, supports verification through Permission or external Guard.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | string | Yes | Treasury name or ID | |
+| `data.deposit.coin` | object | Yes | Asset to deposit | { balance: number } or { coin: string } |
+| `data.deposit.by_external_deposit_guard` | string | No | External Guard verification | Guard object ID or name |
+| `data.deposit.payment_info` | object | Yes | Payment information | |
+| `data.deposit.namedNewPayment` | object | No | Create new Payment object | |
+
+### Important Notes
+
+⚠️ **Two Deposit Methods**: 
+- Deposit through Permission (default, requires permission)
+- Deposit through external Guard verification (use `by_external_deposit_guard`)
+
+---
+
+### Examples
+
+#### Example 2.1: Deposit through Permission
+
+**Prompt**: Deposit 100 WOW into "team_treasury", operate through Permission.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "deposit": {
+      "coin": {
+        "balance": 100000000000
+      },
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      }
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "244617",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 2.2: Deposit through External Guard
+
+**Prompt**: Deposit 10 WOW into "community_fund", verify through external Guard "deposit_guard_u64", simultaneously create a Payment object named "deposit_payment".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "deposit": {
+      "coin": {
+        "balance": 1000000000
+      },
+      "by_external_deposit_guard": "deposit_guard_u64",
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      },
+      "namedNewPayment": {
+        "name": "deposit_payment"
+      }
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0x5b1a...3dbf",
+      "version": "259562",
+      "change": "mutated"
+    },
+    {
+      "type": "Payment",
+      "object": "0x53a4...f121",
+      "change": "created"
+    }
+  ]
+}
+```
+
+> **Important Constraints**:
+> - Deposit amount **must be >=** the value specified in Guard's identifier. Error code 6 (`E_DEPOSIT_INSUFFICIENT_AMOUNT`) will be returned if amount is insufficient
+> - Guard verification creates a Payment object as transaction record
+> - The `namedNewPayment` field allows naming the Payment object for later reference
+
+---
+
+## Sub-feature 3: Withdrawal
+
+### Feature Description
+
+Withdraw assets from Treasury, supports fixed amount withdrawal through Permission, or withdrawal through external Guard verification.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | string | Yes | Treasury name or ID | |
+| `data.withdraw.amount` | object | Yes | Withdrawal amount | { fixed: number } or { by_external_withdraw_guard: string } |
+| `data.withdraw.recipient` | object | Yes | Recipient | AccountOrMark_Address object |
+| `data.withdraw.payment_info` | object | Yes | Payment information | |
+| `data.withdraw.namedNewPayment` | object | No | Create new Payment object | |
+
+### Important Notes
+
+⚠️ **Two Withdrawal Methods**:
+- Fixed amount withdrawal: Set through `amount.fixed`, must go through Permission
+- Guard verification withdrawal: Set through `amount.by_external_withdraw_guard`, amount obtained from Guard table data
+
+⚠️ **Balance Requirements**:
+- **Deposit**: Ensure account has sufficient WOW token balance to deposit
+- **Withdraw**: Ensure Treasury has sufficient balance (greater than withdrawal amount). Error code 7 (`E_WITHDRAW_INSUFFICIENT_AMOUNT`) indicates insufficient Treasury balance
+- Use `faucet` to obtain testnet WOW tokens for testing
+
+---
+
+### Examples
+
+#### Example 3.1: Fixed Amount Withdrawal through Permission
+
+**Prompt**: Withdraw 50 WOW from "team_treasury", through Permission, send to alice.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "withdraw": {
+      "amount": {
+        "fixed": 50000000000
+      },
+      "recipient": {
+        "name_or_address": "alice"
+      },
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      }
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result** (after faucet and deposit):
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "249816",
+      "change": "mutated"
+    },
+    {
+      "type": "WReceivedObject",
+      "object": "0x7de4...7f82",
+      "change": "created",
+      "owner": "alice_address"
+    },
+    {
+      "type": "Payment",
+      "object": "0xfd7c...816e",
+      "change": "created"
+    }
+  ]
+}
+```
+
+> **Note**: Withdrawal creates a Payment object containing the withdrawn funds. The recipient needs to call `owner_receive` on the Treasury or query their received objects to access the funds.
+
+---
+
+#### Example 3.2: Withdrawal through External Guard
+
+**Prompt**: Withdraw from "community_fund", verify through external Guard "withdraw_guard_u64", send to bob, simultaneously create Payment object.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "withdraw": {
+      "amount": {
+        "by_external_withdraw_guard": "withdraw_guard_u64"
+      },
+      "recipient": {
+        "name_or_address": "bob"
+      },
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      },
+      "namedNewPayment": {
+        "name": "withdraw_payment"
+      }
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0x5b1a...3dbf",
+      "version": "264087",
+      "change": "mutated"
+    },
+    {
+      "type": "WReceivedObject",
+      "object": "0x1094...a712",
+      "change": "created",
+      "owner": "bob_address"
+    },
+    {
+      "type": "Payment",
+      "object": "0x3198...b46e",
+      "change": "created"
+    }
+  ]
+}
+```
+
+> **Important Constraints**:
+> - Withdrawal amount is **determined by Guard's identifier value**, not specified in the request
+> - The Guard's identifier value (e.g., 500000000) becomes the exact withdrawal amount
+> - Treasury must have sufficient balance to cover the Guard-specified amount
+
+---
+
+## Sub-feature 4: Manage External Deposit Guard
+
+### Feature Description
+
+Manage Treasury's external deposit Guard list, supports add, set, remove, clear operations.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | string | Yes | Treasury name or ID | |
+| `data.external_deposit_guard.op` | string | Yes | Operation type | "add", "set", "remove", "clear" |
+| `data.external_deposit_guard.guards` | array | No | Guard list | Required for add/set/remove |
+
+### AmountFromDepositGuard Structure
+
+| Field | Type | Required | Description |
+|-------|------|------|------|
+| `guard` | string | Yes | Guard object ID or name |
+| `identifier` | number or null | No | Guard Table data index, whose corresponding value is the storable amount. If null, deposit amount is unlimited |
+| `store_from_id` | number or null | No | Guard table data index for record storage. The value at this index (address or number, including submitted values) will be stored in the record for Guard verification purposes, such as controlling operation frequency |
+
+### Important Notes
+
+⚠️ **External Guard Function**: Allows non-Permission users to deposit through Guard verification.
+
+⚠️ **identifier Parameter**: Corresponds to data index in Guard table, its value is depositable amount, null means unlimited.
+
+---
+
+### Examples
+
+#### Example 4.1: Add External Deposit Guard
+
+**Prompt**: Add external deposit Guard "deposit_guard_u64" to "team_treasury", identifier is 0, meaning depositable amount obtained from Guard table index 0.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "external_deposit_guard": {
+      "op": "add",
+      "guards": [
+        {
+          "guard": "deposit_guard_u64",
+          "identifier": 0
+        }
+      ]
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "265240",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 4.2: Add Unlimited Deposit Guard
+
+**Prompt**: Add external deposit Guard "unlimited_deposit", identifier is null, meaning unlimited deposit amount.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_deposit_guard": {
+      "op": "add",
+      "guards": [
+        {
+          "guard": "unlimited_deposit",
+          "identifier": null
+        }
+      ]
+    }
+  }
+}
+```
+
+---
+
+#### Example 4.3: Set External Deposit Guard (Replace)
+
+**Prompt**: Set "community_fund" external deposit Guard list, replace existing list, only keep "new_deposit_guard".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_deposit_guard": {
+      "op": "set",
+      "guards": [
+        {
+          "guard": "new_deposit_guard",
+          "identifier": 1
+        }
+      ]
+    }
+  }
+}
+```
+
+---
+
+#### Example 4.4: Remove External Deposit Guard
+
+**Prompt**: Remove external deposit Guard named "deposit_guard_u64" from "community_fund".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_deposit_guard": {
+      "op": "remove",
+      "guards": ["deposit_guard_u64"]
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0x5b1a...3dbf",
+      "version": "265243",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 4.5: Clear External Deposit Guard
+
+**Prompt**: Clear all external deposit Guards of "team_treasury".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "external_deposit_guard": {
+      "op": "clear"
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "265241",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+## Sub-feature 5: Manage External Withdrawal Guard
+
+### Feature Description
+
+Manage Treasury's external withdrawal Guard list, supports add, set, remove, clear operations.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | string | Yes | Treasury name or ID | |
+| `data.external_withdraw_guard.op` | string | Yes | Operation type | "add", "set", "remove", "clear" |
+| `data.external_withdraw_guard.guards` | array | No | Guard list | Required for add/set/remove |
+
+### AmountFromWithdrawGuard Structure
+
+| Field | Type | Required | Description |
+|-------|------|------|------|
+| `guard` | string | Yes | Guard object ID or name |
+| `identifier` | number | Yes | Guard Table data index, whose corresponding value is the withdrawable amount |
+| `store_from_id` | number or null | No | Guard table data index for record storage. The value at this index (address or number, including submitted values) will be stored in the record for Guard verification purposes, such as controlling operation frequency |
+
+### Important Notes
+
+⚠️ **External Guard Function**: Allows non-Permission users to withdraw through Guard verification.
+
+⚠️ **identifier Parameter**: Corresponds to data index in Guard table, its value is withdrawable amount.
+
+---
+
+### Examples
+
+#### Example 5.1: Add External Withdrawal Guard
+
+**Prompt**: Add external withdrawal Guard "approved_withdraw_guard" to "community_fund", identifier is 1, meaning withdrawable amount obtained from Guard table index 1.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_withdraw_guard": {
+      "op": "add",
+      "guards": [
+        {
+          "guard": "approved_withdraw_guard",
+          "identifier": 1
+        }
+      ]
+    }
+  }
+}
+```
+
+---
+
+#### Example 5.2: Set External Withdrawal Guard (Replace)
+
+**Prompt**: Set "community_fund" external withdrawal Guard list, replace existing list.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_withdraw_guard": {
+      "op": "set",
+      "guards": [
+        {
+          "guard": "new_withdraw_guard",
+          "identifier": 2
+        }
+      ]
+    }
+  }
+}
+```
+
+---
+
+#### Example 5.3: Remove External Withdrawal Guard
+
+**Prompt**: Remove external withdrawal Guard named "withdraw_guard_u64" from "community_fund".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "community_fund",
+    "external_withdraw_guard": {
+      "op": "remove",
+      "guards": ["withdraw_guard_u64"]
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0x5b1a...3dbf",
+      "version": "265244",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+#### Example 5.4: Clear External Withdrawal Guard
+
+**Prompt**: Clear all external withdrawal Guards of "team_treasury".
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "external_withdraw_guard": {
+      "op": "clear"
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "265242",
+      "change": "mutated"
+    }
+  ]
+}
+```
+
+---
+
+## Sub-feature 6: Receive and Manage Received Assets
+
+### Feature Description
+
+Process CoinWrapper objects received by Treasury, can deposit to balance or unwrap and send to Permission owner.
+
+### Parameter Description
+
+| Parameter Path | Type | Required | Description | Constraints |
+|----------|------|------|------|------|
+| `operation_type` | string | Yes | Operation type | Fixed value "treasury" |
+| `data.object` | string | Yes | Treasury name or ID | |
+| `data.receive` | string or object | No | Receive CoinWrapper | "recently" or ReceivedBalance object |
+| `data.owner_receive` | string or object | No | Unwrap and send to owner | "recently" or ReceivedObjects object |
+
+### Important Notes
+
+⚠️ **receive**: Deposit received CoinWrapper into Treasury balance.
+
+⚠️ **owner_receive**: Unwrap CoinWrapper and send to Permission owner.
+
+---
+
+### Examples
+
+#### Example 6.1: Receive Recently Received CoinWrapper and Deposit to Balance
+
+**Prompt**: Deposit recently received CoinWrapper of "team_treasury" into balance.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "receive": "recently"
+  }
+}
+```
+
+---
+
+#### Example 6.2: Unwrap CoinWrapper and Send to Owner
+
+**Prompt**: Unwrap recently received CoinWrapper and other objects of "team_treasury", send to Permission owner.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "owner_receive": "recently"
+  }
+}
+```
+
+---
+
+## Sub-feature 7: Operate Existing Treasury (Combined Operations)
+
+### Feature Description
+
+Perform multiple operations on existing Treasury in a single transaction, such as simultaneous deposit and withdrawal, or simultaneous management of external Guards.
+
+### Important Notes
+
+⚠️ **Combined Operations**: Can combine multiple operations in the same transaction to improve efficiency.
+
+---
+
+### Example
+
+#### Example 7.1: Combined Deposit and Withdrawal
+
+**Prompt**: For "team_treasury": 1) Deposit 10 WOW, 2) Withdraw 0.5 WOW to alice, in the same transaction.
+
+```json
+{
+  "operation_type": "treasury",
+  "data": {
+    "object": "team_treasury",
+    "deposit": {
+      "coin": {
+        "balance": 1000000000
+      },
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      }
+    },
+    "withdraw": {
+      "amount": {
+        "fixed": 500000000
+      },
+      "recipient": {
+        "name_or_address": "alice"
+      },
+      "payment_info": {
+        "remark": "treasury operation",
+        "index": 1
+      }
+    }
+  },
+  "env": {
+    "network": "testnet"
+  }
+}
+```
+
+**Execution Result**:
+```json
+{
+  "status": "success",
+  "objects": [
+    {
+      "type": "Treasury",
+      "object": "0xbf0f...6249",
+      "version": "254284",
+      "change": "mutated"
+    },
+    {
+      "type": "Payment",
+      "object": "0x45d6...fccd",
+      "change": "created"
+    },
+    {
+      "type": "WReceivedObject",
+      "object": "0xb74b...81d1",
+      "change": "created",
+      "owner": "alice_address"
+    },
+    {
+      "type": "Payment",
+      "object": "0xc462...16ac",
+      "change": "created"
+    }
+  ]
+}
+```
+
+> **Note**: Combined operations execute atomically. If any operation fails, the entire transaction is rolled back.
+
+---
+
+## Important Notes
+
+⚠️ **Treasury operations require Permission or external Guard verification.**
+
+⚠️ **External Guard verification allows permissionless operations with validation rules.**
+
+---
+
+## Related Components
+
+| Component | Description |
+|-----------|-------------|
+| **[Permission](permission.md)** | Permission management |
+| **[Guard](guard.md)** | Trust verification engine - validation rules for external operations |
+| **[Payment](payment.md)** | Direct coin transfers - payment tracking and management |
+| **[Allocation](allocation.md)** | Automatic fund distribution - auto-distribution of treasury funds |
+| **[Reward](reward.md)** | Marketing incentives - incentive pools linked to treasury |
+