Overview
Wallets are where your API revenue lands. Each wallet stores your on-chain addresses across supported networks. When you activate a proxy, you assign it a wallet — all payments for that proxy flow directly to the wallet’s addresses on-chain, with no intermediary holding funds.Supported networks
| Network | Type | Chain |
|---|---|---|
| Solana | Native | mainnet-beta |
| Base | EVM | L2 (Ethereum) |
| Polygon | EVM | Mainnet |
| Monad | EVM | Mainnet |
Wallet configuration
| Field | Description |
|---|---|
| Name | A label to identify this wallet (e.g. “Main Wallet”, “Production”) |
| Solana address | Public key for Solana mainnet-beta |
| EVM address | Address used across Base, Polygon, and Monad |
Funding requirements
Before you can activate a proxy, its assigned wallet must meet minimum balance thresholds:- SOL — required for gas on Solana
- USDC — required as collateral across all supported chains
Funding flow
When you first create a wallet, Corbits displays a funding modal with your Solana address and a QR code. Send SOL and USDC to that address to meet the minimum balance requirements. The modal polls for incoming funds automatically and lets you continue once they’re received.Balance refresh
Wallet balances (native token and USDC) are cached and refreshed approximately every 60 seconds. Each wallet card also has a manual Refresh button if you want to check immediately after funding.Multiple wallets
You can create multiple wallets within an organization — useful for separating revenue streams by product, team, or billing entity. Each proxy is assigned to exactly one wallet.Related
Proxies
Assign a wallet when creating a proxy
Dashboard
View earnings across all proxies