v1.1.4 — Agent-Wallet Integration

Release v1.1.4

This release focuses on strengthening wallet security through Agent-Wallet integration and improving interoperability with different MCP clients via flexible type coercion.

Key Features & Improvements

Agent-Wallet SDK Integration (v2.1.0)

Integrated the @bankofai/agent-wallet SDK to provide professional-grade key management.

• Encrypted Storage: Supports Keystore V3 to keep keys encrypted at rest.
• No Exposed Secrets: Private keys and mnemonics no longer need to be stored in cleartext environment variables.
• Standardized Path: Defaults to ~/.agent-wallet, keeping it consistent with the Agent-Wallet CLI.

Dual-Mode Wallet System

The server now automatically detects and operates in one of two modes:

1. Agent-Wallet Mode (Recommended): Triggered by setting AGENT_WALLET_PASSWORD. Provides high security and multi-wallet management.
2. Legacy Mode: Fallback support for TRON_PRIVATE_KEY or TRON_MNEMONIC for backward compatibility.

Advanced Wallet Management

• Seamless Switching: Internal support for provider.getActive, setActive, and getActiveId.
• Automatic Persistence: Active wallet choices are persisted directly in the SDK configuration, removing the need for a separate AGENT_WALLET_ID environment variable.

Enhanced Parameter Handling

• Smart Type Coercion: Used z.coerce for all numeric/amount fields (e.g., amount, callValue).
• Client Flexibility: Improved compatibility with LLMs and MCP clients that might send numbers instead of strings (or vice versa) for blockchain values.

Maintenance

• Protocol Update: Unified the MCP protocol version to 2025-11-25 across all transport layers.
• Code Quality: Refactored the wallet service for better singleton management and increased test coverage for edge-case signing scenarios.

---

Full Changelog: bankofai/mcp-server-tron@v1.1.3...v1.1.4