broadcast-sign-transfer_skill

Overview

This skill automates constructing, locally signing, and broadcasting EVM transfers via the OKX Web3 API. It supports native token transfers and ERC20 token transfers across supported EVM chains, returning a tx hash and explorer link on success. Private keys never leave the host; signing is performed locally.

How this skill works

The skill validates inputs, fetches chain state (nonce and gas parameters), and builds either a native transfer or an ERC20 transfer call. It locally signs the raw transaction with a private key provided via environment variable, then submits the signed payload to OKX Broadcast API. Results include OKX order ID, transaction hash, and a block explorer URL, or a clear error reason when broadcasting fails.

When to use it

• You need to send a native token (ETH, BNB, MATIC) or an ERC20 token on a supported EVM chain.
• You want local signing so the private key never leaves your machine (private key is loaded from env).
• You plan to broadcast via OKX Web3 API and require OKX Web3 credentials configured.
• You need automatic nonce and gas handling (legacy or EIP-1559) with optional MEV protection.
• You want a simple programmatic or CLI way to send tokens with returned explorer URL.

Best practices

• Always set WALLET_PRIVATE_KEY and OKX Web3 API credentials in environment variables; do not hardcode keys.
• Double-check recipient address and amount before broadcasting; on-chain transactions are irreversible.
• For ERC20 transfers, provide the correct token contract address and allow the estimator to calculate gas (it multiplies estimate by 1.2).
• Use MEV protection only on chains that support it; the skill will error if enabled on unsupported chains.
• Confirm transaction inclusion via returned explorer_url rather than relying solely on broadcast success.

Example use cases

• Send a small BNB payment from a server by calling transfer_native with chain_index="56".
• Distribute USDT payments on BSC by providing the token contract address and amount to transfer_token.
• Integrate into a backend payout flow: construct, sign locally, and broadcast via OKX to avoid exposing private keys to remote services.
• CLI-driven ad-hoc transfers during maintenance or manual fund moves, using the provided script flags.