Revenue & Fees
How partners earn revenue on leveraged trades.
Partner Revenue Model
Lavarage is building a revenue-sharing model for integration partners. Details will be finalised soon.
How it will work
- Lavarage base fee: Applied on every trade (~1% of position size at open AND ~1% at close — see fee structure below; per-token
discountBpscan reduce this) - Partner spread: Partners configure their own fee (in basis points) on top of the base fee
- Revenue: Partners keep 100% of their configured spread
- Settlement: Fees are collected atomically on-chain at both position open and position close
Current state
Partner fee configuration is under development. Contact the team to discuss revenue terms for your integration.
Contact: https://lavarage.xyz/partners
Current fee structure
Protocol fees are charged at both open and close — not only at open. This matches the on-chain program and the trader-facing fee guide.
| Fee | Amount | When |
|---|---|---|
| Protocol open fee | 1% of position size (before per-token discountBps) | On open |
| Protocol close fee | 1% of position value at close (before per-token discountBps) | On close |
| Per-token discount | 0–100% reduction via discountBps | Applied at both open and close |
| Solana network fee | ~0.000005 SOL | On every transaction |
| Account rent | ~0.01 SOL | Returned on position close |
Both the open and close fees are reduced by the token's discountBps field. Check GET /api/v1/tokens — each token includes discountBps (0 = no discount, 10000 = 100% discount). After applying typical discounts, observed effective fees are roughly 0.30–0.45% of position size at both open and close (≈ 0.10–0.15% of collateral at 3x leverage). The exact open fee is in the fee field of POST /api/v1/positions/quote / quote-by-token; the exact close fee is in the fee field of POST /api/v1/positions/close-quote. Always quote these to your users before signing.
Trade-history denomination
When reading historical fees via GET /api/v1/positions/trade-history, the protocolFee field on each row is in raw smallest units of that row's protocolFeeMint (typically the quote token for LONG/BORROW, the base token for SHORT). Divide by 10^decimals of protocolFeeMint for a human amount. Both OPEN and CLOSE rows carry a non-zero protocolFee.