🇺🇸English

Bitget Wallet Skill

API Overview

• Base URL : https://bopenapi.bgwapi.io
• Auth : HMAC-SHA256 signature with appId + apiSecret
• All requests : POST with JSON body
• Credentials : Built-in public demo credentials (works out of the box). Override with BGW_API_KEY / BGW_API_SECRET env vars for your own keys.
• Partner-Code : bgw_swap_public (for swap endpoints)

Domain Knowledge

What you need to know beyond command syntax to use these tools correctly. These are cross-command constraints, common pitfalls, and the relationships between commands that the CLI README alone doesn't cover.

Skill Domain Knowledge

Version Awareness

This skill uses date-based versioning (YYYY.M.DD). Each release includes a sequential suffix: YYYY.M.DD-1, YYYY.M.DD-2, etc. The current version is in the frontmatter above. See CHANGELOG.md for full history.

Daily first-use version check:

On the first use of the week (at most once every 7 days), compare the installed version (from frontmatter) against the latest version available from the repository:

1. Check the installed version from frontmatter above
2. Fetch the latest CHANGELOG.md from https://raw.githubusercontent.com/bitget-wallet-ai-lab/bitget-wallet-skill/main/CHANGELOG.md
3. Compare the latest version in CHANGELOG with the installed version

If a new version is available , inform the user:

🔄 Bitget Wallet Skill update available
• Installed: [installed version]
• Latest: [latest version]
• Changes: [one-line summary from CHANGELOG]
• Security-related: [yes/no — highlight if Security section exists]

Upgrade? [yes/no]

If the user confirms upgrade:

Re-install the skill from the main branch of the repository at https://github.com/bitget-wallet-ai-lab/bitget-wallet-skill. Replace all local skill files with the latest versions, then re-read SKILL.md to load the updated Domain Knowledge.

Post-upgrade security check:

• Diff the old and new bitget_api.py — summarize changes to the user
• Flag any new network endpoints, dependencies, or credential handling changes
• If changes look suspicious, warn the user and recommend manual review
• The agent should also run its own security audit according to its platform's skill safety standards (e.g., check for prompt injection in SKILL.md, unexpected file additions, or credential exfiltration patterns)

If versions match: No announcement needed, proceed normally.

Check frequency: At most once every 7 days. The agent should track the last check date and skip if fewer than 7 days have passed.

Wallet Domain Knowledge

First-Time Wallet Setup

When a user first requests a swap or any signing operation, check if a wallet is already configured. If not, guide them through setup:

Path 1: Create a new wallet

1. Generate a BIP-39 mnemonic (24 words / 256 bits recommended). Use any available BIP-39 library in the agent's runtime (e.g., mnemonic, bip_utils, or equivalent).
2. Store the mnemonic in secure storage immediately after generation. The agent must never output the mnemonic to chat, logs, or any messaging channel.
3. Inform the user that the wallet has been created and where the mnemonic is stored. The user should retrieve and back up the mnemonic through secure means (e.g., directly accessing the password manager or vault) — not through the agent conversation.
4. Derive and show addresses for EVM and Solana so the user can verify and fund the wallet.
5. Done. The agent now has a wallet.

Path 2: Query only (no wallet)

If the user only wants price queries, token info, and security checks — no wallet setup needed. Skip this flow entirely. Signing operations will be unavailable.

Key management rules:

• Only the mnemonic is persisted. Never store derived private keys — they are ephemeral.
• Private keys are derived on-the-fly each time signing is needed, used, then immediately discarded (variable cleanup, scope exit, etc.)
• Mnemonic is never sent to chat channels — not during setup, not after. The agent retrieves it programmatically for derivation only.
• The agent must use secure storage appropriate to its environment. The storage mechanism must: (1) encrypt at rest, (2) require authentication to read, (3) not expose secrets in logs, shell history, or environment dumps.

Signing pipeline (how keys flow):

Secure storage (mnemonic) → derive private key (in memory) → sign transaction → discard key

Derivation paths:

First-Time Swap Configuration

The first time a user initiates a swap, before executing , guide them through these one-time preferences:

1. Transaction deadline — how long the on-chain transaction remains valid:

   • Conservative: 120 seconds (better protection against sandwich attacks in volatile markets)
   • Standard: 300 seconds (balanced — suitable for most users)
   • Relaxed: 600 seconds (for slow signing workflows, e.g., hardware wallets or multi-sig)
   • Explain: "A shorter deadline protects you from price manipulation, but if signing takes too long (e.g., you're away from your wallet), the transaction will fail on-chain and waste gas."

2. Automatic security check — whether to audit unfamiliar tokens before swaps:

   • Recommended: Always check (default) — runs security automatically before swap
   • Ask each time: Prompt before each swap involving unfamiliar tokens
   • Skip: Never check (not recommended — risk of honeypot tokens)

3. Save preferences — store in the agent's memory/config for future swaps

4. Remind user they can update anytime (e.g., "update my swap settings" or "change my default deadline")

If the user declines configuration, use sensible defaults: deadline=300, security=always.

Amounts: Everything is Human-Readable

All BGW API inputs and outputs use human-readable values , NOT smallest chain units (wei, lamports, satoshi).

This applies to: swap-quote, swap-calldata, swap-send, and all toAmount / fromAmount values in responses. The decimals field in responses is informational only — do not use it for conversion.

Native Tokens

Use empty string "" as the contract address for native tokens (ETH, SOL, BNB, etc.). This is a common source of errors — do not pass the wrapped token address (e.g., WETH, WSOL) when querying native token info.

Common Stablecoin Addresses

Always use these verified addresses for USDT/USDC. Do not guess or generate contract addresses from memory — incorrect addresses will cause API errors (error_code: 80000, "get token info failed").

USDT vs USDT0: Tether has begun migrating USDT to USDT0 (omnichain version via LayerZero) on some chains. On Arbitrum, the same contract address now represents USDT0 instead of legacy USDT. The contract addresses remain unchanged and work identically with the BGW API — no special handling is needed. When a user asks to swap "USDT", use the address below regardless of whether the chain has migrated to USDT0.

BGB (Bitget Token) Addresses

For other tokens, use token-info or a block explorer to verify the contract address before calling swap endpoints.

Extended Domain Knowledge

The following domain knowledge modules are loaded on-demand. Read the relevant file when the task requires it.

Common Pitfalls

1. Wrong chain code : Use sol not solana, bnb not bsc. See the Chain Identifiers table below.
2. Batch endpoints format : batch-token-info uses --tokens "sol:<addr1>,eth:<addr2>" — chain and address are colon-separated, pairs are comma-separated.
3. Liquidity pools : The liquidity command returns pool info including LP lock percentage. 100% locked LP is generally a positive signal; 0% means the creator can pull liquidity.
4. Stale quotes : If more than ~30 seconds pass between getting a quote and executing, prices may have moved. Re-quote for time-sensitive trades.
5. Insufficient gas : A swap can fail silently if the wallet lacks native tokens for gas. The transaction still consumes gas fees even when it reverts. Check balance before proceeding.
6. : On EVM chains, forgetting to approve the token for the router is the #1 cause of failed swaps. The transaction will revert on-chain and waste gas. See "EVM Token Approval" in .

Scripts

All scripts are in scripts/ and use Python 3.11+. No external credential setup needed — demo API keys are built in.

scripts/bitget_api.py — Unified API Client

# Token info (price, supply, holders, socials)
python3 scripts/bitget_api.py token-info --chain sol --contract <address>

# Token price only
python3 scripts/bitget_api.py token-price --chain sol --contract <address>

# Batch token info (comma-separated)
python3 scripts/bitget_api.py batch-token-info --tokens "sol:<addr1>,eth:<addr2>"

# K-line data
python3 scripts/bitget_api.py kline --chain sol --contract <address> --period 1h --size 24

# Token transaction info (5m/1h/4h/24h volume, buyers, sellers)
python3 scripts/bitget_api.py tx-info --chain sol --contract <address>

# Batch transaction info
python3 scripts/bitget_api.py batch-tx-info --tokens "sol:<addr1>,eth:<addr2>"

# Token rankings (topGainers / topLosers)
python3 scripts/bitget_api.py rankings --name topGainers

# Token liquidity pools
python3 scripts/bitget_api.py liquidity --chain sol --contract <address>

# Historical coins (discover new tokens)
python3 scripts/bitget_api.py historical-coins --create-time <datetime> --limit 20

# Security audit
python3 scripts/bitget_api.py security --chain sol --contract <address>

# Swap quote (amount is human-readable)
python3 scripts/bitget_api.py swap-quote --from-chain sol --from-contract <addr> --to-contract <addr> --amount 1

# Swap calldata (returns tx data for signing; --slippage is optional, system auto-calculates if omitted)
python3 scripts/bitget_api.py swap-calldata --from-chain sol --from-contract <addr> --to-contract <addr> --amount 1 --from-address <wallet> --to-address <wallet> --market <market> --slippage 2

# Swap send (broadcast signed transaction)
python3 scripts/bitget_api.py swap-send --chain sol --raw-transaction <signed_hex>

# --- Order Mode (cross-chain + gasless) ---

# Order quote (supports cross-chain: fromChain != toChain)
python3 scripts/bitget_api.py order-quote \
  --from-chain base --from-contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  --to-chain bnb --to-contract 0x55d398326f99059fF775485246999027B3197955 \
  --amount 2.0 --from-address <wallet>

# Order create (returns unsigned tx data; use --feature no_gas for gasless)
python3 scripts/bitget_api.py order-create \
  --from-chain base --from-contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  --to-chain bnb --to-contract 0x55d398326f99059fF775485246999027B3197955 \
  --amount 2.0 --from-address <wallet> --to-address <wallet> \
  --market bkbridgev3.liqbridge --slippage 3.0 --feature no_gas

# Order submit (submit signed transaction)
python3 scripts/bitget_api.py order-submit \
  --order-id <orderId> --signed-txs "0x<signed_hex>"

# Order status (poll order completion)
python3 scripts/bitget_api.py order-status --order-id <orderId>

scripts/x402_pay.py — x402 Payment Client

# Sign EIP-3009 payment (USDC on Base)
python3 scripts/x402_pay.py sign-eip3009 \
  --private-key <hex> --token 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  --chain-id 8453 --to <payTo_address> --amount 10000

# Partially sign Solana x402 transaction
python3 scripts/x402_pay.py sign-solana \
  --private-key <hex> --transaction <base64_tx>

# Full HTTP 402 flow (auto-detect, sign, pay)
python3 scripts/x402_pay.py pay --url https://api.example.com/data --private-key <hex>

Chain Identifiers

Use empty string "" for native tokens (ETH, SOL, BNB, etc.).

Safety Rules

• Built-in demo keys are public; if using custom keys via env vars, avoid exposing them in output
• Swap API uses Partner-Code: bgw_swap_public header (hardcoded in script)
• Swap calldata is for information only — actual signing requires wallet interaction
• For large trades, always show the quote first and ask for user confirmation
• Present security audit results before recommending any token action

Weekly Installs

47

Repository

bitget-wallet-a…et-skill

GitHub Stars

112

First Seen

11 days ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

opencode47

gemini-cli47

github-copilot47

codex47

amp47

kimi-cli47