Multi-Token Payment Stream Bundler

WHAT IT DOES

Multi-Token Payment Stream Bundler enables you to create, fund, and manage payment streams that deliver multiple ERC-20 tokens simultaneously to a single recipient through one contract. Instead of creating separate stream contracts for each token, this tool bundles them into a single stream with unified start/end times, cliff periods, and vesting schedules. It reads your connected wallet address, token balances, decimals, current block timestamps, and existing stream contracts to provide a complete dashboard of active streams. You can create new bundled streams, withdraw accumulated tokens, cancel streams to recover remaining funds, and track stream history—all from one interface. This simplifies payroll, grants, and reward distribution where recipients receive multiple tokens over time.

HOW TO USE

Connect your wallet using the BGWallet connector and select your network. Paste the stream contract address you are using—you are responsible for verifying this contract. Enter the recipient's wallet address, then provide a comma-separated list of token addresses and corresponding amounts. Set the stream start and end times as Unix timestamps, and optionally add a cliff duration (in seconds). Click "Create stream bundle" to review the details, then sign the transaction to deploy the stream. The tool will check your token balances and handle approvals for each token automatically. After creation, you can manage existing streams by entering the stream ID and using the Withdraw or Cancel buttons—withdraw pulls accumulated tokens to the recipient, while cancel ends the stream and returns remaining funds to the sender.

THE REAL MECHANISM — BATCHED APPROVAL WITH ATOMIC STREAM CREATION

Unlike simple stream factories that create separate contracts per token, this tool uses a single stream contract that holds multiple token balances and computes vesting schedules in parallel. The contract stores arrays of token addresses and amounts, and tracks withdrawn amounts per token independently. When you create a stream, the tool first fetches decimals for each token via on-chain reads, then parses amounts with the correct precision. It checks your balance for each token and sequentially approves the stream contract for the exact required amount—never unlimited approvals. The entire creation is atomic: if any approval fails or any token transfer reverts, the stream is not created and no tokens move. The contract uses block timestamps to calculate vested amounts, applying the cliff as a minimum lock period before any withdrawals are allowed. Post-creation, the tool reads the stream struct to display current status, and withdrawal/cancel operations update the contract state with proper overflow-protected arithmetic.

WHAT IT CANNOT SEE

Cannot verify off-chain payment obligations—this tool has no visibility into employment contracts, grant agreements, or whether a stream payment is actually owed. It cannot validate recipient identity or confirm that the recipient address belongs to the intended party. The tool cannot ensure token solvency over stream duration—it does not monitor token liquidity, de-pegging events, or token contract upgrades that could affect the stream. It cannot detect if the stream contract is malicious or compromised, or if the contract owner has upgrade or pause capabilities. The tool does not audit the stream contract code, verify its implementation against security best practices, or simulate edge-case scenarios like reentrancy or overflow attacks. It cannot recover funds sent to an incorrect stream contract or reverse transactions after confirmation.

PLEASE NOTE — EVM CHAINS ONLY

This tool exclusively supports EVM-compatible chains where ethers.js can connect via standard JSON-RPC. It does not support non-EVM chains such as Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. All tokens must be ERC-20 standard; native currency streams are not supported. The stream contract must implement the specific interface expected by this tool (createStream, withdraw, cancel, getStream)—custom implementations may not work. Always test with small amounts on a testnet first. This tool is a stream management interface, not a financial advisor or legal counsel.