FRB Pricing Explained: Performance Fees, Gas Costs, and What Users Still Pay
**Answer first** - FRB pricing should be evaluated as a net-execution model, not as a promise of returns. The user still controls the wallet, chooses the strategy, pays network cos
Answer first - FRB pricing should be evaluated as a net-execution model, not as a promise of returns. The user still controls the wallet, chooses the strategy, pays network costs, and accepts market risk. FRB fees apply according to the current terms on the Pricing page, and users should model gas, relay tips, RPC subscriptions, slippage, and failed execution before moving from simulation to live trading.
This article exists because "free bot", "performance fee", and "no subscription" are often used loosely in crypto. The safer question is not "what does it cost to start?" but "what costs show up after a trade is executed, and what can still go wrong?"
The cost stack
Every MEV workflow has more than one cost layer:
| Cost | Who controls it | Notes |
|---|---|---|
| Software fee | FRB terms | Check the current Pricing page. |
| Gas and priority fees | Network conditions | Paid to the chain or validator path, not to FRB. |
| Relay tips | Bundle route | Relevant on lanes like Jito or builder/relay paths. |
| RPC or node cost | User choice | Free endpoints are usually fine for learning, not for serious latency. |
| Slippage | Market and settings | Can turn a gross-positive route into a net loss. |
| Failed execution | Chain and strategy | Private bundles may avoid some on-chain failure cost, but not every path is costless. |
| Operational cost | User environment | Windows security, uptime, wallet hygiene, monitoring, and support time. |
When comparing FRB with subscription bots, Telegram bots, or DIY code, compare total cost after execution outcomes. A cheap tool that causes poor routing, stale pricing, or weak controls can be expensive in practice.
What "performance fee" should mean
A performance-fee model is designed to align software cost with outcomes. In plain English, fees should be tied to net profitable executed trades under the current terms, not to every click or every simulated opportunity.
That does not mean the user has no costs. Gas, relay tips, RPC fees, and slippage remain part of the user's execution environment. It also does not mean every strategy will be net positive. A performance fee is a billing model, not a risk model.
Before live execution, use this simple review:
Net result = realized output - input cost - gas - tips - slippage - software fees
If the route only looks attractive before gas or slippage, it is not a healthy route.
How FRB differs from subscription pricing
Subscription bots usually charge whether the strategy works or not. That can be clean for budgeting, but it can pressure small accounts to overtrade just to justify the monthly bill.
Performance-fee pricing has a different trade-off:
| Model | Better for | Watch out for |
|---|---|---|
| Monthly subscription | Predictable software budget | Subscription can eat small accounts during quiet markets. |
| Per-trade fee | High-frequency casual trading | Fees apply even on trades that are not MEV-positive. |
| Performance fee | Net profitable executed routes | You still need clean cost accounting and risk limits. |
| DIY open-source | Engineers who can maintain infra | Time, security, and missed-execution cost are real. |
FRB is most attractive when the user cares about local control, private-bundle workflows, and simulation-first execution rather than a passive "turn it on and hope" model.
Costs FRB does not remove
FRB is non-custodial by design, but non-custodial does not mean no risk. Users should still plan for:
- Gas spikes that make a route uneconomic.
- RPC rate limits or stale state during volatile windows.
- Slippage when pool state changes between simulation and execution.
- Competition from other searchers.
- Wrong strategy parameters.
- Wallet hygiene mistakes, including excessive approvals.
- Smart-contract or protocol risk.
The safest onboarding path is: review pricing, verify the build, read the risk disclosure, and start in simulation mode.
What to check before paying or going live
Use this checklist before funding a live wallet:
- Confirm the current pricing terms on /pricing.
- Verify the installer signature and checksum on /trust or /releases.
- Run the agent in simulation mode before signing live trades.
- Set wallet, strategy, and per-route limits.
- Model gas, tips, and slippage before the first live bundle.
- Log realized net outcome after every executed route.
- Stop or downshift when realized results diverge from simulation.
Internal links for deeper review
- FRB Pricing
- Risk Disclosure
- Trust Verification
- Wallet Hygiene for MEV Traders
- MEV Capital Requirements
- Profitability vs Risk: Gas and Budget Caps
CTA: Start with the Pricing page, then use Simulation Mode before live execution.
This article is informational only. Crypto and MEV strategies involve execution, liquidity, latency, smart-contract, and market risks. Review the Risk Disclosure before using live capital.
Step after reading
Launch FRB dashboard
Connect your wallet, pair the node client with a 6-character PIN, and assign the contract mentioned above.
Need the signed build?
Download & verify FRB
Grab the latest installer, compare SHA‑256 to Releases, then follow the Safe start checklist.
Check Releases & SHA‑256Related Articles
Further reading & tools
Discussion
No notes yet. Add the first observation, or share the link with your team on X (@MCFRB).