Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Finance & Trading
impossible finance skills
BSC (Binance Smart Chain) trading on Impossible Finance DEX — wallet creation, token swaps, pair discovery, and balance management.
skill openclawclawhub Free
BSC (Binance Smart Chain) trading on Impossible Finance DEX — wallet creation, token swaps, pair discovery, and balance management.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- skill.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- KJ-Script
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Purpose & Scope
This skill enables an AI agent to trade tokens on Impossible Finance DEX (BSC mainnet). Impossible Finance V3 Swap is interface-compatible with Uniswap V2 but includes modifications for higher capital efficiency trades (lower slippage for supported pairs, especially stablecoins). It covers: Wallet creation — Generate a BSC keypair and store it locally for transaction signing. Token discovery — Resolve any BEP-20 token by contract address, check pair existence and liquidity. Swaps — Execute token swaps through Impossible Finance V3 Router with slippage protection. Balance checks — Query native BNB and BEP-20 token balances. Top-ups — Provide the agent's BSC address so the user can fund it.
What This Skill Does NOT Do
It does not manage ClawChain agent registration. For that, see the clawchain skill (skill.md or curl_skills.md). It does not provide investment advice or execute trades without user confirmation. It does not access any files outside of ~/.config/impossible_agent/ and optionally ~/.config/clawchain/credentials.json (read-only, for EVM key registration only).
Transparency: Files Accessed
FileAccessPurpose~/.config/impossible_agent/wallet.jsonRead/Write (created once)Stores the agent's BSC private key and address for signing transactions~/.config/clawchain/credentials.jsonRead-only (optional)Used only if registering BSC public key on ClawChain for EVM event tracking
Transparency: Network Calls
EndpointPurposeBSC RPC (BSC_RPC_URL)Read blockchain state (balances, pair info) and submit signed transactionsImpossible Finance Router/Factory contractsOn-chain calls to discover pairs, get quotes, execute swaps
Configuration (BSC Mainnet)
Set these environment variables before using the skill. All have sensible defaults for BSC mainnet: export BSC_RPC_URL="https://bsc-dataseed1.binance.org" export BSC_CHAIN_ID=56 # Impossible Finance V3 (BSC mainnet) export IF_ROUTER="0xCCF4881b849d94C15c98567Ba71b08eD829ABA33" export IF_FACTORY="0xBf9D97eAF551877E4710d8E9d0519F79E03E5E69" export WBNB="0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c" Block explorer: https://bscscan.com Impossible Finance Swap UI: https://app.impossible.finance/swap
Prerequisites
This skill requires Node.js 18+ and the ethers npm package (v6): npm install ethers # or: pnpm add ethers
1. Wallet Setup — Create Wallet and Save Keys
The agent needs a local wallet file containing a private key and public address so it can sign transactions. This file is created once during initial setup and reused for all subsequent operations. ⚠️ Security: The wallet file contains sensitive key material. See the Security Notes section for encryption and file permission best practices. Only use a dedicated, small-balance wallet — never your main funds.
Option A: Using Node.js (recommended)
Run this script to generate a new wallet and write it to a file: node -e " const fs = require('fs'); const path = require('path'); const { ethers } = require('ethers'); const wallet = ethers.Wallet.createRandom(); const dir = process.env.HOME + '/.config/impossible_agent'; fs.mkdirSync(dir, { recursive: true }); const file = dir + '/wallet.json'; fs.writeFileSync(file, JSON.stringify({ privateKey: wallet.privateKey, address: wallet.address, publicKey: wallet.publicKey }, null, 2), { mode: 0o600 }); console.log('Wallet saved to ' + file); console.log('Address: ' + wallet.address); " Default file location: ~/.config/impossible_agent/wallet.json File format (wallet.json): { "privateKey": "0x...", "address": "0x...", "publicKey": "0x..." } privateKey — Used to sign transactions. This file is restricted to owner-only access (chmod 600). Never log or expose this value. address — The agent's BSC account. The user sends BNB/tokens to this address to fund the agent. publicKey — Derived from private key. Used optionally for ClawChain EVM event tracking registration.
Option B: Custom path
To use a different path, set the environment variable: export IF_WALLET_FILE="$HOME/.config/impossible_agent/wallet.json" # Then in the script, write to process.env.IF_WALLET_FILE
After wallet setup
Read address and publicKey from wallet.json. Tell the user: My BSC address for top-ups is: <address> The user must send native BNB (for gas) and any tokens they want the agent to swap to this address. (Optional) Register your BSC public key on ClawChain for EVM event tracking — see Section 1.5.
1.5. Register Public Key on ClawChain (Optional)
This step is optional. It links your BSC wallet public key to your ClawChain agent account to enable tracking EVM events on Chromia. Skip this if you don't need on-chain event tracking. Prerequisite: You must already have a registered and claimed agent on ClawChain. See the clawchain skill for registration instructions.
Prerequisites
A registered agent account on ClawChain (Chromia) An authenticated session (FT4 keypair from ClawChain registration) Your wallet.json file with publicKey (required) and optionally address The ClawChain credentials file at ~/.config/clawchain/credentials.json (created by the clawchain skill)
Environment Variables for ClawChain
These are the same variables used by the clawchain skill — set them if not already configured: export CLAWCHAIN_BRID="9D728CC635A9D33DAABAC8217AA8131997A8CBF946447ED0B98760245CE5207E" export CLAWCHAIN_NODE="https://chromia.01node.com:7740"
Registration Steps
Option A: Using Chromia CLI # Read wallet info WALLET_FILE="${IF_WALLET_FILE:-$HOME/.config/impossible_agent/wallet.json}" PUBLIC_KEY=$(cat $WALLET_FILE | grep -o '"publicKey": "[^"]*' | cut -d'"' -f4) ADDRESS=$(cat $WALLET_FILE | grep -o '"address": "[^"]*' | cut -d'"' -f4) # Register public key on Chromia chr tx register_evm_public_key \ "impossible_finance" \ "$PUBLIC_KEY" \ "BSC" \ 56 \ "$ADDRESS" \ --ft-auth \ --secret ~/.config/clawchain/credentials.json \ -brid $CLAWCHAIN_BRID \ --api-url $CLAWCHAIN_NODE \ --await Arguments: wallet_type public_key chain network_id address Network IDs: BSC Mainnet: 56 BSC Testnet: 97 Ethereum Mainnet: 1 Ethereum Goerli: 5 Polygon Mainnet: 137 Note: If you don't have an address, use "" (empty string) for the last parameter. Option B: Using JavaScript/TypeScript If you're integrating this into a web application with an authenticated FT4 session: const fs = require('fs'); const walletFile = process.env.IF_WALLET_FILE || '~/.config/impossible_agent/wallet.json'; const walletData = JSON.parse(fs.readFileSync(walletFile, 'utf8')); // Assuming you have a Chromia session object (from @chromia/ft4) const result = await session.call({ name: 'register_evm_public_key', args: [ 'impossible_finance', // wallet_type walletData.publicKey, // public_key (required) 'BSC', // chain 56, // network_id (56 for BSC mainnet, 97 for testnet) walletData.address || "" // address (optional) ] }); console.log('Public key registered:', result);
Query Registered Public Keys
To check which public keys are registered for your agent: # Get all registered public keys for an agent chr query get_evm_public_keys 'agent_name=your_agent_name' \ -brid $CLAWCHAIN_BRID --api-url $CLAWCHAIN_NODE # Get specific public key by wallet type chr query get_evm_public_key_by_type \ 'agent_name=your_agent_name' \ 'wallet_type=impossible_finance' \ -brid $CLAWCHAIN_BRID --api-url $CLAWCHAIN_NODE
Error Handling
"Public key already registered": The public key is already registered for this agent. Query existing keys to verify. "Public key is required for EIF event tracking": You must provide a public key. "Invalid public key format": Public key must start with 0x and be at least 66 characters (0x + 64 hex chars). "Agent not found": Ensure your agent account exists on ClawChain. Authentication errors: Ensure you have a valid FT4 session authenticated with your Chromia account.
2. How the User Can Top Up the Agent Account
The agent does not have an "account" on a server — it has a BSC address (from wallet.json). Fund the agent by sending BNB and tokens to that address:
Get BNB for gas and swaps
Buy BNB on an exchange or bridge from another chain. Send BNB to the agent address: <address> from wallet.json. Add BSC Mainnet in MetaMask (Chain ID 56, RPC above), then transfer BNB to the agent.
Get tokens
Send any BEP-20 token to <address>. The agent can swap via Impossible Finance if a pair exists (e.g. USDT/BNB, BUSD/BNB, IF/BNB).
Check balance
Native (BNB): provider.getBalance(address) Any BEP-20 token: call balanceOf(address) on the token contract.
3. Discovering Available Tokens and Swaps
The agent can work with any BEP-20 token and determine which swaps are possible. No fixed token list is required.
Which tokens are available
By contract address: Any BEP-20 token is identified by its contract address. Accept token addresses from the user or from token lists. Resolve symbol and decimals: Call the token contract (ERC-20/BEP-20): symbol() → e.g. "USDT", "WBNB", "IF" decimals() → use for amount math and display (e.g. 18 or 6) name() → full name (optional) Token lists (optional): Impossible Finance and BSC publish token lists; the agent can also accept any user-provided contract address. Native gas token: BNB is the chain native token; the wrapped version is WBNB (address in config). Use WBNB in router paths.
Which swaps are available
Get the Factory: Use the factory address from config (IF_FACTORY). Check if a pair exists: Call factory.getPair(tokenA, tokenB). If the result is the zero address (0x000...), no pair exists. Otherwise it is the pair contract address. Check liquidity: On the pair contract, call getReserves(). If both reserves are > 0, the pair has liquidity and that swap is available. Quote before swapping: Use the router's getAmountsOut(amountIn, path) (read-only). If the call reverts or returns zero for the output amount, the swap is not feasible (no liquidity or invalid path). Multi-hop paths: If there is no direct A–B pair, try a path via WBNB: [tokenA, WBNB, tokenB]. Call getAmountsOut(amountIn, path); if it succeeds and returns a positive amount, the swap is available. Impossible Finance advantage: Stablecoin pairs on Impossible Finance may offer lower slippage than PancakeSwap due to V3's capital efficiency improvements.
4. Making a Trade (Swap on Impossible Finance)
The agent uses the private key from wallet.json to sign a swap transaction and sends it to BSC.
Impossible Finance contracts (BSC mainnet)
ContractAddressRouter0xCCF4881b849d94C15c98567Ba71b08eD829ABA33Factory0xBf9D97eAF551877E4710d8E9d0519F79E03E5E69WBNB0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c
Common swap methods (Uniswap V2-compatible)
MethodUse caseswapExactETHForTokensSwap exact BNB for tokens (min amount out)swapExactTokensForETHSwap exact tokens for BNBswapExactTokensForTokensSwap exact token A for token BswapTokensForExactTokensSwap tokens for exact amount of token B
Swap flow (any token pair with liquidity)
Load wallet from wallet.json (privateKey + address). Connect to BSC: new ethers.JsonRpcProvider(BSC_RPC_URL) (mainnet: chain id 56). Resolve tokens: Use token contract addresses (from user or discovery). For native BNB use WBNB in the path. Check swap availability: Call router getAmountsOut(amountIn, path). If it reverts or returns zero, try a multi-hop path (e.g. [tokenA, WBNB, tokenB]) or inform the user the pair has no liquidity. Build path: e.g. BNB → token: [WBNB, tokenAddress]; token → BNB: [tokenAddress, WBNB]; token → token: [tokenA, WBNB, tokenB] (or direct if pair exists). Get router contract (address above), ABI for swapExactETHForTokens, swapExactTokensForETH, or swapExactTokensForTokens. Deadline: Math.floor(Date.now() / 1000) + 300 (e.g. 5 minutes). amountOutMin: from getAmountsOut(amountIn, path) then apply slippage (e.g. 1% = amountOut * 0.99). Sign and send: For BNB → token use { value: amountInWei }; for token → BNB or token → token, approve router for the token first, then call the swap.
Slippage
amountOutMin = expected output × (1 - slippage). E.g. 1% slippage → multiply by 0.99. For volatile pairs use 2–5%. Impossible Finance may allow tighter slippage on stablecoin pairs due to V3 capital efficiency.
Token decimals
BNB has 18 decimals. 1 BNB = 1e18 wei. Many BEP-20 tokens use 18 decimals; USDT/USDC often use 6. Check the token contract or docs.
Read wallet (do not expose private key in logs)
Read ~/.config/impossible_agent/wallet.json (or IF_WALLET_FILE). Use address when telling the user where to top up. Use privateKey only inside the signing process (ethers Wallet). Never log or print the private key.
Execute swap (high level)
Load wallet.json. Create ethers.Wallet(privateKey, provider). Build router call (e.g. swapExactETHForTokens) with path, deadline, amountOutMin. Send transaction: tx = await router.swapExactETHForTokens(...); await tx.wait(). Return tx hash to user: https://bscscan.com/tx/<hash>.
Get quote before swapping
Call router getAmountsOut(amountIn, path) (read-only) to get expected amountOut, then compute amountOutMin with slippage.
6. Example Token Addresses (BSC Mainnet)
SymbolAddressNotesWBNB0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095cNative wrapped; use in pathsUSDT0x55d398326f99059fF775485246999027B3197955StablecoinBUSD0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56StablecoinIF0xb0e1fc65c1a741b4662b813eb787d369b8614af1Impossible Finance governance tokenIDIA0x0b15Ddf19D47E6a86A56148fb4aFFFc6929BcB89Impossible Decentralized Incubator Access token Do not limit to these. The agent should accept any BEP-20 address and discover availability via getPair / getReserves and getAmountsOut (see §3). If a pair has no liquidity, try a multi-hop path via WBNB or use the Impossible Finance UI.
File Permissions
wallet.json must be restricted to owner-only access. The wallet creation script sets mode: 0o600 automatically. Verify with: chmod 600 ~/.config/impossible_agent/wallet.json ls -la ~/.config/impossible_agent/wallet.json # Should show: -rw-------
Dedicated Wallet
Use this wallet only for the agent and only with amounts you accept to lose if the machine or file is compromised. Do not reuse a wallet that holds large funds elsewhere. Create a fresh, dedicated wallet. For testnet usage, no real funds are at risk.
Key Handling Best Practices
Never log the private key to console, files, or monitoring systems. Never transmit the private key over the network. All signing happens locally. The agent reads the private key only to construct an ethers.Wallet instance for signing. It is never sent to any remote endpoint. Consider using encrypted keystores (ethers.js Wallet.encrypt()) for production use. The agent would prompt for a password to decrypt at startup.
Optional: Encrypted Keystore
For enhanced security, use ethers.js encrypted wallet format instead of plaintext: // Create encrypted wallet (during setup) const encrypted = await wallet.encrypt("your-password"); fs.writeFileSync(file, encrypted, { mode: 0o600 }); // Load encrypted wallet (during operations) const wallet = await ethers.Wallet.fromEncryptedJson( fs.readFileSync(file, 'utf8'), "your-password" );
8. Errors
ErrorMeaning / actioninsufficient fundsNot enough BNB for gas or not enough token/BNB for the swap. User should top up.execution reverted: INSUFFICIENT_OUTPUT_AMOUNTSlippage too low; increase or retry.execution reverted: EXPIREDDeadline passed; rebuild tx with new deadline.nonce too lowReuse of nonce; wait and retry or refresh nonce from chain.execution reverted: PAIR_NOT_EXISTNo pair exists for this token combination. Try a multi-hop path via WBNB.
9. Links
Impossible Finance Swap: https://app.impossible.finance/swap Impossible Finance Docs: https://docs.impossible.finance Impossible Finance GitHub: https://github.com/ImpossibleFinance BSC explorer: https://bscscan.com
Category context
Trading, swaps, payments, treasury, liquidity, and crypto-financial operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- skill.md