eliza-plugin-insumer 1.0.2 → 1.0.4
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/README.md +11 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -63,7 +63,7 @@ Attestation ATST-A7C3E: PASS
|
|
|
63
63
|
|
|
64
64
|
### CHECK_TRUST
|
|
65
65
|
|
|
66
|
-
Generate a structured wallet trust profile with 17+ checks across stablecoins (USDC on 7 chains), governance tokens (UNI, AAVE, ARB, OP), NFTs (BAYC, Pudgy Penguins), and staking (stETH, rETH, cbETH). Optional cross-chain with Solana and XRPL wallets.
|
|
66
|
+
Generate a structured wallet trust profile with 17+ checks across stablecoins (USDC on 7 chains), governance tokens (UNI, AAVE, ARB, OP), NFTs (BAYC, Pudgy Penguins, Wrapped CryptoPunks), and staking (stETH, rETH, cbETH). Optional cross-chain with Solana and XRPL wallets.
|
|
67
67
|
|
|
68
68
|
**Example conversation:**
|
|
69
69
|
```
|
|
@@ -93,10 +93,20 @@ Batch Trust: 3 profiles
|
|
|
93
93
|
0x1234...: 3/17 checks passed (TRST-D4M6H)
|
|
94
94
|
```
|
|
95
95
|
|
|
96
|
+
## Wallet Auth (JWT)
|
|
97
|
+
|
|
98
|
+
The VERIFY_WALLET action supports `format: "jwt"` when the user requests a JWT or bearer token. The response includes a standard ES256-signed JWT alongside the attestation, verifiable by any JWT library via the JWKS endpoint at `GET /v1/jwks`. Use this for direct API gateway integration (Kong, Nginx, Cloudflare Access, AWS API Gateway).
|
|
99
|
+
|
|
96
100
|
## Provider: WALLET_CREDENTIALS
|
|
97
101
|
|
|
98
102
|
Automatically detects wallet addresses (EVM, Solana, XRPL) in conversation and signals that verification actions are available. Dynamic — only activates when wallet patterns are found.
|
|
99
103
|
|
|
104
|
+
## Handling `rpc_failure` Errors
|
|
105
|
+
|
|
106
|
+
If the API cannot reach one or more data sources (RPC nodes, Helius, XRPL, Covalent) after retries, `VERIFY_WALLET` and `CHECK_TRUST` actions return `ok: false` with error code `rpc_failure`. No signature, no JWT, no credits charged. This is a retryable error — the agent should retry after 2-5 seconds.
|
|
107
|
+
|
|
108
|
+
**Important:** `rpc_failure` is NOT a verification failure. Do not treat it as `pass: false`. It means the data source was temporarily unavailable and the API refused to sign an unverified result.
|
|
109
|
+
|
|
100
110
|
## Supported Chains (32)
|
|
101
111
|
|
|
102
112
|
**11 RPC chains:** Ethereum, BNB Chain, Base, Avalanche, Polygon, Arbitrum, Optimism, Chiliz, Soneium, Plume, World Chain
|
package/package.json
CHANGED