SOL rent and account capacity
Solana accounts hold a rent-exempt SOL balance while they store state. That balance is separate from a transaction's network fee. A supported sponsored action has the server pay the network fee while you fund the account rent.
The app quotes rent from the connected network. It shows the account type, SOL amount and refund conditions before you approve creation.
The default setup
The first USDC deposit offers a preset for two positions and two fallback Request accounts, plus the one-click authorization and account setup required by your current state. Expand the list to see each cost. You can change the preset or switch it off.
Two positions support a two-leg strategy. The two Request budgets keep the conventional submission path available. The standard signed-intent path does not create a Request account for each order; an intent open uses the future Position rent from your prepaid balance.
How capacity is calculated
Both collateral paths use the same canonical account's prepaid SOL. The UI deducts existing commitments before showing additional holding and concurrency capacity.
Conventional pending open commitment = Request rent + future Position rent
Conventional pending close commitment = Request rent
Signed-intent open commitment = future Position rent
The same SOL cannot back eight pending opens and eight future positions independently. Once an open succeeds, its temporary Request rent is released where applicable, while its Position rent stays occupied until that position closes.
Protocol limits also apply: currently 128 positions and 32 on-chain Requests per collateral account. Offline intents have their own nonce window and relay limits; the 32-Request count is not a universal limit on every order message.
Deposits and withdrawals
The SOL row in Account manages prepaid rent. You can top it up before trading and withdraw the unused part. Existing positions, pending requests and other live account commitments reduce the withdrawable amount.
If you skip prepayment, a supported wallet flow asks you to fund the rent when it is needed. The confirmation explains the account being created. A trading-key signature alone does not authorize an external wallet SOL transfer.
Refund categories
Rent management lists the account, staking/reward state, authorization, requests/positions and OH-account items that exist for your wallet. Each available action shows its blocking conditions. Refund all follows the eligible steps and refreshes state between them.
- Cancelling or rejecting a conventional open releases its request rent and future-position commitment.
- A successful open retains Position rent until the position is closed.
- Closing a position returns rent to its recorded payer. If a debt receipt is needed, part can stay with that receipt until cleanup.
- Cancelling an auction order returns unfilled OH first; its SOL can wait for order-index cleanup.
- Closing reward state requires its outstanding rewards and history obligations to be settled.
- Account closure requires its remaining balances and dependent state to be resolved.
The refund follows the recorded rent ownership. A later SOL top-up belongs to the user who deposited it. Wallet token-account rent, the standard OH mint and network fees already spent are separate from these protocol-account refunds.