sdk-wallet-operations_skill

Overview

This skill helps initialize and configure the BankrClient SDK with secure wallet operations for payment and receiving flows. It explains single- and two-wallet setups, environment variables, and client options to get a working BankrClient quickly. The goal is a minimal, secure integration for micropayments and token receipt workflows.

How this skill works

It creates a BankrClient instance with a required payment private key and an optional receiving wallet address. The skill covers initializing the client, overriding wallet per request, and configuring baseUrl and timeout options. It also outlines methods you will use (promptAndWait, prompt, pollJob, getJobStatus, cancelJob, getWalletAddress) to drive requests and manage jobs.

When to use it

• Setting up the SDK or initializing BankrClient for the first time
• Configuring environment variables and private key handling
• Creating a two-wallet architecture (payment vs receiving)
• Deriving or retrieving the current context wallet address
• Overriding wallet address for a single request

Best practices

• Always supply the payment private key via environment variables, never commit keys to source control
• Use two wallets: a hot payment wallet with minimal balance and a cold receiving wallet for tokens
• Keep the payment wallet balance minimal (e.g., $1–$2 USDC) to limit exposure
• Rotate payment keys periodically and revoke if compromised
• Use per-request walletAddress overrides when you need temporary routing of assets

Example use cases

• Basic initialization with a single wallet to start sending micropayment requests
• Recommended two-wallet setup: payment privateKey for signing, walletAddress for receiving swaps and NFTs
• Per-request override to route a specific swap or payout to a different receiving address
• Adjust baseUrl and timeout for non-production endpoints or long-running jobs
• Call getWalletAddress() to confirm the context/receiving wallet your client will use