multichain-protocol_skill

This skill lets you manage a 19-chain wallet from a single ICP canister, enabling sends, swaps, cross-chain bridging, DeFi positions, and automated trading.

Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill multichain-protocol

_meta.json300 B
SKILL.md34.5 KB
wallet_commands.py12.8 KB

Overview

This skill turns an ICP canister or CLI agent into a single, unified 19-chain crypto wallet using MeneseSDK. It supports sending tokens, swapping on major DEXes, cross-chain bridging, DeFi position management, and automation like DCA and stop-loss — all callable from one ICP principal. The first five transactions are free and read-only queries (balances, addresses, quotes) remain free.

How this skill works

The skill exposes MeneseSDK canister calls and CLI helpers to fetch deterministic addresses, check balances across 19 chains, sign and broadcast transactions, request DEX quotes, and execute swaps or bridges. EVM chains require your RPC endpoint for signing and quoting; ICP canister deployments enable timers and multi-user automation. Common patterns include caching deterministic addresses, batching balance reads, and always fetching quotes before swaps.

When to use it

Manage multi-chain holdings from a single ICP principal or canister.
Automate periodic trades (DCA), rebalancing, or stop-loss rules via ICP timers.
Perform cross-chain bridges and fast ETH↔SOL transfers.
Integrate payment flows or escrow using ICRC-2 approve/transferFrom.
Prototype multi-chain wallet features quickly from CLI without local wallets.

Best practices

Cache deterministic addresses once per principal to avoid repeated inter-canister calls.
Always get a quote before executing swaps and set sensible slippage limits.
Provide reliable EVM RPC endpoints (Alchemy/Infura) for production use.
Use canister deployment for multi-user scenarios and to enable timers/automation.
Handle chain-specific return types carefully (many functions return flat records or different result shapes).

Example use cases

Deploy a canister that runs daily DCA purchases across BTC, ETH, and SOL for multiple users.
Accept payments in many chains, auto-convert via ICP DEXes or bridge to a settlement chain.
Build an escrow that uses ICRC-2 approve + transferFrom to manage ICP token flows.
Execute a cross-chain arbitrage flow: quote on DEX, swap, and bridge funds between chains.
Operate a single CLI wallet to view balances, send tokens, and test swaps during development.

FAQ

Yes. EVM operations require your RPC URL; use production-grade providers like Alchemy or Infura for reliability.

Are reads (balances, addresses, quotes) charged?

Read-only operations are free. Transaction signing and execution incur per-action fees after the first five free sends.